Develop Bugs

[CWM Script]Galaxy S3 CWM Wifi Bluetooth Tethering Install Script

Enable Wifi & Native Blue Tooth Tethering on Galaxy S3​
*****Disclaimer: This has only been tested on ATT's Version of the Galaxy S 3 if it works on other Galaxys S 3 providers please let us know. But be warned that this may not work on your device if not using an ATT Samsung Galaxy S3.
Special Thaks: I want to thank Clubtech for providing the framework that allows the Tethering in the first place. I only built the script to make it an easier install for everyone. Which was per a request of the community.
Original Post For Clubtech's Enabling Wifi Tethering Tutorial
Requirements:
-Rooted Samsung Galaxy S3 (ATT Version has only been tested)
-Busybox installed on your Phone
- ATT Android STOCK ICS 4.0.4 (To check this go to Settings-->About Device-->Android Version and you'll see version 4.0.4, If you do not have ICS 4.0.4 I do not recommend trying this mod unless you possibly want a bricked phone.)
-Ensure your Build Number IMM76D.I747UCALG1 (To check this goto Settings-->About Device-->Build Number under this section you will see IMM76D.I747UCALG1.)
Steps:
1. Download the Clockwork Mod Install Script Here! (You do not have to register to download the file just click the download button)
2. Copy the script to your Internal SDCard on your Samsung Galaxy S3 Phone (you may have downloaded this file on your phone already just ensure its in the root directory of the Internal SDCard (/mnt/sdcard)
3. Reboot Phone in to Recovery Mode (Remember you will need Clock Work Mod Recovery to Install This)
4. Scroll Down to Install .zip from sdcard and click either home or power button
5. Scroll Down to Install .zip from Internal SDCard and click either the home or power button
6. Scroll Down to the line that starts with Yes blah,blah,blah (This is ensuring that you want to apply this zip. Make sure this is what you truly want to do)
7. Once installation is finished reboot the device
8. Once device is rebooted goto: Setting-->More Settings-->Tethering and Portable Hotspots Now you see that your device has Bluetooth Tethering there as an option and you will now notice if you start the Portable Wifi Hotspot your phone does not tell you to call ATTs 611 to enable this service.
9. Have fun tethering with your Galaxy S3 but remember if you aren't Grandfathered into ATTs Unlimited Data Limit then this means you do have a Data Limit and at the moment the highest they offer I believe is 2GB so any tethering being done on your phone will use your allocated Data Usage in a month and you may incur overage charges at $10.00 for each GB over 2GB. Even if you go 1MB over the 2GB data plan you will be charged the $10.00 so you might as well use the rest of the 1023MB available to you.
If you have any questions on this script please let me know. If you like this and find it usefull give some thumbs up please.

In other words this allows free tethering right? How does this make ATT not notice it?
--Update---
Tested it works as advertised. BTW if you can reply to my Qs.

In a sense yes. This allow you to bypass calling ATT and paying to have the ability to tether. Tethering still uses your allotted Data Usage. So in a way it's free and not free. Well however Clubtech obtained the file to open up the Tethering I do not know. But most likely because removing the old framework-res.apk from the phone and installing the new one is essentially removing ATTs code from the framework-res.apk. They may have a backup somewhere in the system that will allow them to detect tethering this I'm not sure of because I don't have access to this info. But from what I understand is they have to block it immediately because the only way they can tell data is being used on there network by a specific device is through the IMEI number so they can't tell what's behind the device being tethered to because it still shows data is being streamed from the device with IMEI xxxxxxxxxxxxxx
I was thinking that the code that was in the old framework-res.apk allowed the phone to contact ATT somehow to see if this specific IMEI can have tethering enabled. That's only a thought though
DudeWatsThat said:
In other words this allows free tethering right? How does this make ATT not notice it?
--Update---
Tested it works as advertised. BTW if you can reply to my Qs.
Click to expand...
Click to collapse

linuxboxsolution said:
In a sense yes. This allow you to bypass calling ATT and paying to have the ability to tether. Tethering still uses your allotted Data Usage. So in a way it's free and not free.
Click to expand...
Click to collapse
Not much of a problem since I have 3GB for the month, tethering would be a once or twice a month kinda thing for a very short period. Thanks for answering my Qs!

Which framework?
Which framework did you apply the mod to?
This is very important, since this script can only be run for people running a ROM whose framework is identical to the one you applied the mod to. There are already recovery scripts around for applying this mod (with the cell standby power reporting fix, too) for UCALEM (here, in the thread you mentioned in your OP) and UCALG1 (here, in the mods section).

I have the latest stock Rom. Ucalg I think. Can I use this or do I need to wait.
Sent from my SAMSUNG-SGH-I747 using xda premium

mscott998 said:
I have the latest stock Rom. Ucalg I think. Can I use this or do I need to wait.
Click to expand...
Click to collapse
You can use the one in the "mods" section at the bottom of this post:
http://forum.xda-developers.com/showthread.php?p=28672465
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

My phone is updated to the most recent release from ATT 4.0.4 and the framework works fine for me. Sorry about not explaining that in my initial post i'll edit that now.
drothenberger said:
Which framework did you apply the mod to?
This is very important, since this script can only be run for people running a ROM whose framework is identical to the one you applied the mod to. There are already recovery scripts around for applying this mod (with the cell standby power reporting fix, too) for UCALEM (here, in the thread you mentioned in your OP) and UCALG1 (here, in the mods section).
Click to expand...
Click to collapse
mscott998 said:
I have the latest stock Rom. Ucalg I think. Can I use this or do I need to wait.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
drothenberger said:
You can use the one in the "mods" section at the bottom of this post:
http://forum.xda-developers.com/showthread.php?p=28672465
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse

linuxboxsolution said:
My phone is updated to the most recent release from ATT 4.0.4 and the framework works fine for me. Sorry about not explaining that in my initial post i'll edit that now.
Click to expand...
Click to collapse
Thanks for updating the initial post, but there are two "stock AT&T 4.0.4" releases, I believe. I think both UCALEM and UCALG1 are 4.0.4. It might be good specify the Build Number (I747UCALEM or I747UCALG1) instead, just to be sure. I know they updated the framework as part of the LG1 update.

drothenberger said:
Thanks for updating the initial post, but there are two "stock AT&T 4.0.4" releases, I believe. I think both UCALEM and UCALG1 are 4.0.4. It might be good specify the Build Number (I747UCALEM or I747UCALG1) instead, just to be sure. I know they updated the framework as part of the LG1 update.
Click to expand...
Click to collapse
Taking Care of now thanks for the warning.

drothenberger said:
Which framework did you apply the mod to?
This is very important, since this script can only be run for people running a ROM whose framework is identical to the one you applied the mod to. There are already recovery scripts around for applying this mod (with the cell standby power reporting fix, too) for UCALEM (here, in the thread you mentioned in your OP) and UCALG1 (here, in the mods section).
Click to expand...
Click to collapse
I'm liking your suggestion since it includes both MOD's...

As far as I know, AT&T will still detect wireless tethering and will send you a nasty letter or else force you onto a tethering plan. Has anybody found a way to tether without being detected?

If I'm using my phone internationally without this installed, I can turn on hot spot on with no problem right?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

grkmaster said:
If I'm using my phone internationally without this installed, I can turn on hot spot on with no problem right?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Good question. I would install this just to make sure that you can tether wherever you are. That's what I did.

Worked Perfect
Thank You very much. It worked perfect on my AT&T Samsung Galaxy S III SGH-I747. You da man. :victory:

woody1 said:
As far as I know, AT&T will still detect wireless tethering and will send you a nasty letter or else force you onto a tethering plan. Has anybody found a way to tether without being detected?
Click to expand...
Click to collapse
I was tethering on my Atrix and gs2 quite often and I've never received anything from at&t. And that was on a 2Gb data plan.
Sent from my SAMSUNG-SGH-I747 using xda premium

I do have a question concerning busybox. How necessary is that? Should it just be on the device or should its scripts be installed? Or does it even matter?
Edit: got it working. I'm a tidbit weary of altering somethings as I'm still on stock and most root apps I've messed with have their own busybox to go with them.
But I've done a little homework now and got it all squared away.
Sent from my SAMSUNG-SGH-I747 using xda premium

Bad Link
Link is bad

Link working now
gompka said:
Link is bad
Click to expand...
Click to collapse
I just downloaded and it works great. Give it a try again

linuxboxsolution said:
Enable Wifi & Native Blue Tooth Tethering on Galaxy S3​
*****Disclaimer: This has only been tested on ATT's Version of the Galaxy S 3 if it works on other Galaxys S 3 providers please let us know. But be warned that this may not work on your device if not using an ATT Samsung Galaxy S3.
Special Thaks: I want to thank Clubtech for providing the framework that allows the Tethering in the first place. I only built the script to make it an easier install for everyone. Which was per a request of the community.
Original Post For Clubtech's Enabling Wifi Tethering Tutorial
Requirements:
-Rooted Samsung Galaxy S3 (ATT Version has only been tested)
-Busybox installed on your Phone
- ATT Android STOCK ICS 4.0.4 (To check this go to Settings-->About Device-->Android Version and you'll see version 4.0.4, If you do not have ICS 4.0.4 I do not recommend trying this mod unless you possibly want a bricked phone.)
-Ensure your Build Number IMM76D.I747UCALG1 (To check this goto Settings-->About Device-->Build Number under this section you will see IMM76D.I747UCALG1.)
Steps:
1. Download the Clockwork Mod Install Script Here! (You do not have to register to download the file just click the download button)
2. Copy the script to your Internal SDCard on your Samsung Galaxy S3 Phone (you may have downloaded this file on your phone already just ensure its in the root directory of the Internal SDCard (/mnt/sdcard)
3. Reboot Phone in to Recovery Mode (Remember you will need Clock Work Mod Recovery to Install This)
4. Scroll Down to Install .zip from sdcard and click either home or power button
5. Scroll Down to Install .zip from Internal SDCard and click either the home or power button
6. Scroll Down to the line that starts with Yes blah,blah,blah (This is ensuring that you want to apply this zip. Make sure this is what you truly want to do)
7. Once installation is finished reboot the device
8. Once device is rebooted goto: Setting-->More Settings-->Tethering and Portable Hotspots Now you see that your device has Bluetooth Tethering there as an option and you will now notice if you start the Portable Wifi Hotspot your phone does not tell you to call ATTs 611 to enable this service.
9. Have fun tethering with your Galaxy S3 but remember if you aren't Grandfathered into ATTs Unlimited Data Limit then this means you do have a Data Limit and at the moment the highest they offer I believe is 2GB so any tethering being done on your phone will use your allocated Data Usage in a month and you may incur overage charges at $10.00 for each GB over 2GB. Even if you go 1MB over the 2GB data plan you will be charged the $10.00 so you might as well use the rest of the 1023MB available to you.
If you have any questions on this script please let me know. If you like this and find it usefull give some thumbs up please.
Click to expand...
Click to collapse
Tried this on my Sprint S3 and no luck… Got a red "SIGNATURE VERIFICATION FAILED"…
Can u help me understand what this meant and why i got this..?? Anyway to create a zip file to work on the sprint version..?? Willing to PayPal a few $$ to get a solution to rid my error 67 when i try to activate my HotSpot… Reason being is i want to tether over Bluetooth due to its lower power consumption vs WiFi tether which is a battery killer…

If You Used The TMobile Root Method...

2 things... Would anyone mind verifying that once you use the tmobile root, you can no longer boot into recovery?
I tried to factory reset and the recovery will not boot.. Just flashes the android icon every few seconds.
The only way to boot back into the phone is to put it into download mode and re run the tmobile root. It will restart and all will be good.
Now, if it is not just my phone that no longer has a working stock recovery, does anyone know a way to factory reset without a working recovery? I'm guessing it's not possible. Kies does not work with the Sprint Note 4 yet. They updated it today and you can backup the n4 but not factory reset.
Finally, can anyone that used the Galaxy Tools app to get WiFi tethering to work, check to see if your private mode will turn on? I do not have xposed installed and the wifi tether fix in the galaxy tools app seems to be the only thing I can think of that would have broke Private Mode.
Thanks!

Same thing happened to me. I had to get another note 4. There is no way until samsung releases the firmware dump. Sprint even called best buy samsungs care center to see if they have the reflash files and they don't even have it. Odin wipe the data and bring it into sprint so they can give you another one.

Mine boots just fine to the recovery and tecovery works just fine.
I know when i first downloaded thw CF auto for n910t and used the oding in that package my process failed and phone showed to monitors on screen
So i took battery off and download mode again and used a different odin i allready had same version and did the process again and worked and everything is fine.

Androidwarrior said:
Same thing happened to me. I had to get another note 4. There is no way until samsung releases the firmware dump. Sprint even called best buy samsungs care center to see if they have the reflash files and they don't even have it. Odin wipe the data and bring it into sprint so they can give you another one.
Click to expand...
Click to collapse
It is not that big a deal. I can wait for a custom recovery and then go from there. I wanted to factory reset so that I could get private mode back, but I will just use it as is until there is another alternative.
Others are saying that their recoveries are working fine. I guess you and I are the lucky ones
Thanks Androidwarrior.

CJPRICO said:
Mine boots just fine to the recovery and tecovery works just fine.
I know when i first downloaded thw CF auto for n910t and used the oding in that package my process failed and phone showed to monitors on screen
So i took battery off and download mode again and used a different odin i allready had same version and did the process again and worked and everything is fine.
Click to expand...
Click to collapse
What version of Odin did you use? Thanks

I just auto-rooted with N910T, and tried to install Wifi Tether (and TrevE variant) and neither worked. I don't think it started the tether correctly, it was unable to open the log for write, so I don't have a log. I am pretty sure the root was successful (at least partially). I used the root checker app and it said I was good and within the terminal emulator I was able to switch users to root.
I also unsuccessfully tried X Tether. It started up, and showed up on my computer, but I wasn't able to connect to it, and after a while it invariably told me that I needed to upgrade my service.

loonytunes said:
What version of Odin did you use? Thanks
Click to expand...
Click to collapse
3.07 but a normal odin (with all options available) not modified (that it wont let you chose anything but pda) like the one it came with the cf auto
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
hpmaxim said:
I just auto-rooted with N910T, and tried to install Wifi Tether (and TrevE variant) and neither worked. I don't think it started the tether correctly, it was unable to open the log for write, so I don't have a log. I am pretty sure the root was successful (at least partially). I used the root checker app and it said I was good and within the terminal emulator I was able to switch users to root.
I also unsuccessfully tried X Tether. It started up, and showed up on my computer, but I wasn't able to connect to it, and after a while it invariably told me that I needed to upgrade my service.
Click to expand...
Click to collapse
Have you tried Galaxytools from playstore it worked just fine on mine for hotspot

Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).

hpmaxim said:
Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).
Click to expand...
Click to collapse
Even before root. They were doing that system update everytime y restart. But u can freeze samsung DM service if it bother you

hpmaxim said:
Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).
Click to expand...
Click to collapse
Can you check to see if using galaxy tools to enable tether kills your private mode? Since using the galaxy tools app, whenever I click on private mode it fails saying "Private mode failed to start, try again."

loonytunes said:
Can you check to see if using galaxy tools to enable tether kills your private mode? Since using the galaxy tools app, whenever I click on private mode it fails saying "Private mode failed to start, try again."
Click to expand...
Click to collapse
My private mode is gone but id assume its because of xposed but can't be for sure.

sml2004 said:
My private mode is gone but id assume its because of xposed but can't be for sure.
Click to expand...
Click to collapse
I'm not sure how to use it since this is the first time I've heard of it, but it appears to be there. S Health seems to have been killed somewhere along he way there. No more pedometer, UV sensor, SPO2, or heart rate....

Did some googling and found this. http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
I'm going to try it and see if it works on ours.
Update: Uninstalled Xposed and S Health started working again. Going to back up and try the buildprop edit in a bit.

Shadeoblac said:
Did some googling and found this. http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
I'm going to try it and see if it works on ours.
Update: Uninstalled Xposed and S Health started working again. Going to back up and try the buildprop edit in a bit.
Click to expand...
Click to collapse
In Xposed install "Wanam Xposed", open Wanam, go to Security Hacks, and click "Disable Secure Storage" and S Health will work fine.
Sent from my SM-N910P using Tapatalk

hpmaxim said:
I'm not sure how to use it since this is the first time I've heard of it, but it appears to be there. S Health seems to have been killed somewhere along he way there. No more pedometer, UV sensor, SPO2, or heart rate....
Click to expand...
Click to collapse
pdaddy said:
In Xposed install "Wanam Xposed", open Wanam, go to Security Hacks, and click "Disable Secure Storage" and S Health will work fine.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
That sounds way simpler.
Thanks!......
So I tried that and it didn't work.....hmmmm

Shadeoblac said:
That sounds way simpler.
Thanks!......
So I tried that and it didn't work.....hmmmm
Click to expand...
Click to collapse
Yep, me too... Didn't make a difference.

hpmaxim said:
Yep, me too... Didn't make a difference.
Click to expand...
Click to collapse
Going to try that buildprop edit. I'll report back as soon as I'm done.
Update: The buildprop edit from http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
worked. Xposed and S Health working now.

Shadeoblac said:
Going to try that buildprop edit. I'll report back as soon as I'm done.
Update: The buildprop edit from http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
worked. Xposed and S Health working now.
Click to expand...
Click to collapse
I had the same problem with S Health, but there is an xposed module that will fix the issue for you. Just search in the download section of xposed.

hpmaxim said:
Yep, me too... Didn't make a difference.
Click to expand...
Click to collapse
allaidback said:
I had the same problem with S Health, but there is an xposed module that will fix the issue for you. Just search in the download section of xposed.
Click to expand...
Click to collapse
I'll check it out, but it's working fine now. Now if I could only remember how to get the SD back to normal again.

TWRP should be out today so we can root via an actual Sprint method if you guys wanted to wait a little longer. I believe you can even root via CF now.
Sent from my SM-N910P using Tapatalk

Update from PI3 to official Nougat.

I've seen some posts about updates to official Nougat failing, so I decided to upload the update.zip to get to Nougat. I'd like to note that I didn't update using the update.zip method, so let me know if anyone runs into any issues. Hopefully this helps you guys out.
1) Make sure you are on official NON-ROOTED PI3. Also, make sure you enable any disabled packages.
2) Create a folder on your SD card named fota.
3) Download this zip and rename it to update.zip, then put it in the fota folder you created.
4) Turn off the phone and boot into recovery-volume up+home+power at the same time.
5) Wait a minute for the dead android to go away and recovery finally boots, then select update from SD card. Select the update.zip.
Here is the Odin files for PI3 for those that need it. G930VVRU4API3

