Related
hey everyone!
Alrighty i have been following the massive msm7k overclock thread and i have found a way to overclock stable to a 691 mhz with going to sleep and receive phone calls with no SOD.
I cant take all the credit for this because of it not being made by me sooo thanks to nettrip, mort (mortscrip), and RoboWang (throttling creator).
So if you think your Imagio needs a little kick start! This is your solution! USE AT OWN RISK (NOT ALL DEVICES WILL BE ABLE TO REACH ALL SPEEDS) USE AT YOUR OWN RISK AGAIN!
First off you must know how to regedit, create shortcuts, and navigate through file structures.
Download mort Script cab for you device. (google mortscript ( its the .de site) - download the zip for pcc)
Install it on your imagio
Download the v2 msm7kcupspeed from nettrip's thread here on xda and install. do not change any speed values in the program. You will use this to check that the OC is working and the scripts are installed correctly.
OKay here is the tricky part.... SO PAY ATTENTION!!!
Open your regedit (total commander is a good one) and your going to locate where your DispOn Registry is. Two locations to check. CHECK where it is or youll be doing all this work for nothinnnn!!
reg_root_bkl = "HKCU" <--------
reg_key_bkl = "ControlPanel\BackLight"
reg_val_bkl = "DispOn"
or
reg_root_bkl = "HKLM" <--------
reg_key_bkl = "Drivers\Display"
reg_val_bkl = "DispOn"
The rom i am using has it located at HKLU/ControlPanel/Backlight
Once you find your location download the correct file.
IF YOUR LOACTION IS HKLU then grab CSA_U.mscr
IF YOU LOCATION IS HKLM then grab CSA_M.mscr
Copy this file to your storage card. It is neccesary to put it on the storage card because if you clock too high you can just take out the SD card and run at normal speeds till you made corrections to the file.
You MUST know the location of DispOn to use the scripts. You must manually check.
Using your device file manager (activesync), create a shortcut for the .mscr file (rightclick on it and create short-cut). Then just copy the shortcut file to your device Window/Startup directory.
Then just reset and hopefully, you are good to go. One file, Auto OC.
You can use the MSM7 OC app to check the OC, but be sure to exit from it or you will get an error when the phone awakes.
Now for the OC settings.
This script has these settings in them for safety reasons. Not ALL cpus will overclock above the settings in them, but MOST will at least OC to these values.
values set are
start_speed = 37 710
boost_speed = 36 691
safe_speed = 31 604
These are the values that i am currently using... Feel free to change these values to accommodate your device max speeds. Always keep the safe speed at 31!!!! or you will get SOD's
Goodluck!
i hope this helps out my fellow imagio lovers!!! Its like i bought a new device yesterday! This phone is perfect!
Over Clock
Hey,
I live Va also, could I meet you somewhere in Richmond and have to do this to my Imagio?
Just wanted to say, worked like a charm, no problems, took a little googling outside of what is said here, but that is with never messing with my phone, all this takes is a little bit of common sense, thank you very much!
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
couchlife said:
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
Click to expand...
Click to collapse
Try this:
1. turn it off completely
2. press at the same time the power button (back side) and the two lower side buttons (bottom left and bottom right page)
3. it should start the recovery and restore your device to stock
Link: http://forum.xda-developers.com/showthread.php?t=1137967
Let us know if it works.
hi,
now i don't have the Nook available (i'm at office), but yesterday i was playing with ADB and having a look at nook system folders; i remember seeing a property file in which there is a property like demoMode=enable/disable or something like that (i'm not sure, but if i remember well this file should be in the same folder where also other device specific properties like serial number, mac address, etc.. are stored).
Until reading your message i didn't even know such a mode existed. But now i think that maybe it could be possible to edit that file and enable the "regular" mode on your Nook.
Of course, even if that is possible, you would need to get root and ADB access to to that, and there is the risk of bricking the unit (even though if you can create a backup image to be on the safe side).
When i'll be back home, i will try to find further info about the above mentioned file.
Regards
hi,
i don't know if you already solved, in any case i had a better look at the system folders of Nook, and it seems to me that the Demo Mode is managed by a dedicated application (/system/app/DemoMode.apk). Baksmaling the source code of this app, it seems that it is activated on any Nook unit after boot, but in case the value of setting "demo_mode" is not set to "on", it just exits without doing anything; on contrary, the demo mode is activated (i.e. the continuous loop through a set of images).
So, to get rid of demo mode is activated, you could launch a script to change the relevant value of the setting "demo_mode", to set it to "off"; and then reboot the Nook:
Code:
echo *************************
echo * Setting Demo-Mode off *
echo *************************
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value='off' where name='demo_mode';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
del settings.db
Of course, to be able to launch it, you need to have your Nook already rooted, so that ADB is enabled.
The script is inspired from similar scripts present in the batch file "xe-autoroot.bat" from user xboxexpert of this forum. Therefore, in case you still don't have rooted your Nook, i suggest you to use its script to get it (link to the thread). In this case, you can easily launch the script to disable demo mode from the same folder where you have xe-autoroot.bat, since yu already have all the needed software (sqlite3).
Another possible solution could be just to remove DemoMode.apk from /system/app folder (but i'm not 100% sure this would have side effect).
In any case, not having a demo mode Nook unit, i cannot be sure these methods would work.
Hope this help
That doesn't work
When I have tried to root it I can't because I can not get to the menu to setup the wifi it won't let me get away from the screen saver my mom ordered one of these off ebay for like $40
Figured it out
If it is on an older version you can just drop the official firmware on your nook let it update and it worked like a charm
https://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/
how to disable DEMO mode on Nook simple touch
couchlife said:
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
Click to expand...
Click to collapse
a lot of time passed since other guys had a problem of demo mode on nook. i got my nook (simple touch) as secondhand, unfortunately locked to demo mode.
below is step-by-step how to switch it back to 'normal' mode >>>>>>
--- turn your Nook ON
--- go to Settings - Screen - on Screen window press-and-hold top-right button AND same time keep tapping the "Screen" caption (on a top of display)
--- Demo Mode will pop up on your display
--- undo 'Toggle the demo mode'
--- now to activate "normal" mode switch off-and-on your Nook !
that's It :good:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
+1 intrested to this. I have a lg g watch r.
In Cinema Mode i have Touch2Wake disabled but watch dont show anything and does not vibrate. It becomes really useless if it does not vibrate In Cinema Mode.
mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
I am also searching for this:good:
I've been looking everywhere for a solution to this. I hasn't even considered it as an issue, but just a couple of days is enough to make me realise this is a requirement. I can't believe it didn't come up in development! Aside from your own accidental touches, there's also the issue of inquisitive fingers from children touching that nice shiny screen... Tapping the side button to wake the screen would be perfect (whilst retaining the monochrome screen and notifications).
Cinema mode is really dumb. Just very poorly thought out. There has got to be a way to disable touch to wake. Or even enable vibrating notifications in cinema mode.
Yes there is a way
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
adb root
adb push /system/usr/idc/sec_touchscreen.idc <choose where you want to have the file in your pc>
Click to expand...
Click to collapse
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
# Copyright 2014 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Input Device Calibration File for the Dory touch screen.
#
device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.wake = 1
Click to expand...
Click to collapse
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
adb pull <where you have the file> /system/usr/idc/
Click to expand...
Click to collapse
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
adb pull <where you have the copy> /system/usr/idc/
Click to expand...
Click to collapse
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
dataonlycod said:
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
Click to expand...
Click to collapse
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
-RioT- said:
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
Click to expand...
Click to collapse
Yep you can use it to wake up the device. But as I say, make a backup because this happen with my alpha of the gear 2 neo, so probably this is not going to work with other devices. Just in case xD
Works for me on LG G Watch R
The file name is different "synaptics_rmi4_i2c.idc"
Same edit, copied to sdcard and moved in recovery to /system/usr/idc/ as mentioned above.
I have swipe menu still available and I can swipe down for the quick toggles.
Button is used to wake (and I use screen always on)
Going to be interesting how this performs in the shower and in general. Thanks to the suggestion posted.
Any update on this after using it for a while? Looking to apply this to my LG G watch R running the Urbane port.
Ok well i tried it any ways and i still have the problem when my arms are crossed my arm starts doing things on my watch...
Starting from version 1.6 this app supports wake on touch changing - https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings (here is apk - View attachment AdvancedSettings-v1.6-11.apk)
I downloaded the advanced settings app tried the disable touch wake... it doesn't wake but you can still scroll notifications and long press to change the face.
Any chance of completely turning off the touch screen while in sleep...
..
castructuraleng said:
I tried the Advanced Settings app on my LG Watch Urbane 2nd Edition with Android 6.0.1, which is not rooted. It has an option for "Touch to wake screen" that I tried to set to "off"; however, when I go back to look at it, it is always set to "on". Do I need to root to have this stay, or is the app just not compatible with 6.0.1?
Update... just answered my own question. It appears you need to be rooted to do this.
Click to expand...
Click to collapse
Yep, it works on Marshmallow 6.0.1 when Rooted. Just tested it on my Huawei Watch.
..
I installed "Showear". You can set a simple touch pattern to unlock the watch. Crossing your arms will no longer trigger any action on your watch (except making the screen on).
..
..
Hi m8. I've done this on my LG urbane and works just fine ty a lot... but i modified a little your steps...
1) My lg urbane is rooted
2) I went to the ADB folder in my PC (using windows explorer) then using shift+right click i select "open command window here"
3) in this command window i did:
adb reboot bootloader
fastboot flash recovery (starts twrp)
in the TWRP:
Go to "Mount"
tick the "system" box
In the command window :
adb pull /system/usr/idc/synaptics_rmi4_i2c.idc (Dont need to select the folder, will appear in the ADB folder used to open the command window)***
*** When i tried to write the destination folder have not worked so i strongly advise not to fill this part, the command in the beginning is PULL not PUSH to take from the device and the file to be taken from the device had a different name as someone have stated before ***
4) In the notepad i did
I opened the file with the notepad and edit "touch.wake = 1" to "touch.wake = 0" (I did not delete this part just change the value)
5) in the command window:
adb pull <where you have the file> /system/usr/idc/
6) Reset my phone and works great!
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
pappschlumpf said:
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
Click to expand...
Click to collapse
No problem! This is a tweak that I cant live without! And, congratulations for the amazing job. The ROM is perfect to me, Im using as my daily driver. The only 2 problens that I found, is this one and the low volume in Calls. Thanks to provide this ROM, I really appreciated.
Great! Is working fine...
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
hjfisch said:
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
Click to expand...
Click to collapse
As I said
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Blackphantom said:
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Click to expand...
Click to collapse
Will work. Just change the value to 1, save and exit. But, every time that you reboot the device, u will need make the process again.
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
Dont know. Could you try and post the result?
Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
rootgremlin said:
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
Click to expand...
Click to collapse
Yeah that makes sense. I tried it and realized that it was set back to zero every time i restarted so i figured it would be something like that. Luckily DT2W works now in the build so we don't have to do that anymore.
Thanks for the explanation though. Really appreciated.
Hey there
i followed your steps but i cant seem to find the 12-0038 folder after i2c. Any thoughts?
If you're using Lineage just install the DragonXiaKernel. Double Tap To Wake is working fine.
Tiago A said:
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
Click to expand...
Click to collapse
I installed "lineage-14.1-20170415-UNOFFICIAL-X3". I only get path till sys/bus/i2c/
There is no 12-0038/ folder. Can you help me out on this? I need it badly.
same here, no 12-0038
running smooth with 14.1-20170725-NIGHTLY-hammerhead though
Same for me on 14.1 LG g4 can't t find the file
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Vipxpert said:
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Click to expand...
Click to collapse
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
gavin19 said:
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
Click to expand...
Click to collapse
RR oreo as u said !
Hello XDA community,
Im a noobie when it comes to rooting, thats why i need help...
I deleted some files that i want to recover on my Samsung S7 Edge 2-3 years ago, this device has Android 7.0. (Never updated)
There is a lot of apps such as Disk Digger that offer you to recover every single file but the device must be rooted to access 100% on the internal memory.
Right now my Samsung S7 Edge is not rooted but i need to root to recover this files, so my question is, there is anyway of rooting without factory reset, or there is anyway of doing a fully backup of the internal memory of my device without touching the partitions so then i can try recovering my files later with this apps?
I hope someone can help me...
Regards
It's pretty disappointing that nobody ever responded to this considering how big is a community it is and how popular the S7 Edge was. I know this is pretty old and hopefully you were able to resolve this before this message but I'm going to respond to this just so you don't feel like your question wasn't acknowledged at all. I have an S7 Edge through Verizon which uses the Snapdragon processor. And I will find a link to post for you that although the method says it's discontinued I rooted my phone through this method and it works fine. The only reason that you would have to wipe your phone is if you're changing firmware as far as I know. I've rooted my phones and did not have to wipe them. I kept all the data and everything.
Before I lift this you are also asking about an application that you could use to back up your phone and that would be Samsung smart switch. It has a companion app for the desktop and it sinks to the phone and it'll make a backup of your data.
Now on to the root method all props and praise goes to the people that worked to give this to the people I'm not good at doing all this **** and I'm not meaning to step on any toes I'm just trying to help you since nobody did for two ****ing years.
To root
1. Download PrinceComsys Odin
Odin.Prince.Comsy.zip
drive.google.com
2. Download the engboot.
Engboot Download
Nougat_S7_Edge_EngBoot.tar.md5
drive.google.com
3 make sure you have adb and fastboot installed on your computer (goggle them)
4. Root file
Download the file below.
Nougat_S7_Root_2_82_All_Carriers_V2.zip | by jrkruse for Galaxy S7 Edge
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
BELOW IS THE ROOT AND MOD FOR THE PHONE!!!!!
Follow this method to root:
1. Shut off the phone and boot into download mode (volume down, home, and power). Use Odin And Flash Nougat_S7_Edge_EngBoot.tar.md5 In AP Slot
2. When the phone reboots, unlock developer options by going into the phone settings scroll down to 'about phone' find the build number and tap on it repeatedly after several times it will unlock Developer Options then back out once and in your settings you should have a new option on the very bottom called developer options go into that and enable USB debugging and Disable Verify Apps Over USB.
Plug the phone into the computer and make sure you have adb and fastboot installed to this location
C:\Users\YOUR PROFILE\AppData\Local\Android\Sdk\platform-tools
go to that folder and inside it hold shift and right click then click on 'open command window here'
then in command prompt type
adb devices
then hit enter.
The computer should automaticly detect and run adb
3. Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.zip and hold shift and right click then click on 'open command window here'
In the command window type root.bat then press enter from your PC.
4. This will install root when done phone will reboot
5. The process wipes dalvik cache so it will take a few minutes to reboot
6. If having problems getting Grant SuperSU dialog to come up you can delete the SuperSU app and root will be granted instantly to all root request
Give phone a few min to settle open developer options set animation scales .05 and others to .05
Give phone a few min to settle open developer options set animation scales .05 and others to .05
ODIN FAILED TO WRITE ERROR
Did you get this Failed To Write Message in Odin?
----------------------------
Odin Error Message:
<ID:0/003> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
SOLUTIONS
Did you:
? Open Odin as Administrator?
? Try the Prince Comsy version?
? Enable Developer Settings?
-Open Settings > About Phone > Tap Build Number 7 Times
? Enable OEM Unlock?
-Go Back to Settings > Tap Developer Options > Tap OEM Unlock
? Enable USB Debugging?
-Tap Developer Options > Tap USB Debugging
NOTHING WORKS
Did you try every single thing but nothing works?
Well, did you right click "Odin" each time you go to open it and then click "open as administrator"?
Sometimes you have to try several different versions of Odin.
But I have found that Odin3 v3.12.7 was the one that would work when the others had not.
I always would forget to also open Odin as Administrator.
It's a pain in the neck to have to remember to open as admin every time.
But you usually have to do it.
Did you check that ADB had started? Maybe that might be the reason it won't work?
But I doubt it! But you just never know and I am just trying to help you get it flashed.
It's a very quick flash and you can see that the PDA load was very quick as well.
But as far as the errors, you just have to keep trying...
Which I mean, you sometimes have to open, close, reopen Odin when it doesn't work.
Sometimes that helps, sometimes it doesn't.
It's all about the right Odin version at the time
making sure the cord is good
Opening Odin as Admin
And keep trying again after restarting your phone by holding the download mode button sequence again.
============
Congratulations! You are ROOTED but you're not done
Follow these instructions next
On your phone, open the SuperSU app (installed during the root process) and tap on Settings. Half-way down under Security, tap on "Enable su during boot".
This option will ensure that startup scripts that are installed during this process get to do their job correctly.
Download the fix or fix+debloat script flashable ZIP package appropriate for your model of phone and copy this file to your device:
S7_VOLTE_ICON_FIX_ALL_VARIANTS or S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0) (any Samsung Galaxy S7 or S7 Edge)
turn off auto update of time and date in your phone settings, then set your year to 2013,
Launch FlashFire app on the phone and click the (+) button in the lower right to add a step. Select a 'Flash ZIP or OTA' flash step.
Locate the flashable ZIP package and select it. For options, check on 'Mount /system read/write' and leave the rest of the options unchecked.
Tweaks to Root
Debloat and fix several issues with the phone (CPU lag issues, poor battery performance, phone becoming too hot, Wi-Fi not saving passwords, hotspot/tethering not working,
VoLTE icon appearing, searching for service issues, MMS not working, unauthorized security nag notification, etc.):
Full notes on what this flashable update does:
Adds a rotate button to the native gallery app
.
Adds a shortcut call button in the call log next to each logged call.
Adjusts several CPU tunables, which fixes phone lag and battery life issues.
Disables "No SIM" popup when no SIM card is present.
Disables roaming data by default.
Disables secure storage support, which fixes Wi-Fi passwords not saving issue.
Disables Verizon provisioning for Wi-Fi tethering/hotspot (will still use your data plan, of course).
Enables ADB to run as root by default.
Enables CPU idling/sleeping, which fixes phone heat issues.
Enables mock GPS locations.
Enables native call recording feature in the dialer.
Enables native Wi-Fi calling feature in the dialer.
Enables RIL power saving features.
Enables scheduled messages in the native messaging app.
Enables the camera during calls.
Enables unlimited contact merging.
Enables using the new 3GPP2 Profile ID (Verizon exclusive).
Fixes various 'searching for service' and other cellular network connectivity issues (SMS/MMS not working, calls not working, etc.)
Knox apps, drivers, and data are removed (fix+debloat version).
Prefers LTE network.
Raises the contact name length limit to 1,280 characters.
Raises the maximum SMS recipient limit from 10 to 90.
Remove nagging 'unauthorized actions' security notification (fix+debloat version).
Removes VoLTE icon.
after you flash your stuff change the date back. and you're good.
I know this all seems like a lot and it seems very confusing but it's pretty easy if you just follow the directions this will not wipe your data. Please do research, read through the forms and just tried to get as much knowledge as you can before you go about doing this it's an easy process but it's better to go in with more knowledge, I hope this helps. If you have to reinstall the firmware make sure that you install CSC home so you don't lose your data