Hi, I'm currently on rooted by Tenfar method A2017u locked bootloader. I edited build.prop to improve the ram management and it worked, unfortunately, as a side effect, camera randomly crashes with Camera has stopped. why does that happen and how do I fix it guys? :/ any ideas? thanks.
When you flashed twrp, did you swipe to allow system modifications?
Nik2424 said:
Hi, I'm currently on rooted by Tenfar method A2017u locked bootloader. I edited build.prop to improve the ram management and it worked, unfortunately, as a side effect, camera randomly crashes with Camera has stopped. why does that happen and how do I fix it guys? :/ any ideas? thanks.
Click to expand...
Click to collapse
I've already mentioned this in my thread along with a "fix". I'm not sure what changes you made to build.prop but from what I've seen so far, corruptions only happen when editing the pre-existing build.prop. When adding something to the build.prop, all is fine.
Related
I just noticed today that my stock camera app will not even launch. It just says not responding. Does anyone else have this issue? If so, were you able to resolve this? I tried doing a factory reset and it did not work. Please help me!!!
B4oE said:
I just noticed today that my stock camera app will not even launch. It just says not responding. Does anyone else have this issue? If so, were you able to resolve this? I tried doing a factory reset and it did not work. Please help me!!!
Click to expand...
Click to collapse
That's a pretty known issue and been reported from user back in the Z-Community (ZTE official forums), hope next update fix things.....
DrakenFX said:
That's a pretty known issue and been reported from user back in the Z-Community (ZTE official forums), hope next update fix things.....
Click to expand...
Click to collapse
I had no idea. Do you have that issue too or is it just a random group of people that are experiencing this?
B4oE said:
I had no idea. Do you have that issue too or is it just a random group of people that are experiencing this?
Click to expand...
Click to collapse
I had that issue but no longer after B20 update and factory reset....
I always do factory reset after updates
I've figured out what the problem was. It all started when I made a change to the build.prop enabling the hidden multi-window setting. Even when I tried removing the change, saving it and rebooting my device, the camera still crashed. Factory reset does nothing either. I've tested this a couple times to confirm that this was the issue. The only "fix" was to restore my device from a prior backup that did not involve a modified build.prop.
B4oE said:
I've figured out what the problem was. It all started when I made a change to the build.prop enabling the hidden multi-window setting. Even when I tried removing the change, saving it and rebooting my device, the camera still crashed. Factory reset does nothing either. I've tested this a couple times to confirm that this was the issue. The only "fix" was to restore my device from a prior backup that did not involve a modified build.prop.
Click to expand...
Click to collapse
I have a different phone. The axon mini. My camera once was crashing when switching to manual mode. Nothing could help other than a nandroid restore.
Time when by and accidentally I found the fix.
Thanks great the build pro file from a stock rom. Go to system folder delete ir rename the old one and paste the new one there.
Reboot and ......boom....cameta sorted. No factory reset or restore needed.
B4oE said:
I just noticed today that my stock camera app will not even launch. It just says not responding. Does anyone else have this issue? If so, were you able to resolve this? I tried doing a factory reset and it did not work. Please help me!!!
Click to expand...
Click to collapse
Hi, is this problem fixed? And I not sure if we meet the same problem here, could you sheer a screen shot, thanks !
Hi!
I rooted my galaxy s7 edge that had stock version of android 7 (nougat) on it using this tutorial: http://www.droidviews.com/install-twrp-root-galaxy-s7-and-s7-edge-on-nougat-g935fxxu1dplt/. Now when I open built-in camera app it shows me a black screen for few seconds and then it says "Camera has stopped" and it offers me to "Open app again" and "send feedback" And it keeps happening over and over again.
Lemma: The reason is rooting.
Proof: Camera app worked perfectly. After I rooted my phone it started to crash like I described above. Then I tried to force quit camera app and delete it's cache/data. It did not help. After that I wiped entire cache partition. Still no help. After that I wiped all partitions except system. That did not work either. Then I re-flashed unmodified original stock ROM. Then camera worked perfectly again. Then again I rooted my phone the using tutorial I linked above. And again exactly the same issue. Camera app show black screen for few seconds and then crashes with exact same error message. ∎
Does anyone know fix for that? And why it happens? Is it some kind of samsung's anti-root thing that prevent camera fromworking on rooted phones or what?
Update [SOLUTION]:
In case someone else has same problem.
My solution was to skip restarts in TWRP steps. No restart between format and installing packages. Restart once when everything in TWRP part is done.
Root doesn't break your camera
I just Rooted my G935F that had Nougat as official firmware and had zero problems with the camera.
Sent from my SM-G935F using Tapatalk
I have international version of samsug with exynos CPU. Maybe this changes anything?
Root doesn't break your camera
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
I downloaded original firmware from here: https://www.sammobile.com/firmwares/database/SM-G935F/ (I chose baltic (only 1 occurrence in the table))
Maybe that specific tutorial I linked is bad one? Could anyone check that?
Rooted my G935F and no problems here for me.
I suggest you follow the tutorial here on xda and try again.
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
sysctl said:
Could you post link to tutorial please? Then I could be sure I used the same tutorial as you did.
PS! Now I also noticed that with rooting I lost auto brightness adjusting and also manually changing brightness didnt do anything. Right now I am back on un-rooted rom because I need camera functionality to work. But would love to get it rooted. Is there any info on cf-auto-root and android 7 yet?
Click to expand...
Click to collapse
A simple search here you'll find all you need. You are the only person I've ever read of that had camera problems like you've stated after Root. Again rooting won't break your camera.
I've Odin to stock literally hundreds of times testing Rom/Mods/themes as a tester for several teams from my s3 up to and including my G935F.
I've also flashed every Rom available for the G935F and the only ones with camera problems are the Lineage or AOSP Roms which more than likely are kernel related. Start here https://forum.xda-developers.com/announcement.php?a=81
Then this
Here's one
https://forum.xda-developers.com/showthread.php?t=3489011
sysctl said:
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Again rooting won't break your camera.
Click to expand...
Click to collapse
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Ok here is what you need to do.
Download a logcat app and get a logcat of it forceclosing.
I can't magically look in your device and see what, if anything is wrong.
As far as you saying you've searched well if you really did you would've found several tutorials.
How do I know?? Because I've used them myself.
It took me less than 5 minutes to root my new G935F using the TWRP Guide here on XDA
You seem to be the only one in hundreds that's claiming root broke your camera.
Provide a logcat in the Q&A and maybe a dev can help you.
sysctl said:
But then how do you explain that before rooting camera worked and after rooting it didnt work?
And how do you explain that after I flashed original rom back, camera started working again?
And finally, how do you explain that after rooting 2nd time the camera again started to show black screen and crash?
How can you be so sure if you didnt even answer these? Just because it worked for you doesnt mean it works for all. Looks like you dont even try to read what I write. You just read the title of topic and then jump to comment with out even reading the content of post itself...
I have done nothing else than rooting. I have not added any custom mods or anything. For me it starts working again every time I flash original stock rom and shows that black screen and gives error every time I root it.
Also, posting some specific link rather than general starting point would help to guarantee that I use right tutorial for rooting. From these links you posted I didnt find any specific tutorial. I did search and dig these links, but I didnt find any specific tutorials. All I found was some tools and some roms. But cf-auto-root works for android 6 but I have 7 on my phone so I cant use that and I did not find any rooting tutorials on this forums.
Edit: I have also tried this tutorial: https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084 . The same issue. The camera stops working after that.
Click to expand...
Click to collapse
Sent from my SM-G935F using Tapatalk
You could try to reset your settings
Same issue on smg935w8 lost camera and screen brightness. Also can't mount micro sd... we're you able to fix? I thought it was a bad root then I re flashed and the issue came back...twrp 3.1.0 supersu 2.79 and no verity 5.1
---------- Post added at 10:15 PM ---------- Previous post was at 09:50 PM ----------
im re flashing stock and tomorrow ill redo twrp and super su and skip dm verity patch think that might be the issue as it worked before for me last week and i then messed up by turning dev mode off and disabling oem and when i reflashed after that i have been flashing the dm verity patch....
give that a try if your still having issues
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Gray.Fox said:
had similar issue, my camera app keeps crashing, i went to settings, applications then cleared cache after stopping it, i hope that will fix your camera too
Click to expand...
Click to collapse
Thanks I've tried clearing cache for everything no luck. I originally thought it was because I might have deleted a system app with titanium but when I reflashed it all (firmware,tarp,supersu,no small verity disable 5.1) I still had the issue.
Lastnight I wiped and flashed the entire firmware. Everything works. Tonight I'm goi g to try and only flash twrp then supersu as I only want root. Hopefully that fixes my issues.
OP have your issues been resolved?
I'll let you know once I get it working on mine and we'll get you sorted out. I believe it's something with the steps or order as I had root fine for a day then had to reflash due to messing around and didn't do it my original way and that caused my issues.
flashed twrp 3.1.0 from odin with auto reboot off.
then booted to twrp. swiped right to mount system,
wipe data(format data) type yes.
mount microsd as mtp copy supersu 2.79 over if its not already on you microsd card.
else just install it from zip
cleared cache/delvik
rebooted to system
log in and setup everything and restore
camera and auto brightness...stilll doesnt work.
ok so after multiple tries to fix this (flash stock) everything works,, root and it breaks tried clearing all cache in system and twrp no difference... then i loaded phone info and used the secret codes to find out that my camera firmware is not installed....so im trying Flashfire to reflash the AP only while injecting supersu and maintaining root.... it is just booting up.....and OMG!!!!it works!!!!
so....for some reason...firmware was corrupting..... no clue why tired multiple methods and nothing... and im not a noob either.....
what finallllllllly worked was.... flash your rom and get root how you would normally. camera/auto brightness/and mounting usb doesnt work....boot to twrp. get your ap md5 file on your internal storage
reboot to system,. get flashfire from playstore or chainfires website
install and then click the + select firmware and select the tar file
only install system....uncheck boot and cp
then in the everroot select injject supersu, preserve recovery
and flash.... it will start flshing and boot to syteem once done..
everything is working nice
finalllyyyy!!!!
hope this can atleast help OP
no clue why i was losing firmware on the flashes
@unit68 Tnx for sharing. This time I got camera and brightness adjustment work out of box. But if in any point of time I happen to need your tutorial, I'll give it a try and let you know.
I am not sure if it is by chance or not but what I did differently this time was:
1) I paid attention to step where it asked to disable auto reboot (can anyone explain why?)
Previously I thought it shouldnt matter so I kept auto reboot for convenience.
2) I did format data, install no-verity-opt-encrypt-5.0 and SuperSU-v2.79-201612051815 and wipe dalvik cache with out rebooting between (Anyone know if that matters?).
Previously I had done it: format - reboot - install no enc - wipe dalvik cache- reboot - install super su - wipe dalvik cache - reboot .
Now I did it format - intall no enc - install super su - wipe dalvik cache - reboot.
I'll see for few days if anything else comes up or if camera breaks down again. Btw @unit68 what happens when you try some bloatware remover that run with root access? Do you get rid of bloatware or not? I tried few of them such as no bloat for example. Some complain that uninstall failed some seem to uninstall the app but when they reload app the app is still there and it's also still in app menu. Just curious if you have the same same issue. And is it safe to delete apk file manually? Or would it cause phone to crash/boot loop? When I ran supersu it complained about knox and asked me to disable it but it never managed to (however root checker tells me I am root). Maybe knox is protecting bloatware? Any ideas?
Flash your able too get it working! It was soooo frustrating. So for Knox supersu asks to disable then seems to hang so I go about my business reopen supersu it'll ask again and then is successful.
To remove bloat I normally just go to titanium and remove the ones I don't want
No issues on that and all my apps that require root work fine (titanium,adaway, flashfire)
This time disabling knox worked too... It turned out that all 3 apps that I used were note able to remove bloatware. App you named worked and also ROM toolbox lite works.
Btw when I google bloatware, the lists are incomplete.... Do you happen to know list of apps that must not be uninstalled? I guess white list would be better idea than black list.
Is installing/uninstalling app same as removing/adding apk files? So that I could cut and paste everything expect file manager and launcher to usb memory stick and then start adding required apps back one by one?
ive seen some samsung debloating software around. i honestly just remove stuff based on manually debloating for last fewyears. if i dont know what theapp is for i google it to see if its ok to remove. normally i remove samsung knox, few other samsung apps, some google apps (music, games, videio), briefings some edge panels, live wallpaper, and carrier branding apps(for me rogers) stuff like that. if you are going to i recommend you do a backup first as it ccan mess up your phone if you uninstall an important app. . also once your do uninstall you need to reboot ... the paid version of titanium allows you to freeze applications so you can try that first before removing it.
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
ScreAmeR01 said:
I had the exact same issues: camera crashing, blue light filter not working, brightness not working, etc. It was supersu. You need the right version of supersu, it's 2.79 SR0. It's checksum is f4ecbf5814215bf569ff3324fc1c91f5
Click to expand...
Click to collapse
Interesting..ill check that if I need to to Flash. I have 2.79 but maybe I grabbed an old version or a beta. Mine says 20161205 I think it may have been sr3
Edit _ just checked I grabbed sr0 the stable release from 20161215 not the sr3 beta
Maybe it was corrupt when I flashed
TLDR: App Manager crashes Settings on selection in all scenarios tried, both rooted and unrooted. Solutions or explanations?
So it's basically as described there. App Manager is crashing on a new Moto G4 XT1625 no matter what I do. I am at a loss. It crashes while rooted with Magisk, crashes when Magisk is uninstalled, crashes when I do a fresh flash of the Motorola stock ROM. I've even rooted and gone into Titanium Backup and ensured nothing is frozen, and it crashes.
I can long press apps on the drawer to reach individual app settings, but I cannot get into the App Manager itself. I've tried clearing the cache via this entry into the settings app info, and I've cleared the cache via TWRP. Neither has seemed to affect the crash either.
The only common denominator I can think of between all attempts is that the bootloader is obviously unlocked, but I can't connect that to the crash in my head.
At a loss here - any ideas? What am I missing, or what else might I try? Thanks for any education.
got this crash as well on my xt1622, TWRP, marshmallow, rooted
BUT THE MOST IMPORTANT REASON that cause this is because I deleted some unused (india) apps after rooting. Then the app manager messed up.
I just flashed the stock Nougat yesterday (https://forum.xda-developers.com/moto-g4/help/xt1622-nougat-root-questions-t3701145) - clean, no root, no TWRP, no modifications. Then, the app manager worked as expected. I doubt this will help as you stated that you already tried to flash the stock rom. You might have some other problem there.
libralibra said:
got this crash as well on my xt1622, TWRP, marshmallow, rooted
BUT THE MOST IMPORTANT REASON that cause this is because I deleted some unused (india) apps after rooting. Then the app manager messed up.
I just flashed the stock Nougat yesterday (https://forum.xda-developers.com/moto-g4/help/xt1622-nougat-root-questions-t3701145) - clean, no root, no TWRP, no modifications. Then, the app manager worked as expected. I doubt this will help as you stated that you already tried to flash the stock rom. You might have some other problem there.
Click to expand...
Click to collapse
Indeed I have, which makes it all the more confusing as to what could remain unchanged and still affect it. Although, it is something that you encountered it under the same general environment (twrp, marshmellow, rooted). I disabled a few apps when I first rooted, and assumed that was the cause as you saw, but no idea why the flashing did not fix it...
My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
bschmidy10 said:
My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
Click to expand...
Click to collapse
Flash back to stock
Yeah. I got a Google security alert saying a pixel accessed my account. Changes PW just to be sure.
Sent from my PH-1 using XDA Labs
bschmidy10 said:
My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
Click to expand...
Click to collapse
I wonder what it reports to carrier ... would it mean we can get volte if carrier has approved Pixel XL? (he thinks without looking into volte at all)
sorry not much help to you though
It's pretty strange. Same thing happened to my one plus 3 but I was running a custom rom so I didn't care at all. I'm 90% sure it's from the Google framework magisk module. I have never owned an actual pixel but for instance in my Google play music authorized devices section it lists 4 PIXEL XL phones lol. They are all from my location upon my security checkup and like I said my phone thinks that's what it is so I don't have a concern about being hacked. Only thing I'm confused about is why did removing the module not resolve the issue... Or how did they do it in the first place so I can make a module to turn it back into an essential phone lol. Only thing I found from searching was a deprecated GitHub repo for the module.
I'll probably just give in and wipe everything and go back to stock. Been wanting to avoid that because of the convoluted process of flashing and rooting with A/B partitions. I read somewhere there was a new method to maintain TWRP now though? Does anyone know anything about that? Appreciate the input (even if it wasn't much help lol)
I'm not running the framework module.
But I did install the pixel sound effects.
Sent from my PH-1 using XDA Labs
Hi everyone.
I edited my build.prop. Because oneplus didn't update the 6T with the latest security patch, I edited it in the build.prop myself. It worked, but for some reason settings then changed back to 2020-7-1. But the build.prop said 2020-10-1. I re-edited and reboot. An boom, it just reboots to twrp. I tried using adb pull /system/build.prop, edit it back to 2020-7-1. it didn't work. I even tried using :
But it still didn't work. Is there any fix, i didn't prperly back up my whatsapp, so its important that i don't wipe and factory reset my 6T.
Any help will be great. My 6T is currently in the recovery (TWRP 3.4.0-2), I was on 10.3.5 with Magisk 20.4
The issue was simple. the build.prop setting for security patches are in 0000-00-00. So its 2020-10-01
Extreme_Ninja2099 said:
Hi everyone.
I edited my build.prop. Because oneplus didn't update the 6T with the latest security patch, I edited it in the build.prop myself. It worked, but for some reason settings then changed back to 2020-7-1. But the build.prop said 2020-10-1. I re-edited and reboot. An boom, it just reboots to twrp. I tried using adb pull /system/build.prop, edit it back to 2020-7-1. it didn't work. I even tried using :
But it still didn't work. Is there any fix, i didn't prperly back up my whatsapp, so its important that i don't wipe and factory reset my 6T.
Any help will be great. My 6T is currently in the recovery (TWRP 3.4.0-2), I was on 10.3.5 with Magisk 20.4
The issue was simple. the build.prop setting for security patches are in 0000-00-00. So its 2020-10-01
Click to expand...
Click to collapse
Editing build.prop doesn't do nothing for the security patch. It's just editing the string that is shown in settings. So editing is useless. So put there 1.1.21 and bam you have January 2021 patch? Actual patch is in the rom files and libs. You can never fix it without a source code which is not available. Source code should be fixed with google security fixes and recompiled.
Reinstall the rom dirty, that should fix your problem. Good luck.
Sent from my ONEPLUS A6013 using Tapatalk
DaOldMan said:
Editing build.prop doesn't do nothing for the security patch. It's just editing the string that is shown in settings. So editing is useless. So put there 1.1.21 and bam you have January 2021 patch? Actual patch is in the rom files and libs. You can never fix it without a source code which is not available. Source code should be fixed with google security fixes and recompiled.
Reinstall the rom dirty, that should fix your problem. Good luck.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. But it already says that the issue has been fixed. I just pulled the build.prop and edited the security string to the proper format, done it now boots.