Testing now
---------- Post added at 11:51 PM ---------- Previous post was at 11:17 PM ----------
Still not working. Didn't get the log though, but there was a mounting error and then I believe I saw something status 7. Not sure what else is wrong.

Are you on PI3?

CVertigo1 said:
Are you on PI3?
Click to expand...
Click to collapse
I am.

Download "Phone Info *Samsung*" from the PlayStore. Open it up and upload a screenshot of the firmware page.

CVertigo1 said:
Download "Phone Info *Samsung*" from the PlayStore. Open it up and upload a screenshot of the firmware page.
Click to expand...
Click to collapse
Thank you for your help.

Everything appears to be in order. Is your SD card encrypted? I recall that being an issue with the beta builds.

CVertigo1 said:
Everything appears to be in order. Is your SD card encrypted? I recall that being an issue with the beta builds.
Click to expand...
Click to collapse
It is not

The best advice I have is to Odin all four PI3 files, but not Home_CSC. It will give you the cleanest install and take everything else out of the equation. I'd backup everything with Smart Switch first, then restore it all after updating.

CVertigo1 said:
I've seen some posts about updates to official Nougat failing, so I decided to upload the update.zip to get to Nougat. I'd like to note that I didn't update using the update.zip method, so let me know if anyone runs into any issues. Hopefully this helps you guys out.
1) Make sure you are on official NON-ROOTED PI3. Also, make sure you enable any disabled packages.
2) Create a folder on your SD card named fota.
3) Download this zip and rename it to update.zip, then put it in the fota folder you created.
4) Turn off the phone and boot into recovery-volume up+home+power at the same time.
5) Wait a minute for the dead android to go away and recovery finally boots, then select update from SD card. Select the update.zip.
Click to expand...
Click to collapse
What if you are on PKC? You think it will still work?

