Related
Hey everyone. between my brothers and I, we have five Evo's. two of us are running full roots and nand unlocks, the other three are using unrevoked. those that unrevoked can use the wifi router without issue, but for my brother and myself, using the wifi router results in the app crashing and having to force close.
has anyone seen anything similar? can anyone offer me some solution?
and btw, this is my third rom. they all have the same results(full wipe, data and davik cache clear each time)
Delete wi fi tether from the phone and re-download it. This has worked for me everytime i change roms =)
Hope it helps.
Do you mean the wireless tether app? I am running my own rom but it seems that it worked for me when I was using fresh. But that is the only other rom I have tried. Have you tried re-installing the tether app?
I'm not sure i can remove the base wifi tether app. it's always cooked into the rom. and i have tried reinstalling the app. i've gone from the original version, to the newer version and finally the beta version with no luck
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Hmmmmmm. I am sure someone else can offer better advice, but does the super user app come up to ask for permission or it fc's before that?
topdawgn8 said:
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Click to expand...
Click to collapse
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
I am not sure if your signature is correct but have you tried flashing the newest radio? I am not sure if that would fix it or not. And the same thing happens to the other phone? Puzzling indeed. I'm sure someone will drop in and tell you how to fix it soon. Worst case, start over. Even though I know you said you tried various roms, maybe you are accidentally skipping a step, I do that sometimes
SilverStone641 said:
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
Click to expand...
Click to collapse
Ok, go back through the same process and try this one instead of what was in step 3.
http://code.google.com/p/android-wi...me=wireless_tether_2_0_2.apk&can=2&q=NexusOne
If that doesn't work, I've got nothing else. The first one was the beta you probably tried earlier. This is the stable one; however, I never tried it with this one. I always got it working using the 2_0_5 version.
Also, for ****s and giggles, have you tried updating you profile and prl?
- you didn't flash the wireless n patch over a 1.47 base Rom correct? Can you connect to a WiFi router or is it just the tether app?
elegantai said:
Also, for ****s and giggles, have you tried updating you profile and prl?
Click to expand...
Click to collapse
uh....what?? you got me there! i thought i knew what those were, but it escapes me now.
the only thing i can think of is that the rooting process screwed up somehow. but for it to screw up in the same way for two separate phones is odd, but it's the only thing that has remained constant since the very beginning.
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
elegantai said:
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
Click to expand...
Click to collapse
done. same results. "Unable to start tethering. Please try again!"
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
elegantai said:
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
Click to expand...
Click to collapse
i do have the wireless N enabled, but i do not have the new 1.47 yet. i'm waiting on OMJ to release an update
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
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
*I TAKE NO CREDIT FOR ANY OF THIS, IM JUST TELLING HOW I DID IT. I AM ALSO NOT GUARANTEING YOU WILL HAVE THE SAME OUTCOME*
*I recommend going to this new update guide by CVertigo1 in the ROM's section as this version of the PlayStore ROM is outdated.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695)
ROOTING
1)Flashed stock Nougat ROM
2)Flashed ENG-ROOT found here https://www.androidfilehost.com/?fid=457095661767141717
- Make sure to flash the correct kernel included in the zip file
3) Install SuperSU. Link: https://www.androidfilehost.com/?fid=529152257862710010
- I used the regular Root.bat not the one with tweaks
FIXING LAG
1)Install Flashfire from PlayStore
2)Download the PlayStore Rom from https://www.androidfilehost.com/?fid=457095661767144652
-Transfer the file to the S7
3)Open Flashfire and flash the zip choosing only Mount/ system read/write
4)Now AROMA Installer will pop up and go through all of the terms and conditions
-When asked what to wipe I choose to wipe everything
-Next when asked what bloat to remove I choose the PlayStore Rom which removes all bloat and replaces stock apps with google apps (To see full list of changes refer to the PlayStore thread)
5)Now when my S7 boot it showed no launcher, I simply held the home button down which opened the google search, in there I searched for the playstore app and installed Nova Launcher.
-Now reinstall SuperSU by double clicking the root.bat like before
6) Installed the following apps to help with lag; Lspeed, Greenify, Kernal Auditor, LeanDroid, Force Doze, and SSD Boost
-I used most of the settings found on Lag fix threads for the MM root
My S7 is smooth as butter after all of this, no lag spikes and random crashes like I was experiencing with just the ENG Root flashed.
EXTRA
1)I did have to to a reboot to get the camera to work properly
2) I had to download a Dialer/Contacts and Message app from the playstore because the stock ones were deleted in this process. But the store ones work just fine, I am recieving calls and messages like normal.
3) *Battery life is just a little worse than stock, might be worth waiting for Xposed to released for Nougat.*
Credit for Root and PlayStore Rom goes to jrkruse (https://forum.xda-developers.com/member.php?u=1949695) :good:
setup wizard keeps stopping...
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance
Bunrin said:
I have followed your step with my phone (Galaxy S7 Verizon - Android 7), but when go to step no 5 my phone always alert (The process com.android.phone has stopped, Setup Wizard keep stopping...). I tried to hold HOME button but still nothing and message always alert even reboot phone.
Please help. thank in advance
Click to expand...
Click to collapse
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.
UPDATE
Went through the entire process once more and found that wiping but keeping SU image works the best, I chose "no wipe" but it caused random reboots. I then wiped my phone and did as stated in my original post and it is working smooth once again.
ikoyhn said:
Weird, did you wipe your S7 completely before doing the process? I would flash fresh nougat and try again.
Click to expand...
Click to collapse
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
The rom is for Verizon and T mobile devices. Your good to go.
Blade22222 said:
The rom is for Verizon and T mobile devices. Your good to go.
Click to expand...
Click to collapse
Bunrin said:
My S7 model (SM-G930V). it's not compatible with VZW_TMO_HYBRID_PLAYSTORE_BS_FREE_STOCK_V6.zip? while installing show DEVICE: Samsung Galaxy S7 G935V
Click to expand...
Click to collapse
Yup it says G935 but it also works with the G930.
ikoyhn said:
Yup it says G935 but it also works with the G930.
Click to expand...
Click to collapse
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks
Bunrin said:
When install finish after reboot my phone show "Setup Failed....". any ideas. thanks
Click to expand...
Click to collapse
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
ikoyhn said:
Did you start on a factory fresh Nougat? It must be trying to run the setup that you first have to do when you get/wipe your phone. But you should have already done this prior IF you wiped your phone completely and started from there.
Here is another guide that you might find helpful: https://forum.xda-developers.com/verizon-galaxy-s7/development/rom-t3576124
Click to expand...
Click to collapse
Thanks for your support.
Is this for the Qualcomm processor?
Gon Rouge said:
Is this for the Qualcomm processor?
Click to expand...
Click to collapse
Yes the *US*S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.
ikoyhn said:
Yes the S7 does have the Qualcomm processor, and this ROM does work with it. If you are looking to see if it will work for another device with the processor then I recommend looking here: https://forum.xda-developers.com/member.php?u=1949695, for more information on the ROM and compatibility.
Click to expand...
Click to collapse
Not all s7s are Qualcomm, we sometimes get international users in here.
Blade22222 said:
Not all s7s are Qualcomm, we sometimes get international users in here.
Click to expand...
Click to collapse
Whoops forgot about that, I fixed my reply. Thanks for pointing it out:good:
My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.
IDCM said:
My phone is now stuck on the boot text (Samsung Galaxy S7) have yet to see past it.
Click to expand...
Click to collapse
-After what step did it get stuck on the boot text?
-Did you start factory fresh?
ikoyhn said:
-After what step did it get stuck on the boot text?
-Did you start factory fresh?
Click to expand...
Click to collapse
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:
IDCM said:
I've got it all in working order, but to address the issue.
It was just straight after using the first Odin file. (Flashed ENG-ROOT)
Although with hours of sitting here and determination, I came to a solution using this post and many others.
I now have my S7 (Verizon) rooted and functioning with no issues.
Thank you for sharing. :highfive: :good:
Click to expand...
Click to collapse
Glad you got it all sorted out:good:
I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?
fjgrf said:
I haven't rooted a phone in a few years but I feel like I missed a fundamental step of the root process so I have a stupid question: I get to the rom flashing step and my phone can't reboot because "Custom binary locked by SECURE BOOT (boot.img)." Then I reflash the ENG-ROOT boot.img and that same secure boot blocks because of the custom modem binary. So I just reflashed stock to get it working again, but it still gives that message if I try to install something like magisk. Am I missing something?
Click to expand...
Click to collapse
You cannot use any custom kernels on us snapdragon models. No magisk or anything. The only root option is engboot and root.bat plus the setups to smooth it out or no root at all
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.