How I Rooted my S7 on Nougat. PlayStore ROM V3 *outdated but still working* - Verizon Samsung Galaxy S7 Guides, News, & Discussi

*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

Related

G930A_PF2_Stock_DeOdexed_Debloated_ROM (7/12/2016)

**You can begin the following process from any Build but you must already have Root Access**
**Required** [root] FlashFire
Download:
- G930A_PF2_Stock_DeOdexed_Debloated_ROM.zip
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app, grant root access, and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Press "Flash Zip or OTA" and locate and select the ROM. Use the default settings under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" to "Download."
6. Press the lightning bolt then "Ok" to begin the flash . The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition.
7. Once the flash is complete and the device reboots into "Download" mode, flash the G930A_PF2_Stock_Modem_Recovery_Bootloader using Odin's AP slot. The device will take 10 - 15 mins for the first boot!
8. To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The above process will update your Modem, Non-hlos, System, Bootloader, and Stock Recovery.
3. The ROM will automatically wipe all User Data!
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Will it work for g935a? And does it fix lag?
Sent from my SAMSUNG-SM-G935A using Tapatalk
Awesome!
Ok how many folks have successfully flashed this?
It's still using eng boot? And will I be able to update super su script once installed? Also curious if maybe deodexed means I can get v4a running on this bad boy sorry for the question blast just excited to see the att s7 taking off into #root =D in Texas it goes "y'all got root?!"
4. Follow this guide if you do not already have root access: http://forum.xda-developers.com/att-...g935a-t3410538
Click to expand...
Click to collapse
Can you fix the URL? I get a 404 when clicking it.
Thanks,
Aaron
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
smknutson said:
I can confirm. This flashes!
I needed to run root.bat twice to get it to take, but everything is working, AND...
Knox still reads 0x0!
Click to expand...
Click to collapse
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
I think I am. It's either this Rom or the eng bootloader, but it runs hotter. It's running in interactive governor but cpu temperature is averaging idle at 45°c whereas on stock it felt much cooler. Something about this installation is causing this thing to heat up.
Carlos Terán said:
Do you fix the lag?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Click to expand...
Click to collapse
I'm not sure what lag you're referring to?
noobtxtech said:
Noticing any difference from original Rom performance wise? I'm thinking about joining ya but I got this thing running so buttery smooth I don't want to fix it if it ain't broke.
Click to expand...
Click to collapse
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
noobtxtech said:
You tried to get v4a sound mod running by chance? Also are you running xposed framework/modules?
Click to expand...
Click to collapse
Haven't tried v4a but Wanams modified Xposed is working and I have several modules operational.
smknutson said:
Okay, I figured it out guys.
After flashing, rooting, and starting to set it up, you will probably notice it feels a bit sluggish and runs hot, even after correcting the CPU governor to Interactive.
I believe I found the fix over in the Verizon S7 area.
Head to this thread: http://forum.xda-developers.com/showthread.php?p=67605246
And follow the directions in the Recommended Next Steps section. I flashed the Fix and Debloater zip, and my phone is now fast and running very cool.
OP may need to consider adding this tip to the OP.
Click to expand...
Click to collapse
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
dirtydodge said:
Did you use the modified Odin to flash the bootloader or did you use the regular Odin?
Thank you
Click to expand...
Click to collapse
Modified Odin for both EngBoot and this threads addon .zip
smknutson said:
Modified Odin for both EngBoot and this threads addon .zip
Click to expand...
Click to collapse
Ok thank you. Figured so but just wanted to make sure. I'm downloading the Rom now. Glad you found the fix and debloat from the Verizon thread, I seen that the other day and used it and his other guide on how to set up Greenify and amplify. My phone is running awesome on the stock rooted but I always like to grab muniz's deodex versions and run them.
Also, if you want to get rid of the Custom icon on boot and reset it to Official in status, use the XTouchWiz xposed module.
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
joe3681 said:
Is this rooted? Id love to flash a deodex, debloated rom but have no root on it...
Click to expand...
Click to collapse
You have to be rooted prior to flashing this.
Clearly. I meant post flash
joe3681 said:
Clearly. I meant post flash
Click to expand...
Click to collapse
" To regain root access, re-run "root.bat" once the device has fully rebooted. Make certain usb debugging is enabled. Enjoy! " is copy pasted from the OP so that would imply that it isn't rooted until you root it, as for why you would want a deodexed Rom (which is a performance hit) without root is beyond me. From what I gather reading this short thread you will need root and possibly even xposed to get it running right. In order to do that you would have to do some more reading. Hope this helps.

