yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
If you're sure you have the proper firmware and an AT&T phone........then check that you're using odin 3.12 or 3.12.3 and not the Princecomsy odin. Next, get the 'Phone Info' app from playstore and see exactly which bootloader version you have on your phone and if you're stuck in a bootloop go to recovery, pwr button + home button + volume up at same time when booting. In recovery I think it shows bootloader version and you can also hit return stock or something like that and it will get you out of bootloop but you will still be on engboot kernel. Once you know bootloader version then that's really what you need to match and if you did have correct firmware from the start then try without the BL file and see what happens.

Why return to stock in the first place? The lag and such goes away with a few reboots and in maybe a day long if that. Anyway hopefully something above will help. Keep us posted.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] codala2012@gmail.com:
+1

I'm seriously considering trying it, but I use my phone too much to have something happen to it.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] twizt3d:
Haven't tried myself either. I wish there was an easier way to root, and with how the leaked nougut builds flash I wouldn't want to have to put the effort into configuring fixes for root over and over.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] codala2012@gmail.com:
If one were to revert back to pk1, root. Then update to nougat with an app like root keeper, would that even work? Pk1 is rootable, right? I thought I read that somewhere
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] twizt3d:
I believe since the nougat ota wipes system it would not retain root. But again I haven't tried.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] codala2012@gmail.com:
tried everything, used the search function in multiple different ways, forums, search engines, everything!!!! im on apk1, but i try to root and get the "sha56 is invalid" error, all setting are right, what can i be doing wrong, tried with princecomsy and 3.12.3, nothing, adb is installed and everything, usb debugging, did i say everything? please help!

---------- Post added at 02:01 AM ---------- Previous post was at 01:36 AM ----------

wow, im an idiot, i wasnt running odin as admin............ :mad:
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jonathanjr321:
I want to make some clarification regarding the links to download the files, first those who decide to work for free for the community, is by own decision !!!

If they are going to share the work that is not easy and we all know it well, share it from your heart or keep it at home.

If they want to collect or get donations is fine is their right, many do not have or do not want to work for free, we also understand.

Whatever the case we have to show respect to the community, I have many complaints of the files, people to whom I personally and recommended to this website.

*XDA is a website of respect, many people here work hard and are respected by the trajectory as developments, here there is no time to play games or lies, if they are going to share files have to be real (free or for money) but Real!! not **** or zip files full of viruses, games or stupid things that damage the reputation of developments and websites, not stupid things to damage the customers' electronics, either xda or any other website, anyone!!!

No development of respect or respect his own self do that stupid stuff !!!!!.

If there are people who want to play does games, we have to eliminate them !!

Once again if we are going to share something have to be clean and real or then it is time to clean the potato sack !!!!.

If someone does not like my english you can start learning spanish!!!!!

yo quiero hace unas aclaracion con respecto a los links para bajar los files, primero los que deciden trabajar gratis para la comunidad, es por decision propia!!!

si van a compartir el trabajo que no es facil ya todos lo savemos bien, lo comparten desde el corazon o lo guardan en su casa.

si quieren cobrar o obtener donaciones is fine es su derecho muchos no tienen o no quieren trabajar gratis, tambien lo entendemos.

cualquiera que sea el caso tenemos que mostrar respeto a la comunidad, tengo muchas quejas de los files, personas a las cuales yo personalmente e recomendado a este website.

XDA es un sitio web de respeto, muchos personas aqui trabajan duro y son respetadas por la trayectoria como developments, aqui no hay tiempo para andar con juegos ni mentiras, si van a poner files que sean reales (gratis o por dinero) pero que sean de verdad, no una mierda, ni zip files llenos de virus,juegos o cosas estupidas que danan la reputacion de los developments y los websites, no cosas estupidas para danar los electronicos de los clientes, sea xda o cualquier otro website, sea la persona que sea!!!

ningun development de respeto anda con esas estupideses!!!!!.

si hay personas que quieren hacer dano a los demas hay que eliminarlos!!

una vez mas si vamos a compartir que sea todo limpio y de verdad o entonces es tiempo de limpiar el saco de papa.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] Yamaha169:
Your phone browser....

Try downloading with chrome instead (if your trying to download to your device)

I have that issue alot... :-/
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
wtf??? Ok...
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
Wow!!!!! Wtf

I have ran root for a week and all is well. Deb loathe one thing at a time. Find it,Google it, read about it, then freeze it.wait to see if anything adverse happens, then remove. Support here was awesome! Battery is all day. Kept WiFi calling. All I can say for anyone else is to READ READ and read some more. Many thanks to all
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
I spoke too soon. Woke up on 7th Day to find bootloop and cannot cycle. Tried adb reboot and lost complete communication with device. Got a null error once and now device is bricked