Crsdr37 said:
What if you are on PKC? You think it will still work?
Click to expand...
Click to collapse
Im on pkc also

Probably not, but you are welcome to try. If it doesn't work, then flash back to PI3 and update from there.

Also if you use package disabler pro like most of us. Ensure you go back into there and enable all bloatware you can re-disable after the update goes through

Crsdr37 said:
Also if you use package disabler pro like most of us. Ensure you go back into there and enable all bloatware you can re-disable after the update goes through
Click to expand...
Click to collapse
I already put this in the steps, but I guarantee a lot of people will forget to follow it lol.

I got mine updated. Here's what I did.
I reluctantly used the Verizon software repair tool to "repair" the OS. It took quite a while but did reload everything. After that I just took the OTA and it seemed to work fine. I would imagine that Odin would have worked too.

I'm on a VZ Galaxy S7, PI3 firmware on Boom Mobile (VZ MVNO). Tried OTA update, Samsung Smart Switch and Verizon Software Upgrade. All 3 are showing that my firmware is up-to-date on version 6.0.1 PI3. Have they just not rolled it out to everyone?
Is my only option to use the procedure on here?

mogulman01 said:
I'm on a VZ Galaxy S7, PI3 firmware on Boom Mobile (VZ MVNO). Tried OTA update, Samsung Smart Switch and Verizon Software Upgrade. All 3 are showing that my firmware is up-to-date on version 6.0.1 PI3. Have they just not rolled it out to everyone?
Is my only option to use the procedure on here?
Click to expand...
Click to collapse
Updated using the process from OP, worked fine.

