Unprovisioned tethering on rooted Nougat? - AT&T Samsung Galaxy S7 Edge Questions & Answers

So, I ran into a slight problem on my rooted S7 edge. I'm still on the AT&T firmware, and tethering will not work. Unmodified, it tries to verify that I can tether (which is obnoxious), and then fails with a server error. So, I tried disabling the packages and altering build.prop, but now neither even attempts to start. Hitting the enable switches do nothing.
I have set net.tethering.noprovision to true and also did ran the "settings put global tether_dun_required 0" command from a root ADB shell.
Anyone get their rooted AT&T S7E to tether?
EDIT: Ok, it looks like I forgot to set tethering_provision in the firewall. That fixed it for now, but I would really like my phone to stop asking permission to do a basic function.

I got a hack that works. You have to root and use root Explorer to copy and paste and change permissions. Let me find the file
Sent from my SAMSUNG-SM-G935A using Tapatalk
http://cloud.tapatalk.com/s/58ca04071cd81/TetheringProvision.apk

jshamlet said:
So, I ran into a slight problem on my rooted S7 edge. I'm still on the AT&T firmware, and tethering will not work. Unmodified, it tries to verify that I can tether (which is obnoxious), and then fails with a server error. So, I tried disabling the packages and altering build.prop, but now neither even attempts to start. Hitting the enable switches do nothing.
I have set net.tethering.noprovision to true and also did ran the "settings put global tether_dun_required 0" command from a root ADB shell.
Anyone get their rooted AT&T S7E to tether?
EDIT: Ok, it looks like I forgot to set tethering_provision in the firewall. That fixed it for now, but I would really like my phone to stop asking permission to do a basic function.
Click to expand...
Click to collapse
vikes4life said:
I got a hack that works. You have to root and use root Explorer to copy and paste and change permissions. Let me find the file
Sent from my SAMSUNG-SM-G935A using Tapatalk
http://cloud.tapatalk.com/s/58ca04071cd81/TetheringProvision.apk
Click to expand...
Click to collapse
Could you guys give a little more detail?
 @vikes4life do I need to do anything besides replacing TetheringProvision.apk with the one provided and set the correct permissions?
 @jshamlet what exactly do you mean by setting tethering_provision in the firewall?
Thanks!

1) Find the /system/priv-app/TetheringProvision folder in a root capable file manager.
2) Make a backup copy (move somewhere else) of the current TetheringProvision.apk. Note, don't leave two APK files in the folder, move it elsewhere or change the .apk to something else.
3) Copy the new APK file to this folder.
4) Change the permissions on the new APK to 644 ( RW, R, R ).
5) Profit, and thank vikes4life.

jshamlet said:
1) Find the /system/priv-app/TetheringProvision folder in a root capable file manager.
2) Make a backup copy (move somewhere else) of the current TetheringProvision.apk. Note, don't leave two APK files in the folder, move it elsewhere or change the .apk to something else.
3) Copy the new APK file to this folder.
4) Change the permissions on the new APK to 644 ( RW, R, R ).
5) Profit, and thank vikes4life.
Click to expand...
Click to collapse
Thanks @jshamlet & @vikes4life !!
Solid workaround, worked flawlessly. Not a big fan of daily driving the ENG kernel and only needed root to do the aforementioned. You know of a good way to flash the back the stock kernel without wiping system? I extracted the boot.img from the stock firmware, created a TAR, and tried flashing in official & hacked Odin. Bootloops until I flash back the ENG kernel. No worries if not, I'll live.
Thanks again for everything!

HumanCaviar said:
Thanks @jshamlet & @vikes4life !!
Solid workaround, worked flawlessly. Not a big fan of daily driving the ENG kernel and only needed root to do the aforementioned. You know of a good way to flash the back the stock kernel without wiping system? I extracted the boot.img from the stock firmware, created a TAR, and tried flashing in official & hacked Odin. Bootloops until I flash back the ENG kernel. No worries if not, I'll live.
Thanks again for everything!
Click to expand...
Click to collapse
I know some changes can be left in place when unrooting, but I'm pretty sure anything that would cause dm-verity to fail on a stock kernel will trip the Knox flag if that is a concern to you.

I'm interested in this but curious. What's your battery life with root?

t12icky0 said:
I'm interested in this but curious. What's your battery life with root?
Click to expand...
Click to collapse
That is an interesting question, because it varies. I'm generally seeing a drain of about 2-3% per hour if it's just sitting on my desk. Screen on time is hard to judge, but it feels acceptable. I haven't dropped below 85% unless I'm playing a game or browsing the web pretty heavily. However, it can vary a bit, and I haven't figured out why yet. At times, it can drop 5-6% per hour just sitting. Of course, that was during the first few days when it seemed like everything was updating or configuring.
Then, at other times, the phone will surprise me. I played a few hours of Lara Croft Go, and it was still sitting around 75%. Go figure?
All in all, as the ROM settles with root, and I've found optimum settings for the kernel governor and tweaks, I'm finding the lag has dropped tremendously and battery life has plateaued. I would say it is still on the "good" side - far better than my old phone. It's not quite "stock", but it's close enough that I don't notice it most of the time.

jshamlet said:
That is an interesting question, because it varies. I'm generally seeing a drain of about 2-3% per hour if it's just sitting on my desk. Screen on time is hard to judge, but it feels acceptable. I haven't dropped below 85% unless I'm playing a game or browsing the web pretty heavily. However, it can vary a bit, and I haven't figured out why yet. At times, it can drop 5-6% per hour just sitting. Of course, that was during the first few days when it seemed like everything was updating or configuring.
Then, at other times, the phone will surprise me. I played a few hours of Lara Croft Go, and it was still sitting around 75%. Go figure?
All in all, as the ROM settles with root, and I've found optimum settings for the kernel governor and tweaks, I'm finding the lag has dropped tremendously and battery life has plateaued. I would say it is still on the "good" side - far better than my old phone. It's not quite "stock", but it's close enough that I don't notice it most of the time.
Click to expand...
Click to collapse
Yeah, my concern was mostly over battery. What kernel tweak tools & settings are you using if you don't mind me asking?

