Related
Since I updated my phone to firmware JPU, people try to ring me and it doesn't show up on my phone, my phone vibrates for like a second but I don't see any notification showing any call coming through, anyone know what the problem could be and how to solve it?
Sent from my Samsung Galaxy S I9000
Samr happened to me. The vibrate that occurs is a force close. I wadnt able to find any other soloution for this bu to flash a different firmware.
Sent from my GT-I9000 using XDA App
I hoping someone else has problem, and has a solution, I like this firmware and don't really wanna flash again and have to restore all my apps.
Sent from my Samsung Galaxy S I9000
Has no one else had this problem since upgrading?
I have JPU (but in the form of darky's rom v5.2) and the phone rings fine, so I'm not sure if the problem lies in the jpu rom (but maybe it was a bug that darky fixed in the rom, not sure). Unfortunately, I don't know how one would solve this without flashing, but if you are gonna flash, then I really recommend darky's rom, it's one of the best out there atm.
I flashed the low level package with ODIN and phone calls have been fine. Actually asked someone to call me to make sure lol, been a quiet weekend....
TheMaverick said:
Since I updated my phone to firmware JPU, people try to ring me and it doesn't show up on my phone, my phone vibrates for like a second but I don't see any notification showing any call coming through, anyone know what the problem could be and how to solve it?
Sent from my Samsung Galaxy S I9000
Click to expand...
Click to collapse
I can only guess you have a bad app or you have old settings left from other firmware.
Its nothing wrong with jpu firmware.
**Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
I hope you are not using setcpu .. i had this kind of problem when using secpu ..
Well I've re-flashed now, and didn't restore system data and everything is great now.
P.S. anyone know how to stop 2 notifications every time I get a message, one comes through Handscent and one through the the standard messaging app.
TheMaverick said:
Well I've re-flashed now, and didn't restore system data and everything is great now.
P.S. anyone know how to stop 2 notifications every time I get a message, one comes through Handscent and one through the the standard messaging app.
Click to expand...
Click to collapse
That sounds like it's something that you have to change with your provider. I am with 3 aus and switched off the option to be sms reminded every missed call and it's unnecessary especially seeing as though the phone has that functionality and if you have voice mail you should be sweet to go. Good luck!
TheMaverick said:
Well I've re-flashed now, and didn't restore system data and everything is great now.
P.S. anyone know how to stop 2 notifications every time I get a message, one comes through Handscent and one through the the standard messaging app.
Click to expand...
Click to collapse
You need to go to the stock samsung Messaging app, then press Menu button to go into Settings, and scroll all the way down to 'Notification Settings' and untick the Notifications option. Now you should only receive it through Handcent only.
My friend had the same problem.
Here is the solution:
1, flash XXJPU
2, do a factory reset and wipe data + cache from recovery menu
3, do not restore system apps from titanium backup, just the 3rd party softwares.
That's all, the phone app will work.
The problem is, the old phone app leaves some cache and other crap and the new phone app doesn't works. That's way the solution is factory reset and wipe data + cache.
I hope it helps you. You do not need to flash again the phone, etc. Just do what I wrote.
Not a FW problem
Hi, this happend to me with XFJP7 FW. It started after I did several things:
1) did fix permissions in CWM
2) tried stock lockscreen (didn't work the several times, but finally worked)
3) restore with TitaniumBackup
I had backup of /system/framework directory, but restoring it didn't help. I ended up with flashing again with selective restore. Didn't try stock lockscreen nor fix permissions yet.
HTH
Mody
Probably same source here which also causes the "No-Vibration-Issue".
In most cases this is being caused by using a Lockscreen-/ Extended Power Menu-/ Circle-Battery-Mod that wasn't originally build and modified especially for your firmware. There's only a limited amount of ressources available for the system.
In some cases they first -seem- to work fine.
But in the backgound they (mostly) disable or block other functions because your new firmware wants to use the same registers or adresses (which the "wrong Mod" uses) for other os-functions.
In the end, I just re-flashed and only restored apps instead of system data + apps and now its working fine. Bingo!
When I receive a call, first the lockscreen shows up on my screen (instantly) for like a second and then it changes and I can answer the call. I have stock android lockscreen and 2.2.1. Do you think I have the same problem as others here or is this a different one?
"Unfortunately, System UI has stopped" won't stop popping up. So frustrating.
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new
Factory reset?
309041291a said:
Factory reset?
Click to expand...
Click to collapse
I guess that's my last resort. Damn
Edit: How would I even factory reset it? I literally can't use the phone. It's bricked. And in the recovery mode menu there is no option to factory reset. (tried pressing power and volume up)
If your phone is still locked, save the data (if needed) via adb and unlock it. But there could be easier way.
Sent from my Nexus 4 using xda premium
go to gmail account settings and sync everything. Google play will have your apps backup but not app data. Save all music, pics and files that you dont want to lose to your computer. Then just go to backup and reset in your settings menu and select Factory Data reset.
if that doesnt solve your problem you might have to use fastboot to reinstall the Jellybean.
neotekz said:
go to gmail account settings and sync everything. Google play will have your apps backup but not app data. Save all music, pics and files that you dont want to lose to your computer. Then just go to backup and reset in your settings menu and select Factory Data reset.
if that doesnt solve your problem you might have to use fastboot to reinstall the Jellybean.
Click to expand...
Click to collapse
I've had something similar to this on my G2x at one point; Android keeps popping up with errors and you can't do a single thing but reboot...which ends up erroring the same way when you're back in in an endless loop.
OP, you'll have to wipe and reinstall. If you've rooted it and enabled USB debugging then you're golden. If not, you'll have to go through several hoops to flash a factory image.
This link should help. http://forum.xda-developers.com/showthread.php?t=2016395
Several users have managed to invoke ADB commands.
Launcher
Smitty50 said:
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new
Click to expand...
Click to collapse
I have go launcher. After changing a wallpaper it starts the system ui loop pop up.
So after the restart I went to settings to come back to default launcher.
No more pop up
Tell me if it works with you...
cadiutori said:
I have go launcher. After changing a wallpaper it starts the system ui loop pop up.
So after the restart I went to settings to come back to default launcher.
No more pop up
Tell me if it works with you...
Click to expand...
Click to collapse
This thread is 4 months old. I'm sure he fixed it already lol
Sent from my Nexus 4
time and space don't exist
spaceman860 said:
This thread is 4 months old. I'm sure he fixed it already lol
Sent from my Nexus 4
Click to expand...
Click to collapse
maybe useful for someone else
cadiutori said:
maybe useful for someone else
Click to expand...
Click to collapse
Yes. Maybe he didn't restore the default keyboard before removing.
Hey, thread is old but have not found soultion for fixing "unfortunately systemUI has stopped" for PAC-man V05.. The ROM has all the options within it to customize without adding a theme and yet the friknnnnnn thing does this.. I went all the way back to flashing 4.1.2 again, rooting, formatted all storage... And even gave a 2gig partition for ROM(safestrap) still get error, sad cause has been my daily Rom for quite some time.. Just started out of the blue?? Suggestions??
XT912 RaZR SpYdEr CDMA
1droidmod said:
Hey, thread is old but have not found soultion for fixing "unfortunately systemUI has stopped" for PAC-man V05.. The ROM has all the options within it to customize without adding a theme and yet the friknnnnnn thing does this.. I went all the way back to flashing 4.1.2 again, rooting, formatted all storage... And even gave a 2gig partition for ROM(safestrap) still get error, sad cause has been my daily Rom for quite some time.. Just started out of the blue?? Suggestions??
XT912 RaZR SpYdEr CDMA
Click to expand...
Click to collapse
Flash factory image
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Flash factory image
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
He doesn't have a nexus. He's in the wrong place
From my BLACKED OUT N4
Sorry.. Googled topic, brought me here, did not realize... And i did fastboot the firmware, still systemUI issue but only with PAC-man... Handful of others I tested no issues.. I read on github (after i posted here) is a Know issue for PAC and why!!! Just strange, V05 was released weeks ago, why sooo long for issue to submerge... And no issues with V01-V04
XT912 RaZR SpYdEr CDMA PAC-manVO5
I am having this situation right now for my Nexus 4 (running stock 4.2.2 and installed Quick Settings mod from kevdliu, use the ROM for a long time and one day want to wipe all, after wiping, and reboot system I got this) and I think I figured out the solution: Wait until the battery is exhausted and automatically turned off, then put it into the charger for some time. Then pull it out of the charger, press volume up + down + power to get into fastboot. From here, we can wipe all and flash a new rom, or restore to stock rom, or do anything fastboot can do.
nubhihi219 said:
I am having this situation right now for my Nexus 4 (running stock 4.2.2 and installed Quick Settings mod from kevdliu, use the ROM for a long time and one day want to wipe all, after wiping, and reboot system I got this) and I think I figured out the solution: Wait until the battery is exhausted and automatically turned off, then put it into the charger for some time. Then pull it out of the charger, press volume up + down + power to get into fastboot. From here, we can wipe all and flash a new rom, or restore to stock rom, or do anything fastboot can do.
Click to expand...
Click to collapse
why install quick settings when stock 4.2.2 comes with its own form of quick settings? I'm willing to bet that's your problem!
hp420 said:
why install quick settings when stock 4.2.2 comes with its own form of quick settings? I'm willing to bet that's your problem!
Click to expand...
Click to collapse
you haven't used stock 4.2.2 have you? Its quick settings is so frustrating, it always takes me to Settings to turn on or off Wifi. I want a quick Settings that takes only one click to turn on or off Wifi, so I have to install that mod. Btw, I'm still waiting for the battery to die
_______________________________________
Update: Just to confirm, it works as I expected
hey i know this thread was already answered but i found that this messaged popped up after changing some settings for the navigation bar at the bottom of the screen. i didnt want it on my screen because i kept clicking either the back button or the home button which was very frustrating. so i tried to turn it off..that didnt work so instead i set all of the buttons to empty and the visibility to 0% and only after tracing back the steps i took (having to click the ok button for the stupid message about 80 times) i finally managed to find out that the navigation bar was the problem. hope you guys are able to fix your problem as simply as i did without doing anything drastic.
cjleven4 said:
hey i know this thread was already answered but i found that this messaged popped up after changing some settings for the navigation bar at the bottom of the screen. i didnt want it on my screen because i kept clicking either the back button or the home button which was very frustrating. so i tried to turn it off..that didnt work so instead i set all of the buttons to empty and the visibility to 0% and only after tracing back the steps i took (having to click the ok button for the stupid message about 80 times) i finally managed to find out that the navigation bar was the problem. hope you guys are able to fix your problem as simply as i did without doing anything drastic.
Click to expand...
Click to collapse
I recently had this issue and determined also that it must be something with my status/notification bar as it seemed to resize the screen to show the bar and then immediately resized it again as it displayed the System UI message. I use both Wanam and XBlast and disabled those as well as all Xposed modules. I also disabled Nova Launcher as default and rebooted. Re-enabled all and rebooted again and problem was resolved. Hopefully this will help others as well.
Same thing happened to my phone - Huawei Ascend y511. System UI has stopped Help!!!!!
Smitty50 said:
The phone is brand new, I just got it in yesterday and had it only for a day.
I was using swype, and just uninstalled it, and when I rebooted the phone, that error keeps popping up and won't go away, making it unable for me to use the phone.
Here's a video of what i'm talking about
How do I fix this? God the phone is brand new
Click to expand...
Click to collapse
Hi I have huawei ascend y511 and after disabling google keyboard i turned off phone and put it back on. This happened. Help me please, How do I get it back to normal? If I factory reset, will it work? Or should I let the battery drain out and do something. I can't do anything on my phone now because I can't even press anything because of the really frequent pop out of "system ui has stopped" . Help please.
Hey,
I recently rooted my Note 3, installed Titanium Backup, got rid of all the bloatware, then unrooted and am currently happy with my phone. Although, I thought, what if I want to sell this phone? Many features aren't working because I uninstalled them permanently, even after a factory reset via the settings. I am just wondering if theres a way to get that stuff back. Thanks.
P.S. If anyone knows why my auto screen rotation isnt working and how to fix it, I'll be thankful even more
ZachMyers14 said:
Hey,
I recently rooted my Note 3, installed Titanium Backup, got rid of all the bloatware, then unrooted and am currently happy with my phone. Although, I thought, what if I want to sell this phone? Many features aren't working because I uninstalled them permanently, even after a factory reset via the settings. I am just wondering if theres a way to get that stuff back. Thanks.
P.S. If anyone knows why my auto screen rotation isnt working and how to fix it, I'll be thankful even more
Click to expand...
Click to collapse
Do a Nandroid backup
verny94 said:
Do a Nandroid backup
Click to expand...
Click to collapse
I'll check that out, will update with results. Thanks for the reply
Basically as most of us know, updating to android L will remove root and custom recovery, also there are not many stable custom roms out yet for our G3 so many of us are still on stock rooted KitKat (It is also better than many of us expected with a cool remote control app that i don't think has been ported to custom roms yet). It even has option to hide and disable many bloatware apps (thanks LG). The annoying thing is that we get a pesky notification every day to update software. This should help everyone remove that notification, and don't worry should you change your mind the same method can re-enable it.
depending on your model go to dialer and enter hidden system settings.
some models here: if you have another model just google how to get to system settings (hidden)
Intl. LG G2 D855: 3845#*855#
AT&T LG G3 D850: 3845#*850#
T-Mobile LG G3 D851: 3845#*851#
Sprint LG G3 LS980: 5689#*990#
Verizon LG G3: ##228378 + send
Bell LG G3 D852: 3845#*852#
after you are in the hidden system settings:
- WLAN Test
- OTA Option
- disable or enable.
I just tried this so this isn't 100% verified working, will take a day or two to be sure it works but i've found cases of people saying it works on other sites so I thought i'd share it here, any feedback is appreciated as to if it works on all models etc.
- on my D852 bell version this actually DID NOT WORK ^^^... i'm going to leave it there because of reports it works on some models. check below for a working mod for D852
However BELOW is a fix that did work for me.
grab this app from play store : https://play.google.com/store/apps/details?id=cn.wq.disableservice&hl=en
go to system apps > Software Update > DMNotiService
- uncheck that service, grant root access, then reboot and wait and see if you get the notifcations still. I'm pretty sure this will work but obviously only time will tell. I dont think this will do any harm because you can re-enable the service should any apps start to malfunction, however as usual you are responsible for modifications you make to your device. It's been 3 days or so since I did this and I haven't seen a OTA update notification.
Hope this helps a few people out there
~ KS
this didn't work for me actually, about 12 hours after i applied it on d852 i got the software update notification; i've tried applying it again will report back if it works or not.
You can just hold the notification down go to app options and uncheck the show notifications option. And 90% of what you said about lollipop is not valid anymore.
ymcc said:
You can just hold the notification down go to app options and uncheck the show notifications option. And 90% of what you said about lollipop is not valid anymore.
Click to expand...
Click to collapse
seriously? LOL thanks for correcting me. Where is info about android L root etc..?
KronicSkillz said:
seriously? LOL thanks for correcting me. Where is info about android L root etc..?
Click to expand...
Click to collapse
If you just flash a lollipop ROM from recovery you don't lose anything. Bu i agree with you on the stability part.
code works for Verizon to access hidden menu but there is no WLAN Test option only Device Test; ELT Test; Log Enable. Anyone else been able to use this route to disable this OTA notification?
Steve
ymcc said:
If you just flash a lollipop ROM from recovery you don't lose anything. Bu i agree with you on the stability part.
Click to expand...
Click to collapse
are you talking about a stock version of android L or a custom rom that's android L?
If there is a stock version of android L that's twrp flashable can you please link it?
ymcc said:
You can just hold the notification down go to app options and uncheck the show notifications option. And 90% of what you said about lollipop is not valid anymore.
Click to expand...
Click to collapse
k so btw the unchecking of notification options is disabled in my version so that method must only be for some variants... and what exactly did i say about L that isn't valid anymore?
Vernon29RW said:
code works for Verizon to access hidden menu but there is no WLAN Test option only Device Test; ELT Test; Log Enable. Anyone else been able to use this route to disable this OTA notification?
Steve
Click to expand...
Click to collapse
if you want to try the method i just posted on the original post it's a good lead, although if you are on another variant the software update app could have another name, you should be able to locate the app by seeing what app info screen you end up when long pressing the notification when you get it. I have a hunch this is going to be the universal fix because when i used this app i noticed the software update in google framework is already disabled by default so thats probably why the builtin method didn't work but we are still guessing so far that's just a thought.
KronicSkillz said:
k so btw the unchecking of notification options is disabled in my version so that method must only be for some variants... and what exactly did i say about L that isn't valid anymore?
Click to expand...
Click to collapse
İf that doesn't work you can use titanium backup to freeze app updates, software updates and update center apps. That's a solid fix.
http://forum.xda-developers.com/showthread.php?t=2961073
That's the latest rooted stock lollipop.
ymcc said:
İf that doesn't work you can use titanium backup to freeze app updates, software updates and update center apps. That's a solid fix.
http://forum.xda-developers.com/showthread.php?t=2961073
That's the latest rooted stock lollipop.
Click to expand...
Click to collapse
that's for d855 and the titanium backup might work but freezing the entire app can cause more problems then disabling the notification, some of the other services are responsible for updating some of the stock apps like quick remote (i think) and personally i want those updated i just don't want to lose root
Kronic,
So I followed your suggestion by downloading that app. Opened it up and went into System Updates (my phone doesn't have Software Updates) but didn't find a DmNotiService option. I do however have a DmDownloadService that is checked and highlighted in blue. I'm wondering if this is it. Any ideas? Also do you know what the significance of something in blue is? I see red means it has been unchecked by can't figure out blue. Thanks for investigating this. Look forward to hearing your input on this.
Steve
Vernon29RW said:
Kronic,
So I followed your suggestion by downloading that app. Opened it up and went into System Updates (my phone doesn't have Software Updates) but didn't find a DmNotiService option. I do however have a DmDownloadService that is checked and highlighted in blue. I'm wondering if this is it. Any ideas? Also do you know what the significance of something in blue is? I see red means it has been unchecked by can't figure out blue. Thanks for investigating this. Look forward to hearing your input on this.
Steve
Click to expand...
Click to collapse
my phone doesn't have system updates so that is probably just the same app with a different name; I would try to disable it and see if your update notifications go away, if anything else goes wrong you can always re-enable it later.
I'm not sure why the DmDownloadService is highlighted blue but if that service is inside the system update app it's probably the service that actually downloads the update where as the noti service is just giving you the notification. I haven't tried disabling the download service because i don't think it will ever run on it's own without you clicking the update, and if it does it's probably already ran... not too sure to be honest. It's been a few days since i disabled the DMNotiService on my phone though and i haven't seen an update notification since so i'm happy as a clam
So I forgot to write back. I skipped this completely, downloaded Titanium Backup and just froze the entire System Update folder which is what the update notification is linked to. Once I did that I rebooted the phone and not one update since. Been quite a few days and nothing so I'm almost positive it worked.
Vernon29RW said:
So I forgot to write back. I skipped this completely, downloaded Titanium Backup and just froze the entire System Update folder which is what the update notification is linked to. Once I did that I rebooted the phone and not one update since. Been quite a few days and nothing so I'm almost positive it worked.
Click to expand...
Click to collapse
ya it probly did that's one of the ways u can do it
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