Related
Hi,
I have a 1+ yr old Galaxy S3 (so out of the warranty period). I'm getting camera fail messages. When it's not working, here's what happens:
When I try to use the stock camera app, it goes into the camera interface, hangs for a bit, and then I get a message saying "Camera Failed"
If I try to use another app that uses the camera, I get a message that the camera is in use.
So it seems to me like there is some app that is hijacking my camera, rendering it unavailable. I got in touch with Samsung tech support, and they had me reboot into safe mode, test the camera, and then reboot normally. That works to reset the camera, and I can then access it, until it happens again.
Does anyone know what the problem might be, or which app might be interfering? Is there a way to get a list of all apps that use the camera, so I could do some trouble shooting?
Thanks in advance for any help you can give.
Could you post your about phone details? Are you sure you have a Verizon Galaxy SIII (sch-i535)? Because we do not have a stock, non-rooted 4.2.2 rom.
Oops, 4.1.2, not 4.2.2
SlimSnoopOS said:
Could you post your about phone details? Are you sure you have a Verizon Galaxy SIII (sch-i535)? Because we do not have a stock, non-rooted 4.2.2 rom.
Click to expand...
Click to collapse
Yes, and I made a mistake in the title, it's 4.1.2, not 4.2.2.
Model SCH-I535
Android 4.1.2
Baseband version 535VRBMF1
Kernel Version 3.0.31-1152558 [email protected] #1 SMP PREEMPT Sat Jun 8 17:20:08 KST 2013
Build Number JZO54K.I535VRBMF1
Hardware Version I535.10
seattlecubsfan said:
Yes, and I made a mistake in the title, it's 4.1.2, not 4.2.2.
Model SCH-I535
Android 4.1.2
Baseband version 535VRBMF1
Kernel Version 3.0.31-1152558 [email protected] #1 SMP PREEMPT Sat Jun 8 17:20:08 KST 2013
Build Number JZO54K.I535VRBMF1
Hardware Version I535.10
Click to expand...
Click to collapse
Ahh, ok haha kinda got my hopes up for a second lol hmm, as a stock user, your options are kinda limited. What I can suggest is that you use Odin (a Windows program) to flash VRBMB1 firmware and see if this will resolve your camera issues. This is the quick and simple method. Essentially doing this will downgrade your modem to VRBMB1 and several files to VRBMB1 4.1.2. Doing this is compatible with all ota's even older ones. You can download the tar file here and Odin from here. You can follow step one in that guide but all you're flashing is the VRBMB1 firmware that I linked. Alternatively, the more complete suggestion is to Odin flash a full 1 GB stock tar which will erase all of your data on the phone and it will be reset to out of the box stock. If your camera does not work still then it would very likely be a hardware issue.
Does anyone know what the problem might be, or which app might be interfering? Is there a way to get a list of all apps that use the camera, so I could do some trouble shooting?
Click to expand...
Click to collapse
I'm not too sure about this question btw. Maybe someone else can provide input on an app or utility that does this? For now, the best I could suggest is uninstalling any apps you know access the camera then trying to add them one by one until you can see the issue.
I am new with this Asus Transformer TF300T device and i have still lot to learn, but what i have learned is Asus make ****ty bootloaders.
The situation with my device is now with newest nighty CM 11 and Scanno TWRP with Grimlock Kernel. I tested it couple of hours and it crashed one time. I would need the device 95% to play games and rest of time surfing internet. Thats mostly what i do with device and im wondering is the CM 11 best to it or is there something better. This is first custom Rom im testing and there is a little performance upgrade since Stock Rom but not much so im thinking the problem could be the nightly build so i would like to go back to some stable roms. Battery time is not priority 1 because i can charge the tablet daily and i have keyboard to it.
But the question is what is the best and fastest rom and what is easiest way to do it? Should i allways install the latest official Asus update to device that bootloader etc. will be stock and then install TWRP or is there other way? I think Android KitKat still need lot of fixing so i could go back to Android 4.3X or Android 4.2X which have been around very much longer and maybe better fixed. The little advices how to do that would be great same as what not to do.
Matatusku said:
I am new with this Asus Transformer TF300T device and i have still lot to learn, but what i have learned is Asus make ****ty bootloaders.
The situation with my device is now with newest nighty CM 11 and Scanno TWRP with Grimlock Kernel. I tested it couple of hours and it crashed one time. I would need the device 95% to play games and rest of time surfing internet. Thats mostly what i do with device and im wondering is the CM 11 best to it or is there something better. This is first custom Rom im testing and there is a little performance upgrade since Stock Rom but not much so im thinking the problem could be the nightly build so i would like to go back to some stable roms. Battery time is not priority 1 because i can charge the tablet daily and i have keyboard to it.
But the question is what is the best and fastest rom and what is easiest way to do it? Should i allways install the latest official Asus update to device that bootloader etc. will be stock and then install TWRP or is there other way? I think Android KitKat still need lot of fixing so i could go back to Android 4.3X or Android 4.2X which have been around very much longer and maybe better fixed. The little advices how to do that would be great same as what not to do.
Click to expand...
Click to collapse
If you really want speed, stability, and reliability, CROMi-x is a really good option in my opinion. I always have had a preference to AOSP ROMs, because of that I use CM or PAC or Omni or AOKP. 4.2.2 based on the stock ROM seems to fit all of your needs, nightlies tend to be more cutting edge, and with that comes unpredictability.
cmendonc2 said:
If you really want speed, stability, and reliability, CROMi-x is a really good option in my opinion. I always have had a preference to AOSP ROMs, because of that I use CM or PAC or Omni or AOKP. 4.2.2 based on the stock ROM seems to fit all of your needs, nightlies tend to be more cutting edge, and with that comes unpredictability.
Click to expand...
Click to collapse
That CROMi-x seems to be good rom but im not completely sure will it work with newest stock rom which is 10.6.1.27.5 not 10.6.1.27.1 and how i get back to stock because now i have something other? And is my TWRP wrong? There is many of questions that i cant find answer from forums which is very strange. Usually there are guides for these things.
I would like to do this: http://forum.xda-developers.com/showthread.php?t=2455922 to my tablet just in case but i dont know is my version right for that.
This is Exactly information from my tablet:
Model: TF300T
Android: 4.4.2
Kernel: 3.1.10 Grimlock CM_0.8
Cyanogenmod Version 11-20140120-Nightly-Tf300t
Build Number: CM_TF300T-userdebug 4.4.2 KOT49H
SELinux: Enforcing
So first things i need is how do i get back to newest stock rom 4.2.1 with 10.6.1.27.5 and will i need to install TWRP in that installing progress or how? Some help would be nice. If im correct the easiest way would be go back to Stock 10.6.1.27.1 and make the device unbreakable then flash TWRP and go to CROMI-X but i need to know how to do that. The biggest question is that TWRP.
Matatusku said:
That CROMi-x seems to be good rom but im not completely sure will it work with newest stock rom which is 10.6.1.27.5 not 10.6.1.27.1 and how i get back to stock because now i have something other? And is my TWRP wrong? There is many of questions that i cant find answer from forums which is very strange. Usually there are guides for these things.
I would like to do this: http://forum.xda-developers.com/showthread.php?t=2455922 to my tablet just in case but i dont know is my version right for that.
This is Exactly information from my tablet:
Model: TF300T
Android: 4.4.2
Kernel: 3.1.10 Grimlock CM_0.8
Cyanogenmod Version 11-20140120-Nightly-Tf300t
Build Number: CM_TF300T-userdebug 4.4.2 KOT49H
SELinux: Enforcing
So first things i need is how do i get back to newest stock rom 4.2.1 with 10.6.1.27.5 and will i need to install TWRP in that installing progress or how? Some help would be nice. If im correct the easiest way would be go back to Stock 10.6.1.27.1 and make the device unbreakable then flash TWRP and go to CROMI-X but i need to know how to do that. The biggest question is that TWRP.
Click to expand...
Click to collapse
Yes, you can do NvFlash Backups for your bootloader, I have them on mine. If you want some clarification, you can look here: [URL="http://goo.gl/aM2M3y"]http://goo.gl/aM2M3y
[/URL]
You can do NvFlash from the CM11 ROM you are on right now. Once you do that, you can reflash TWRP 2.6.3.1 and then factory reset from the recovery and then install CROMi-x.
Matatusku said:
That CROMi-x seems to be good rom but im not completely sure will it work with newest stock rom which is 10.6.1.27.5 not 10.6.1.27.1 and how i get back to stock because now i have something other? And is my TWRP wrong? There is many of questions that i cant find answer from forums which is very strange. Usually there are guides for these things.
I would like to do this: http://forum.xda-developers.com/showthread.php?t=2455922 to my tablet just in case but i dont know is my version right for that.
This is Exactly information from my tablet:
Model: TF300T
Android: 4.4.2
Kernel: 3.1.10 Grimlock CM_0.8
Cyanogenmod Version 11-20140120-Nightly-Tf300t
Build Number: CM_TF300T-userdebug 4.4.2 KOT49H
SELinux: Enforcing
So first things i need is how do i get back to newest stock rom 4.2.1 with 10.6.1.27.5 and will i need to install TWRP in that installing progress or how? Some help would be nice. If im correct the easiest way would be go back to Stock 10.6.1.27.1 and make the device unbreakable then flash TWRP and go to CROMI-X but i need to know how to do that. The biggest question is that TWRP.
Click to expand...
Click to collapse
CROMi-X works fine and is based from 10.6.1.27.5
Hi!
I cant post to android developement so i have to ask here. Does the CM11 OTA work if i have Grimlock kernel instead of the CM kernel and does it works if some of gapps etc have been deleted?
I would like to have some help how to do this: "You can do NvFlash from the CM11 ROM you are on right now. Once you do that, you can reflash TWRP 2.6.3.1 and then factory reset from the recovery and then install CROMi-x. "
http://forum.xda-developers.com/showthread.php?p=47902196#post47902196
What if i dont have "That is for stock Android Versions: 10.6.1.15.3 - 10.6.1.27.1." i have 10.6.1.27.5 or at least i had before i upgraded to CM or did the bootloader stays the same when upgrading to CM? Just does not show on the screen?
Sorry that my answering took so long here but i had other issues to do first Now i have time to play with this tablet. But the Cromi-X is what im going to have in my device but i need some help with it.
Matatusku said:
Hi!
I cant post to android developement so i have to ask here. Does the CM11 OTA work if i have Grimlock kernel instead of the CM kernel and does it works if some of gapps etc have been deleted?
I would like to have some help how to do this: "You can do NvFlash from the CM11 ROM you are on right now. Once you do that, you can reflash TWRP 2.6.3.1 and then factory reset from the recovery and then install CROMi-x. "
http://forum.xda-developers.com/showthread.php?p=47902196#post47902196
What if i dont have "That is for stock Android Versions: 10.6.1.15.3 - 10.6.1.27.1." i have 10.6.1.27.5 or at least i had before i upgraded to CM or did the bootloader stays the same when upgrading to CM? Just does not show on the screen?
Sorry that my answering took so long here but i had other issues to do first Now i have time to play with this tablet. But the Cromi-X is what im going to have in my device but i need some help with it.
Click to expand...
Click to collapse
Yep you should be fine. The bootloader is the same for all three Stock ROMs.
INFO:
Model: SGH-M919
Kernel: 3.4.0-cyanogenmod-g93df44d [email protected] #1 Fri Jan 31 22:47:46 2014
ROM: CM 10.2.1-jfltetmo
Build #: cm_jfltetmo-userdebug 4.3.1 JLS36I 5ce70171d1 test-keys
Recovery: ClockworkMod 6.0.4.7
Basically, ever since I flashed AOKP a while back, my phone has been acting weird. Every once in a while the phone will freeze and black lines will appear, immediately followed by the phone re-booting. It happens completely at random. Afterwards, I flashed various ROM's and Android versions thinking that maybe the ROM was the issue, to no prevail.
Also, apps such as GoSMS, Instagram, PowerAmp, and my Camera, to name a few, bug out and either crash or freeze the phone and again it re-boots. The phone doesn't produce sound (from internal speakers or headphones, when plugged in). The Camera app will not record videos, or lag when record button is pressed, overall most of applications bug out and dont work the way they're suppose to.
My main concern is the random re-booting and what might be causing it, and what can do to fix it?
Thank You for the Help!
SlinerX said:
INFO:
Model: SGH-M919
Kernel: 3.4.0-cyanogenmod-g93df44d [email protected] #1 Fri Jan 31 22:47:46 2014
ROM: CM 10.2.1-jfltetmo
Build #: cm_jfltetmo-userdebug 4.3.1 JLS36I 5ce70171d1 test-keys
Recovery: ClockworkMod 6.0.4.7
Basically, ever since I flashed AOKP a while back, my phone has been acting weird. Every once in a while the phone will freeze and black lines will appear, immediately followed by the phone re-booting. It happens completely at random. Afterwards, I flashed various ROM's and Android versions thinking that maybe the ROM was the issue, to no prevail.
Also, apps such as GoSMS, Instagram, PowerAmp, and my Camera, to name a few, bug out and either crash or freeze the phone and again it re-boots. The phone doesn't produce sound (from internal speakers or headphones, when plugged in). The Camera app will not record videos, or lag when record button is pressed, overall most of applications bug out and dont work the way they're suppose to.
My main concern is the random re-booting and what might be causing it, and what can do to fix it?
Thank You for the Help!
Click to expand...
Click to collapse
Flash stock firmware via Odin to fix rom affected issiues.
LS.xD said:
Flash stock firmware via Odin to fix rom affected issiues.
Click to expand...
Click to collapse
I flashed the latest stock firmware, 4.4.2, via odin 3.09. The problems still stand, everything seems fine at first and then things start crashing and phone reboots. Any other thoughts on what might be causing it?
Don't worry about the rebooting my main concern are those black lines appearing I would flash to stock and claim warranty
Sent from my Nexus 5 using Tapatalk
markdapimp said:
Don't worry about the rebooting my main concern are those black lines appearing I would flash to stock and claim warranty
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I've already triggered the Knox Warranty Void
Heya guys, my brother's Nexus 5, bought alongside mine almost 1 year ago now, has suddenly started rebooting, seemingly at random. I would like some help diagnosing and hopefully solving the issue.
Here is a timeline of the steps I have done so far:
Uninstalled Facebook Messenger app, as ppl online mentioned it was a causing reboots after an update. Reboots continued.
Then tried to clear cache on recovery mode, only to get the msg that "E:/Cache could not be mounted. From that moment on the phone started behaving erratically, showing wrong date/time, not connecting to data signal or wifi, among other issues.
I proceeded to unlock bootloader and flash the latest 4.4.4 img, phone booted ok and started going through the backup restore process. After about 8 or 9 apps installed, phone rebooted on its own again
Asked my brother to run the phone in safe mode for a while and try to observe whether it reboots or not while running only Google apps. We are currently at this step, as I want him to run the phone for at least 12 hours in safe mode
What else would you do? Any apps you would install? I was thinking of rooting the phone and having it run a custom kernel to see if it magically solves the issue. Sometimes when the phone reboots it becomes stuck on a loop, not getting past the Google screen but eventually it boots.
I would like to stress that sending it back to Google or to the store is out of the question since we moved to South America and there's no way to send the phone to the US, where it was bought. In light of this, I want to try everything I can before giving up on the phone.
how much storage do you have left, total?
simms22 said:
how much storage do you have left, total?
Click to expand...
Click to collapse
Will get back to you with the exact info in a few hours but since I did a factory reset when unlocking the bootloader I would expect the phone to have most of the storage available.
Will update with the % left once I get a hold of the phone again.
simms22 said:
how much storage do you have left, total?
Click to expand...
Click to collapse
11.3gb free out of 12.59 available. Phone reboots even while in safe mode.
simonarturo said:
11.3gb free out of 12.59 available. Phone reboots even while in safe mode.
Click to expand...
Click to collapse
ok, i was actually more curious if the phone actually saw the storage or not. its fairly common for the nexus 5 storage to get corrupted. and one of the symptoms is rebooting. but, good thing that its not your issue. it can very much be an app that causing reboots.. to test, id wipe(factoiry reset) then not install any apps for a day. id no reboots, then id install 1 app at a time to check which app it is.
simms22 said:
ok, i was actually more curious if the phone actually saw the storage or not. its fairly common for the nexus 5 storage to get corrupted. and one of the symptoms is rebooting. but, good thing that its not your issue. it can very much be an app that causing reboots.. to test, id wipe(factoiry reset) then not install any apps for a day. id no reboots, then id install 1 app at a time to check which app it is.
Click to expand...
Click to collapse
Thanks for the response, I will certainly try that.
In the case of memory corruption, is there anything to be done?
simms22 said:
ok, i was actually more curious if the phone actually saw the storage or not. its fairly common for the nexus 5 storage to get corrupted. and one of the symptoms is rebooting. but, good thing that its not your issue. it can very much be an app that causing reboots.. to test, id wipe(factoiry reset) then not install any apps for a day. id no reboots, then id install 1 app at a time to check which app it is.
Click to expand...
Click to collapse
OK, phone became stuck on boot loop now. It will try to start and go back to Google logo. I think it all points to memory corruption as you said.
Can it be fixed? We don't mind data loss as long as we get the phone back to normal. Thanks in advance
Okay, when you unlock the bootloader and reboot back into fastboot, does the bootloader lock itself? If it does, then that is most likely hardware corruption on the emmc chip. If it stays unlocked, you can try heading into your recovery, getting adb shell privileges, and running e2fsck -fyc on your /system, /cache, and /data partitions (after making sure each one is unmounted). Not sure if this will work, but it's worth a shot. Best of luck.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
It's the power button. ? It's sticking.
lolcakes203 said:
Okay, when you unlock the bootloader and reboot back into fastboot, does the bootloader lock itself? If it does, then that is most likely hardware corruption on the emmc chip. If it stays unlocked, you can try heading into your recovery, getting adb shell privileges, and running e2fsck -fyc on your /system, /cache, and /data partitions (after making sure each one is unmounted). Not sure if this will work, but it's worth a shot. Best of luck.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
Click to expand...
Click to collapse
Bootloader remains unlocked but the phone keeps rebooting, cannot get it to start
KJ said:
It's the power button. ? It's sticking.
Click to expand...
Click to collapse
Ding ding ding, we have a winner. Tried your theory by just pressing the volume down button when it restarts and it takes me to the recovery menu (and keeps restarting) so the power button is indeed pressed on its own.
Do you have any suggestions for fixing it? Any tutorial you'd recommend?
It would be nice if we could just send the phone back and get a new one but it's not an option so we have to tackle the issue head on
simonarturo said:
Bootloader remains unlocked but the phone keeps rebooting, cannot get it to start
Ding ding ding, we have a winner. Tried your theory by just pressing the volume down button when it restarts and it takes me to the recovery menu (and keeps restarting) so the power button is indeed pressed on its own.
Do you have any suggestions for fixing it? Any tutorial you'd recommend?
It would be nice if we could just send the phone back and get a new one but it's not an option so we have to tackle the issue head on
Click to expand...
Click to collapse
Get it replaced at a local cell phone repair shop. It's a cheap fix
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
simonarturo said:
Bootloader remains unlocked but the phone keeps rebooting, cannot get it to start
Ding ding ding, we have a winner. Tried your theory by just pressing the volume down button when it restarts and it takes me to the recovery menu (and keeps restarting) so the power button is indeed pressed on its own.
Do you have any suggestions for fixing it? Any tutorial you'd recommend?
It would be nice if we could just send the phone back and get a new one but it's not an option so we have to tackle the issue head on
Click to expand...
Click to collapse
Sometimes gotta start with the simple things. ?
As soon as I hear reboots... I think power button. Guess cause I had 2 Samsungs and it happened to both. Lol
Glad you figured it out. ?
Personally, I'd take the sound advice above. But if your brave, just google it... I'm sure you'll find a walk through or video.
Good luck!
Haha looks like I assumed a more complex situation first. Glad that you solved the issue
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
lolcakes203 said:
Haha looks like I assumed a more complex situation first. Glad that you solved the issue
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
Click to expand...
Click to collapse
jd1639 said:
Get it replaced at a local cell phone repair shop. It's a cheap fix
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Ok guys, quick question. I have to buy the repair parts online since no one in my country stocks them, and I found that there are two parts to the power button: the actual button and a piece that goes underneath with a small switch that the power button squeezes when pressed. Which one should I buy? No repairman will open my phone until I provide the parts and I only have a week or so until the family members that are in the US will travel back to my country.
Any help would be appreciated, thanks
I think you should purchase both just to be on the safe side.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
Might anyone know the name of the part which is circled in the attached picture? Or it's part number?
According to my research, the power button itself is not the problem, but what's underneath it, which is a piece that comes soldered to the mobo, though I have seen it being sold separately from Hong Kong sellers (which I'm trying to avoid due to delays and price increase with shipping). I want to procure one of these parts but so far I haven't found anything. Sometimes they would call the piece "power button", the same as the actual button, but it is a different piece altogether.
lolcakes203 said:
I think you should purchase both just to be on the safe side.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
Click to expand...
Click to collapse
Damn bro ur signature is hella long
Sent from my Nexus 5
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Agrajag27 said:
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Click to expand...
Click to collapse
your bootloader detects that, so there is no way to get rid of it.
my note 4 does this but I have actually never seen it on my P900, could you give more details on your exact model, rom, and kernel? I'm curious.
one way around that, I think, would be a kernel that is enforcing at boot, then use a script or an app to toggle it back to permissive (if necessary for your purposes)
edit: oops I see now -- CM 12, but still.. are you using the lollipop bootloader from the official update?
Hmmm.... I just rooted my Note Pro last night, stock rom with TWRP (latest). And though it boots up fine otherwise, I'm also getting the "Not SEAndroid enforcing" message. Would like that gone. And it is interesting that CM12 is having the same issue, because I was beginning to think about flashing it and ditching stock Lollipop.
Specifics: I used Odin 3.10 from a Windows 7 laptop for my initial boot flash of the CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 file to the tablet. No errors were reported. I also flashed TWRP 2.8.7 that way. Again, no errors. There was a beta version of SuperSU (2.49) but I didn't install that. Think I'll try it next... and hope for the best. I did install SuperSU Pro (2.46) once I'd booted the tablet, but maybe that's not available on boot?
Sterist said:
could you give more details on your exact model, rom, and kernel? I'm curious.
Click to expand...
Click to collapse
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Agrajag27 said:
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Click to expand...
Click to collapse
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Sterist said:
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Click to expand...
Click to collapse
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Agrajag27 said:
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Click to expand...
Click to collapse
I don't think there would be a way to go back to kitkat, even if you wanted to, after having installed the lollipop bootloader (happens when you OTA or Odin to stock lollipop)
to the user it's no problem at all -- it's just a visual notification to stores when you take the device back that it's been customized / modded, and voids the knox warrantee hence "Set warrantee bit: kernel"
knox, despite popular belief, is just a form of security and productive software for corporations to rely on when giving their employees a "work phone" to use, so they know that any potentially sensitive corporate information is safe from the security risks of rooting (though virtually never exploited, rest assured)
that's the most relevant answer I can give you, without repeating what I explained in my previous post *hint* lol
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Agrajag27 said:
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Click to expand...
Click to collapse
the display at boot is not an error, just a notification of sorts.
the only thing I can think of is the CM maintainer may have compiled the kernel to boot as permissive and switch back via script for compatibility.
I have seen some roms that do this. not many, nor recently. I wouldn't worry about it though, especially since it's a Wi-Fi device that doesn't have any reason to visit a carrier store.
also note that the notification will show when booting a permissive recovery kernel -- these notifications are not permanent nor need to be "cleared" or "reset" they just inform the user (or technician) of the S.E.A. mode of the respective kernel at the time of boot.
Thanks. I can live with that. I'm a bit OCD and an old QA professional so it'll give me pause every time I reboot and see it, but I'll get over it. <grin>
Otherwise, I have to say, the tablet is working better than EVER with CM 12.x. Apps that caused crashes no longer do. Bluetooth keyboard works again. It's faster. I have only a single bug (the running apps list sometimes has graphic issues).