Right now I'm running conservative on the fast cores and performance on the slow cores. I also have Lspeed set to performance as well. Between that and disabling a crap ton of unnecessary AT&T and Samsung bloat, it feels like it's almost back to stock.

vikes4life said:
I got a hack that works. You have to root and use root Explorer to copy and paste and change permissions. Let me find the file
Sent from my SAMSUNG-SM-G935A using Tapatalk
http://cloud.tapatalk.com/s/58ca04071cd81/TetheringProvision.apk
Click to expand...
Click to collapse
Is this for nougat or marshmallow?
---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------
HumanCaviar said:
Thanks @jshamlet & @vikes4life !!
Solid workaround, worked flawlessly. Not a big fan of daily driving the ENG kernel and only needed root to do the aforementioned. You know of a good way to flash the back the stock kernel without wiping system? I extracted the boot.img from the stock firmware, created a TAR, and tried flashing in official & hacked Odin. Bootloops until I flash back the ENG kernel. No worries if not, I'll live.
Thanks again for everything!
Click to expand...
Click to collapse
I'm just working through this, but it appears that you can root, install this apk, then unroot according to the rooting method posted here: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
I haven't done it yet, just got the phone yesterday and I'm researching how to get tethering enabled. But my plan would be to use that root method, install this tether apk hack, then unroot using the home_csc method described in the root post for returning to stock without it wiping data (since the eng kernel sounds too buggy for daily driver). Still researching but this looks like it will work?
---------- Post added at 02:20 PM ---------- Previous post was at 01:50 PM ----------
robbieas said:
Is this for nougat or marshmallow?
---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------
I'm just working through this, but it appears that you can root, install this apk, then unroot according to the rooting method posted here: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
I haven't done it yet, just got the phone yesterday and I'm researching how to get tethering enabled. But my plan would be to use that root method, install this tether apk hack, then unroot using the home_csc method described in the root post for returning to stock without it wiping data (since the eng kernel sounds too buggy for daily driver). Still researching but this looks like it will work?
Click to expand...
Click to collapse
Crap. that home_csc file isn't for the 930A.... can't seem to find the N firmware that has it anywhere either.

robbieas said:
Is this for nougat or marshmallow?
---------- Post added at 01:50 PM ---------- Previous post was at 01:45 PM ----------
I'm just working through this, but it appears that you can root, install this apk, then unroot according to the rooting method posted here: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
I haven't done it yet, just got the phone yesterday and I'm researching how to get tethering enabled. But my plan would be to use that root method, install this tether apk hack, then unroot using the home_csc method described in the root post for returning to stock without it wiping data (since the eng kernel sounds too buggy for daily driver). Still researching but this looks like it will work?
---------- Post added at 02:20 PM ---------- Previous post was at 01:50 PM ----------
Crap. that home_csc file isn't for the 930A.... can't seem to find the N firmware that has it anywhere either.
Click to expand...
Click to collapse
It's basically the same as the other csc but without the pit file packed inside. You could essentially do the same thing by modifying our existing csc tar.md5 by removing the pit thus bypassing the re-partitioning. I do think, however, that you'll still end up with a conflict between the TetherProvision in ODIN and with the modified one on the phone. I would assume that the ODIN TetherProvision would win out in that situation reverting the change, but I havnt tried it yet.
Not keen on reflashing right now though to test, I'm having a decent experience at the moment.

Of course, I wasn't thinking that through, I'm sure you're right. These Odin files are new to me. Thanks for the reply.
I've got an in dash Nexus 7 and no tethering is killing me. S7 is the only phone they are giving out at work now and I broke my Nexus 6.... Which of course made all this a breeze with it's glorious unlocked bootloader.

I would be interested to know if flashing the root file, then the file, the going back to stock would work also. I hate not having hotspot with my phone.

HumanCaviar said:
It's basically the same as the other csc but without the pit file packed inside. You could essentially do the same thing by modifying our existing csc tar.md5 by removing the pit thus bypassing the re-partitioning. I do think, however, that you'll still end up with a conflict between the TetherProvision in ODIN and with the modified one on the phone. I would assume that the ODIN TetherProvision would win out in that situation reverting the change, but I havnt tried it yet.
Not keen on reflashing right now though to test, I'm having a decent experience at the moment.
Click to expand...
Click to collapse
Did you ever do this process?

I didn't. I'm positive the TetherProvision would wind up getting overwritten so I didn't bother. I've been on Nexus devices for years, so I wasn't thinking through the Odin flashing process and how those files get moved around. On Nexus you can whatever you want!
It seems like in the last week there's been pretty significant progress on the root however. User Quickvic30 created a modified root.bat that sure sounds like it runs like a champ. As I type this my phone is rebooting and is hopefully rooted, and hopefully it runs smoothly as everyone in the thread seems to indicate.
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502