Any ideas
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
Stock Odin sees phone. Added stock files and Odin so far is hung on 《id:0/003》setup connection
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
After waiting Odin fails. Phone bricked?
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
Sounds more like usb configuration not set correct or usb debugging is completely off. If you cant get into phone then go into phone recovery, vol up + home + pwr on, and do factory reset. That should get you back into phone. You'll still be on engboot kernel but no root. Then make sure you have usb debugging ON and usb config to mtp or ptp. Once you get into phone you could rerun root.bat and v15 fix and leave at that. The only thing I can think of that would have failed originally is something was frozen or deleted that the system needed to operate correctly. So this time around try just leave everything stock and turn off updates in playstore and only freeze security log agent. and turn off firmware updates too.......just cant remember where right now and I'm driving, so this is hard.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
Dude I can wait!

---------- Post added at 06:21 PM ---------- Previous post was at 05:54 PM ----------

Ok so I had tried home power up several times during this and it did nothing. I figured I was going to have to wait until power died. I am not sure how close I got but I tried home power down and got I to download mode and was able to flash stock.(brain fart when trying Odin earlier....... need to be in download mode). So phone is up and on stock. Whew. After reload os/reboot it was At 15% battery. I am slow charging it to be nice to the rapidly discharged battery. Then start over.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
OK obviously I missed something. Playstore updates were off

Security log agent was frozen in tb.

Att software update was frozen in tb.

I thought I had covered my bases.

What did I miss?

There must be something that updates on Sunday night because from what I read it seems that this happened to the other people on sun nights too.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
Do you have security policy updates set to auto update? It's in settings/ lock screen and security / Other security settings/security policy updates.......make sure set to off. That's the other setting I couldn't remember yesterday in the car. I don't know if it matters but it could be what updates every sunday and hoses things up???
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] CreeperPVP:
So i tried downloading the Engineering Kernel again and the site always times out after i click Download.. Anyone have a new link?
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jonathanjr321:
volume down and power bottom for few seconds have to work for u

volume down and power bottom for few seconds have to work for u then download mode which odin u have?

---------- Post added at 08:18 PM ---------- Previous post was at 08:03 PM ----------

go here https://xdaforums.com/verizon-galax...l-xposed-unroot-t3411039/page307#post71087356
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
I got both odins, all 4 stock files, eng kernel, v15 and a backup phone. I acquired everything I could think I would need before I tried this. I got back up and reflashed root and waiting til sun night/Monday morning to see if I crash again. not sure if I had security policy updates disabled before but it is disabled now.

I have been wondering...... when you flash new stock firmware is there anyway to prevent the next ota "nougat" from upgrading your device. I know its not here yet but I don't want to lose the capability to root if go back to stock for any reason. like the last crash I had I flashed stock first to check to see if phone was in working order, adb permission with computer and to reset developer options etc.... I know the minute it has any connectivity that's one of the first things it does is update the os
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
If 4g is off and you're not on an internet network then the update can't happen. Besides that, you should be given the option to update......meaning, update is not an automatic thing....at least on at&t it isn't automatic.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
When I bought this phone i threw sim in and turned on not thinking and I had checked to see what firmware. And while I was doing that it started downloading update. It did not ask. I also didn't try to stop it because I wanted to update before root. But not any more. Wish me luck on getting past Monday morning bootloader! :eek:

---------- Post added at 02:40 AM ---------- Previous post was at 02:40 AM ----------

Bootloop
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
So it looks like something is updating every sunday morning 12am that hoses your phone......very strange. Do you have any apps in place that would have logged the activity that hosed things up. I suppose if you can't get into your phone after tbe incident and then have to factory reset or Odin stock then finding a log file could be difficult. Maybe look for a logging app that will write file to external microsd. Next then, if you're still willing to try another test.....you could turn off your data and wifi, basically like airplane mode on steroids next Saturday and Sunday around the time you think the update happens and see if that fixes. Also might be able to log something at that time with the right app.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
It was Monday morning. And I have only dealt with it once. This coming Monday will be my 2nd Monday on root. This has happened to others in an identical situation. What happened last week is on Monday morning the phone was "gltchy" I would slide thru a screen and it was hanging up, so I say to myself" needs to be rebooted" and that's when bootloop happens. This scenario is in this post and another.... I think. I have read so much it becomes a bit of a blur. The logging app might work. The device was not completely dead. I don't know how limited it was because I went right to boot. Will see tomorrow morning and if it happens again will look into logging
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] qwewqa:
The "adb logcat" command on a computer may help.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
That's right....thanks.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
Monday morning update......