I was on PI3 firmware and I kept checking without getting the new software from yesterday. Just now I connect my phone to the PC and open up Smart Switch, it tells me the new update is available.

I was having this same problem. I couldn't get my phone to take the OTA even after unrooting and I had to end up using Odin and flashing that BL file as well as the other three that you normally flash. give that a go if you're still having problems!

Upgraded directly from PKC (beta) using SamFirm to download and flash new verizon firmware via odin. Worked great. Didn't have to downgrade back to pe1.

[ROM][Status Official] Verizon TMO Hybrid method for Debloating Stock ROM With Knox

This method creates the ability to debloat the Verizon GS7 (non-Edge Snapdragon) by modifying @jrkruse's method for the S7 edge posted here. Huge thanks to jrkruse for making the GS7 what it should be without massive bloat.
After my OP, he and @CVertigo1 evolved the method to fix the safetynet fail issues, so it now should work perfectly. I personally have not yet tried the updated method but will do so tomorrow. I'm copying instructions from the CVertigo1 thread here, but also keeping the old instructions below in post 1.
Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay.
New CVertigo1 method:
CVertigo1 said:
Yet again, all thanks go to @jrkruse for this one. I have modified his zip to work on the Verizon S7 flat. The ROM is silky smooth since it uses the factory kernel. I'm going to tweak his instructions to work for the flat. I can confirm that SafetyNet passes using this method.
Download
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
S7_SU_2_79_Root_Unroot_WO_Tweaks.zip
VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip
Install Instructions From Any Build
Warning: This will wipe your device. Some of these instructions are redundant, but they will ensure that everything goes as planned. If you don't follow them to the T, don't complain.
1) Unzip Odin and the firmware bundle zips. Boot the phone into download mode and flash the G930T BL, AP, and CP files in Odin.
2) Don't bother logging into any accounts, as the phone will get wiped again. Copy the FlashFire.apk and VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip to your SD card.
3) Shut off the phone and boot into download mode (volume down, home, and power). Flash the S7 Nougat root kernel in the AP slot in Odin. This file was in the firmware bundle.
4) When the phone reboots, unlock developer options and enable USB debugging. Unzip the S7_SU_2_79_Root_Unroot_WO_Tweaks.zip and run root.bat from your PC.
5) Now install FlashFire. Go into FlashFire settings and click option to allow flashing Bootloaders.
6) Now click flash firmware and chose AP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT_meta.tar.md5 SELECT ALL OF THE PARTIONS!!!
7) Now click install zip and choose VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V5_VZWS7FLAT.zip Make sure to click mount system when FlashFire asks. View attachment 4073928
VERY IMPORTANT NOTE: MAKE SURE TO UNCHECK INJECT ROOT AFTER ADDING THE ZIP!!!!!!!- Thanks @dclutter1
8) The phone will restart and FlashFire will flash the firmware first(it will take a couple minutes to find and flash everything), then the Aroma installer will start.
9) In Aroma, select wipe data(DO NOT KEEP SU)
10) The phone will say custom status on first boot, but it goes away after setup and reboot.
Click to expand...
Click to collapse