jshamlet said:
1) Find the /system/priv-app/TetheringProvision folder in a root capable file manager.
2) Make a backup copy (move somewhere else) of the current TetheringProvision.apk. Note, don't leave two APK files in the folder, move it elsewhere or change the .apk to something else.
3) Copy the new APK file to this folder.
4) Change the permissions on the new APK to 644 ( RW, R, R ).
5) Profit, and thank vikes4life.
Click to expand...
Click to collapse
Anyone else here on AT&T using this hack and getting terrible tethering service?
For example, if I attempt a speed test from the connected tablet, it takes 60 seconds to even start. I'll get ~5mbps up/down, with a reasonable ping, but it takes forever to start. Same thing using TuneIn, I start a stream and it takes 60 seconds to start playing, but then plays fine. Pandora times out half the time, but if I keep trying it will finally connect then play okay. On my old Nexus 6 everything just worked like a normal internet connection... TuneIn for example started a stream in 2-3 seconds.
I didn't do any build.prop edits, just the hack as described. Any thoughts or suggestions would be greatly appreciated.

robbieas said:
Anyone else here on AT&T using this hack and getting terrible tethering service?
For example, if I attempt a speed test from the connected tablet, it takes 60 seconds to even start. I'll get ~5mbps up/down, with a reasonable ping, but it takes forever to start. Same thing using TuneIn, I start a stream and it takes 60 seconds to start playing, but then plays fine. Pandora times out half the time, but if I keep trying it will finally connect then play okay. On my old Nexus 6 everything just worked like a normal internet connection... TuneIn for example started a stream in 2-3 seconds.
I didn't do any build.prop edits, just the hack as described. Any thoughts or suggestions would be greatly appreciated.
Click to expand...
Click to collapse
For what's it's worth, my root felt a little rough, so I applied the build.prop edits in this thread.... and for whatever reason, my tethering problems were solved. It just works like it's supposed to. I'm on day 1 so maybe it's dumb luck, but these seemed to help my tethering and some of the root lag issues I was seeing.
https://forum.xda-developers.com/showpost.php?p=71739423&postcount=727

robbieas said:
For what's it's worth, my root felt a little rough, so I applied the build.prop edits in this thread.... and for whatever reason, my tethering problems were solved. It just works like it's supposed to. I'm on day 1 so maybe it's dumb luck, but these seemed to help my tethering and some of the root lag issues I was seeing.
https://forum.xda-developers.com/showpost.php?p=71739423&postcount=727
Click to expand...
Click to collapse
Must have been dumb luck, my tethering is still a mess.

Related

VZW update fix

if your have issues with the update not finishing 100% this will work
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
download the zip using heimdall flash like normal
factoryfs-factoryfs.rfs
zimage-zimage
param.lfs-param.lfs
cache-cache.rfs
recovery-zimage
ignore the rest of the files
then before first boot wipe data and cache reboot
manually use update.zip or just let it download itself
install update and your done
you can verify by going to "about device" build number will be SCH-I800.EC02
use superoneclick for root z4mod not working keep getting f/c's
it seems like anybody who used z4mod to root or flashed recovery "back to stock" is having problems a 100% fix is just download the files from my post and flash like normal then use superoneclick for root
***for it to work you must download the recovery files from my post***
the files in my post are created using a temp. root so the files are a pure clone of unrooted rom 100% stock that is why you have to use superoneclick to root I tried everything and have done this to 6 tabs with no errors
EC02 stock ota update.zip download
http://www.4shared.com/file/qIHEta11/update.html
Thanks, I noticed you posted this on the other thread too. I have never used Heimdall so I was REALLY trying to avoid this but I guess I will have to take the plunge and figure it out.......
this works
I have tried every which way and this way has worked every time for me
Finally worked
works 100% just followed the steps and no problems finally updated!!!!!
It works, 100% Thank you so much for this
This does work, 100%, but please note that it DOES NOT WIPE THE DEVICE. It will boot up with all your stuff. This is not neccessarily practical, but it will probably be fine. If you have any root dependent mods, such as set cpu or lcd density, they wont work and it may operate funny/slow until you reroot and set them back up.
stock restore files download
http://dl.dropbox.com/u/21215221/Verizon-GTab-Stock.zip
or
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
Download Mode (Volume down and power)
Download Heimdall from Here:
http://www.glassechidna.com.au/products/heimdall/
Also just below version 1.1.0 is Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses.
Launch download mode on your tab that is already connected to your PC.
unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device or might say it other ways
Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end leaving Tab plugged in and in download mode
Unzip the stock files.
the zImage goes in both the Kernel AND Recovery slot.
The factoryfs.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs make sure you use param.ifs not param.rfs
and the cache.rfs goes in the cache slot.
ignore the rest of the files in the zip and just use these
After you have the files in place click start to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
After this runs you will more then likely have to Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do not hold power too long, just long enough to turn it on, then continue holding up volume till you see recovery. WIPE DATA AND CACHE. Tab should boot.
then let update download install it and you can use superoneclick if you want root back
This worked!
Thank you lexriley! That seemed to work. I forgot to wipe data/cache before i applied the update.zip, it still worked anyway. I should probably have wiped the data/cache.
Thank you !!!!!! Great Work!
Thanks so much. I rooted using Z4 and the update failed. I used your instructions and got up and running again! You saved my Tab!
I'm happy its working for everyone like it worked for me
100% fully working!!!!!!!
thank you lexriley your guide is easy to follow and do your the man!!!!!!
This should be a sticky!!!!
Sent from my ADR6300 using Tapatalk
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
oldmacnut said:
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
Click to expand...
Click to collapse
Well let me tell you what I have noitced with the upgrade
1) Stock browser speed is faster, but I dont use the stock so that wasnt much help
2)There is now a item in the top of settings for you to activate your device through verizon (like you would using *228 or whatever it is from your phone)
3)The wifi searching thing. I often forget to turn wifi off so when I drive it drains battery searching, the drain is significantly less now.
4) BLUETOOTH HID SUPPORT! Sorry for the caps but I have been wanting this one for quite some time now. First thing I did was try my MX5500 at home and it paired up and worked perfectly.
5)Hyperlinks in emails issue. Constantly many hyperlinks were cut off and I wasnt able to click them, this has now been resolved.
If none of these things are appealing to you then by all means you have no need to upgrade. But I found that most of this was a welcomed change. The tab seems faster, but I believe that is just due to the fact that I do not have LCD density changing the density, which I find slows down many things on the tab.
lexriley said:
I'm happy its working for everyone like it worked for me
Click to expand...
Click to collapse
At first it didn't work for me. I got "failed to access device. Error: -12". But that was my fault. I had forgotten to load the zagdig drivers for Heimdall. So I did that following the instructions in this thread and tried again. First try, I simply got a "fail", second try worked like a charm. When finished the Tab rebooted on its own.
As soon as it rebooted, I got the message that an update was waiting to be installed (EC02). Since I had already wiped the cashe (twice) on earlier attempts, I just went ahead and let the update install. Worked like a charm and now I've got EC02 update.
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Now to begin the task of re-rooting, installing ADW, and putting my Tab back into shape the way I had it.
BIG THANKS goes out to lexriley!! (And by all means, make this thread a sticky.)
Robin
Excellent work! This worked perfectly.
Got it, installed the newest Keis for drivers.
i hate to be that guy but is it possible to get odin files too? i can never get heimdall to work but odin works just fine
Robin M said:
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Click to expand...
Click to collapse
So if I just restore the vcast stuff then I should be able to update without doing all the recovery stuff? I just renamed them all with a .bak at the end instead of deleting just incase I needed them again so I still have them all.
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
shiltz said:
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
Click to expand...
Click to collapse
You're welcome. ...Isn't it great when you answer your own questions? I find myself doing that more frequently now, as I learn more about Android and my Tab - mostly from this forum.
PS... Now that you've successfully updated, take a look at the recovery.log file in your /cashe/log folder. I was amazed at the number and the variety of files this upgrade patched.

