Terrible mistake - Galaxy S 5 Q&A, Help & Troubleshooting

Hi folks!
I did a terrible mistake on my rooted SM-G901F yesterday, maybe I was drunk or something!..
I noticed that the settings process was draining a lot of battery, so I decided to do a backup with TiBackup, and then uninstall the settings.apk to see if it makes any changes. There was the mistake...
The changes are that the phone boots properly and seems to work well, but it's not the case anymore with the touchscreen wich doesn't work at all, so I'm totally unable to use it.
The only thing I managed to do for now is to retrieve the settings.apk backup but I need to force the installation by USB I presume.
Any clues? It may be quite simple but it's out of my knowledge, your help would be greatly appreciated.

After some research it seems possible to install an APK in a .tar container with ODIN, but I'm unsure about that.
Or the other solution is to re flash the 5.0.2 official ROM, am'I gonna loose all data if I do it?

Related

help please! my tab's wifi wont stast! [error]

hello xdadev,
i really need your help. I am a newbie in android world [just purchased my first android device] last month [samsung galaxy tab p6800]. since then, i was really excited to explore android world and its features where I was led to this site.
now, heres my problem: just this afternoon, at first, i used my wifi to access a shopping mall internet connection. but minutes after turning my wifi off, when i turned it on again to connect to another network, i was surprised that it wont start and when i open the settings menu, under it says error. im really worried.
had my unit restored to factory settings but still no changes. Rooted my galaxy tab but today, i unrooted it thinking that the rooting caused the trouble.
im also hoping to update my tab to ICS but with this problem, im really stuck! i dont know how to access my apps in the appstore.
is this a firmware error or a hardware problem? please help me. my tab helps me a lot.
thanks in advance. im willing to add some details if you could help me.:crying:
try to go back to the mall where it 1st connected, if it still doesn't connect, then use your warranty and ask for replacement.
7.7 is notorious for being a bit choosy when it comes to wifi, sometimes, it just stuck with "obtaining IP address" then will revert back to scanning.
I also encountered your error before, but I just simply turn the wifi on and off again
before going back to your retailer, try to totally deplete the battery first (it's like removing the battery) then charge your unit and try to connect again
good luck
the last thing i could remember was busybox got updated but failed to install. is there any possibility that the failure caused the problem?
nope
biopsin said:
nope
Click to expand...
Click to collapse
Ah, sorry, busybox could, and may very likely be the culprit! An older version did just that to my (I have the 6810), and a number of others, tabs.
This was for Stericson's version 8.0 and here was his reply to my email:
Sadly you fell prey to a bug that was in Version 8.0 of my installer. I fixed it in 8.1, but it seems many still got the bugged version.
To fix the issue, you need to reflash your current rom. You do not need to wipe or clear any data.
You can also look in this thread: http://forum.xda-developers.com/showthread.php?t=1691410&page=2
It has an update method that should fix your issues.
Again, I apologize for this error
Please let me know if you need anything else from me.
I did just that and reflashed my rom using Odin and then re-rooted. I haven't, since, re-installed Stericson's busybox although later versions supposedly fixed the problem. I see there has just been another update in the Play store.
Damn I got the same error today, also after a lot of updates came trough.
Still working on fixing it. Will restore backup first after full wipe..
EDIT : Ok just went to recovery via power+volume up , factory reset, a nandroid restore and wifi working again.
Phew.
Ah! Got my tab working again. Thanks guys for the link and comments. The (update. Zip), did fix the issue. Busybox related bug. Starting to re download my apps again since I got my tab data wiped. :-(
Sent from my GT-P6800 using xda app-developers app
Not rooting my phone as of now. Will wait for the ICS first before rooting again. Tab is fully working already.
Sent from my GT-P6800 using xda app-developers app

[Q] SGS4 WiFi/Bluetooth Death, ZERO working solutions, willing to pay.

Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.
Wexberg said:
Hi everyone, I'll try to keep this as concise and clear as possible. Thanks in advanced for reading this.
Phone: SGS4
Running: Android 4.3
Carrier: Bell Canada
Rooted: No
Rom: Stock TouchWiz.
Problem: The phone will not turn on WiFi or Bluetooth. If you attempt to switch either on, it remains a dim green for a few seconds and then turns back off shortly after.
Solutions tried:
(a) Battery pull.
- Unsuccessful. (At first, if battery pulled during Samsung logo animation after restarting from ON state, both WiFi/Bluetooth would turn on again, sometimes for minutes, sometimes hours. Eventually, this stopped working. It would only work on a restart pulling the battery during the animation, never at any other time)
(b) Update to latest firmware through Samsung Kies.
- Unsuccessful.
(c) Boot into safe mode to see if any applications were the cause.
- Unsuccessful.
(d) Wipe device clean and start fresh.
- Unsuccessful.
(e) Change WiFi power saving state to off through *#0011# menu.
- Unsuccessful.
I have not tried loading other roms or kernels.
A quick google search shows that many people have the same problem, I have yet to find a working solution. If anyone here can point me in the right direction, I'm willing to pay at this point. I cannot return it to Samsung as there is a crack on the screen which has voided the warranty. I could fix the screen and try sending it in but I'm hoping for a software solution.
I feel as if it is not a hardware issue as the battery pulls worked initially.
Any input would be greatly appreciated. Once again, I'm willing to pay for a working solution, the number is up to you as long as it is reasonable.
Click to expand...
Click to collapse
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
DeadlySin9 said:
When you say wipe device clean, how did you do that? Did you use ODIN and flash the firmware or just do a factory reset?
Click to expand...
Click to collapse
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Wexberg said:
I did not use ODIN, I did a simple factory reset. I will try that ASAP and post an update. If there any other solutions as well, I would really appreciate them in case that does not do the trick.
Thank you for your response DeadlySin, it is greatly appreciated.
Click to expand...
Click to collapse
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
DeadlySin9 said:
Just try that first, as doing a factory reset does not actually change the system files but rather wipes all userdata. Just use the file for whatever firmware you have in the I337m firmwares thread.
Click to expand...
Click to collapse
Wexberg said:
DeadlySin9,
I finally got around to using odin to reset the firmware, first to stock 4.3 from my carrier, then 4.2, both of which still failed to change the state of the problem. At this point, it seems like an obvious hardware problem but if that was true, I still can't understand why I could re-initiate WiFi/Bluetooth after a specific pattern of battery pulls (this does not work anymore but worked for awhile, stopped, then started again, now finally stopped). Any last ideas? I really appreciate your help.
Click to expand...
Click to collapse
I don't know why that would work. At this point I'm not sure what else you could do. I know I used to have WiFi issues after some flashes with my Inspire but i never really had a fix even then.
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Been there, done that.
It's not a hardware problem. It is, I believe, problems with the restrictive 4.3 update not playing nicely with some system settings. In short your system drivers or configuration settings are getting messed up to to bugs in how Knox and the bootloader are interacting with the modem.
I had your exact symptoms after installing certain custom ROMs, also noted that the problem could be temporarily "fixed" if the boot process was interrupted or by specific sequences of modem changes. The situation is not helped by Bell being more restrictive than other Canadian carriers e.g. Rogers, something that also caused me problems when I was enabling AWS on a Bell firmware.
The effective solution was to install a custom recovery to facilitate a complete wipe of files, then flash a Rogers stock image. Cured. And continuing to work properly if subsequently returned to a Bell stock image. Although, frankly you'd have a more stable and flexible platform if you you kept the Rogers image in the end. If the build properties edit doesn't solve your issue, then here is a path for you to pursue.
.
1/2 Lit Toggles - build.prop editing issue
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
jrwebdev17 said:
I have the exact same problem - I'm on US AT&T, I337UCUAMF3, Android 4.2.2 and this solution looks promising. I followed the steps and have RW set up, but ro.securestorage.support does not exist in my build.prop file. Does anyone know if this property is specific to certain builds and/or if there is an equivalent property?
Click to expand...
Click to collapse
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
DeadlySin9 said:
Adding it to the end shouldn't hurt as long as you make sure you set properties on the build.prop
Click to expand...
Click to collapse
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Editing build.prop is a plausible workaround if the OP has root access. If he doesn't wish to root his phone, then he can clean up his system configuration by reinstalling as I described earlier in the thread without requiring root. Two approaches to the same result.
And yes, you can add the entry if it doesn't already exist in your configuration.
.
jrwebdev17 said:
Thanks for the tip, good to know it wouldn't screw anything up. I did add it to the build.prop file, rebooted and it seems to have had no effect. Seems that if the property is not present in the file, adding it does not resolve the problem.
Click to expand...
Click to collapse
UPDATE: I didn't have any luck using the build.prop fix, nor with the wpa_supplicant.conf fix that some of you may have seen mentioned. I ended up Recovering to stock MF3, (I was already on MF3). This gave up my root access, and I didn't take any additional steps to hide busy_box or anything like that, after my MF3 recovery it looked like I was safely unrooted and I contacted AT&T support via web-chat, and they asked some questions and sent me to a nearby AT&T device center. I took it there, they didn't ask a single question about how it happened, whether I had rooted it, etc(although I was paranoid that there would be traces left behind and they would turn me away). Long story short, they replaced the phone no questions asked!
In my opinion it would seem that while this problem could in some cases be caused by rooting and tinkering, it's enough of a known issue to AT&T that they would replace it under warranty. Hopefully Bell or other carriers would do the same. My advice is to try your carrier, particularly if you are with AT&T.
Just to help people who are searching for a solution. I had flashed a T-Mobile rom and my wifi stopped being togglable on my AT&T S4. That is, I couldn't turn on wifi. The button would get stuck on. After trying to flash what I thought was the right MK2 modem and still having the same issue, I thought I was out of luck. However, I found this one here: http://forum.xda-developers.com/devdb/project/dl/?id=3275 and hit paydirt. Flashing it using Safestrap and then wiping cache and delvik worked. The file is called jflteatt-MK2-modules.zip.
Only for WIFI, for me what worked was I had to open a litte bit the one side of the phone and close it again (removing a little the plastic, like if you were going to open the device) Wifi started working again, no need to flash any roms, it seemed to be something related with pressure, humidity or something inside the phone.
Regarding bluetooh I had no luck still not working, only keeps saying activating and never gets activated.
does anyone find a solution for this yet?
I have had the same issue for months. Started after warranty was up. I have AT&T on nc1. I tried everything mentioned here but nothing worked. Even left it with the phone repair guys for a week with no luck. It first started after I flashed Hyperdrive ROM. A reboot helped for a while. It actually came back for a week on Kevp's ROM, but then had an error that reboot the phone and lost it again. Phone is now on Craigslist and I am back to my S2. On a high note it's nice to not have a unlocked bootloader again.
you need to flash the exact same model/firmware's modem file atleast thrice before giving up.... i have a simalar issue the thing is my model number is 1377z and google doesnt have a working flashable modem file for it so basically i am screwed too wifi calling and video recording doesnt work....
update :: saw that you got it replaced !!
smoooth .....
Amb669 said:
i had issues enabling wifi after installing a custom kernel & with certain roms (same 1/2 lit green toggle crap, sometimes it would toggle back off sometimes it would just stay 1/2 lit and make my phone burn)
my solution has been 100% working for myself so far, if you'd like to try it here's the directions
1. install es file explorer
2. set root permissions AND mount as writable, within es file explorer
3. use es file explorer to navigate to the root of your phone (system directory, i think) and open the build.prop file than select the es file editor
4. find the line that says ro.securestorage.support=true and edit it to false, save and close
5. reboot phone, and hopfully you have no more wifi issues
i was skeptical when i first did this because nothing worked to fix my wifi, but this works 100% for me on every rom
Click to expand...
Click to collapse
Just tried this on my sgh-i337m that was having the same wifi issues after rooting and flashing a kernel. Rebooted and wifi is up and running. So far so good. Thanks a lot!

[Q] Advice Please - Mobile Odin - Could not detect device model - USB not recognizing

Hi all, hoping to get some advice in regards to a brick wall I've hit.
So background, my Galaxy S4 (i9505 running 4.2.2) has had ongoing USB recognition issues and thus I haven't been able to upgrade to a custom rom for a while. After following a couple of very detailed and useful guides on here, without success I had decided that it was likely one of two things:
A hardware problem (I have a third party charging port installed after the OEM stopped working)
Or when I was playing around with settings I derped and uninstalled the MTP application or some related core service.
So I left it for a while but today I decided to do something about it and discovered Mobile Odin (4.20), bought it and clean flashed SlimKat 4.4.4 (http%www%slimroms%net/index.php/downloads/dlsearch/viewcategory/1182-jflte). Took a while but the rom booted, really liked the look and I tried to install 3rd party apps and set up phone as usual but noticed that Google Play Store was missing. Manually installed V4.9 but it kept opening and closing so I uninstalled and the flashed the normal gapps and the AIO gapps through Mobile Odin (with and without clear cache), both processed OK but upon reboot none of apps ever installed.
So I decided to re-flash the SlimKat, I had to re download as I performed a factory restore in amongst things and had the original rom stored on internal. When I flashed inject root was checked as were all the other default options but upon reboot Mobile Odin is giving me "Could not detect device model" which after looking around basically means I lost root .
So my questions are: Without connecting via USB (because it's still not working) what are my options for flashing another rom or regaining root? Is there a way to get to stock 4.4.4 without USB?
Really appreciate any advice, currently the phone has network service and WiFi so in the mean time, without Google Play store it is just a significant inconvenience, but still operational.
Regards,
Marc
#Update
I don't know how but my root has been restored while I was playing around clearing app cache's etc. So now I have SlimKat 4.4.4 but unfortunately still no Google services/Store etc. When I manually install it, it has this issue where it automatically opens and then closes, so still working on fixing that. Again appreciate any input.
Hello, I've been flashing ROMs for a while now and I can't think of a way to regain root from within the ROM itself. How did you get root on your device in the first place to install mobile odin?
I have never used a play store application for any type of flashing, was never sure if it would be reliable or not. That being said, have you installed a custom recovery into your phone whilst you were playing around with it? If you did then you can fix this without fixing your USB connection.
However if you still have stock recovery, you probably need a USB connection to regain root. If that is the case, what have you actually tried to fix the USB problem?
lichking21st said:
Hello, I've been flashing ROMs for a while now and I can't think of a way to regain root from within the ROM itself. How did you get root on your device in the first place to install mobile odin?
I have never used a play store application for any type of flashing, was never sure if it would be reliable or not. That being said, have you installed a custom recovery into your phone whilst you were playing around with it? If you did then you can fix this without fixing your USB connection.
However if you still have stock recovery, you probably need a USB connection to regain root. If that is the case, what have you actually tried to fix the USB problem?
Click to expand...
Click to collapse
Hey @lichking21st. Mobile Odin is allegedly just odin without the need for USB. I have tried to fix the USB to no avail
Actually just about to update my original post, I don't know how but my root has been restored while I was playing around clearing app cache's etc. So now I have SlimKat but unfortunately still no Google services/Store etc. When I manually install it, it has this issue where it automatically opens and then closes, so still working on fixing that. Again appreciate any input.
Problems solved!
Clean flashed stock rom then clean flashed back to SlimKat. Google play and root carried over.
USB still not working have to put it down to a hardware issue now. Oh well, so happy
@MOD you can close this. Thanks again for the help LichKing
grinchenator said:
Problems solved!
Clean flashed stock rom then clean flashed back to SlimKat. Google play and root carried over.
USB still not working have to put it down to a hardware issue now. Oh well, so happy
@MOD you can close this. Thanks again for the help LichKing
Click to expand...
Click to collapse
Glad to see your problem is fixed, I would still advise you to get a custom recovery so you have some options if you really get stuck without root for next time. I recommend using TWRP but CWM works too.

Samsung Galaxy Tab 4 T530NU Firmware/TWRP/Bootloop

:crying: -Sigh- Alright, this has been a pretty stressful two days so I'll try to be as specific as I can.
Device details:
- Samsung Galaxy Tab 4 10.1 T530NU 16 GB Black with WiFi capabilities.
- I was running Lollipop 5.0.2.
Problem:
I wanted to get Xposed installer on my tablet, and found out if I wanted to get the modules I wanted working with what I wanted to do, I needed the Xposed Framework installed onto my tablet. I went to research on how that works/what do to to get that up and running for me, and I found out I needed TWRP, had to add it on my tablet with Odin, and then add what I needed for Xposed in a custom boot through my SD card.
As soon as I got TWRP on my tablet, I've been stuck on a bootloop.
Things I've tried:
- Wiping all data.
- Clearing cache/dalvik.
- Charged to full, and retried clearing cache/wiping again.
Additional Details:
- I have access to a PC
- Able to connect my tablet to a PC via USB cord.
- I'm in the US (Since I've some some region specific things floating around)
What kind of help I'm looking for:
- A updated(?) and working stock firmware for my device.
- TWRP version that will work properly on my device.
- Xposed framework ZIP to add to my device.
I've been spending hours and hours trying to find websites and threads on here and on the internet in general to help me fix it, or find stock firmware for my tablet to start over from scratch. I have had no luck anywhere at all. My desktop is just piled with .ZIP files that have claimed to work but no longer work(?).
I'm just at a loss...It's really diving me crazy. So, as a last resort, I'm writing to see if I can get some help on here. I'm not one to really ask for help on things like this..I usually do enough research to figure it out but I feel like I've visited every single thread/site I can and have had no luck. I would greatly appreciate some guidance
Resurrecting this thread after over a year hoping someone is paying attention...
Tying to the thread hopefully getting enough people talking about this... again.
forum.xda-developers.com/tab-4/help/samsung-galaxy-tab-4-10-1-sm-t530nu-t3441044#post74700970
I have the same problem as well. I have downgraded from 5.0.2 to 4.4.2 hoping that would work. I flashed PACMAN custom ROM and GAPPS 6.0 nano last night and was able to get in and through setup, but the wifi will not work nor does it detect any nearby networks.
Looking for answers here... Corrupted partitions maybe? I have stable stock ROM's
Maybe sideload APK's to evaluate/fix the issue from the ui side - if any apps exist?

Flashlight being used by another app. Camera doesn't work

After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others
Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.
This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps

Categories

Resources