older method just for the record
Here is an OLDER METHOD with ADB install
Download stuff:
ODIN v3.12.3.zip
Firmware bundle for the G930. Includes VZW and TMO firmware (G930VVRU4BQA2 and G930TUVU4BQB1) as well as engineering bootloader and stock boot_recovery.image
ROM: There are two basic options to choose from:
PlayStore Rom - so called because it has almost NO apps and you download what you want from the PlayStore. Has an experience very similar to the Pixel.
Hybrid ROM - close to Samsung Stock experience by massively debloated
Method:
Reboot phone to recovery wipe data
Reboot to bootloader
In odin flash:
In BL slot: BL_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT.tar.md5
In AP slot: AP_G930TUVU4BQB1_CL10376601_QB12449118_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5
In CP slot: CP_G930TUVU4BQB1_CL10376601_QB12449107_REV02_user_low_ship_MULTI_CERT.tar.md5
Leave CSC slot Blank
Go through setup don't add any accounts your going to wipe again when finished reboot back to bootloader
In odin Flash Engineering Boot.img from above (in AP slot)
When phone reboots and computer reconnects to phone Open HYBRID_PLAYSTORE_ROM.zip folder
Click Verizon_TMO_PlayStore_Install.bat
When done click press to continue the phone will reboot back to download mode
In odin flash:
In CSC slot: CSC_VZW_G930VVZW4BQA2_CL10280325_QB12417265_REV02_user_low_ship_MULTI_CERT.tar.md5
In AP slot: G930TUVU4BQB1_Boot_Recovery_Image.tar.md5.tar
Phone will reboot to recovery and fail
In Recovery click Mount System
Wipe data
Reboot phone
During Boot Phone will Say Custom Status this will change after phone is setup and a reboot is performed
Once through setup open Rom Control App
Navigate to Phone and Settings
Click on IMS Settings
Choose Ims service switch
Click on MMTEL switch
Click on RCS switch
Under MMTEL section I enabled all the options
Click Back Button until your back to Phone and Settings Menu in Rom Control
Choose Activate Advanced Calling
Make sure under Advanced Calling that HD and Video calls are enabled
Activate WifiCalling
Known issues:
Safety net check fails (so Venmo does not work)
Some sites are blocked. Turning on "data saver" in Chrome settings worked for me but not everyone
I found that I had to go into settings > applications > phone and explicitly choose the phone as my default application for calls before it would correctly create a notification when the phone rang.
Some slightly more varsity moves:
Keeping apps from your stock:
You can modify the .bat file to not remove any apps you want to keep.
For example, I wanted to keep the "always on" display, so I deleted these lines from the .bat file:
Code:
adb shell rm -r /system/priv-app/AODService_v20
You can also further delete apps. Essentially during steps 5 - 7 above, the phone is rooted. During that time you can remove other packages. (My advice would be to pull them to your computer so you can push them back if needed)
For instance, I wanted to remove Hangouts, the AOSP browser (I use Chrome) and VisualVoiceMail. So I repeated step 5, then did:
Code:
adb root
adb remount
adb pull /system/app/VisualVoicemail
adb shell rm -r /system/app/VisualVoicemail
adb reboot bootloader
Then repeat steps 9 - 11
Wipe CACHE, (NOT data)
Reboot