[ROOT] Kindle Fire HD 7" fix for 7.3.1

If you are having issues rooting your kindle with guides online the reason behind it is that you are using an outdated version of "Root_with_Restore_by_Bin4ry_v*" Currently most of the guides all have you downloading and using Root_with_Restore_by_Bin4ry_v17. You want to use a version of Root_with_Restore_by_Bin4ry_v version 21 or above. I did mine with version 21 and my gf's with version 28. I just wanted to make sure that it would work with a latest i could find.
Root_with_Restore_by_Bin4ry_v21 can be found with the link provided below. You can also google other Root_with_Restore_by_Bin4ry_v and try them out until you get your kindle rooted.
apparently i can't link outside
d -h.st /dm9
just copy it and paste it then backspace on the spaces to make it a usable url
Re Routing kindle that has updated
Ferrous said:
If you are having issues rooting your kindle with guides online the reason behind it is that you are using an outdated version of "Root_with_Restore_by_Bin4ry_v*" Currently most of the guides all have you downloading and using Root_with_Restore_by_Bin4ry_v17. You want to use a version of Root_with_Restore_by_Bin4ry_v version 21 or above. I did mine with version 21 and my gf's with version 28. I just wanted to make sure that it would work with a latest i could find.
Root_with_Restore_by_Bin4ry_v21 can be found with the link provided below. You can also google other Root_with_Restore_by_Bin4ry_v and try them out until you get your kindle rooted.
apparently i can't link outside
d -h.st /dm9
just copy it and paste it then backspace on the spaces to make it a usable url
Click to expand...
Click to collapse
hi, thanks for the above.
as a total noob to this, i sppent most of thursday researching how to do this, then carried it out eventually successfully too, only to wanke up on friday morning to see my device had updated to 7.3.1.
ive now downloaded binary v28, root with restore - how do i use this version? i used this guide -
androidforums com/kindle-fire-hd-all-things-root/669366-idiots-guide-rooting-kindle-fire-hd-7-7-2-3-a.html
to carry out my rooting, so i now need to know how to do it using the v28 version, and if there is any differences to the process linked above.
also, i downloaded droidwall, and thought i had blocked the updating app, but it obviously hadnt. then i noticed at the top it said "firewall disabled" how do i enable this?
and finally, how do i get to change the launcher / user interface/ how can i change this to a one similar to the galaxy tab or something else like this?
yes, i am a noob, and all help is welcome guys. many thanks in advance.
jaktlad said:
hi, thanks for the above.
as a total noob to this, i sppent most of thursday researching how to do this, then carried it out eventually successfully too, only to wanke up on friday morning to see my device had updated to 7.3.1.
ive now downloaded binary v28, root with restore - how do i use this version? i used this guide -
androidforums com/kindle-fire-hd-all-things-root/669366-idiots-guide-rooting-kindle-fire-hd-7-7-2-3-a.html
to carry out my rooting, so i now need to know how to do it using the v28 version, and if there is any differences to the process linked above.
also, i downloaded droidwall, and thought i had blocked the updating app, but it obviously hadnt. then i noticed at the top it said "firewall disabled" how do i enable this?
and finally, how do i get to change the launcher / user interface/ how can i change this to a one similar to the galaxy tab or something else like this?
yes, i am a noob, and all help is welcome guys. many thanks in advance.
Click to expand...
Click to collapse
Yeah the only difference is that you are using an upgraded version of program they have so instead of using v17 use newer version. I think once you install the new google play store all you have to do is find GO Launcher in the market place.
Ferrous said:
Yeah the only difference is that you are using an upgraded version of program they have so instead of using v17 use newer version. I think once you install the new google play store all you have to do is find GO Launcher in the market place.
Click to expand...
Click to collapse
thanks for that. how do i install it and launch it once ive rerooted and downlaoded go launcher?
also, if this works, can anyone advise on the correct way to disable updates - as said above, i thought i had done it, but obviously not lol.
jaktlad said:
thanks for that. how do i install it and launch it once ive rerooted and downlaoded go launcher?
also, if this works, can anyone advise on the correct way to disable updates - as said above, i thought i had done it, but obviously not lol.
Click to expand...
Click to collapse
Download DroidWall from the googplaystore, that app disables updates. I don't know much about golauncher. If you follow the guide and have googleplaystore then you should be able to download everything.
I have confirmed that Bin4ry (I used v26) method works fine for both 7.3.0 and the new 7.3.1 update that is just rolling out. Here are some instructions that hopefully is clear for everyone (link). Obviously the main credit goes to the root method.
Was having trouble getting root again after my kindle went to 7.3.1. This worked for me. Thanks for the help!
Problems with attempting to root on 7.3.1
Hello-
I have used the "Root with Restore by Bin4ry_v29" to no avail and I am extremely perplexed as to whats going wrong. I have followed all the instructions outlined and during the process I do see multiple instances within the application saying "permissions denied" yet it continues as if everything is ok. Well, once it says everything is finished and I have rebooted the device multiple times, its EXTREMELY sluggish and borderline unresponsive. It also doesn't have root access as Superuser isn't on the device. So I am asking for any advice/guidance anyone can provide that maybe knows whats up or has had this happen and knows what the problem is.
Please help!
ps: Not new to rooting either as I have rooted all the android phones I have ever had with no problems but I know the Kindle is a different beast.
Thanks!
I'm on my phone so I can't post the link but if you search you'll find it, but I just rooted a new KFHD four days ago by using prokenexus how to root for noon guide. I followed it from start to finish and was completely successful. Took a total of about 45 minutes. He has two ways to root in his thread, automated and manual. I always like doing manual so I can see everything that is going on. But it worked like a charm. So might want to give that a look.
from my Viped out one x
Used this method on my kindle and it worked flawlessly without issue
7.4.1!
Coderedpl said:
Used this method on my kindle and it worked flawlessly without issue
Click to expand...
Click to collapse
So did I - and it worked happily for three seconds until it rebooted again and I found I had 7.4.1 on the Kindle.
I can't find anything else on the web atm on 7.4.1 so either I've been hacked or I'm one of the first to get it.
I just did mine a second ago. Second time Ive done this, but I cant rememeber what i did last time to remedy the issue. Once I did it, it fixed the lag. hmmm... someone please help me remember....
DroidJay123 said:
Hello-
I have used the "Root with Restore by Bin4ry_v29" to no avail and I am extremely perplexed as to whats going wrong. I have followed all the instructions outlined and during the process I do see multiple instances within the application saying "permissions denied" yet it continues as if everything is ok. Well, once it says everything is finished and I have rebooted the device multiple times, its EXTREMELY sluggish and borderline unresponsive. It also doesn't have root access as Superuser isn't on the device. So I am asking for any advice/guidance anyone can provide that maybe knows whats up or has had this happen and knows what the problem is.
Please help!
ps: Not new to rooting either as I have rooted all the android phones I have ever had with no problems but I know the Kindle is a different beast.
Thanks!
Click to expand...
Click to collapse
---------- Post added at 03:06 AM ---------- Previous post was at 02:51 AM ----------
Found this article and worked.
Super slow after boot solved!
Ok even though this guide stated that if you are on version 7.2.3, you don't need to run rootqemu. Bat method, that was not true in my case. After running through the runme phase in cmnd prompt, choosing normal root, and letting the process finish and reboot, my device was ridiculously slow, and not rooted might I add. Here's the trick though, immediately after that process finishes, you need to run the Rootqemu method also. But when you try to run Rootqemu.bat by right clicking and running as administrator, it doesn't recognize the device. What I had to do was left click on ONLY the folder that contained the Rootqemu files, and while only that folder is highlighted, you hold down the shift key and right click on the folder. Then you are going to click on "run command prompt here". Once the command prompt opens, you are going to type Rootqemu.bat and press enter. Then you can press 1 to root, let the program run through its few stages, and after it reboots several times and finishes it's process, voila no more lag, and you should be finally rooted. Also after that process, download a program called Kindlefree. It's an absolutely amazing, and simple way to install all the essential Google apps "aka" Gapps to your rooted Kindle fire hd. I hope this helps everyone like it did me!
scooby092477 said:
I just did mine a second ago. Second time Ive done this, but I cant rememeber what i did last time to remedy the issue. Once I did it, it fixed the lag. hmmm... someone please help me remember....
Click to expand...
Click to collapse
Funny thing
cthonus said:
So did I - and it worked happily for three seconds until it rebooted again and I found I had 7.4.1 on the Kindle.
I can't find anything else on the web atm on 7.4.1 so either I've been hacked or I'm one of the first to get it.
Click to expand...
Click to collapse
I Have i too but i accidentally cut the kindle off in the prosses so i kinda have it. all i got out of it was adding the batt % in status bar. also amazon says it is a minor update so there are no release notes.
For future referencef any further visitors
Hello fellow users and visitors. I've been following this site for a while now, yes I'm considered a "noob" here but I have my experiences well beyond the level of a "noob." This is my first post, and I indeed have a KF HD 7. Since there is so much confusion as far as CLEAR NEWBIES INSTRUCTIONS, I've decided to give everyone the guide I used to root my Kindle, which was derived from a guide here at XDA itself. You can find it here at
androidcowboy (DOT) com /2013/04/root-kindle-fire-hd-7-3-0-firmware/
This DOES indeed work for 7.3.1 as mine was, it took me two tries. But heed my warning, rooting this beauty MAY cause some issues as it has to mine such as randomly shutting off, battery showing up as 0% on some occasions when it is turned on, and sometimes refusing to charge more frequently than it used to. Those issues eventually happen without root, some people have these problems the first week of having a fresh new KFHD7, and I have friends with the same Kindle, rooted, and theirs do not present same issue, so I guess some do some don't.
Good luck and happy rooting. Now you can revive Google Play!
Another confirmation for 7.3.1. I followed Android Cowboy's procedures for both rooting and installing Google Play. Very easy. Thanks Cowboy!
Sent from my KFTT using Tapatalk HD
If you have issues rooting, please go to my thread in my signature. I addressed the issue of rooting on 7.3.1, and have written quick explanation for rooting with Bin4ry's method. The guide goes on to help you flash a custom ROM, should you so desire to get rid of that nasty Amazon OS interface.

