Develop Bugs

[Q] root on p607t?

Am I just being stupid or is there a way to root the new note 10.1 2014 edition on t-mobile's network? The model is SM-P607T & I don't see that listed anywhere on odin/s list or anything. Or is it just too soon from release?
Extra info: Baseband P607TUVUANE2, Android 4.4.2, Kernal 3.4.0-1433887

riffy504 said:
Am I just being stupid or is there a way to root the new note 10.1 2014 edition on t-mobile's network? The model is SM-P607T & I don't see that listed anywhere on odin/s list or anything. Or is it just too soon from release?
Extra info: Baseband P607TUVUANE2, Android 4.4.2, Kernal 3.4.0-1433887
Click to expand...
Click to collapse
I am looking for this as well since i got one today. It looks like it is the same thing as the P605 which is LTE. The non LTE ones do not use the Qualcomm chip. It also looks like 4.4.2 just came out for the P605 not to long ago and there really isn't anything out for it yet. Bigbuff is talking about updating TWRP to 4.4.2 for the P605. At that time I am sure we will get a recovery and be able to flash SuperSU. If it is out already I have not found it and would like to know as well.

OK so it's not just me then. Usually by the time I get a device all this stuff is out all ready.

I wonder if you can use the international version P605. That's got the qualcomm chip with LTE. I have the 605v and there's been no development for it. Verizon has locked the bootloader, as they tend to do, so we are stuck. If you understand Knox and how that works I would try the P605 method. I tried it on mine and it failed and it didn't cause any damage.
Sent from my SM-N900P using Tapatalk

Have you guys tried to put your tablets into download mode. My underdstanding you need to hold down volume down plus the power button for three seconds, but when I try this mine boots into regular mode and not the download mode. Can someone else try this and see if you get a different outcome?
Sent from my SM-P607T using XDA Premium 4 mobile app

Haven't tried it but you have to add home to that as well I thought. Yeah, Google search:
Boot your phone into Download Mode by Pressing and Holding the Volume Down + Home + Power buttons at the same time till you see a warning message on your screen. You’ll be asked to hit the Volume Up to continue into download mode.

draigons said:
Have you guys tried to put your tablets into download mode. My underdstanding you need to hold down volume down plus the power button for three seconds, but when I try this mine boots into regular mode and not the download mode. Can someone else try this and see if you get a different outcome?
Sent from my SM-P607T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
its Power + Vol-D + Home gets you to a screen that says vol up to get to download mode or vol down to reboot. I can get to Download mode by doing that. I am going to try doing the P605 root they have out and see how that goes in asec. Make sure you down the Full Odin Firmware.
http://www.sammobile.com/firmwares/3/?download=29807
So you can use this if you need to.

Good luck! I'm not adventurous enough to try it.

WARNING: By doing this your Spen will not work anymore
Ok here is how to root the P607T right now. It is the same way as Root for the P605 right now. After reading http://forum.xda-developers.com/showthread.php?t=2766394&page=9
on post 88. Someone with the P605 used the P905 CF-Auto root to root their 605.
here are the steps
1. Download to your PC http://download.chainfire.eu/385/CF-Root/CF-Auto-Root/CF-Auto-Root-viennalte-viennaltexx-smp905.zip
2. Reboot your P607T into Download Mode. You can do this by turning off the tablet. then hold Home + Vol-D + Power you will get a screen that says Press Vol D to get into Download mode.
3. Plug your P607T into your PC.
4. Open Odin 3.07 which is included with the down you already did. You should see a Blue tab that says something like Com1.
5. Make sure the only thing that is checked is Auto-reboot.
6. Click PDA and file the CF-Auto-Root-viennalte-viennaltexx-smp905.tar that was in the Zip file you just unziped.
7. Click start and wait.
Your tablet will now reboot into a P905 recovery and flash SuperSU. It can take awhile for the reboot into recovery to happen so just wait. After this is all done your tablet will boot back into Android. Go into the play store and update SuperSU. SuperSU will keep FCing until you update it in the Playstore.
Now here is the problem we run into if you do all this. After CF-Auto Root is done it is going to put a P905 recovery on your Tablet not a P607T recovery. If you want to get your P607T recovery back for future OTAs you need to Odin the full Firmware for the P607T which you can find here. http://www.sammobile.com/firmwares/3/?download=29807 Once they get a working TWRP for KitKat and the P605 we should be able to get everything else we need to get back our old recovery.
Now another problem That I have found as well is that the Spen does not work after doing this. I do not really care because I do not really use the Spen. I know there is a fix in this thread http://forum.xda-developers.com/showthread.php?t=2766394&page=9 but I have yet to get it to work because I do not know how to type the *#2663# in phone app and then update wacom firmware from kernel to get the Spen to work. We do not have a Phone app to do that. So you are warned that your Spen will not work after doing this.
Other Wise enjoy root until a better way is out.