Cool, cant wait to walk a friend thru this.

Just got up and running on PlayStore, everything seems good except I can't get the call recording to work. Thanks for putting this together
Sent from my SM-G935V using Tapatalk

JPSloan1 said:
...
7. Click Verizon_TMO_PlayStore_Install.bat.
...
Click to expand...
Click to collapse
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.

thrillerbee said:
Where is this .bat file?
Also, on jrkruse's thread, I only see a single ROM for download: VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V2.zip. Am I missing something?
Edit: I found the Play Store ROM; it contains the .bat file. The new ROM in jrkruse's OP won't work with this method, I assume.
Click to expand...
Click to collapse
Yes It appears he updated his method to one that uses a different kind of temporary root as well as flashable files. I'll have to look at it and see if it's customizable the way the other one was, but it looks like you found the correct playstore ROM zip from before. Here is the other ROM. Sorry for the confusion.

Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,

if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.

t1231 said:
Do we need to flash the Verizon modem? And if so would you have a flashable file? Thanks,
Click to expand...
Click to collapse
I tried but the .zip kept failing so maybe I didn't create it right.... So ultimately I did not bother and my service seems just fine at the moment.

Hobson318 said:
if i want to just put the tmobile firmware on my verizon phone and still use verizon service, do i just flash the tmobile firmware and then the verizon csc file and call it a day? not looking for the debloat and all that other stuff. just straight up tmobile firmware working on verizon.
Click to expand...
Click to collapse
I think that would work (and wouldn't think you need to bother with the engineering bootloader steps either then) but to be honest it might be safer to ask jrkruse, because I don't deeply understand it - really just adapted his method for the S7 flat.

You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.

S3NTYN3L said:
You speak of rebooting into recovery and wiping the cache. How exactly? All I seem to get is a dead robot on my screen.
Am I missing something?
Attempting this on a G930V, FWIW.
Click to expand...
Click to collapse
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.

JPSloan1 said:
After which step?
At one point I did get a robot with a yellow triangle saying "no instructions" or something, but I waited a DL few minutes and pressed a few buttons and it booted into recovery.
Click to expand...
Click to collapse
Step 10.
Hmm, It seems that I wasn't holding the buttons down long enough.
If DL = Damn Long, then, yes, I agree.

OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.

S3NTYN3L said:
OK, made it to step 15 and now I'm boned.
I had to install that ROM Control app manually as it didn't get pushed to the phone for some reason.
While attempting to follow along by clicking on IMS Settings, a toast message complains about no CSC binary or customer.xml
EDIT:
Hmm, I'll just wait a bit until you all get this sorted out I guess. In the meantime, it's back to stock for me.
Click to expand...
Click to collapse
If ROM control didn't install manually it's because the .bat file didn't execute correctly. Did you modify it? Did it successfully acquire root and execute all the commands all the way through to the "click to continue" prompt? OR did it give error messages along the way? (There will be a few during the remove steps because it's removing packages that only exist on the S7 edge, not flat.
I would try it again if you have the patience.

I didn't modify anything.
I only recall a few minor errors regarding removal of non-existent directories.
Yes, the script went through to the end.
Yes, the phone had root and the TMobile rom wouldn't let me forget it, lol.
It kept complaining the whole way through.

JPSloan1 said:
Basically this method temporarily roots the phone to modify the packages installed, removes a ton of them, and then reverts. So with this method, Knox counter is still 0x0, and I can confirm I have repeatedly used Samsung pay
Click to expand...
Click to collapse
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.

CVertigo1 said:
Can you do me a huge favor and install 'Phone info *Samsung*' from the PlayStore and upload a screenshot of the firmware page. I replicated jrkruse method since he changed it, but swapped the boot.img for the S7 flat images. Everything works great, but I fail SafetyNet. I need to find out where I'm mixed up. If I can figure this out, then I believe I can make a simple zip to take care of everything else.
Click to expand...
Click to collapse
Yeah attached. I think I also have this problem as do those in the other thread, and that's why I get an error on device check with Venmo.

I thought you posted that Samsung Pay worked for you in the OP.

CVertigo1 said:
I thought you posted that Samsung Pay worked for you in the OP.
Click to expand...
Click to collapse
I followed the method in the OP, installed Play Store version. Samsung Pay is working for me.
Sent from my SM-G935V using Tapatalk

Having trouble with the service.

My problem started some months ago, when a friend tried to root my phone, he told me that he rooted it but every app that checks for root told me that it wasn't rooted and i couldn't use apps that needed root also, the downside to all this is that i couldn't use apps that do not allow root, like the banking app, or Pokemon Go, but i used the phone like that for some months until last week when i decided to try and fix it. I thought that if i flash a stock firmware everything should be fine and the phone should be as new. On the phone, it says that the model is SM-N910F(behind the battery), in the settings it also said SM-N910F, so i tried flashing a rom for this model at first and it kept failing with me not knowing why. After trying different thing and googleing some time, i finally noticed that in "Fast Download", it says that the phone's model is SM-N910P, so i started searching about this, i didn;t understand why there were 2 different models on my phone, then i found out about searching my IMEI on imei.info, so i tried it and here it was SM-N910C, i had no idea what all this meant, but at this time i already got stuck into bootloop. Eventually, i found this thread: https://forum.xda-developers.com/note-4/help/help-sm-n910f-sm-n910p-bootloader-t3299285 and did what cam_bob22 said, it worked, i finally flashed the firmware on my phone and it worked, i could use the bank app, pokemon go, everything was fine except the fact that i couldn't select or change my mobile operator, when going to mobile networks, the mobile operators options was greyed out and couldn't be pressed(i want to mention that i did have service and that data worked but the internet would work only in roaming and i couldn't get 4G). So i tried updating the software from 5.1.1 to 6.0.1 like it was said in the instructions and hopping that this update would fix the issue, but unfortunately for me after the update i somehow lost service completely, the signal sign was in the shape of a triangle with no bars, and the mobile operators setting was exactly as before.
So far i tried going back to 5.1.1 but besides the Hands Free activation that i can't make to go away, i still can't use the mobile operators setting and my data only works with roaming activated and doesn't get 4g. One thing that i forgot to mention is that the IMEI with the 5.1.1 firmware was of a samasung Galaxy S5 not a note 4, i checked it on imei.info.
I was wondering if there is any way for me to go back to the OS i had before my friend tried to root my phone, when it said in the settings that it was SM-N910F and everything worked as it should have.
Thank you for reading and i really hope someone can help me.

@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.

aaron74 said:
@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.
Click to expand...
Click to collapse
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.

robert11arad said:
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.
Click to expand...
Click to collapse
Oh ok. So do you have service?

aaron74 said:
Oh ok. So do you have service?
Click to expand...
Click to collapse
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)