ROM issues

I'm pretty sure this has been asked a lot, but I'm trying to install the "TeamSPR Rom" and i'm following the steps exactly. I still get stuck on the bootscreen with the logo with the blue LED glowing. What am I doing wrong, and this happens with TeamSPR and Renegade.
Software Version: G920PVPU3CPF4
Hardware: G920P.02
Model: SM-G920P
Android: 6.0.1
Saafir said:
Wait 20 minutes.
Click to expand...
Click to collapse
My versions are correct for this right? and do I need anything else besides twrp?
steezoe said:
My versions are correct for this right? and do I need anything else besides twrp?
Click to expand...
Click to collapse
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Saafir said:
From the information in your post, you seem to be on the right track. That ROM has taken upwards of 25 minutes to boot for some folks. As long as the blue light is slightly pulsing, it's doing it's thing. As long as you have TWRP installed and working, you should be good to go.
Click to expand...
Click to collapse
So pulsing plus the samsung logo, is a good thing?
koop1955 said:
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
And I'm using the latest TWRP.
p.s. Thank you guys so much, I'm skepticle when it somes to asking for help on forums, cuz usually people are short tempered and or a-holes. I really appreciate it though.
1 last thing, do i install/flash the OTA part after it optimizes all the apps?
finished everything, it's booted up now, but my screen is spamming "unfortunately, "APPNAME" has stopped" is that normal?
EDIT: Can't get into my text messages either.
Saafir said:
You shouldnt receive any errors. I would reboot to TWRP, do a wipe and reinstall the ROM. Let the device boot and set it up. Once all is good with the initial install, reboot to TWRP and install the update.zip. This should ensure a nice clean start.
Click to expand...
Click to collapse
1. Flashed ROM, waited 20 is mins.
2. Phone loaded up, restarted into TWRP and Flashed the OTA zip.
3. Phone loaded up. This is when I start getting a popup saying "Unfortunately the process android.process.acore has stopped working." and my message app still won't open after i cleared cache and data.
Thanks in advance
Saafir said:
Set the device up before flashing the OTA.
Click to expand...
Click to collapse
Meaning I was supposed to wipe everything on my phone?
Saafir said:
Setup the device as go through the Setup Wizard..
Click to expand...
Click to collapse
I did exactly that. Im currently reflashing the Full ROM taking longer at the samsung screen. But I'll wait. If all else fails I'll probably go back to stock.
I'm now back to stock 6.0.1, going to give this one more go.
Would anyone mind giving me specific step-by-step directions. please?
I feel like im forgetting something crucial.
everthing finally worked out. just having an issue with xposed literally taking hours at the boot screen