No issues, no bootloop. I expected it so left phone at partial charge. Woke up and tested a few things and did 2 reboots. Seems to be working fine today.:good:
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
I have seen this mean little dude a few times. Anybody know what this is?
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
So you are saying that by turning off the Security Policy Updates in Settings that fixed the boot loop problem that occurred mondays on a weekly basis for your Tmo phone.

Edit: at&t phone.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
It's 930a- att phone - not t-mobile. And it only happened to me once so far, on my first Monday while running root os. So I turned off security updates in settings and also froze some security stuff in titanium backup above and beyond security log agent and att update.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
Did you run the v15 fixes right after you ran root.bat? Just trying to find out if the fixes turned that stuff off or not. I thought it was suppose too but I can't remember. I did the fixes and also made sure everything was turned off or frozen that looked suspect, but it was too long ago to remember what I had to actually do manually or what the fixes took care of.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
Remove sim

Flashed phone to stock.

USB debugging set to on

Registered computer with adb

Flash Odin eng kernel

Flash adb Root.bat

Check USB debugging

WiFi on just long enough to download flashfire,then back off

Flash v.15 fix

Reboot/wipe cashe

WiFi back on just long enough to download titanium backup, then back off.

At this point the first time I froze securitylogagent and att software update. The second time I froze a few more things pertaining to security items. And made sure auto update was off in security settings

Clear cashe and install sim card

Both times I had also froze the bloatware and knox
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
Is that how you did it before the bootloop issue? Or is that how you just did it to solve the bootloop issue?
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
Identical process both times except for the additional items I froze and disabling security updates. not sure if I had disabled the first time but MADE SURE I DID the second time
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
Sounds like it's fixed then. If it makes it another week then for sure.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
Yes I want to see a few weeks for sure before I am out of the woods. Do you have any idea who this mean little dude is associated with?
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] l1me_:
after trying to flash supersu my phone rebooted multiple times and now my phone is stuck booting. please help (im a total noob with rooting)
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
If you haven't figured this out yet try and get into recovery......starting with phone off press home button, volume up button, and power button all at same time, sort of like you did to get into odin download mode but volume up not down. Once in recovery look for return to stock and press that and that should get you back into phone. Upon reboot make sure you get a custom unlocked padlock on one of the screens during boot process. If you do have the unlocked padlock then you have engboot kernel so you can now try too run the root.bat procedure over again and make sure your phone and computer are set up correctly per the op and reread the op to make sure you did everything correctly from the beginning to end.

Alternatively, if things are still not work for you then look for your exactly same firmware with same bootloader version, make sure not Nougat, and you'll have to use that firmware to odin back to stock. Just put the four files you get in the firmware package into same spots in odin, stock odin 3.12. or 3.12.3 not Princecomsy.....Princecomsy odin is for engboot kernel only....and put your phone back in download mode like you did for the engboot kernel and run odin to return to stock.

NOTE: before return to stock backup any personal files you need because everything gets over write I'm pretty sure.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] ragomes7:
Can't Root Samsung SM-G35A

Hi guys, I'm sorry if this is not the right place to post...

I have a S7 Edge from At&t and with a Snapdragon CPU, on 6.0.1, and I have followed several different tutorials to try and root my phone but none seem to work.

I flashed the rooted boot with Odin and installed SuperSU via fastboot by running the root.bat file via prompt command, and after my phone reboots RootChecker says the phone is not rooted even thou it has SuperSU install.

SuperSU always prompts me to try and remove Knox the first time I run it but no matter what I choose it always fails. It also prompts me to update the binaries every time but if I choose to do so by selecting "Normal" mode instead of custom recovery, it always fails to update as well. I've also tried not updating but the root didn't seem to be work.

I've repeated the process several times with a few tweaks, or even downloading files from different sources, or using different tutorials but nothing seems to work.

I noticed most tutorials are over 5 or 6 months old so I'm not sure if my phone is actually rootable as of now. Information and comments are also contradictory, with some people able and others unable to root their phones.

Any help will be greatly appreciated.

Thanks!
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] jruka:
I just did mine. Att 930a firmware 6.0.1. Read this post, the Verizon post that goes into detail about v15 fix and I have a short outline a few posts up with what I did. I recommend gathering all files,both Odins and stock firmware first. I wasn't asked to disable knox or the other stuff. Make sure you register adb permissions before you start too or root.bat won't work.

---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------

I reread your post and when I did root.bat it was from adb command prompt, not Fastboot.