LTE still work?

riffy504 said:
LTE still work?
Click to expand...
Click to collapse
No clue I don't use LTE I just opened a 200mb line to get the Tablet on EIP. I will pop in my sim when i get home from work and check it for u.
Edit: yes lte still works I am still trying to fix the spen however that still doesn't work.

Also looks like TWRP has a working recovery now for the P607T. here is a link to a odin file for it. http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776 I would use that and just flash SuperSU with it. should give you root and hopefully a working Spen.

May be possible to use mobile odin pro and inject root to the stock firmware, without tripping the knox flag?
This works on the note 3, upgrading to 4.3.
Edit: mobile odin requires to have already root, I used it when upgrading to 4.3
to not lose root.
Thanks.

To late... I already tripped stupid knox. hehe I love the samsung note lines but I really REALLY hate knox! Just a reason for them to deny warranty, or else it'd be optional.
That odin file worked great. Now to wait for some custom roms.....

Just jumping in on the got-this-yesterday train and glad to see some folks have jumped on ahead of me. Thanks for the information you've all provided thus far. I'm hopeful that development on this thing will be strong, I'm liking the device so far.
I'm interested in rooting ASAP but I've been out of the Android loop for a little while, so this KNOX thing freaks me out a bit (I'm just getting familiar with what it is). Seems like it is a simple warantee related thing. Is it irreversible? How common is flashing a custom ROM without triggering it? Does it affect usability at all to have it triggered?
I'm interested if flashing this this evening but not really sure what I'm in for as far as KNOX.

amirite said:
Just jumping in on the got-this-yesterday train and glad to see some folks have jumped on ahead of me. Thanks for the information you've all provided thus far. I'm hopeful that development on this thing will be strong, I'm liking the device so far.
I'm interested in rooting ASAP but I've been out of the Android loop for a little while, so this KNOX thing freaks me out a bit (I'm just getting familiar with what it is). Seems like it is a simple warantee related thing. Is it irreversible? How common is flashing a custom ROM without triggering it? Does it affect usability at all to have it triggered?
I'm interested if flashing this this evening but not really sure what I'm in for as far as KNOX.
Click to expand...
Click to collapse
Edit: Originally used root de la vega method for the note3. Mobile odin requires root.
The procedure to inject root with mobile odin pro is on the international note 3 forum.
Worked for my tmo note 3 upgrading to 4.3 and not lose root, but only flashing the original firmware.
Any custom rom, custom recovery or custom kernel will trip knox.
This is not tested yet on the note 10.1 2014.
Will check on the mobile odin thread or Chainfire's blog.
Tripping knox for now is irreversible and voids the warranty.
Normal device operation is not affected. What is lost is the security feature.
Only a concern if your company uses knox, and you use your device for work.
I am going to wait a few weeks, hoping for a no knox tripping root method,
to keep the warranty. But I know that eventually will not care on tripping knox.

Well fudge! I never thought to test the s pen before I rooted. Guess what, it doesn't work.

riffy504 said:
Well fudge! I never thought to test the s pen before I rooted. Guess what, it doesn't work.
Click to expand...
Click to collapse
I posted a big huge warning sign saying that the s pen would not work if you rooted
Sent from my HTC One_M8 using Tapatalk

No I mean it didn't work hardware wise. I thought the touch screen was off by 1/4th an inch but never thought to try the s pen before last night. I even flashed back to stock and it was the same way. Where ever you touched with the s pen it'd either do nothing or it'd randomly draw in a tiny little square up near a corner. The touch screen was really noticeable trying to click on links in chrome cuz I'd always missing, but I thought it was me till I realized the s pen didn't work either. Then I figured it was just the hardware was messed up. Messing around in the drawing app proved that the touch screen was off to a corner by 1/4th an inch. Even if I turned the device around it always was off to that same physical corner.

Oh! Also, I used the new Odin file btw. I assume the s pen works on that one. Never did use the one for the P905, that you posted with that warning.

[Q] GT-I9195 Black Edition - What to do in which order?

Hi,
please give keywords and guiding advice, I will try to find the corresponding threads by myself
I have a brand new GT-I9195 Black Edition. I want to do as less damage as possible, so what do I have to do to get CM11 with Xposed framework running?
I just switched it on, started KIES 2 and connected. No SIM-card is inserted, no microSD-card, no WiFi connection. The phone is offline.
KIES says that the firmware is the most recent and gives this:
Code:
I9195XXUBML4 / I9195YBTBNA2 / I9195XXUBML4 / I9195XXUBML4 (DBT)
I assume this is not the newest firmware, and according to this thread (German) "I9195XXUCNE6 I9195OXACNE6 DBT 4.4.2 23.05.2014 is newer.
I have or see no possibility to upgrade via KIES.
Would the new firmware give me another, better modem/baseband firmware? If so, I would flash with Odin 3.09.
I think I need root permissions for Xposed and XPrivacy, at least this is what I did with my Sony Xperia mango. Is that correct?
What steps do I have to take to get root access without interacting with KNOX? Does it make sense to avoid the KNOX counter increase?
What part of the warranty will be void if KNOX is triggered?
What recovery should I use? There is already a recovery available, accessible by pressing Volume Up and home button at the same time when switching on.
I wanted to start with CM11 and no special kernel, just what CM11 brings, to keep it easy. So flashing serranoltexx M9 or later should be sufficient?
How do I get Xposed and XPrivacy to work? I want it working before putting in the SIM card and connecting to the internet. Do I have to worry about dalvik and ART?
GApps 20140105 from http://wiki.cyanogenmod.org/w/Google_Apps are the right ones?
Did I forget something?
Thank you
Raubsau

You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.

MarkAndroid.UK said:
You answered most of it yourself, just go for it and you will learn even more doing it.
If I were you I would probably flash TWRP 2.7.1, latest stable CM11, and a gapps from CM or wherever. Install xposed and whatever modules. Done.
Xposed is sort of contained/maintained within itself but it and its modules install just the same. Its easy to set up. I don't know Xprivacy at alll.
You can flash and try any compatible kernels from here anytime. Remember Nandroid and Titanium backups are your best mates.
Forget about Kies, you won't need it. CM11 firmware should provide a more than adequate modem and everything you need to go.
Click to expand...
Click to collapse
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?

Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
Why is it so important to you to install XPrivacy before first boot?

Raubsau said:
I don't want to brick the device, that's why I'm asking.
Each thread seems to recommend CWM - why do you suggest TWRP?
I want to install Xposed an the XPrivacy module even before starting CM for the first time - I'm not afraid of injecting the .apk via ADB, if there is a way to connect without enabling dev mode or similar. Any idea about how to do that?
(XPrivacy is restriction management on a very fine grain level - if you want to restrict the phone app from actually making a phone call, or any (even system!) app from reading your conatcs or only certain contacts, this is your best friend. Similar but way mightier to the good old PDroid :good
I thought the modem was something independent from the ROM? More like a driver for an auxiliary processor?
Click to expand...
Click to collapse
No one wants to brick their device, do they? I've never bricked mine and I've made lots of mistakes. It is highly unlikely unless you try to flash something not meant for your device or something similarly bad.
I certainly haven't found CWM being recommended over TWRP - devs here tend not to recommend, just point things out; ALL choices are yours. There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it. ROM's are built from components and not everything has to be there - one of the brilliant things about Android is how it interfaces with all the different aspects of a mobile device - it appears to be one program running everything but it is extremely modular.
With external apk's I just copy them to external SD and install them on the phone.

Raubsau said:
Do I have to worry about dalvik and ART?
Click to expand...
Click to collapse
Forgot this bit!
No. You can elect to use ART in the system setting of some ROM's (certainly SLIM) and I know some people who do. However, ART is still under development and by no means are all apps ready for it yet. Xposed Framework itself will not work under ART and won't be for quite a while yet.

MarkAndroid.UK said:
There is always a risk but if you want to be safe then why are you here!
I first flashed TWRP because it was touch screen and had more options to back up partitions separately, such as EFS strangely enough; EFS partition contains the modem stuff. So you could archive your EFS and flash it back if any ROM overwrites it.
With external apk's I just copy them to external SD and install them on the phone.
Click to expand...
Click to collapse
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.

Raubsau said:
I just want to minimize the risk, this phone was more expensive than the last one which had to take one or two for the team.
I will root with Odin as suggested here: http://forum.xda-developers.com/showpost.php?p=43622999&postcount=1
How do I delete the Knox stuff, then? Just flash CM11? I understood Knox is independent from ROM?
dalvik/ART: Good, I will not try to activate/use ART, then.
Click to expand...
Click to collapse
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.

MarkAndroid.UK said:
Yes, those root instructions are good. The Knox issue shouldn't be a problem and you can deal with it post ROM flash by removing those files mentioned in your link. The flag will be tripped (it appears it is tripped if the bootloader is modified rather than just root but it is that sort of level) but that doesn't void the warranty in the EU anyway.
---------- Post added at 06:51 PM ---------- Previous post was at 06:43 PM ----------
Quick addition : No 7 in those instructions MUST be done otherwise I don't think you get root. It is tricky, just be prepared - it resets quickly. If you miss it I think you go back to no 3 again to get to download mode.
Click to expand...
Click to collapse
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?

Raubsau said:
Alright, that went smooth. Now which GApps do I need? http://wiki.cyanogenmod.org/w/Google_Apps
If so, why not "small"?
Click to expand...
Click to collapse
'Small' would be fine

MarkAndroid.UK said:
'Small' would be fine
Click to expand...
Click to collapse
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help

Raubsau said:
I flashed CM11 M9, booted, installed Xposed Framework, installed XPrivacy and will now proceed to install the small GApps.
Thanks for your help
Click to expand...
Click to collapse
That's great, have fun and you're welcome

Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
I intend to buy the 'black edition' too but I am worried whether the internals changed as it's a later model and hence CM wouldn't run on it...
black edition:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
"ordinary" black version:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-1.jpg
Thanks a lot

soikku said:
Hello RaubSau
Have you successfully installed CM onto your Galaxy S4 mini black edition?
Thanks a lot
Click to expand...
Click to collapse
If the model number of the device you wish to buy is I9190 or I9195 then you can follow standard procedure.
Black edition is just cosmetic variation. Nothing special about that. Model number is always I9190/2/5.
So use normal procedure from threads in this forum. Good luck.

My phone looks like this:
cdn2.gsmarena.com/vv/pics/samsung/samsung-galaxy-s4-mini-I9190-black-edition.jpg
Info in the Settings menu says "GT-I9195".
As I was using XPrivacy fromt the start, some of these problems may have occured because of wrong restrictions:
- orientation of indicator in Google Maps shows wrong direction
- no compass app is working
I use my phone for calling, reading and writing mails, and remote control my media box. In the few cases I needed it for navigation, it worked fine (regardless of the wrong indicator).
Hope that helps.

Thank you for the replies, Raubsau and sasank360
Thank you for pointing out that the 'black edition' indeed is identical to the previous one internally.
I ordered the phone now and am looking forward to happy flashing (CM11 for the time being as freecyngn doesn't work for CM12 (yet)).

[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

How I Rooted my S7 on Nougat. PlayStore ROM V3 *outdated but still working*

*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

[A11/CTL1+ and A10/BTJ3+] [MOD] [S20 Ultra] JBNCK Fixes and Tweaks v2.0

Hi there,
I've combined some custom-kernel-like tweaks into a single flashable .tar file and I wanted to share it with you.
This .tar file contains:
-patched vbmeta image
-working magisk root with full Android 11 support
-magisk manager helper preinstalled
-a cleaned up boot screen + no bullsh*t on boot screen
-a cleaned up unlocked bootloader screen + no bullsh*t on unlocked bootloader screen
Prerequisites
-an unlocked bootloader
-firmware version CTL1 (A11)/BTJ3 (A10) or newer
-Odin 3.XX.X
-all data backed up
-fully functional brain
-stock recovery and firmware (this will not work if you have a custom recovery or run a custom rom)
STOCK BASED ROMS LIKE BEYONDROM WILL ALSO NOT WORK!
PLEASE NOTE:
-I am not responsible for a bricked device, please make backups and make sure to
always have the official firmware if something goes wrong
-flashing this requires you to factory reset your phone or else the phone won't boot
Instructions:
-unlock your phone's bootloader
-boot into download mode
-in Odin uncheck auto-reboot
-put the .tar file into the AP slot (If it doesn't work try USERDATA)
-after flashing boot into recovery with the key combination
-select factory reset and confirm (This will wipe everything from your phone)
-after factory reset reboot into system
-setup the phone and restore your backup (if you made one)
-Install Magisk and you're good!
If you have any problems
Please don't just comment "Doesn't work" and instead tell me about
the errors you encountered, your software info and other information
you think would be helpful.
Happy flashing!
If you still have questions make sure to ask them below
DOWNLOAD CTL1+: https://1drv.ms/u/s!AtNTTTF5vqOe73aVGDPSRGr5aria?e=dICFlS
DOWNLOAD BTJ3+: https://drive.google.com/file/d/1KqOGRbAy4fY1ghro4HoP-eDDYh4G7b5Z/view?usp=sharing

Tried it on my friend's phone,works great.Thanks

Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..

@[email protected] said:
Can i flash it as my firmware version starts with QP1A.??(build number)..
Thanks in advance and cheers..
Click to expand...
Click to collapse
This doesn't say anything. Can you tell me what custom ROM you are running? If you are on rooted stock also tell me.

Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..

@[email protected] said:
Hi,yes,phone is rootedAndroid 10,,one Ui,v 2.1,build number QP1A 190711.020.G988BXXU1ATCT..
Click to expand...
Click to collapse
Geeeeeez! Update your phone! You have to have OneUI 2.5 BTJ3 or OneUI 3.0 CTL1 at least. What are you doing on 2.1? If you don't update, this will break your phone.

Okay buddy,ty..will do that.

Hi again m8,can i update Android 11,,One GUi 3.0,RP1A200720.012 G988B...

And ,or which file i have to use??

@[email protected] said:
And ,or which file i have to use??
Click to expand...
Click to collapse
Depends on the version. I don't want to be rude but how did you even manage to root your phone with this lack of knowledge?
If you update to Android 11/One UI 3.0 you chose the One UI 3.0 one. If you only update to 2.5 you chose 2.5. Remember to check the end of your firmware number:
There are supported firmware endings:
One UI 2.5:
-BTJ3
-BTJ4
One UI 3.0:
-CTL1
-CTL6
-Any One UI 3.0 firmware above that.
Download SM-G988B / Galaxy S20 Ultra 5G SM-G988B in Samfw - Samsung firmware download
Pick your CSC there, chose the newest one preferably (A11), press "Download on website", unzip it and flash it with Odin while in download mode. You should know how to do that.
After it's finished, complete setup (do not restore any backups yet!) and go into download mode again. Flash the file as AP or USERDATA (whatever works) and perform another factory reset. Done.

So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?

BCityModz said:
So i just reflashed stock because Beyond rom is givving me issues, says you removed all the BS from the boot screens but i still have that unlocked bootloader msg. i flashed in AP with no issues, that msg mean it didnt work?
Click to expand...
Click to collapse
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha

JanBoyGamer23 said:
The unlackiert bootlaoder Massage Stars Tiere just wichtig Themen Bulletin
Edit: German Autocorrection sorry wait haha
Click to expand...
Click to collapse
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.

JanBoyGamer23 said:
Ok disabled the autocorrection. What I was trying to say is: The unlocked bootloader message is still there just without the bull**** about your phone being vulnerable to hackers and this other ****. It now just says that it is unlocked.
Click to expand...
Click to collapse
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.

BCityModz said:
Ok sweet, so Im no pro at any of this but i know the basics to flash. and wasnt able to unlock my last phone because the unlock option never popped up in settings. but now my camera isnt working, i open it up and its just black, no errors or anything.
Click to expand...
Click to collapse
That can't be an issue with the script as it doesn't modify anything related to the camera

JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
Ok I may have to make a copy of my girls phone and flash original back to the phone and go again.

JanBoyGamer23 said:
That can't be an issue with the script as it doesn't modify anything related to the camera
Click to expand...
Click to collapse
yea IDK, did it all over again, even booting up to make sure the cam was working. same thing black screen when i open the camera app.

ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??

frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
Short answer: Yes
Long answer: You are unlocking your bootloader and flashing a custom image so you lose your warranty and trip knox

frostmore said:
ok, i tried searching to see if this trips knox...so i am gonna ask at the risk of appearing stupid...
Does it trip knox??
Click to expand...
Click to collapse
If you want to use s health: Download build.prop editor, grant it root access and and change the value of 'ro.config.tima' from 1 to 0