Sky Go / Device Spoofer / Root issues? Please help! - Nook HD, HD+ General

Hi all
Relative newbie here with incredibly frustrating issue that has wasted many of my hours recently!
I saw this a thread about getting sky go (a UK video streaming service) working on a nexus 10 by spoofing build prop to think it's a nexus 7http://forum.xda-developers.com/showthread.php?t=2045403
I flashed stock rom from Leapinlar's great thread (http://forum.xda-developers.com/show....php?t=2062613) then rooted with very green's equally great zip (http://forum.xda-developers.com/show....php?t=2437575).
Used device spoofer to switch build prop to nexus 7 and hey presto, skygo appears in play store - whoopee!
The problems come when I look to remove root - I used supersu to perform full uproot, reboot, clear cache, factory reset etc but whatever I try, skygo still gives me an error message saying my device is rooted.
Does anyone have any idea what might be causing this despite full unroot? Could it be the fact that the above process leaves me with cyanogenboot / non stock recovery? If so is there any way of rooting and spoofing whilst maintaining stock boot/recovery?
Thanks in advance for your help!
Mike

EDIT: Please do not create multiple threads for one specific reason, especially when you've just copied and pasted your message. I've replied to you in your other thread.

Related

[Q] Disable OTA notifications? [Solved]

I sideloaded 4.4 and found enough drawbacks that I restored 4.3. Now, any suggestions on how I can get rid of the OTA notification that finally showed up -- and keep it from coming back?
Update: It's been 3 days now, and no update nags!
tjupille said:
I sideloaded 4.4 and found enough drawbacks that I restored 4.3. Now, any suggestions on how I can get rid of the OTA notification that finally showed up -- and keep it from coming back?
Click to expand...
Click to collapse
AFAIK, there is no way aside from installing a custom ROM that wouldn't even try to receive it. POSSIBLY by rooting and deleting a file in your system area, but I can't remember specifics.
I'm curious; what drawbacks did you find, exactly?
I'm curious; what drawbacks did you find, exactly?
Click to expand...
Click to collapse
1. No Flash.
2. My bluetooth mouse refused to pair.
3. My preferred browser (Maxthon) FCs when opening a URL
4. No battery percentage
5. Stickmount launches, but won't actually mount anything
Except for the Stickmount problem, none of these, individually, is a show-stopper (no Flash comes close), but in the aggregate, I'm happier with 4.3.
FWIW, 2 & 3 seem to be hardware-specific. The mouse will pair with 4.4 on a 2012 N7 (but the response is so jerky as to make it useless) and Maxthon does run on the N7.
tjupille said:
I sideloaded 4.4 and found enough drawbacks that I restored 4.3. Now, any suggestions on how I can get rid of the OTA notification that finally showed up -- and keep it from coming back?
Click to expand...
Click to collapse
After reading many of the posts re: 4.4, I decided I wasn't going to install the OTA whenever it did come. Well it came yesterday and I wondered the same thing. I posted a similar question in another thread but didn't get any response. So I ended up just removing the zip file from the cache folder to see what would happen. I copied it to my sd card so I'd have it just in case and then just deleted it from cache. I tried a few things to see if it would automatically download the file again, but so far it hasn't. System Update in Settings still says, "Android 4.4 System Update, downloaded & verified - 219.9MB, Restart & Install." But hitting the install button doesn't do anything. It just says "Rebooting" but it doesn't actually reboot, so I hit Cancel Install. Been working with the device all day and haven't received any additional notifications for the OTA.
A whole bunch of suggestions in the Nexus 7 Forum:
http://forum.xda-developers.com/showthread.php?t=1998378
I went ahead and ran the install, knowing it would fail with TWRP (which it did) and then renamed otacerts.zip (in the system/etc/security directory) to otacerts.bak. Check for updates shows system up to date. Hopefully, it'll stay that way.
1. No Flash.
2. My bluetooth mouse refused to pair.
3. My preferred browser to (Maxthon) FCs when opening a URL
4. No battery percentage
5. Stickmount launches, but won't actually mount anything
Except for the Stickmount problem, none of these, individually, is a show-stopper (no Flash comes close), but in the aggregate, I'm happier with 4.3.
FWIW, 2 & 3 seem to be hardware-specific. The mouse will pair with 4.4 on a 2012 N7 (but the response is so jerky as to make it useless) and Maxthon does run on the N7.
Sent from my Nexus 5 using XDA Premium 4 mobile app
sharksfan7 said:
After reading many of the posts re: 4.4, I decided I wasn't going to install the OTA whenever it did come. Well it came yesterday and I wondered the same thing. I posted a similar question in another thread but didn't get any response. So I ended up just removing the zip file from the cache folder to see what would happen. I copied it to my sd card so I'd have it just in case and then just deleted it from cache. I tried a few things to see if it would automatically download the file again, but so far it hasn't. System Update in Settings still says, "Android 4.4 System Update, downloaded & verified - 219.9MB, Restart & Install." But hitting the install button doesn't do anything. It just says "Rebooting" but it doesn't actually reboot, so I hit Cancel Install. Been working with the device all day and haven't received any additional notifications for the OTA.
Click to expand...
Click to collapse
Is your device rooted?
coppercents said:
Is your device rooted?
Click to expand...
Click to collapse
Yes.
Try notification Helper
Gesendet von meinem GT-N7100 mit Tapatalk
Are there any ways in solving this problem without rooting?

[Q&A] [VZW_Stock Based TW Rom][5.0 Lollipop BOE1 Build Deodexed]

Q&A for [VZW_Stock Based TW Rom][5.0 Lollipop BOE1 Build Deodexed]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [VZW_Stock Based TW Rom][5.0 Lollipop BOE1 Build Deodexed]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
Works great thank you for the work. Also wondering about the advanced calling feature, but thanks for everything so far.
Advanced/Video calling
I'm having issues with advanced calling on this ROM as well. I was not able to get it working on BOD5, so perhaps it is the same issue. Any new input?
Great, but no Side load apps
You can side load apps on the original BOE build, but after installing the MODS_V2, you can side load anything. It does not allow you to click on the install button, bottom right hand of the screen
---------------
Edit:
This Version of the BOE build does not allow you to side load apps
CVertigo1 said:
I'm having issues with advanced calling on this ROM as well. I was not able to get it working on BOD5, so perhaps it is the same issue. Any new input?
Click to expand...
Click to collapse
I am also wanting to get advanced calling working. Is it possible?
Restarting with alarm.
I'm also having issues with the phone restarting at times when my alarm is alarming. I noticed this same issue on your BOC4 build, but didn't mention it because I updated to your BOD5 build. I didn't have this issue on the BOD5 build. I believe the issue is related to themes. I used your themes on BOC4 and BOE1, but not on BOD5, which may be the reason why I never experienced the concern in BOD5. I'm using Alarm Clock Plus, if that is helpful at all. I'm going to dirty flash the BOE1 ROM without themes and see if that fixes the concern. I'd love to use your themes if possible, but it isn't a deal-breaker.
Dirty flashing the ROM without theming appears to have solved the issue.
---------- Post added at 11:12 AM ---------- Previous post was at 10:18 AM ----------
Does anyone else have any issues with app updates not staying updated? After I update my apps and reset the phone, it takes forever to reboot, and it optimizes the same number of apps. When the phone finally boots back up, it tells me that those same apps need to be updated. I had this issue in the past, maybe on OC4, but I never found the cause. I am not themed anymore, so it isn't related to my theme issues.
Deleting the apps and reinstalling them does not fix the issue. I did backup the apps with TiBu, delete them, reinstall them from the play store, then restore data only. I'll give it a shot without restoring any data this time.
Deleting the apps and reinstalling them without restoring data did not work either. Also, I updated the play store using Aptoide, and that update sticks, but it did not fix the problem. The other apps appear to stick when updating with Aptoide, but it still shows them as needing to be updated in the play store.
CVertigo1 said:
Deleting the apps and reinstalling them without restoring data did not work either. Also, I updated the play store using Aptoide, and that update sticks, but it did not fix the problem. The other apps appear to stick when updating with Aptoide, but it still shows them as needing to be updated in the play store.
Click to expand...
Click to collapse
I had the same issue. After trying everything, I whiped and re-flashed the rom and everything has been working great since.
volume warning
Any chance of getting a volume warning mod, hate those.
straight talk
call straight talk and have them reset your data access, I've had to do this almost every flash of a rom but once you get your rom good, make sure the network mode is in lte/cdma not global. I've had good data for a while now with the kinks worked out, but you have to call straight talk to reset.
Fingerprint lock screen
nice rom, thou it looks like fingerprint lockscreen is broken. It just sticks to "swipe" to unlock when you set it to use fingerprint unlock.
Try flashing muniz_ri's g900v ROM first to get advanced calling working. That contains an actual image of the system partition, so you might have more luck.
Updates not sticking semi-fix.
cadditon said:
I had the same issue. After trying everything, I whiped and re-flashed the rom and everything has been working great since.
Click to expand...
Click to collapse
I figured out what causes the symptoms, but I'm not sure what causes the actual issue. I wiped the "system only," and re-flashed the ROM, but that didn't fix it. After doing some reading on other devices, I looked in the /data/app folder and found multiple apps had multiple data folders. The only apps with multiple folders were the ones that would not keep the updates after restart. There was a separate folder for every time I attempted to update the app, some as high as 15 folders. That explained why my storage space plummeted recently lol. I deleted all the duplicate folders and kept only the most recent folders, then the updates stuck after reboot! I had another occasion where the same occurrence happened, but I knew how to fix it at that point. I didn't like the thought of it possibly continuing to do this, so I backed everything up, did a factory reset today, and restored all my apps and data. I had a few updates afterwards, all of them are sticking after reboot, and I don't have any duplicate folders.
Bottom line: The issue lies in the user data partition, not in the system. Re-flashing or wiping the system will NOT fix this.
I don't know the actual cause of the duplicate folders being created in the first place. Other threads for other devices have mentioned similar issues and some have stated that odex files in the /data/app folder cause the issue. Maybe jrkruse can explain, because I'm baffled.
Hello, I updated to latest 5 android and now my lte doesn't work, I'm in russia now, but it worked on 4.4 , so , can I use this firmware to Odin my s5 verizone ?
Can xposed work with this and if so what are the install steps?
Quick Connect option
I have been looking for the Quick Connect option. How can I add it back? Thanks in advance for any assistance. Love the ROM by the way. Thanks for the great work.
Can I update from origin BOE1 ? I installed boe1 using Odin, and now is it posible to flash this via Odin?

A501 won't download from Google Play or install other ROMs

Hi,
I have an Acer A501 on which I installed CWM and a custom rooted 3.2 ROM shortly after purchasing it in order to use a certain app that required root permissions. I noticed that after the root, the device would give me a "server error" when trying to download apps from Google Play, but I didn't really pay much attention to it, since I didn't download new apps very often and I figured I could just get APKs from other sources. Recently, though, I have been trying to give the tablet a new life by getting Google Play back to work (since searching for APKs on dodgy sites isn't exactly the most reliable way of getting new apps) and maybe installing ICS. I flashed a stock 3.2 ROM and got rid of CWM, since I assumed it was the reason for Google Play not working, but apparently I was wrong, since I am still getting that error. I have also been trying to flash a stock ICS ROM, but every single one I've tried so far shows an error (the Android robot with the yellow warning sign) almost immediately after starting to flash. Does anyone know the solution to these problems? Any help would be appreciated. Thanks in advance.
Bump... Anyone?
vidyaftw said:
Hi,
I have an Acer A501 on which I installed CWM and a custom rooted 3.2 ROM shortly after purchasing it in order to use a certain app that required root permissions. I noticed that after the root, the device would give me a "server error" when trying to download apps from Google Play, but I didn't really pay much attention to it, since I didn't download new apps very often and I figured I could just get APKs from other sources. Recently, though, I have been trying to give the tablet a new life by getting Google Play back to work (since searching for APKs on dodgy sites isn't exactly the most reliable way of getting new apps) and maybe installing ICS. I flashed a stock 3.2 ROM and got rid of CWM, since I assumed it was the reason for Google Play not working, but apparently I was wrong, since I am still getting that error. I have also been trying to flash a stock ICS ROM, but every single one I've tried so far shows an error (the Android robot with the yellow warning sign) almost immediately after starting to flash. Does anyone know the solution to these problems? Any help would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
Yeah, I remembered I had the same error.
Anyway, pls try to check this link...
http://forum.xda-developers.com/showthread.php?t=2733038
In my case, I just removed the existing account. Then, add the same account & it is working OK.
Thanks for the link. As for removing and re-adding the account, I have done that multiple times, to no avail. I have tried force-stopping and clearing the cache of Google Services Framework, as suggested in the thread, but now, I get a connection error merely trying to add a Google account to the device... I even did a factory reset, but I still can't add a Google account, as if the Google Services settings hadn't been reset at all.
EDIT: I just realized that the reason I got a connection error after the factory reset was not being connected to Wi-Fi. However, after clearing the cache and data of Market, Google Services Framework and Download Manager, I get the same connection error while trying to add a Google Account, even while connected to a Wi-Fi network.
EDIT 2: I have rebooted the device, and now I'm back where I started. The error code is RPC:S-7:AEC-0 LOWQ-XYAM-M7MTS.
Any Luck? Same problem here with a stock A500 after a factory reset. I've tried two good google accounts. Getting "Google Talk Authentication Failed" and " Error retrieving data from server"

Messed up Settings app

Hi,
I'm going crazy ever since I factory reset my S5 Duos after getting stuck in a bootloop. My Settings app seems to have become totally different and I don't know how to fix it. I've
- lost two tabs (the Quick Settings and the Applications tabs)
- and the Menu (three dots)
- plus the Status Bar now sits transparently on top of the app (not the app below it) .
- The search bar is in a different place and
- some settings options are missing (e.g. Printing)
- one of the icons is too large (Download Booster) though I suspect a themeing error for that one).
Now I have reloaded one heck of a lot of apps (>300) and xposed modules plus trialled others then unistalled them so it may not be the factory reset per se. I do recall a recent OTA Security Update too (I think it was). Would that account for anything?
I've tried Googling but get swamped with too many generic topics. I've reset my theme to default and deselected all xposed modules and rebooted. No effect on the Settings errors (even the overly large icon)
Anyone shed some light on any of the above? Help would be greatly appreciated. I'll post some screen shots to aid in recognizing what's happened (pre reset shot.. actually a shot of my S5 not my S5 Duos but the two were the same bar Dual SIM options…. a current screen shot showing the problems and a crop of my status bar from my homescreen to help pick out the overlapping error which .only appears with Settings (no other app)).
Regards Mallow1
Galaxy S5 Duos (G900FD) running KitKat 4.4.2 stock Rom (rooted)
Mallow1 said:
Hi,
I'm going crazy ever since I factory reset my S5 Duos after getting stuck in a bootloop. My Settings app seems to have become totally different and I don't know how to fix it. I've
- lost two tabs (the Quick Settings and the Applications tabs)
- and the Menu (three dots)
- plus the Status Bar now sits transparently on top of the app (not the app below it) .
- The search bar is in a different place and
- some settings options are missing (e.g. Printing)
- one of the icons is too large (Download Booster) though I suspect a themeing error for that one).
Now I have reloaded one heck of a lot of apps (>300) and xposed modules plus trialled others then unistalled them so it may not be the factory reset per se. I do recall a recent OTA Security Update too (I think it was). Would that account for anything?
I've tried Googling but get swamped with too many generic topics. I've reset my theme to default and deselected all xposed modules and rebooted. No effect on the Settings errors (even the overly large icon)
Anyone shed some light on any of the above? Help would be greatly appreciated. I'll post some screen shots to aid in recognizing what's happened (pre reset shot.. actually a shot of my S5 not my S5 Duos but the two were the same bar Dual SIM options…. a current screen shot showing the problems and a crop of my status bar from my homescreen to help pick out the overlapping error which .only appears with Settings (no other app)).
Regards Mallow1
Galaxy S5 Duos (G900FD) running KitKat 4.4.2 stock Rom (rooted)
Click to expand...
Click to collapse
That does not look stock so I'd suggest reflashing stock, a factory reset is not sufficient for a reflash.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Thanks for your reply Rakuu.
I'm really hoping to avoid a full reflash having just done a factory reset last month and full reinstallation of everything. My ROM is stock (I'm just a heavy themer).
One option may be for me to get hold of a stock apk for Settings if someone with a S5 Duos would extract it and PM it to me. In the interim, I'll look at extracting my own from the factory reset partition (if that is possible… I'm quite a noob on Android after many years here on the WM side… even as far back as the old XDAs!).
That would at least eliminate anything I may have loaded then uninstalled leaving behind the mess. Keep your fingers crossed for me. .
Mallow1
Mallow1 said:
Thanks for your reply Rakuu.
I'm really hoping to avoid a full reflash having just done a factory reset last month and full reinstallation of everything. My ROM is stock (I'm just a heavy themer).
One option may be for me to get hold of a stock apk for Settings if someone with a S5 Duos would extract it and PM it to me. In the interim, I'll look at extracting my own from the factory reset partition (if that is possible… I'm quite a noob on Android after many years here on the WM side… even as far back as the old XDAs!).
That would at least eliminate anything I may have loaded then uninstalled leaving behind the mess. Keep your fingers crossed for me. .
Mallow1
Click to expand...
Click to collapse
There is no "factory reset partition", factory resetting doesn't flash anything, it wipes /data and /cache, if you brick factory resetting won't do anything, you will still be bricked.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Hi Rakuu,
Thanks for that insight. Greatly appreciated. It all adds to the personal knowledge base and big thanks to you for your time in replying
So back to my options:
-stick with what I have
-flash a new ROM
-install a new Settings apk if I can source an appropriate one
-live in hope of additional solution
Regards Mallow1
You *might* find the stock settings app in one of the zips in this thread......
http://forum.xda-developers.com/showthread.php?t=3286441
(I can't remember if I included it or not, but it should be there)
For info.....The included apps were ripped from a stock 4.4.2 firmware.....
Edit.....If I included them (there are 2 possibilities....Sec Settings apk and Sec Settings Provider apk) they'll be in the 'SystemPrivApp' zip as that is their location in the firmware.....
http://i.imgur.com/rVnFwJM.jpg
Hi KR39,
I appreciate your reply. I'll head off there and investigate. Just a double check first, this is re S5 Duos not merely the S5? I'm just cautious esp as XDA doesn't seem to have an S5 Duos forum… I guess we are a rare breed!
M1
Duos? As in dual sim card?
I don't *think* that'll make a difference unless there's a specific section of the settings that deals with the sim cards.....it's certainly not present in the archived app if that is the case.....
What *might* be more critical is what version of Android your device is running as Samsung might have changed critical areas of the Touchwiz framework between 4.4.2 and 5.0.0 (bearing in mind the changeover to 'Material Design').......
If you do try this, make a backup of everything first.
Make sure to delete/remove the original settings app AND the associated ODEX file when you copy the new settings app into the priv-app folder.
Also don't forget to set the correct permissions for the freshly copied app.
And then REBOOT the device in order for the new app to become active......
It may be that none of this works, in which case the only option may very well be to odin flash back to full stock.
http://i.imgur.com/rVnFwJM.jpg
Yes Duos as in dual SIM hence my pics show two sig strengths (bar the one I state is a shot from my S5 not my S5 Duos).
Ergo I wouldn't wish to flash anything not for the Duos (sorry folks I can't find an S5 Duos xda forum and an S5 is closest). So yes, the Settings app includes dual sim specific options.
Ok, so, so far, yes dual sim, yes need dual sim settings app and I need to educate myself re Odex or non-odex.
Overview so far… I'm not looking to get more complex… just a quick fix.
M1
It's looking like you're going to have to use Titanium Backup (or similar) to.....
1) backup everything you need.
2) make a recovery flashable zip (using TiBu) of that backup.
Then....
3) Odin flash back to full stock
4) re-root and flash a custom recovery, then use that recovery to...
5) flash the 'backup' zip to return your device to +/-90% the way it was before you started.....
I would leave the xposed mods and modules entirely out of that backup just in case it was one of them that caused the problems....you can always apply them individually and manually after you have your device up and running again.
The backup or update zip should just contain the playstore apps and their associated data......
http://i.imgur.com/rVnFwJM.jpg
Thanks KR, my issues while irritating aren't major enough for me to reflash my whole set up just yet (I may wait until CM13 is out of nightly beta only and xposed modules are fully MM compatible before I finally leave KK 4.4.2 behind). Thanks for your step process it'll be useful when I do change as I'll do it in steps as an educational process.
In the interim I'll rummage through my Ti backups and see if I can simply restore the settings app from there in isolation… might that work do you think?
Regards M1
Very good question.....to the best of my knowledge and limited TiBu experience, it will *definitely* back up (and restore) user installed playstore apps.....but I'm doubtful about system apps......
I've created update zips using TiBu in the past, and just out of interest, I've extracted them.....having done this, I've discovered that all my user apps are included inside the zip as actual app files, but I've *never* come across a system app......
My best guess is that when TiBu backs up apps, it does it in two ways.....
For user apps, it creates a backup of the app itself as well as it's data, but for system apps, it is only able to back up the data (anybody reading this, please correct me if I'm wrong).......
http://i.imgur.com/rVnFwJM.jpg
Yep my Ti backs up sys apps (option under backup setting preferences). Sadly I'd only got 1 back up as max history setting and that Settings apk resulted in the same view. Hayho… back to creative thinking. Next level is to hope another Duos user can extract the Settings apk for me (if 4.4.2) and send it to me… anyone out there?
Good luck fella....sorry I can't help out on that one......
Have you tried downloading the correct firmware from Sammobile or Samsung-updates and extracting it from that?
http://i.imgur.com/rVnFwJM.jpg
Hi KR,
Both great suggestions and gives me plenty of new scope to explore this. I'll also look into simply editing what I've currently got (extract, decompile, edit, recompile etc) as per:
http://forum.xda-developers.com/showthread.php?t=2184207
Your time and help has been much appreciated.
All the best Mallow1

Rooting Galaxy s7 edge (SM-G935F) nougat causes black camera with crash.

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

Categories

Resources