Hey I was wondering if someone could help me out with my situation.
I recently bought a used GS4 off someone and it was working fine. I went to get the device unlocked and the wifi stopped working. I found out the previous owner had rooted the device and changed some stuff. But because im not 100% sure what was modified, I'm not sure how to undo it.
Basically, my problem is that when I boot the phone, I get "KERNEL IS NOT SEANDROID ENFORCING SET WARRANTY BIT:KERNEL". Everything boots up fine and runs fine until I try and make a call. I'm able to open the phone app and dial. But once I push call, I get a blank screen. The phone i'm calling rings, but once it's answered, neither of us can hear each other. I'm also not able to use my camera. Once launched, I get "camera failed" and the app closes. Finally, My wifi stopped working. It just wont turn on at all. Everything else runs fine on the phone including text messages.
What I tried to do to fix the problem:
-Unroot the device
-Root the device and slap CM10.1 on there (This solved my camera and wifi problem. But not my calling problem. It also caused a new issue of not being able to play videos of any kind)
-Complete factory restore
I'm thinking the problem has something to do with the kernel because even after a full restore, I'm still getting the "KERNEL IS NOT SEANDROID ENFORCING SET WARRANTY BIT:KERNEL". But I can't seem to find a STOCK kernel for my device.
View attachment 2417158
View attachment 2417159
Related
hi all.
As I mentioned in my other post I have been having some serious wifi problems. Basically if I leave the wifi off the phone seems to work fine. When I turn it on however, the phone becomes laggy and it does not work. After turning the wifi on from the settings page, it says it is scanning for networks. After 20-30 seconds a little bubble pops up and says "unable to scan for networks" it will continue to try and scan on and off but never is successful. The phone is better to start up with the wifi off because if on, the phone becomes almost unresponsive and I am assuming it is because it is trying to scan in the background.
I just rebooted into the recovery menu and wiped the cache and device, but no luck. Any other ideas as to why this is happening?
Little update:
I found a few other threads where people complained about the same problem. Their recommended fix involved removing the file "/data/wifi/bcm_supp.conf"
The full thread is here: http://androidforums.com/samsung-moment/46179-unable-scan-networks.html
I tried that and also did a factory reset but unfortunately have not been able to fix the problem. Does anyone else have any other ideas?
hi Scales11
I'm also having the same problem..
did the
1. factory reset
2. new ROMs - Darky 7.01, Cognition 2.3...
3. delete the /data/wifi/bcm_supp.conf file
and still no luck... and realised bluetooth isn't working either..
anyone?? please help?
If you have flashed other ROMs and still the same issue. I would say its a hardware issue.
my fix
Geekboy9:
I meddled it for hours and while others have found various odd reset/rom fixes, I concluded that it was a hardware issue which cannot be fixed.
I flashed it back to a stock rom and went to att. They agreed that it didnt have any water damage and gave me a number to call about getting a replacement. Since the phone was less than a year old and its failure was not due to my use, the replaced it with a refurb. All in all the refurb seems fine, even after I rooted and flashed the cognition rom. I would recommend you do the same.
My phone has reboot a few times since ive purchased it, on active phone calls, twice today alone. I have a feeling its a software compatibility issue with one of my apps, but i just wanted to see if other people have experienced this, and any advice before i try a factory reset.
My phone is not rooted. It has the latest OTA update. When i first booted phone, it did a google backup
My other question was on the NFC. When i have NFC checked in the wireless area, it works great. But as soon as i turn it off, and try to turn it back on, it gives an error code. It wont turn back on until i reboot the phone, and than it checks just fine again until i turn it back off. I played with a phone at BB and it gave an occasional error when i cycled the check mark fast, but it always corrected the error eventually. This is probably another software bug, but just seeing if anybody else is experiencing this.
If i reset my phone, i will lose all my save game data correct?
My Nexus S is also resetting during phone calls, four times in a row now.
Is there any news on this issue?
http://forum.xda-developers.com/showthread.php?t=880497
I just reported rebooting issue to the Google. Please add your comments and star it, so Google will be aware of the problem and start fixing it!
http://code.google.com/p/android/issues/detail?id=13674
I exchanged the phone, and it was great for a week or so, but just tonight reboot twice during an active calls. I suspect it to be some sort of software bug, but, I'm most likely going to be exchanging it again. Works great until you need to use the phone as a phone, than it doesnt work.
Psosmith82 said:
My other question was on the NFC. When i have NFC checked in the wireless area, it works great. But as soon as i turn it off, and try to turn it back on, it gives an error code. It wont turn back on until i reboot the phone, and than it checks just fine again until i turn it back off. I played with a phone at BB and it gave an occasional error when i cycled the check mark fast, but it always corrected the error eventually. This is probably another software bug, but just seeing if anybody else is experiencing this.
Click to expand...
Click to collapse
I can recreate this problem as well, and was a major concern for me (didn't want to have a defective NFC down the line when/if it becomes common use). After speaking with some people over at Android Central, one of the editors had this to say:
"Yes, if I toggle the NFC switch enough times I will see the error notification. It still works as intended though. Looks like there is a "cool down" time on the NFC hardware, and messages to the kernel are getting picked up as errors. Either the filter needs tweaked (the filter that reports kernel messages) or the output from the NFC hardware needs "re-worded"
Makes sense to me. I wouldn't worry too much about it. However, I did create a report to bring to Google's attention, if you feel like starring it: http://code.google.com/p/android/issues/detail?id=13581
I got this phone a month ago and flashed various stock based ROMs with no trouble. I then tried AOSP (cm10.1, eclipse) and everything seemed to be ok although, I couldn't make phone calls because I have no service where my house is and was never able to test (I remember that in settings->about phone->system status it said it wasn't activated and it didn't display my phone number, but when I went back to stock it did display my number). Then I went back to a stock ROM and my phone would not make or receive calls. It would send and receive text and was able to received data via 4g but when trying to make a call, it would say "dialing" and then eventually just stop without making any type of connection. when calling the phone it would go straight to voice mail as if it was off. I used odin to go entirely stock and had the same problem. I ended up returning the phone and getting a new one and I am running Clean rom 5.5.1 and everything is working fine but I'd really like to try other roms but I don't want to have the same problem again. anyone know if it was just a bad phone or if I did something wrong? if so, what? any ideas would be greatly appreciated! Thanks!
You should have consulted xda before returning the phone. With your original phone, you needed to reprovision your sim to properly have your data return since you had Odin flashed. That code only works on ICS though.
The loss of data on your prior phone was from flashing CM10.1, you just needed to follow this post to resolve your issue without Odin flashing a stock rom.
Edit: The sim reprovision code suggestion is still valid BUT disregard the data loss part...
Hello! Here I am with my Q.
I got it last week, rooted w/o BL unlock, then a few days later I went to Moto to unlock the boot loader. all went well. (AHAHA, They worded the terms for the unlock as if EVERYTHING at ONCE will break. It seems to me that this has become reality.)
Then I had issues with GPS and Camera not working at all.
With each flash I got one or the other working, not usually both.
Now Both Camera and GPS are working wonderfully. Here's the kicker, I've found that calls are not working well.
I make calls, they go through but end shortly after they start with silence. when you attempt to end the call, it wont do it, or it will about 5 minutes after end has been pressed.
On receiving calls, often times it wont come through at all, if it does there's a chance that you wont get to pick it up. It will act like the caller has hung up. Missed call. Some times it will let it through, and a few seconds in and go to silence.
Here was my process.
1. Rooted with Motochopper. Played around in stock for a while then got fed up with it and all of it's bloat. Not to mention horrible batterylife.(Still has horrible battery life on CM, even when underclocked.)
2. Unlocked bootloader via Motorola.
2a flashed OpenRecovery, CM10.1 (Yes the CDMA version)and gapps.
3. Yay CM. Sadly, nothing works right. (Yes there were wipes.)
4. Was suggested to flash JB FXZ, did that.
5. Flashed TWRP and CM+Gapps. (No camera, but GPS worked.)
5a. Flashed 5/20 Build. Camera worked but no GPS.
5b. Flashed 5/26 build over 5/20 and both Cam and GPS work now.
The call issues were persistent throughout all of the builds I tried.
5/20 5/23 5/26
Sys info screenshot
lionspaws.net/android/ignoreme/Screenshot_2013-05-29-21-48-50.png
Please help me diagnose this.
I'm not looking for "It's you/your device/doin' it wrong/works for me" or "go back to stock"
I'm looking for help. I need a working device.
Here's some logs with a test call.
it failed about 2 sec in. Skype hung up due to dead line. Phone wont hang up.
Radio reset, data resync.
then I powered off the device after it 'hung up'(radio reset)(If I dont hit hang up, the call timer will continue count up)
lionspaws.net/android/ignoreme/logs.zip (zip,bzip2)
Halp!
Bump?
I've been having the same call issues, with every rom except stock.
Sounds like you tinkered alot.
I suggest you do a full reflash with rsd/ stock rom. Since u have unlocked bootloader I suggest you to install custom recovery like twrp or cwm. That will also root your device. After that retry flashing cm10.1 nightly and gapps exactly as described in their threads.
Everything else would be tinkering around broken builds. So start with fully clean device through rsd.
Also about the gps problem: it is suggested to get a gps lock on stock rom before installing aftermarket rom.
I'm having the same problem, I've RSD'd to stock and all that stuff too. I ALWAYS clean install. Yet I'm having this problem on most roms. I haven't tried any kernels yet, so maybe that would help things but I dunno. I'm gonna play around with that some time and figure it out.
xLoveHateLegend said:
I'm having the same problem, I've RSD'd to stock and all that stuff too. I ALWAYS clean install. Yet I'm having this problem on most roms. I haven't tried any kernels yet, so maybe that would help things but I dunno. I'm gonna play around with that some time and figure it out.
Click to expand...
Click to collapse
This is the first I have ever heard of this type of issue...
Logs please, with thorough detail on what happened. I can't recreate this, and 99% of others can't either (or just put up with a non-functional phone. Seems doubtful...)
Edit - as far as I know, the OP has fixed all of the issues they were having... maybe they can chime in with the process, but my kernel would have nothing to do with cell service.
Alright, here's a logcat... it's weird, I can only hear the first word they say and vice versa. Then the call gets quiet but stays connected. Then after clicking hang up, the call isn't really hung up. I have to go back to the dialer and click hang up again. Then, after a minute or so I'll hear the hang up tone and it'll finally hang up. I'm doing clean installs so I'm not sure what's going on here. Hopefully this will help resolve this issue, 'cus it's a huge problem for me :/
EDIT: Just flashed a stock rom and I'm not having this issue at all.
Sent from that one MoPho... Q
Anyone have a clue what's going on with my phone?
ok so ill explain everything step to step (what happened to phone) please someone help me
so i heard that if you disable bloatware apps (like amazon kindle amazon music etc.) phone could get faster and have more free ram. i did disable everything i could and yes phone got faster but week after i noticed that knock on stoped working...
i searched for it and heard that if i restart my phone it would work again. it didnt help. 2 weeks after second screen STOPED RESPONDING when main was off (second screen was on but did t respond it only showed time i couldn't go to quick settings) when main is on i can use second screen normally and it works as it should. then i noticed that knock off still worked and got confused (knock on isn't working but knock on is). i restarted one more time and heres wtf happened. my phone couldn't read sim card ( got locked to sprint again??? or is it software issue because they told me i my phone is unlocked when i talked to sprint agent) the bloatware apps were gone, HOW ARE THEY EVEN GONE THEY ARE PART OF THE SYSTEM YOU CANT DELETE THEM and fb and messenger were disabled even though i didnt disabled them before factory reset. it still has the second screen and knock on issue. phone otherwise phone still functions but i don't have knock code knock on and second screen when main is turned off and i cant call anyone . to be more specific second factory reset that caused all this **** was done with recovery mode. please help