I can not use my s5 censors. release him using ssu.apk on OD3 with 4.4.4 kernel NK4.then update to 5.0 OD3 whit kernel stock, in 4.4.4 that the camera did not work well, but I have no censors: accelerometer, gyroscope, gravity, linear, rotation, just proximity, light, pressure, magnetometer I have only those
Does it work on a stock rom? Make sure it is working on stock first, if it doesnt work there might be a hardware issue.
Right. Odin a stock tar and see if it works. If it does then it isn't a hardware issue. It's your rom. Use a different one. Chances are one that old isn't going to be worked on again...ever.
www.sammobile.com/firmwares is the most reliable place to get the tar.md5 files. If you need help with instructions on how to flash the tarballs in odin, let us know
Mine is doing the same! I guess it's hardware
bayron_olaff said:
Mine is doing the same! I guess it's hardware
Click to expand...
Click to collapse
Have you flashed the stock firmware via Odin? That fixes tons of stuff, hardware issues aside
Related
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
tfc87 said:
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
Click to expand...
Click to collapse
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Trozzul said:
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Click to expand...
Click to collapse
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
tfc87 said:
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
Click to expand...
Click to collapse
maby just wait till next firmware and they will fix it?
Trozzul said:
maby just wait till next firmware and they will fix it?
Click to expand...
Click to collapse
Yeah I'm sure it will be fixed. Either way, I don't recommend that newest firmware...signal seems to be the worst out of all of the ones I've tried...for me at least. Seems to be a lot of complaints out there with it anyways.
Similiar issue?
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Sterling8356 said:
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Click to expand...
Click to collapse
did you figure this out?
im having same problem
I had the same problem while flashing one of my friend's S3...i just did the whole process once again..and everything works fine
Sent from my Galaxy Note II using xda premium
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I have had the same problem when I installed a certain custom rom (can't remember the name ) on my s3. But later I found that during installation of the rom, there was an option to choose one of four kernels, and if I chose Boeffla kernel (included in the options) my camera wouldn't work. So I just reverted back to the stock kernel and walah! My camera works again.
20C Baseband with 10D Radio
SMS Send Bug Fix
!!d800 Only!!​
Edit (2015.05.12) - I have dumped and posted d80020y modem to my website. It seems that 20y might have fixed this issue. I have been using it for a day or so now and have not noticed this bug. You may wish to try that modem before this one.
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: ROMs that require the KK Modem (for rotation to work) cause SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
https://www.gregtwallace.com/lg-g2/d800-modems/
(It is the Modded One - Baseband: D80020C; Radio: D80010D)
Install:
1) Copy .zip and .md5 to the root of your sdcard.
2) Reboot into TWRP.
3) Install -> Select .zip File.
4) Check "Zip file signature verification." (File is properly signed.)
5) Swipe to install the zip. (MD5 and Signature should verify and modem should install.)
6) Wipe cache/dalvik (for good measure.)
7) Reboot System and Enjoy!
Note: In "System Settings" under "About Phone" -> "Software Information" the Baseband version will be listed as ending in ".190034". This is the 10D baseband.
10D & 10O Baseband Rev: M8974A-AAAANAZM-1.0.190034
Default KK Baseband (20c) Rev: M8974A-AAAANAZM-1.0.190082
This Patched KK Baseband Rev: M8974A-AAAANAZM-1.0.190034
Please respond with any issues, etc.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
Reserved
So basically this is an all in one modem for stock KitKat ROMs (ex. CloudyG3,etc) and works on AOSP roms with working rotation,etc?
c_brown93 said:
So basically this is an all in one modem for stock KitKat ROMs (ex. CloudyG3,etc) and works on AOSP roms with working rotation,etc?
Click to expand...
Click to collapse
No, this will not work for ROMs based on the old source (e.g. CM11).
This only works for KK based ROMs. It allows KK based ROMs to be fully functional, while still using the old baseband (radio).
This looks promising, I'll provide feedback once I return from work tonight!
Besides fixing the stuck SMS sending bug, any other advantages to this modem? Battery life or signal strengths?
I'm running Lam Hoang G3 ROM on D800 but it should still be fine
Thanks for this man, I always had a better signal with the original radio and now I can use it with kk roms. You're the man.
bps119 said:
Thanks for this man, I always had a better signal with the original radio and now I can use it with kk roms. You're the man.
Click to expand...
Click to collapse
You're welcome.
XERO_Racer said:
Besides fixing the stuck SMS sending bug, any other advantages to this modem? Battery life or signal strengths?
Click to expand...
Click to collapse
This isn't anything fancy. It is exactly what it professes to be. All of the KK modem files, except the 10D radio files were swapped in. So if you had any other 'better' things on 10D vs. the KK modem, you might get them in this, but probably not.
Used this modem all day today. No issues. Didn't have the SMS issue at all.
blastagator said:
Used this modem all day today. No issues. Didn't have the SMS issue at all.
Click to expand...
Click to collapse
You think this will help with reboots caused by low LTE signal?
RenderBroken said:
You think this will help with reboots caused by low LTE signal?
Click to expand...
Click to collapse
I've never had that problem, so I have no idea.
blastagator said:
I've never had that problem, so I have no idea.
Click to expand...
Click to collapse
Thank you kindly for the reply. Now one last question. I am fairly new to the G2 still so I was not around during the new KK source days dealing with the KK modem and AOSP. This sounds like it should work for AOSP roms. Am I correct in that assumption? Thanks again!
The sending delay bug was very annoying, I just flashed it and will report back if there are any issues!
RenderBroken said:
Thank you kindly for the reply. Now one last question. I am fairly new to the G2 still so I was not around during the new KK source days dealing with the KK modem and AOSP. This sounds like it should work for AOSP roms. Am I correct in that assumption? Thanks again!
Click to expand...
Click to collapse
To be honest, I'm not 100% sure. It's easy enough to figure out though. Usually the ROM post says which to use. If not, you can just flash one of the modems, if your sensors work, you're using a modern that is compatible with your ROM. Easiest sensor to check is rotation. Open Maps and your gps blip will have an arrow showing your rotation orientation (compatible) or there won't be an arrow (wrong modem).
OMG Thank you SO much!
blastagator said:
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: Stock KK Modem (on KK based ROM) causes SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
Modem: https://drive.google.com/file/d/0B_5fX5B47GiwNTA4S1c3MG00M0k/edit?usp=sharing
MD5: https://drive.google.com/file/d/0B_5fX5B47GiwSXBGdnhxbnBadzA/edit?usp=sharing
(For people unfamiliar with Google Drive, click the download button at the top to download the flashable zip.)
Please respond with any issues, etc.
Click to expand...
Click to collapse
I have been waiting for a solution for this problem for so long. Downloading now. If this works I would be more than happy to donate. I love the CloudyG3 roms, but the issue with SMS getting stuck in "sending" has been a complete headache for me.
blastagator said:
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: Stock KK Modem (on KK based ROM) causes SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
Modem: https://drive.google.com/file/d/0B_5fX5B47GiwNTA4S1c3MG00M0k/edit?usp=sharing
MD5: https://drive.google.com/file/d/0B_5fX5B47GiwSXBGdnhxbnBadzA/edit?usp=sharing
(For people unfamiliar with Google Drive, click the download button at the top to download the flashable zip.)
Please respond with any issues, etc.
Click to expand...
Click to collapse
is this a bug in the stock vanilla rom(like what came with the lgg2) that or just custom kk roms like ( optimus3g)? ive had this issue for a long time and i decided to leave stock and go with optimus 3g but my sms always get stuck, i reverted back to stock kk rom but have dori kernel installed. im jus tnot sure if i first noticed this while having a custom rom or if it was an issue on my stock kk rom. also can it be used with dori kernel?
I flashed this radio on the official CM 11 ROM. Rotation/compass doesn't work for anybody who wants to know. Everything else seems OK.
joeynox said:
is this a bug in the stock vanilla rom(like what came with the lgg2) that or just custom kk roms like ( optimus3g)? ive had this issue for a long time and i decided to leave stock and go with optimus 3g but my sms always get stuck, i reverted back to stock kk rom but have dori kernel installed. im jus tnot sure if i first noticed this while having a custom rom or if it was an issue on my stock kk rom. also can it be used with dori?
Click to expand...
Click to collapse
I believe the bug is a part of the KK radio and ROM independent. In my Q&A someone reported having the problem on the stock KK, completely untouched.
phatmanxxl said:
I flashed this radio on the official CM 11 ROM. Rotation/compass doesn't work for anybody who wants to know. Everything else seems OK.
Click to expand...
Click to collapse
This modem is not intended for CM11. CM11 is not stock KK based.
blastagator said:
I believe the bug is a part of the KK radio and ROM independent..
Click to expand...
Click to collapse
thanky you for responding. will i have any issue if i use this with dori kernel?
blastagator said:
I believe the bug is a part of the KK radio and ROM independent. In my Q&A someone reported having the problem on the stock KK, completely untouched.
This modem is not intended for CM11. CM11 is not KK based.
Click to expand...
Click to collapse
I like flashin' stuff....things
I just thought I'd give it a try and see what happens.
joeynox said:
thanky you for responding. will i have any issue if i use this with dori kernel?
Click to expand...
Click to collapse
Kernel and Modem should be independent and thus not cause a problem, but I don't know for sure since I haven't done it.
phatmanxxl said:
I like flashin' stuff....things
I just thought I'd give it a try and see what happens.
Click to expand...
Click to collapse
Oh, okay
I updated to the new firmware (4.4.4) this weekend. Everything is working great, except the g-sensor seems to be a bit wonky... Often, the screen does not auto-rotate. Also, I use Screeble Pro app to keep the screen on when not laying flat and it consistently thinks the phone is laying flat when it is not (did that make sense?). I've tried the basic calibrate function in the settings, but that did not help. Also, flashed the new firmware with both the RUU. and SD card methods... Even went back to 4.4.3 firmware with no change... Anyone else having this issue? Any ideas? Thanks for the help.
Sent from my HTC6525LVW using Tapatalk
OK, update... The sensor info to Screebl seems to be working, but the auto rotate (can't even force it to landscape) stopped working at all.
Sent from my HTC6525LVW using Tapatalk
Did you flash the firmware via ADB? Did you flash it 2x??
I had an issue with my IR blaster after I updated to 4.4.4. Could have been caused by my not flashing the firmware twice, or because of non-matching firmware/rom.
Freedom First said:
Did you flash the firmware via ADB? Did you flash it 2x??
I had an issue with my IR blaster after I updated to 4.4.4. Could have been caused by my not flashing the firmware twice, or because of non-matching firmware/rom.
Click to expand...
Click to collapse
Flashed it twice... via fastboot RUU method (as well as with the SD card method) I am currently running a 4.4.3 based ROM (ViperOne 2.5). Am hoping that when that ROM gets updated to the 4.4.4 version and I do a clean install maybe the problem will go away...
I'm currently on the latest Cyanogen build "12.1-YOG4PAS3JL" and I noticed the proximity sensor isn't working. I've heard that flashing a modem can solve this issue, but I'm not sure what modem I should flash and where I can find the right one?
I am using the 05/15 firmware. Everything here works fine.
How did upgrade?
With custom recovery? Which?
Go to settings and check baseband
Must have DI. 3..0.c6-00241-Mxxxxxxx
Have c7 on mine.
Sent from my A0001 using Tapatalk
Quick Solution, works for both kitkat and lollipop android versions, I've tried myself and it was the only solution I found.
1 - Flash this: https://www.androidfilehost.com/?fid=95784891001607675 (44S Modem)
2 - Flash this: https://www.dropbox.com/s/bdnirlhnrj60ojs/Android-5.0.2-CM11S-OldSensorPatch.zip?dl=0 (Proximity sensor patch)
arthas_sp said:
Quick Solution, works for both kitkat and lollipop android versions, I've tried myself and it was the only solution I found.
1 - Flash this: https://www.androidfilehost.com/?fid=95784891001607675 (44S Modem)
2 - Flash this: https://www.dropbox.com/s/bdnirlhnrj60ojs/Android-5.0.2-CM11S-OldSensorPatch.zip?dl=0 (Proximity sensor patch)
Click to expand...
Click to collapse
Sadly I had tons of problems with that modem.
I am beginning to hate and loathe this piece of junk phone.
EDIT:
I flashed the 05-15 modem (v241) and it seems signal is better AND the proximity sensor works.
I'm not sure why everyone still insists on that old KitKat modem.
Hi buddies,
I know maybe It is a wrong place to ask this, but I've got a strange problem regarding to speaker.
My speaker in my S6 gets some ticks and lags during the play. I mean constantly the music stops and plays over and over.
I have the issue frequently and at the moment when I check the hardware with *#0*# there is no problem with the speaker.
I have the problem in games softwares and music players, and just recently got it.
I've tested different ROMs and kernels, both stock and unofficial, in both Lollipop and marshmallow, but the problem is still keeping up.
Attachment I've uploaded you an instance to better understand the problem.
I really appreciate if you just give me a hand with this.
Thanks.
https://drive.google.com/file/d/0B684uiQkcfJZbVJGWXYzeXVxQkk/view?usp=docslist_api
What model S6 do you have?
Might have installed the wrong model, can you please try to flash an original stock rom and see if that works then go from there to see where you went wrong
Valkiry said:
What model S6 do you have?
Might have installed the wrong model, can you please try to flash an original stock rom and see if that works then go from there to see where you went wrong
Click to expand...
Click to collapse
I've got the international version (G920f).
I've flashed stock ROM bunch of times from different bases, and now I am on stock marshmallow ROM with stock kernel. Still have the issue.
If you've tried different stock roms I'd say your speaker is faulty? If you haven't triped Knox send it back?
Valkiry said:
If you've tried different stock roms I'd say your speaker is faulty? If you haven't triped Knox send it back?
Click to expand...
Click to collapse
But I test during the issue, the speaker is allright, (using *#0*#)
And also I don't enable the Knox at all.
When I use that code I goto imie viewer. Knox is always active on stock rom regardless, it sounds hardware related not software, since you've tried other roms and it's still the same issue it doesn't make sense that you broke your device speaker.
Valkiry said:
When I use that code I goto imie viewer. Knox is always active on stock rom regardless, it sounds hardware related not software, since you've tried other roms and it's still the same issue it doesn't make sense that you broke your device speaker.
Click to expand...
Click to collapse
Oh, I really sorry that was a blunder
I meant *#0*# ...
So How can I really make sure that It's a hardware issue?
Does flashing ROM with box helps?
Well if you keep flashing different roms and nothing is working to fix the problem, which is including kernel issues on stock and custom I'd say it's hardware related.