Maybe that's why
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
If you have adb installed correctly or even in the same folder as root files on your computer and usb debugging turned on on your phone then just double click root.bat and sometimes running it twice helps. But as long as you got good connection between phone and computer and all the appropriate files correctly on computer then not much too it, it should work easy.

As far as knox, you shouldn't get any messages about that.....or at least I never did.

The supersu binary will nag to update and you can just turn off updates from playstore apps or go ahead and update the binary just like it wants you to and it should message back it fails, then reboot phone and you should be set after that and no more nags. I can't remember if it actually did update or not but either way you won't get any more su nag screens and your phone will be fine.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] ragomes7:
Thanks for the help. I'm very frustrated with this. I've re-done the whole process again making sure that every single thing was right. Everything went well with flashing and SuperSU installation, but I open RootChecker it says my phone is not properly rooted.

This time when I opened SuperSu it didn't say anything about Know and I ignored the request to update the binary.

Does it have anything to do with the fact that I'm doing the whole process from a virtual machine running Windows 10 on a Mac?

I don't get it...

Is there a specific online tutorial that you can point me to that you know for sure it works?

Thanks again!
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
Does your phone reboot like its suppose to after you root.bat? Otherwise, yes it must be the virtual machine thing that something isn't getting installed properly. You could try running root.bat two times in a row back to back. Otherwise, if that doesn't work, put all the essential files in one directory, that way any path issues with the virtual machine won't come into play, and doubleclick root.bat from their.
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] ragomes7:
Yes, my phone is being rebooted and everything how it's supposed to be I guess.

I ran the process again but kept the DOS window open at this time (it was automatically closing before) without any luck again.... Here's the content:

C:\Users\Ricardo\Desktop\SuperSU-v2.74-2-S7QC>adb wait-for-device

C:\Users\Ricardo\Desktop\SuperSU-v2.74-2-S7QC>adb shell mount -o rw,remount /system

C:\Users\Ricardo\Desktop\SuperSU-v2.74-2-S7QC>adb shell mount -o rw,remount rootfs /

C:\Users\Ricardo\Desktop\SuperSU-v2.74-2-S7QC>adb push SuperSU-v2.74-2.img /data/su.img

1481 KB/s (33554432 bytes in 22.115s)

C:\Users\Ricardo\Desktop\SuperSU-v2.74-2-S7QC>adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh

291 KB/s (4686 bytes in 0.015s)

C:\Users\Ricardo\Desktop\SuperSU-v2.74-2-S7QC>adb install -r SuperSU-v2.74-2.apk

1574 KB/s (6348638 bytes in 3.937s)

pkg: /data/local/tmp/SuperSU-v2.74-2.apk

Success

C:\Users\Ricardo\Desktop\SuperSU-v2.74-2-S7QC>adb shell 0<supersu.cmds

touch /system/xbin/su

chmod 0755 /system/xbin/su

chcon u:object_r:system_file:s0 /system/xbin/su

chmod 0700 /system/etc/launch_daemonsu.sh

chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh

if [ `cat /system/etc/init.sec.boot.sh | grep daemonsu >/dev/null 2>&1; echo $?` -ne 0 ]; then

echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh

fi

sync

reboot

root@hero2qlteatt:/ # touch /system/xbin/su

root@hero2qlteatt:/ # chmod 0755 /system/xbin/su

root@hero2qlteatt:/ # chcon u:object_r:system_file:s0 /system/xbin/su

root@hero2qlteatt:/ #

root@hero2qlteatt:/ # chmod 0700 /system/etc/launch_daemonsu.sh

on u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh <

ec.boot.sh | grep daemonsu >/dev/null 2>&1; echo $?` -ne 0 ]; then <

> echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh

> fi

root@hero2qlteatt:/ #

root@hero2qlteatt:/ # sync

root@hero2qlteatt:/ # reboot

Can you pls advise? Thanks!!
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] saf4xdadev:
Are you sure you're not rooted because it looks like you should be, plus I reread your previous post about getting a message to update the binary. You wouldn't get that message if you weren't rooted.

I suppose you could be partially rooted though, that would mean your initial download of the root package was incomplete or compromised. Try downloading the root package again maybe?? Not to mention, you are downloading the correct supersu package linked in the op......and run it twice back to back ......
[AT&T Samsung Galaxy S7 Guides, News, & Discussion] Blackbrawler:
Been trying to root with G930AZ (cricket verstion) but with no luck. Each time I odin the engboot the phone immedietely goes into a boot loop. Once its in the boot loop not even a factory reset works, I have to go through a whole round about process to get it back to stock.

The firmware should be very similar to AT&T so I'm not sure why it wouldn't work. I've tried twice and haven't been able to get past the engboot. Any ideas?