robert11arad said:
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)
Click to expand...
Click to collapse
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?

aaron74 said:
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?
Click to expand...
Click to collapse
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5

robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Ok. About the best advice i can give is, because your on pure Sprint Rom, something is messing up with csc or something.
All i can suggest, is maybe try updating to QC1 with Odin and then try flashing my gsm Rom. Which is essentially just a tmobile rom.
And if that don't give you the function you you need. Then maybe try an international Rom.
It's hard to say what the last person did to the phone.

robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?

aaron74 said:
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?
Click to expand...
Click to collapse
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.

robert11arad said:
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.
Click to expand...
Click to collapse
Well, first, let me state,about bricking device. I have to state that it's not impossible to brick. But after hundreds of flashes never had problem. These devices are hard to brick. What hard bricks a device is messing with boot loader and partitions that shouldn't be messed with, like trying to unlock lte bands. But just flashing roms is fine unless you flash a Rom not for your phone and it over writes wrong partition.
All snap Dragon note 4s have the same layout so all you need is correct kernel, csc, and some ril lib files to get data working.
Now, mine main worry is that the phone is still unlocked,because I don't know what possible changes were made to it.
But with all that being said,I'll move on. With another post.
---------- Post added at 05:52 PM ---------- Previous post was at 05:13 PM ----------
@robert11arad
Before we go too deep into this and upgrade and stuff. I'd like to just test a custom Rom on your phone and see what works.
So what firmware are you on right now?
5.01, 5.1.1, or 6.0.1?
I'm gonna take a guess and move on. You last stated you were on OG5 which it's 5.1.1. So if that's true, let's try the following.
First I'm gonna assume you already used Odin to flash that firmware. So now we need to flash Twrp. So download this on pc https://eu.dl.twrp.me/trlte/twrp-3.1.1-0-trlte.img.tar
1 . Put phone in download mode. Open Odin and plug in phone.
2. In Odin options make sure everything is unticked except Reset Flash Counter.
3. Now click on AP and select the Twrp file.
4. Flash it. Let it flash until it states it's completed. Once done. Unplug phone. Pull out battery. Put back in and boot to recovery by holding power+home+vol.up
5. Now you should have Twrp. Just reboot phone so we can continue to next post.

PM sent

@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.

aaron74 said:
@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.
Click to expand...
Click to collapse
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...

robert11arad said:
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...
Click to expand...
Click to collapse
Ok. I must have forgot something in csc. Sorry. I'll get back with you.