[Q] Viper4Android and Bricking

Figured I would be a lurker forever, but I guess my hand was forced.
Well, I was annoyed by the sound on my Note 3 and some applications with no equalizer, so I tried a couple out with very limited success. Lots of people suggested Viper4Android as working better than the random ones you could find on Google Play. So I tried going to what looks to be the official thread. The installation seemed simple, aside from modifying a build.prop file(still simple but possible to mess up).
Long story short, I restarted the phone when the application told me to and was greeted with a permanent white 'Samsung Note 3' text-logo. I never get to see the Samsung or Sprint carrier video-logo. Holding down power merely reboots the phone after a few seconds. Seemingly the Power/VolDn/Home combo still works for download mode... but at the moment I don't know what to do with that access.
I would try posting on the official thread, but being a lurker, I don't have the required 10 posts.
Searching the Viper4Android thread, I only see happy Note3 people... and no one at all having the extremely bad luck that I have had. I don't even see any particular warnings about this being possible. The only thing I can think of is the driver that it installs and the build.prop file. If something seriously went wrong there with the audio, it could possibly prevent the videos from playing and the boot process wouldn't continue.
I'm at a temporary loss and thought I would post somewhere to get my options rolling as I think. Primarily, given that Viper4Android was the last thing that I did before this happened... is there something different I should be looking for rather than a generic method of undoing a soft-brick?
jljtgr said:
Figured I would be a lurker forever, but I guess my hand was forced.
Well, I was annoyed by the sound on my Note 3 and some applications with no equalizer, so I tried a couple out with very limited success. Lots of people suggested Viper4Android as working better than the random ones you could find on Google Play. So I tried going to what looks to be the official thread. The installation seemed simple, aside from modifying a build.prop file(still simple but possible to mess up).
Long story short, I restarted the phone when the application told me to and was greeted with a permanent white 'Samsung Note 3' text-logo. I never get to see the Samsung or Sprint carrier video-logo. Holding down power merely reboots the phone after a few seconds. Seemingly the Power/VolDn/Home combo still works for download mode... but at the moment I don't know what to do with that access.
I would try posting on the official thread, but being a lurker, I don't have the required 10 posts.
Searching the Viper4Android thread, I only see happy Note3 people... and no one at all having the extremely bad luck that I have had. I don't even see any particular warnings about this being possible. The only thing I can think of is the driver that it installs and the build.prop file. If something seriously went wrong there with the audio, it could possibly prevent the videos from playing and the boot process wouldn't continue.
I'm at a temporary loss and thought I would post somewhere to get my options rolling as I think. Primarily, given that Viper4Android was the last thing that I did before this happened... is there something different I should be looking for rather than a generic method of undoing a soft-brick?
Click to expand...
Click to collapse
looks like a factory reset ,volume up, power home, factory reset
Did you choose the correct driver to install?
jaythenut said:
looks like a factory reset ,volume up, power home, factory reset
Click to expand...
Click to collapse
Even losing absolutely everything doesn't really bother me. Only hard-bricking does.
munnarg said:
Did you choose the correct driver to install?
Click to expand...
Click to collapse
I had very few choices. I used the ViPER4Android_4.x_2313.apk since I have Android 4.3; a no brainer. Once installed and open, the changelog popped up, SuperSU asked to authorize, then V4A asked to install the driver. By this point I had already done the build.prop modification so I clicked Yes. It told me that it would automatically detect my CPU type which matches what the official thread says. It then prompted me to select the driver profile(?) with the options of Battery Saving, High Quality Mode and Super Audio Quality. Since the thread didn't give any suggestions, I went with the middle-ground of High Quality Mode. After the selection was made, it told me to reboot. I closed the application, held the Power button and selected Restart(then OK). And was stuck there.
Looking at some other various threads, it seems that improper modification of build.prop can indeed cause the type of bricking that I am seeing. I'll have to try V4A without that one step since it looks like it was added in after the fact... and in some cases optional if the lines to modify don't exist.
Don't think you had to mess with the build.prop at all. I sure didn't do it.
SwiftKey Flowed from my tiny Galaxy Note 3
munnarg said:
Don't think you had to mess with the build.prop at all. I sure didn't do it.
SwiftKey Flowed from my tiny Galaxy Note 3
Click to expand...
Click to collapse
I would have not done so if it had not asked me to.
http://forum.xda-developers.com/showpost.php?p=39156718&postcount=2
1. ROOT your device.
2. Install busybox if doesn’t come with root.
3. Modify build.prop (Thanks [email protected])
a. Open up /system/build.prop in text editor using any file explorer with root access.
b. Change the line (If you can’t find these lines, skip this step.)
Ipa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
Click to expand...
Click to collapse
As a side note, factory resetting doesn't seem to affect this. Doing so says that it's wiping out /data and /cache. Where as what I modified was in /system. Some of my other reading proposed that re-rooting will undo those sorts of changes. Looks like I'll have to go down that research path.
I guess it should be unsurprising to me, but I never encounter only small problems.
Factory resetting in recovery mode and re-rooting in download mode, while successful, do not allow the device to boot past the first screen.
jljtgr said:
I guess it should be unsurprising to me, but I never encounter only small problems.
Factory resetting in recovery mode and re-rooting in download mode, while successful, do not allow the device to boot past the first screen.
Click to expand...
Click to collapse
if its still not working download your firmware from www.sammobile.com and flash with odin
jaythenut said:
if its still not working download your firmware from ----sammobile---- and flash with odin
Click to expand...
Click to collapse
I'm willing to try... but will that really replace more than what the CF-Auto-Root image has? Nevermind... just looked at the file size. That certainly changes a lot more than the CF-Auto-Root image. It'll take me a while to get it off of their free file hosting, probably.
Well, I have a blank but working device now... and that's what really matters.
Reading around... if I were to make a wager that I can't collect on, I would say that I ran into a bug with ES File Explorer. I read someone else bricking their device in the same way editing the same file. ES-FE makes a backup by renaming the file, then fails to save the new file. I swear I saw it do this once before on a less critical file and I was annoyed to have to do the cp through terminal. I didn't hit refresh to make sure it did it correctly... I just assumed when it said it saved, it saved.
Thanks for the responses. Back to lurking!
Just for info, V4A is running flawlessly on my N3. All I did was install the APK, open it, install driver as prompted and restart!

