Related
So i have a Nook Simple Touch I was using about 9 months ago, which fell to disuse for a bit for a variety of reasons. It's running 1.1.0, and is rooted.
I dusted it off to recently give it some more use again, and wanted to update some of the apps, but discovered that the Market doesn't seem to work anymore - I know it used to, but now, whenever I try to download anything, I get a dialog: "Download Errror: Download was unsuccessful, please try again." I've waited an extra day, as I remember that was originally necessary to complete the registration process, but still nothing. Searching (with Market Search) works, even for things I haven't looked up before, and it still recognizes my account, as I see my email, though I noticed that the Nook Touch doesn't get listed in the Google Play Store under devices.
Any ideas what might be going wrong here, or things to try? I'm also willing to upgrade to a newer firmware (1.2.1), but am not sure of the best method to update a rooted device. I can pull it into a separate post, but I'll include it here for now:
I'm sure I'l have to root again, but Is it possible to upgrade the rooted device and then simply re-root, or will I lose everything I've installed? Is it just better to wipe, update and re-root? If so, is there any convenient way to keep all of my settings?
Thanks!
mrgygar said:
So i have a Nook Simple Touch I was using about 9 months ago, which fell to disuse for a bit for a variety of reasons. It's running 1.1.0, and is rooted.
I dusted it off to recently give it some more use again, and wanted to update some of the apps, but discovered that the Market doesn't seem to work anymore - I know it used to, but now, whenever I try to download anything, I get a dialog: "Download Errror: Download was unsuccessful, please try again." I've waited an extra day, as I remember that was originally necessary to complete the registration process, but still nothing. Searching (with Market Search) works, even for things I haven't looked up before, and it still recognizes my account, as I see my email, though I noticed that the Nook Touch doesn't get listed in the Google Play Store under devices.
Any ideas what might be going wrong here, or things to try? I'm also willing to upgrade to a newer firmware (1.2.1), but am not sure of the best method to update a rooted device. I can pull it into a separate post, but I'll include it here for now:
I'm sure I'l have to root again, but Is it possible to upgrade the rooted device and then simply re-root, or will I lose everything I've installed? Is it just better to wipe, update and re-root? If so, is there any convenient way to keep all of my settings?
Thanks!
Click to expand...
Click to collapse
Sad, no one wants to reply. Or perhaps no one knows.
Did a backup, and experimented. I couldn't update directly, so I wiped back to a stock ROM, and upgraded to 1.2.1. Rooted with ManualNooter, and the market worked. So I have no idea what was going on, but it works now. Sadly, a computer accident made me lose my backups (including unrooted images). But at least I've got something functional.
I am currently in the same boat with my NST (BNRV300) running rooted 1.1.2. I last installed and/or updated some Market apps successfully perhaps about a year ago, and have not made any other change to the Nook, so I am at a lost as to what might be the cause. Any pointers would be greatly appreciated.
For now, my workaround this problem is to download the desired app's apk file from an alternate source (e.g., APKPure) then side-load it onto the NST.
My guess would be that somehow your authtication with Google has been lost on the device.
If you go to the PlayStore on a computer do you see your NST listed as a device, and if so, when you select an app that way does it eventually appear on your NST?
Sent from my NST
nmyshkin said:
My guess would be that somehow your authtication with Google has been lost on the device.
If you go to the PlayStore on a computer do you see your NST listed as a device, and if so, when you select an app that way does it eventually appear on your NST?
Click to expand...
Click to collapse
I think you are right -- my NST credential with the Playstore must have expired or more likely become invalid when I changed my password on my Gmail account.
If so I can't figure out how to re-validate the credential: I recall entering my Google login/password via the YouTube app during the course of rooting my NST using the MinimalTouch tool's 2-phase process, but now I can't even get the YouTube app to start (error message: ... problem starting up, please check your network connection and system time).
Look here
I responded to a related issue awhile back. Not sure if the info at the link might kick-start the signing in process.
Thanks for the pointer.
I decided to go the route of "factory reset, upgrade to 1.2.1 and re-root using Nook Manager", as simply re-rooting 1.1.2 using the old tool (Minimal Touch) is tedious & somewhat error-prone -- plus I'd like to try out 1.2.1.
That was what I would usually suggest but the farther I have gotten from that "day 1", the less likely I am to take/offer the same advice. I've made so many modifications at this point I don't think I'd ever get it back to its present state! Back up early and often...and, apparently, access the Market every so often, even if you don't want anything.
Good luck!
I am on stock rooted MK2 with TWRP recovery installed. I woke up this morning to see that my phone had automatically downloaded the new system sfotware(i assume 4.4.2). The notification cant be removed from the notification bar and just says click to install. i dont want 4.4.2. My wife updated her s4 and it caused all sorts of minor issues with it. She was not rooted however. How can I get rid of the downloaded update and the notification? Also, is there a setting I can change so it wont try to automatically download updates in the future?
thanks
dbenney said:
I am on stock rooted MK2 with TWRP recovery installed. I woke up this morning to see that my phone had automatically downloaded the new system sfotware(i assume 4.4.2). The notification cant be removed from the notification bar and just says click to install. i dont want 4.4.2. My wife updated her s4 and it caused all sorts of minor issues with it. She was not rooted however. How can I get rid of the downloaded update and the notification? Also, is there a setting I can change so it wont try to automatically download updates in the future?
thanks
Click to expand...
Click to collapse
Im sure I will be needing the same information as I am still on 4.3 and want to stay here also, I can tell you I had the same thing with my Galaxy S2 and I remember I had to do something in Titanium backup to stop the update process, but I cant remember the exact steps.
I will be watching this thread closely, Thanks for asking the question!
Search fellas. On the notification . press and hold it. Then you should get a popup of "app info" select it and uncheck "show notification". This will get rid of the annoying update notifications. You can also delete the file from system although I am forgetting right now where.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Search fellas. On the notification . press and hold it. Then you should get a popup of "app info" select it and uncheck "show notification". This will get rid of the annoying update notifications. You can also delete the file from system although I am forgetting right now where.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Did that and deleted the file! It downloads it back and the notifications resurrects again.
I froze Configupdater, Sprint Installer, System Update
Disabled System Update on start up.
Dunno what else can stop this OTA notification!!
For me it's even more dangerous because I have the 720T running sacs for 720, hence the update that the system is trying to intsall is the NAE not NAF.
To be on safe side I'm thinking unroot and get to stock MK5 then upgrade to NAF then flash sacs again. This way the update notification will go away. Tedious but thats the only way I think I can get rid of this annoying notification.
Any thoughts?? Keep in mind I'm on 720T
frukyyy said:
Did that and deleted the file! It downloads it back and the notifications resurrects again.
I froze Configupdater, Sprint Installer, System Update
Disabled System Update on start up.
Dunno what else can stop this OTA notification!!
For me it's even more dangerous because I have the 720T running sacs for 720, hence the update that the system is trying to intsall is the NAE not NAF.
To be on safe side I'm thinking unroot and get to stock MK5 then upgrade to NAF then flash sacs again. This way the update notification will go away. Tedious but thats the only way I think I can get rid of this annoying notification.
Any thoughts?? Keep in mind I'm on 720T
Click to expand...
Click to collapse
interesting... I had recently ODIN'd back to stock and saferoot'd before calling it a day and woke up in the morning to an update. I also know that the update only downloads if you're on wi-fi. I know before I ODIN'd I was already saferoot'd with a whole bunch of crapware "frozen" by TiBackup and I never got the update. not exactly sure which crapware I froze, but I did it again this time around and I still haven't seen an update message for the past week. below is a list of what I froze... if you have the time to weed out the exact crapware needed to disable the update, please let me know! would be nice to uninstall the crapware that wont affect the update from happening while cleaning up the rest of the crapware.
1Weather
ANT HAL Service
ANT Radio Service
ANT+ Plugins
BaconReader
BlurbCheckout
Bubbles
CBS Sports
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
eBay
EpsonPrintService
Flipboard
Google Play Books
Google Play Games
Google Play Magazines
Google Play Movies & TV
Google Play Music
Group Play
HP Print Service Plugin
KLMS Agent
KNOX
KNOX Store
Lookout Security
Lumen Toolbar
Messaging+
Mobeam Service Application
Mobile Print
MobilePrintSvc_CUPS
MobilePrintSvc_CUPS_Backend
Phase Beam
Samsung Apps Widget
Samsung Books
Samsung Games
Samsung Hub
Samsung Music
Samsung Print Service
Samsung Video
Samsung WatchON
Samsung WatchON Video
SamsungHub Updater
Share music
Share video
Smart Device Manager
SNS
Sprint - Discover Apps
Sprint Music Plus
Sprint TV & Movies
Story Album
Story Album Widget
TalkBack
Weather Widget
Yahoo! Finance
Yahoo! News
looks like the inevitable just happened... with all the above items turned off/frozen, I still got the OTA download last night! I'm rooted with the hotspot mod and despite all of that, the OTA still came through. the update is located in /cache.
dimm0k said:
looks like the inevitable just happened... with all the above items turned off/frozen, I still got the OTA download last night! I'm rooted with the hotspot mod and despite all of that, the OTA still came through. the update is located in /cache.
Click to expand...
Click to collapse
Indeed! I gave up on OTA block. The only way I can think of if you stop all framework notifications, but I dont want to do that. Got to NAF and CF rooted. Waiting for stable KK before trying it on 720T. I don't care for sparks.
As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.
0Gravity said:
As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.
Click to expand...
Click to collapse
as I stated in my last post, the downloaded update file is located in /cache. for the time being I've deleted that file and created a zero-byte file with the same name and its permissions set to read only. not sure what's going to happen if I try to update with an empty file or if I reboot, but I have it this way to hopefukky assure me that if I accidentally press update that it won't update successfully. I doubt cleaning up the OTA downloads will prevent it from downloading again unless you can somehow fake your version number.
dimm0k said:
as I stated in my last post, the downloaded update file is located in /cache. for the time being I've deleted that file and created a zero-byte file with the same name and its permissions set to read only. not sure what's going to happen if I try to update with an empty file or if I reboot, but I have it this way to hopefukky assure me that if I accidentally press update that it won't update successfully. I doubt cleaning up the OTA downloads will prevent it from downloading again unless you can somehow fake your version number.
Click to expand...
Click to collapse
Doesn't sound like a bad idea! But I can't believe there isn't a fix for this out there though. In my research I found a file for the S2 called fota-killer, you would think something like that wild be available for the S4.
0Gravity said:
As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.
Click to expand...
Click to collapse
OK I tried the fotakill.apk method and so far I have not received the notification like I was eveytime I rebooted earlier go to here http://forum.xda-developers.com/showpost.php?p=30205683&postcount=1 for the instructions I used and a link to the file.... I used the manual method rather then installing the zip thru recovery because they said the zip method is device specific..... I'll stop back in a couple days to update how it's working or b4 that if it doesn't!
0Gravity said:
OK I tried the fotakill.apk method and so far I have not received the notification like I was eveytime I rebooted earlier go to here http://forum.xda-developers.com/showpost.php?p=30205683&postcount=1 for the instructions I used and a link to the file.... I used the manual method rather then installing the zip thru recovery because they said the zip method is device specific..... I'll stop back in a couple days to update how it's working or b4 that if it doesn't!
Click to expand...
Click to collapse
24 hours and still no update message!
OK it's been 4 or do days and this fix worked for me, we have not heard anything from the thread starter so I assume he has also fixed his, thanks for the help guys!
The 5.0 update is being forced onto me like crazy. Right now I am quite upset at whomever is developing Android, I guess google, not very knowledgable about it. Anyway, it's worse than Microsoft in forcing the update down my throat.
It started with the notification, which I could not get rid of no matter what I tried, but I lived with it. Then, android *insert censor word here* me by downloading the entire update in the background while on mobile data. I'm pretty much now at my limit, and I still have 25 days to go in the billing cycle. And now apparently since it's downloaded, it keeps "refreshing" my notification that the update is downloaded and ready to install, which I am afraid that if I ever need to restart my phone (freeze, etc), it will automatically install it, risking my data.
How can I stop the update?
First, can anyone please tell me how can I find the OS update folder to delete the update that was downloaded? I believe in doing so it will not automatically update if I need to restart my phone.
2nd, is there a way to stop the notification? Basically I want to update my OS when I am ready to 5.0.
Currently running Vanilla OS, 4.4.4
Thank you.
Google officially maintains android.... It's the one who has built lollipop... No. It will keep forcing you.. If you have root.. Check in the root folder for the downloaded OS and erase it.. That should help I think
Sent from my Nexus 4 using XDA Free mobile app
Do I have to root my phone in order to have access to the folder where the download was downloaded?
Messerschmitt262 said:
Do I have to root my phone in order to have access to the folder where the download was downloaded?
Click to expand...
Click to collapse
I just ignore the update messages at every new update. I don't dare do any updates at version .0 until at least the next release and when all apps have been updated as well; who needs the headache. Now if indeed the OS would eventually update itself without my knowledge, that would be very, very troubling as I might not have the most recent nandroid and titanium backups, but that has never happened to me in the past.
Without root, you can press the update notification, tap app info, and the untick show notifications. The problem with this is that you will stop all notifications from google play services. If you get root, than you should install xposed and then install the notify clean module, which will hide the update notification and only the update notification, nothing else.
My problem is now that the update has already been downloaded, and I am afraid that if I will ever need to restart the phone, it will automatically start updating at the next boot.
That is what I did until now, I ignored the update messages, but it somehow got pushed into my phone.
Messerschmitt262 said:
My problem is now that the update has already been downloaded, and I am afraid that if I will ever need to restart the phone, it will automatically start updating at the next boot.
That is what I did until now, I ignored the update messages, but it somehow got pushed into my phone.
Click to expand...
Click to collapse
Back up your phone and clean it off. I had 5.0 on my phone for exactly 24 hours before I wiped it and started over. Did not like it at all.
I went from 4.2.2 to 5, no looking back. My Nexus has had a new lease of life. The battery was barely lasting a day and it's now 30% better! No bugs or issues, it's running as smooth as a baby's bottom. Only one of my (free) apps isn't compatible, I can cope with that.
Sent from my Nexus 4 using Tapatalk 2
Sent from my Nexus 4 using Tapatalk 2
I just want to delete the already downloaded update. Could anyone point me in the right direction how I can do that?
Messerschmitt262 said:
I just want to delete the already downloaded update. Could anyone point me in the right direction how I can do that?
Click to expand...
Click to collapse
/cache/
Since that folder is empty, I assume I will have to root my phone?
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
Has anyone gotten latest version of PoGo working on latest Oreo with ElementalX? I've never played but my friends keep asking me to join so I figured what the heck..
Slight problem... Device Not Compatible??
I had magisk and xposed, but I tried disabling, and even fully uninstalling xposed (and all additional xposed modules), and adding PoGo to the MagiskHide options, with no luck.
It still says that my device is not compatible...I would assume that's due to the rooting?
Or is it because I'm using ElementalX kernel?
I read somewhere that there's a (not pokemon go-specific) bypass sort of thing involving SatefyNet, but you have to install Magisk *before* going through initial phone setup, but any guide I've ever read about flashing/rooting ph-1 says to go through setup and then install magisk. I tried to find the post that talks about it but I can't find it right now. Anyway, I would imagine there's some kind of checksum against system and if magisk has been added after the fact, the checksum wont match? I really have no idea, just a guess.
I haven't seen any other posts specifically mentioning Essential being incompatible, so maybe it's just me.
I was originally thinking it was because of root or magisk remnants(?), but maybe it's the non-stock kernel.
If anyone could help, I'd really appreciate it.
I feel silly asking such a noob question, I've just never play PoGo...or any Pokemon...ever.
extra info:
I have successfully created an account using their google auth option.
I get through the first Professor Willow part, then character selection.
Usually part way through character selection, I get the error in the attached image.
Its not on any one specific section, however, it can/has occur at any point during the loading.
I've cleared cache and data a hundred times because it seems to get further each time if I do a fresh data wipe and start over -- I know the next step already so I can get through faster maybe lol
--update--
I finally got through character selection and made it to the first chance to catch pokemon. I hit a squirtle and it was trying to break free, and then that error popped up.
Haven't been able to get back in far enough again to see if it actually added to my PokeDex or not.
Sorry for the late reply, but you have to hide root detection under magisk.
For Pokemon go to work, go to Magisk > MagiskHide > then search for Pokemon go and select it then reboot.