Root s7 at&t g930a & g935a
- Thread starter princecomsy
- Start date
- Status
I didn't change anything else. Just the govenor. I did reboot to recovery and clear cache, though. As for busy box, I didn't have to install it. I'm using titanium backup just fine.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Sweet! Worked for me. Thanks for the tip
Sent from my SAMSUNG-SM-G935A using XDA-Developers mobile app
Yes, I'll a few pages back I did. The guy who helped was great I'll get the link to fix it.
---------- Post added at 04:02 AM ---------- Previous post was at 04:01 AM ----------
Just wanted to quote you for someone
guess not :\
---------- Post added at 03:08 AM ---------- Previous post was at 03:05 AM ----------
---------- Post added at 03:08 AM ---------- Previous post was at 03:05 AM ----------
So I need to go back to stock then root again ?
Were you rooted and everything already? And then you rebooted and got bootloop?
Sent from my SAMSUNG-SM-G935A using Tapatalk
and if I use this odin will it allow me to change the wifi so it saves?
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
yea, but I changed the wifi property so it could save and restarted and it stopped working
---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------
yea, but I changed the wifi property so it could save and restarted and it stopped working
I'm not 100% sure, but have you already disabled packages before trying this? I'm not sure, but my speculation is that any changes to the system (WiFi fix, xposed install, engboot) needs to be done before any packages are disabled. It seems it has something to do with that. Everyone's problems so far has been packages. If I'm wrong could someone correct me on this.
Sent from my SAMSUNG-SM-G935A using Tapatalk
maybe its because I deleted the security alert thing
---------- Post added at 03:19 AM ---------- Previous post was at 03:17 AM ----------
seems like I gotta factory reset again smh
Sorry I couldn't be more help. I just completely powered mine off and back on to see. Mine booted up and I have the WiFi fix. Maybe someone else could chime in.
Sent from my SAMSUNG-SM-G935A using Tapatalk
You are correct. The problem has been found to be deleting or disabling packages. You want to leave everything enabled and installed until after you finish the entire process. Otherwise you'll end up in a boot loop, stuck on the carrier splash screen, black screen with vibrations, etc.
If it happens, just restore the firmware to stock and start from scratch and you should be fine. Disabling stuff is fine, but only after you've finished rooting/installing xposed/etc. and you need to enable them all again before you update those things or change them in the future.
I feel your pain man. I literally went 5 hours without the phone because no one else had the issue. Then I found his post with the stock Rom.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
62Warning this is engboot, meaning its not made to be used on day to day basis you may run into some issues. Hopefully we can fix them as we go!
Also do not update supersu through playstore untill we are for sure that it wont mess anything up
Notice from @Chainfire:
Quote:
Originally Posted by Chainfire
I'm just going to leave this here...
SuperSU-v2.74-2-S7QC.zip
You will need:
- Engineering boot images
- Patched version of Odin3 (only AT&T models ?)
- Extract files, and run root.bat with adb on the path
This version of SuperSU is not officially supported. I recommend against updating the APK from the Play Store, or otherwise updating the binaries, unless someone knowledgable has tried before you and confirmed it worked.
If it breaks, you get to keep all the pieces.
First of all thanks to @Chainfire for helping achieve su
I take no responsibility for anything that happens to your device, same goes for everyone that helped.
1. Download Modified Odin and Engineering Kernel
Odin:
MOD EDIT: DOWNLOAD LINK REMOVED
This is special Odin to bypass SHA-256 made by Princecosmy
Second file you will need is
Kernel:
G935A (Edge) MOD EDIT: DOWNLOAD LINK REMOVED
G930A (S7) MOD EDIT: DOWNLOAD LINK REMOVED
This is the engboot
2. Flash the kernel to your phone
a. Boot into download mode (Power, Volume Down, and Home button)
b. Put the Kernel file into AP on Odin
c. Flash, and boot phone
3. Download SuperSU made for our phone, and extract into C:\adb\super
(You're going to need to create the "super" folder)
SuperSU: https://download.chainfire.eu/968/Su....74-2-S7QC.zip
4 Open a command prompt in C:\adb
(Shift right-click in the folder, click "Open command window here")
then navigate to the super folder: type "cd super" into the command prompt
5 Enable USB debugging on your phone, and enter the following command into the command prompt
a. "Root.bat"
(This is what the command prompt will display when finished:
6. The program should run, reboot your phone, and you have root!
For the bounty id prefer if you just donate to elsa3id.3agwa@gmail.com PayPal
Makes more of a lasting impact then what i could do with any of it.
Again thank you to everyone who helped!
We made it fam!
If you are successful after rooting and can give better instructions please let me know!9PSA: I've added stock Odin-flashable images to my root/unroot guide for the following carriers: AT&T, Sprint, T-Mobile, and US Cellular (already had Verizon) for both the Samsung Galaxy S7 and Samsung Galaxy S7 Edge. This covers models SM-G930A, SM-G935A, SM-G930P, SM-G935P, SM-G930T, SM-G935T, SM-G930R, SM-G935R, SM-G930V, and SM-G935V. These files are hosted on my unlimited-bandwidth GoDaddy dump server, so enjoy them ad-free.8
Just so everyone has realistic expectations, a root method without the engboot will likely not happen in the "next few days" or any time soon and here is why:
The leaked engineering boot image is a T-Mobile image for G935TUVE2APD7. TMO is known to impose the least amount of restrictions on their ROMs and that is probably why this kernel is working for all carriers (TMO is the hero of the day again!) The way the boot process in Marshmallow works is through a trust chain. What it means is that the bootloader checks the integrity of the boot image (aka kernel) to make sure it is unaltered and properly signed by Samsung. If that fails the phone does not boot and/or your knox flag is tripped. If that passes, the kernel is loaded and the kernel in turn checks the integrity of the system partitions (known as dm-verity). If that fails you get a bootloop.
With an engineering kernel this last step is disabled because engineers keep changing the system files as they develop a release. That is why this engineering boot image allows the injection of SuperSU, and that is why this root method can work. If you flash a user (non-engineering) image, such as the G935U boot image, it immediately detects the changes in the system and bootloops.
So you see, it is a fundamental protection that did not exist in previous Android versions and that is why it is unlikely that a root method on the non-engineering version is accomplished any time soon; you cannot touch the system because the kernel checks it and you cannot touch the kernel because the bootloader checks it. So the only possible options are as follows:
1- The bootloader is unlocked by the carriers so modified kernels can be loaded (not gonna happen). This is how nexus phones are rooted.
2- Another (engineering?) kernel without dm-verification (with better performance) is leaked/released that allows changes to the system, hence root. This is how the present root for S7 has been accomplished.
3- A vulnerability is found in Android system that allows a process to obtain root after the phone boots up. This is much more likely. In fact this is how Xpreia devices such as Z3/Z4/Z5 recently got root. This is also how towelroot worked in Kitkat which didn't have dm-verity activated. The problem in marshmallow is that this kind of root has to be temporary (should disappear after a reboot) and you will have to stay away from changing the /system otherwise the phone barfs upon the next reboot because of dm-verity.
4- A vulnerability is found in the kernel or bootloader code that is exploited to change /system. For that to happen someone has to sit down and dissect the kernel/bootloader code and read and analyze it line by line. I only remember a few times this ever happened during the exciting days of Android (when a Samsung phone didn't look and feel like an iphone). That is how Jellybean got rooted on early Note 3 devices. No one has the time or interest to do that anymore and people at that level of skills already have a very busy life. As valuable as their contribution is, the custodians of this current root method did not do it either. They used method 2 above.
So stay with the unlocked ROM and be happy for now. I posted a small analysis of the situation here: http://xdaforums.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538/post67633470#post67633470 Reasons for rooting after flashing the unlocked ROM are few, if any.7OR
OR, and bare with me here, you could just download this new root i made with the su binary from supersu2.76 and a working performance script. see attachments
literally extract anywhere and double click root.bat
but for anyone who wants to do it manually:
script:Code:#!/system/bin/sh echo 91 >/sys/module/msm_core/parameters/throttling_temp echo 0 >/sys/module/msm_thermal/vdd_restriction/enabled echo N >/sys/module/msm_thermal/parameters/enabled echo interactive >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor echo ondemand >/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor echo 1593600 >/sys/devices/system/cpu/cpufreq/cpufreq_limit/little_max_freq echo 307200 >/sys/devices/system/cpu/cpufreq/cpufreq_limit/little_min_freq echo 2150400 >/sys/devices/system/cpu/cpufreq/cpufreq_limit/big_max_freq echo 307200 >/sys/devices/system/cpu/cpufreq/cpufreq_limit/big_min_freq exit
and to get it to work, make a folder in /data
put it in that folder /data/folderyoumade/<script>
find init.sec.boot.sh in /system/etc
add "/data/folderyoumade/script.sh" to the end of init.sec.boot.sh
then run
chmod 0755 /data/folderyoumade/script.sh
chcon ubject_r:app_data_file:s0:c512,c768 /data/folderyoumade/script.sh
press that thanks button yo7Root for ALL S7 QC models
Here's a complete package for ALL S7 QC models with clear instructions in the ReadMe file.
Also, made a Root.BAT mod which should disable the "Security Notice" and FOTA (test and report back).
Big thanks to PrinceComsy, Br3w3r, and Chainfire for making it all happen.
G930x QC
https://www.androidfilehost.com/user/?w=settings-dev-files&flid=159117
G950x QC
https://www.androidfilehost.com/user/?w=settings-dev-files&flid=181928
Enjoy!!
BillA
New posts
-
Features disabled on fastboot and bootloader. How do I enable them?- Latest: mayberandomparable
-
-