Root Success SM-G530AZ 5.1.1!!!

All credit goes to captaingowa and his post (http://forum.xda-developers.com/grand-prime/general/att-samsung-galaxy-prime-sm-g530a-links-t3283066) for the AT&T version.
I'm just providing stock kernel for 5.1.1 SM-G530AZ
1. Root SM-G530AZ 5.1.1 with kingroot 4.6.2 or higer (kingroot.net)
2. DON'T Reboot
3. Download and install Flashify on play store or APK
4. Flash stock kernel with flashify (http://www.mediafire.com/download/2fk19cadccq0xd7/boot.img)
5. Reboot.
6. Replace kinguser with supersu (optional) (http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip)
7. Enjoy
wally86 said:
All credit goes to captaingowa and his post (http://forum.xda-developers.com/grand-prime/general/att-samsung-galaxy-prime-sm-g530a-links-t3283066) for the AT&T version.
I'm just providing stock kernel for 5.1.1 SM-G530AZ
1. Root SM-G530AZ 5.1.1 with kingroot 4.6.2 or higer (kingroot.net)
2. DON'T Reboot
3. Download and install Flashify on play store or APK
4. Flash stock kernel with flashify (http://www.mediafire.com/download/2fk19cadccq0xd7/boot.img)
5. Reboot.
6. Replace kinguser with supersu (optional) (http://www.mediafire.com/download/x1efi7ev6nf3mvd/Replace_Kinguser_with_SuperSU-v2.0.zip)
7. Enjoy
Click to expand...
Click to collapse
Awesome, thank you so much. Going to try it right now, but I'm betting it will work. Thank you again for putting this all together.
Nice, think I flashed the wrong boot.img from that thread, there are two different img's, one as tar and the other as img. We actually need the img in the tar, which you have posted above. Thanks for posting this up.
guys thank you very much! i will try this and report results to the forum!
HELP!!
kenboyles72 said:
Nice, think I flashed the wrong boot.img from that thread, there are two different img's, one as tar and the other as img. We actually need the img in the tar, which you have posted above. Thanks for posting this up.
Click to expand...
Click to collapse
I tried the same procedure and my wifi will still not work!!!
thecomputerdude87 said:
I tried the same procedure and my wifi will still not work!!!
Click to expand...
Click to collapse
There are a couple things you can do here.
1. Try re-downloading the boot.img and reflashing with flashify
2. Try flashing the boot.img with Odin3
3. Restoring your phone with Kies http://forum.xda-developers.com/showpost.php?p=61977268&postcount=14
I rooted my phone and had to restore with kies three times before i got my wifi working. This is only if I switched to SuperSU, if you stay with kingroot, you wont have the wifi issue.
Help help help!
I did this and now my wifi won't turn on!! AT ALL
so the root metod its safe??? now there is another metod done from between Android using terminal emulator to switch from kingroot to chains fire super su! you have to be fully rooted to be able to work on terminal emulator.
but the root metod for sm g530az its safe?
flashing the stock kernel, do you click boot image or recovery image?
---------- Post added at 06:57 AM ---------- Previous post was at 06:18 AM ----------
OK, I got the wifi to turn back on by using the link above again.
I still cant get the wifi tether app to work, tho.
any suggestions?
well..happy to report that root on criket grand prime sm-g530az its a big...SUCCESS!!!
Im rooted on lollipop 5.1.1.
i do have cwm recovery but i need to flash it and see how it goes.for those with the Wi-Fi problem flash that boot image again.i have two one didn't work so i flash that second and Wi-Fi was working again.
Samsung bootlogo reports as "custom" so guaranty its gone
but I don't care abt that,im rooted thnx guys for sharing all that informacion!
I got the root to work with kingroot, but didn't do the 'optional' SU part, but now I want to.
Can anyone tell me what the step is with that zip file? do I download it directly to the phone? use Flashify? if I'm using flashify, do I flash it as a "boot image", a "recovery image" or a "zip file" ?
LOL talk to me like I'm five, please! I'm a noob at this. I'm smart at some things but this is a little overwhelming. LOL I'm a critical care nurse. I can fix a PERSON, but phones are a little more complicated :laugh:
---------- Post added at 03:39 AM ---------- Previous post was at 03:10 AM ----------
Oh OOH OOOHH!!!
Did that final step and the wifi tethering app WORKS!!!
WHOO HOOOOO!!!!
Thanks, wally, you are AWESOME!!
Root wifi teather
What wifi teather apk do yuo use?
hello try to this post :
http://forum.xda-developers.com/gra...t/cm-13-android-6-0-1-grand-prime-sm-t3291892
this post help you to install custom rom on grand prime sm-g530h and other . . .
adj5064 said:
well..happy to report that root on criket grand prime sm-g530az its a big...SUCCESS!!!
Im rooted on lollipop 5.1.1.
i do have cwm recovery but i need to flash it and see how it goes.for those with the Wi-Fi problem flash that boot image again.i have two one didn't work so i flash that second and Wi-Fi was working again.
Samsung bootlogo reports as "custom" so guaranty its gone
but I don't care abt that,im rooted thnx guys for sharing all that informacion!
Click to expand...
Click to collapse
Wait you have cwm compiled for our sm-g530az? That would be useful
Okay thanks a ton for the info, finally got my wifi back after flashing the correct boot.img, not sure where it was on the original forum never saw it but luckily others that had same issue posted it.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
Going to try to blow the dust off my builduntu box and see if I cant get us a recovery going for the cricket version, I usually like twrp but now that cwm has touch as well could go that route....is their a custom recovery built for the other variants at all yet....if so then forking those repos would be a good starting point, should only take minor edits to get it working proper for us.
toxinburn said:
Okay thanks a ton for the info, finally got my wifi back after flashing the correct boot.img, not sure where it was on the original forum never saw it but luckily others that had same issue posted it.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
Going to try to blow the dust off my builduntu box and see if I cant get us a recovery going for the cricket version, I usually like twrp but now that cwm has touch as well could go that route....is their a custom recovery built for the other variants at all yet....if so then forking those repos would be a good starting point, should only take minor edits to get it working proper for us.
Click to expand...
Click to collapse
I already built twrp for this phone, but as you found out, the damn security checks prevent the use of it. This is my device tree, can't remember if I pushed my last commits and I dont have what I had, due to a hdd failure.
https://github.com/LoneStar-/android_device_samsung_grandprimeltetu
kenboyles72 said:
I already built twrp for this phone, but as you found out, the damn security checks prevent the use of it. This is my device tree, can't remember if I pushed my last commits and I dont have what I had, due to a hdd failure.
https://github.com/LoneStar-/android_device_samsung_grandprimeltetu
Click to expand...
Click to collapse
So can you get a custom recovery working for this device? I have tried many ways but they all ended with my flashing stock img. twrp or cwm would be fine by me. Or another alternative is to find out how to disable the security check. Anyway please find a way to get custom recovery for 5.1.1 SM-G530AZ. Thanks
Illyakulinych said:
So can you get a custom recovery working for this device? I have tried many ways but they all ended with my flashing stock img. twrp or cwm would be fine by me. Or another alternative is to find out how to disable the security check. Anyway please find a way to get custom recovery for 5.1.1 SM-G530AZ. Thanks
Click to expand...
Click to collapse
Okay I think we should put our heads together to try and kick this lockdown to the curb, things I have tried so far...I found that on some other variants they have the option within their settings/developer settings menu to enable oem unlock which is what we are needing to be able to flash custom recovery, I have replaced my settings.jar and settings.odex with theirs with no luck the option is still not showing up for me, but I think it may be the right direction into getting that to show up, the question i am now posing is this. Are the checks in place simply reading carrier info to allow/disallow this option? If so would we possibly be able to change the build.prop or other settings with our newly found root access to trick the device into giving this option? If that is the case then we need to get as much info from the stock devices that have that option as possible and maybe try swapping certain files out with theirs to get the option back and/or editing certain files on our own device to get it to show up. It only takes one g530AZ with unlocked bootloader to share the boot.img i would think. I had thought about flashing another boot.img or aboot.img from another variant but I am pretty concerned about brickage although I think it could be recoverable as long as one can get back into download mode. Has anyone zeroed out the download partition to see if a fastboot is hidden behind it?
toxinburn said:
Okay I think we should put our heads together to try and kick this lockdown to the curb, things I have tried so far...I found that on some other variants they have the option within their settings/developer settings menu to enable oem unlock which is what we are needing to be able to flash custom recovery, I have replaced my settings.jar and settings.odex with theirs with no luck the option is still not showing up for me, but I think it may be the right direction into getting that to show up, the question i am now posing is this. Are the checks in place simply reading carrier info to allow/disallow this option? If so would we possibly be able to change the build.prop or other settings with our newly found root access to trick the device into giving this option? If that is the case then we need to get as much info from the stock devices that have that option as possible and maybe try swapping certain files out with theirs to get the option back and/or editing certain files on our own device to get it to show up. It only takes one g530AZ with unlocked bootloader to share the boot.img i would think. I had thought about flashing another boot.img or aboot.img from another variant but I am pretty concerned about brickage although I think it could be recoverable as long as one can get back into download mode. Has anyone zeroed out the download partition to see if a fastboot is hidden behind it?
Click to expand...
Click to collapse
Any progress?
Illyakulinych said:
Any progress?
Click to expand...
Click to collapse
Only thing I have done Is zeroed out the sec partition which caused non problem however it did no good either....also playing around with the databases and able to change some options just not the one in wanting yet...I work a ton son my freetime is limited but if anyone that has a different variant that could share their system apps primarily their settings all and databases and xml associated with it is really like to look through them.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk

AT&T Samsung Galaxy S7 G930A Root Install Instructions?

If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?
Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.
I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar

Categories

Resources