[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 many here are rooted/running custom ROMS?

I used to be extremely heavy into the rooting game. I started with the Galaxy s2 all the way to the Note 5 but then it kind of seemed to me like rooting lost some of it's appeal and development seemed to slow down for some devices. After the Note 7 issue with the recall I switched to iPhone for a little while. I am back now though and I'm highly looking into rooting. I see the Pixel XL has tons of development and am just wondering what do you guys think, is it worth it to root? Many people I have talked to say Android has come so far, that it's not really even necessary anymore. What are the Pro's/cons?
If this is a topic that has been posted before, I apologize, I tried looking and couldn't find anything. Also, this is my first stock google phone, in the past I have always been a galaxy/note user.
rbtrucking said:
I used to be extremely heavy into the rooting game. I started with the Galaxy s2 all the way to the Note 5 but then it kind of seemed to me like rooting lost some of it's appeal and development seemed to slow down for some devices. After the Note 7 issue with the recall I switched to iPhone for a little while. I am back now though and I'm highly looking into rooting. I see the Pixel XL has tons of development and am just wondering what do you guys think, is it worth it to root? Many people I have talked to say Android has come so far, that it's not really even necessary anymore. What are the Pro's/cons?
If this is a topic that has been posted before, I apologize, I tried looking and couldn't find anything. Also, this is my first stock google phone, in the past I have always been a galaxy/note user.
Click to expand...
Click to collapse
I still root because of theming and my call regarding app. Imo, custom roms are still smoother.
Sent from my Pixel XL using Tapatalk
just_visiting said:
I still root because of theming and my call regarding app. Imo, custom roms are still smoother.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I was always a huge fan of theming! Hmm, perhaps it's time to pull the trigger!
I've always rooted every device, starting with my HTC Hero years ago, but I have to admit, the stock Pixel experience was the first time where I've had to ask myself is it really worth it this time.
So I tried it un-rooted for a couple of months, (which is a personal record for me!) and I loved it. But I eventually made the decision to root because I missed:
1)Dark U. I (Using Substratum)
2 Adaway Adblocker
3)Custom Roms
Now I'm on PureNexus, and couldn't be happier.
With Google seemingly tightening the screw by making it harder to modify our devices, I just hope Root access will continue to be available to me in the future.
Just like buzzboy for the most part:
- Theming. (Domination from daveyannihilation on the playstore)
- Ad blocker.
- Custom ROM.
- For pushing theme ready apps to system/data partition.
- Kernel manager app (EXKM)
- Certainly other things I forget right now...
Cheers...
buzzboy said:
I've always rooted every device, starting with my HTC Hero years ago, but I have to admit, the stock Pixel experience was the first time where I've had to ask myself is it really worth it this time.
So I tried it un-rooted for a couple of months, (which is a personal record for me!) and I loved it. But I eventually made the decision to root because I missed:
1)Dark U. I (Using Substratum)
2 Adaway Adblocker
3)Custom Roms
Now I'm on PureNexus, and couldn't be happier.
With Google seemingly tightening the screw by making it harder to modify our devices, I just hope Root access will continue to be available to me in the future.
Click to expand...
Click to collapse
Ya, I was looking into that PureNexus rom too.
rbtrucking said:
Ya, I was looking into that PureNexus rom too.
Click to expand...
Click to collapse
Hello... Been using it since the Nexus 6, Nexus 6P and now Pixel XL. I have never been disappointed. Pixel stock firmware features + just enough customization in my opinion.
Cheers...
pure nexus + elementalx because perfect performance
Forgot about AdBlock and custom kernel. Also few other things that are escaping me at the moment.
Sent from my Pixel XL using Tapatalk
5.1 said:
Hello... Been using it since the Nexus 6, Nexus 6P and now Pixel XL. I have never been disappointed. Pixel stock firmware features + just enough customization in my opinion.
Cheers...
Click to expand...
Click to collapse
What's the best tutorial for rooting in your opinion? Been looking on YouTube and trying to decide which one to follow.
rbtrucking said:
What's the best tutorial for rooting in your opinion? Been looking on YouTube and trying to decide which one to follow.
Click to expand...
Click to collapse
No, no and no! Don't go on YouTube when you have the best on XDA. That doesn't make sense...
Download TWRP: https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img
Download SuperSU 2.79 sr3: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
And place in the root of your internal storage
Reboot your phone in bootloader.
You must have latest ADB/fastboot from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it and place TWRP image inside platform tools folder with ADB/fastboot.
Open a command prompt on your computer and boot into TWRP:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
It will boot TWRP. Once booted, tap "install" and select SuperSU. Swipe to install and let it do its job.
Once done, just reboot. It will likely reboot two or three times. Don't worry, that's normal. You'll have Root with full stock. TWRP will vanish after the reboot.
Don't try to flash this TWRP image or you may have to reflash a full stock image... Read TWRP thread for more infos!
I think you could have found the same how-to here either in the guide or Q/A section though... :good:
Good luck...
5.1 said:
No, no and no! Don't go on YouTube when you have the best on XDA. That doesn't make sense...
Download TWRP: https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img
Download SuperSU 2.79 sr3: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
And place in the root of your internal storage
Reboot your phone in bootloader.
You must have latest ADB/fastboot from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip it and place TWRP image inside platform tools folder with ADB/fastboot.
Open a command prompt on your computer and boot into TWRP:
fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img
It will boot TWRP. Once booted, tap "install" and select SuperSU. Swipe to install and let it do its job.
Once done, just reboot. It will likely reboot two or three times. Don't worry, that's normal. You'll have Root with full stock. TWRP will vanish after the reboot.
Don't try to flash this TWRP image or you may have to reflash a full stock image... Read TWRP thread for more infos!
I think you could have found the same how-to here either in the guide or Q/A section though... :good:
Good luck...
Click to expand...
Click to collapse
Hmm I may have jumped the gun here I actually attempted before you responded and followed Max Lee's video on youtube and now I am stuck in a bootloop. What can I do? it's saying your devices software cab't be checked for corruption please lock the bottloader, then it says visit link on another device g.co/ABH
rbtrucking said:
Hmm I may have jumped the gun here I actually attempted before you responded and followed Max Lee's video on youtube and now I am stuck in a bootloop. What can I do?
Click to expand...
Click to collapse
Why?
You are on the forum where SuperSU and Magisk, likely the two best Root method are released. And you go somewhere else looking how to install it...
What did you do to get stuck? How did you proceed?
5.1 said:
Why?
You are on the forum where SuperSU and Magisk, likely the two best Root method are released. And you go somewhere else looking how to install it...
What did you do to get stuck? How did you proceed?
Click to expand...
Click to collapse
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop
rbtrucking said:
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop
Click to expand...
Click to collapse
You used the old root method for 7.1
If you know how to flash a Kernel then flash the factory Kernel and then use the directions above. If you dont the easiest way is ro just flash back to stock without a data wipe. First post in thw thread below.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page16
rbtrucking said:
I've followed Max Lee's videos many times before and they have always worked. I guess I shouldn't have. What I did was download fastboot, the root marlin pixel and the usb driver and basically boot into the stock recovery by holding down power and volume down and doing the comman in command prompt to unlock the bootloader and then boot to root.img now it's stuck in a bootloop
Click to expand...
Click to collapse
No offence here. Just, the method you tried is not up to date... If you took the time to search a little bit before proceeding you would have known that. All infos you need to flash/root/mod are most likely already posted here. All questions have already been answered as well. Use the search function next time or at least, wait for someone to reply :good:
Good luck...
PS: hoping you'll get it fixed. 3am here, I'm off to bed...
TonikJDK said:
You used the old root method for 7.1
If you know how to flash a Kernel then flash the factory Kernel and then use the directions above. If you dont the easiest way is ro just flash back to stock without a data wipe. First post in thw thread below.
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page16
Click to expand...
Click to collapse
I really appreciate all the help for some reason now my computer is not showing the phone in my computer so I can't access the files on it. I think it's got something to do with what I did to root it, I changed the driver for the phone. I used the file called android_winusb
rbtrucking said:
I really appreciate all the help for some reason now my computer is not showing the phone in my computer so I can't access the files on it. I think it's got something to do with what I did to root it, I changed the driver for the phone. I used the file called android_winusb
Click to expand...
Click to collapse
These are the drivers you want. Sounds like what you have. It needs to be booted to see the files. Did you get it flashed?
https://developer.android.com/studio/run/win-usb.html
EDIT... Nope you got the wrong drivers, use my link.
TonikJDK said:
These are the drivers you want. Sounds like what you have. It needs to be booted to see the files. Did you get it flashed?
https://developer.android.com/studio/run/win-usb.html
EDIT... Nope you got the wrong drivers, use my link.
Click to expand...
Click to collapse
Yes I did get it booted but the usb is still not working and it's saying the file in the link you provided is not compatible.
Well it looks like this is a problem with the phone because i cant access anything when I hook it to my mac either.

[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

Categories

Resources