Root for the Verizon Samsung Galaxy S6 SM-G920V (G920VVRU1AOC3///OE2)Before you begin disable your reactivation lock. There's a chance for it to get stuck ON once your device is rooted, which could cause issues with ROMs (unknown currently, but be safe!)
** You can turn it back on once you're rooted. **
WHATEVER YOU DO DO NOT ACCEPT OTA "G920VVRU2AOF1" OR YOU WILL NOT BE ABLE TO ROOT USING THIS METHOD. IF YOUR PHONE CAME THIS WAY, I'M SORRY THIS WILL NOT WORK.-About-
Great job Keen Team! Thank you very much for your work and bringing us root! This method and exploit were found by them and orignally posted here. The purpose of this post is to simply 1) Have a dedicated post for root under OUR forums to make it easier for newer members to get their device rooted, and 2) Simplify the installation of SuperSU for those who don't want Kinguser, while also having detailed instructions so the newer/novice users don't get lost.
-Credits-
Original Exploit/Root Team: Keen Team
Original Poster: @idler1984, over here.
Vulnerability: memeda, wushi
Original idea of exploit: memeda
Exploit: idl3r, Qoobee
Testing & SU management: Kingroot team for help testing and great root manager
ADB Line Commands: @Gunthermic at Post#269
-Steps to a rooted device:-
1) Go to Settings -> About phone -> and verify that your Build number (or Baseband version) is "LRX22G.G920VVRU1AOC3//OE2." SW up until "G920VVRU2AOF1" will work with this method.
2) Go to Settings -> Lock screen and security and enable "Unknown Sources" (*You may turn it back OFF once you're rooted, if you'd like*)
3) Plug your phone into your computer.
4) Scroll to the bottom of this post and download "pingpongroot_<ver>.apk" (currently "pingpongroot_beta6.apk").
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^ (Screenshot of what to look for)
5) Put the APK on your device; install and then open the application on your phone.
6) Install SuperSU when the install pops up, then open it once and return (you'll get errors in SuperSU as you're not rooted yet) to Ping Pong Root and tap "Get root!" -- if your phone reboots on its own during this, open the app and try again. Once the app finishes rooting your device, close the pop up message and reboot.
~Enjoy.
-FAQ-
Q: Will this trip my Knox Counter?
A: No.
Q: Will this let me flash ROMs/Kernels and have a custom recovery?
A: No. The bootloader is still locked.
Q: Why does my device say "Custom" when booting up?
A: That just means Samsung's system checker sees the su/root. If you flash back to stock using Misterxtc's ODIN files here, then you will no longer be rooted or show "Custom." For now, until the bootloader is unlocked, deal with it if you happen to get caught by the checker.
Q: Does this work on the edge?
A: Not yet.
Q: I'm lost, confused, stuck, or getting errors that are hindering me from root access / SuperSU.
A: Post below, I can help or in the OP for the root method, here. Often your issues can be resolved just by restarting the root process from step one. On my 20th or so rewipe and root, I ran into some issues but just refollowed every step and was fine.
1 post, just in case.
This is rather exciting. I'm staring at my Note 4 which I like better than my s6, but it was never able to get root.
This may be the reason I was looking for to use my s6 over my Note4
Thanks for putting this guide together. Hopefully it should help those new to rooting. I'd add a link to the video as well.
Anyone else having trouble updating binary through chainfires su?
oconnell84 said:
Thanks for putting this guide together. Hopefully it should help those new to rooting. I'd add a link to the video as well.
Click to expand...
Click to collapse
Sure thing! Can you post it? On my phone atm so it's harder to dig.
jparasita said:
Anyone else having trouble updating binary through chainfires su?
Click to expand...
Click to collapse
Unroot through the settings in chainfire's SuperSU and reroot if you're having fatal issues that are preventing root/superuser. What errors are you specifically getting with updating the binaries?
At step 10, when I type "su" I get this error:
[email protected]:/ $ su
su
[-] Connection to ui timed out
[email protected]:/ $
StrumerJohn said:
Unroot through the settings in chainfire's SuperSU and reroot if you're having fatal issues that are preventing root/superuser. What errors are you specifically getting with updating the binaries?
Click to expand...
Click to collapse
Works find just wont let me update binaries and just curious if its just me
ascallop said:
At step 10, when I type "su" I get this error:
[email protected]:/ $ su
su
[-] Connection to ui timed out
[email protected]:/ $
Click to expand...
Click to collapse
Open up Kinguser, and then grab a rootchecker app off of the playstore. See if you're properly rooted, if not retry the pingpongroot app.
jparasita said:
Works find just wont let me update binaries and just curious if its just me
Click to expand...
Click to collapse
If you have the time, I'd redo the ADB steps later. Not a big deal since your root access works, but it's nice to keep SU binaries up to date.
This is what I get when trying to install su and binaries. Please help me
I think you're missing a step in number 12. I tried your guide and got an error message so I went to the original post below, then I got it all working right.
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
gti2756 said:
I think you're missing a step in number 12. I tried your guide and got an error message so I went to the original post below, then I got it all working right.
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
Click to expand...
Click to collapse
Whoops! I accidentally cut off the beginning of a line! Thanks a lot..
THADDIUS25 said:
This is what I get when trying to install su and binaries. Please help me
Click to expand...
Click to collapse
jparasita said:
Anyone else having trouble updating binary through chainfires su?
Click to expand...
Click to collapse
ascallop said:
At step 10, when I type "su" I get this error:
[email protected]:/ $ su
su
[-] Connection to ui timed out
[email protected]:/ $
Click to expand...
Click to collapse
Anyone having issues, go ahead and re-do the adb steps. My apologies.
In other news, I'll start working on a cleaned up stock ROM for you guys. Might take awhile due to school and work, but it'll be next on my list (no custom recovery, but FF flash. See Misterxtc's post here.)
I just rooted my phone and things are working great! I have two questions:
1.) Can anyone with more experience than me let me know if we can now install the Stock Samsung Browser as a system app (the stock browser has fingerprint reader as password which is awesome!) Please see the post here: http://forum.xda-developers.com/gal...xy-s6-apps-t3041330/post59644234#post59644234
2.) Can we modify the build prop or anything to allow us to tether for free without use of FoxFi? I know FoxFi works, but it makes me have a passkey on my phone which I hate. I also tried to install the FoxFi certificate as a system certificate and it still required me to have a passcode for some reason.
Just looking for some guidance! Thank you!
Works awesome! Thanks!!!
StrumerJohn said:
If you have the time, I'd redo the ADB steps later. Not a big deal since your root access works, but it's nice to keep SU binaries up to date.
Click to expand...
Click to collapse
Think it was cause you missed a command tryed again worked flawless cannot wait to see youre work
Is this (the superuser part) possible to do with a mac? I downloaded and extracted the ADB folder but cant figure out how to open a command prompt from the folder. (I already rooted but now trying to switch to SU)
What and where can I find the reactivation lock?
Related
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Reserved
*I am big fan of this device. Looking forward to using it as my daily driver, and very happy to extend NRT support*
just added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
Nice to see you here WugFresh!
Good to see you, glad you've joined us :thumbup:
Hi! Very nice to see you here! You're always been my backup when I screw up something in the past with my nexus devices. I'm know I can always get back to stock with NRT
Verstuurd vanaf mijn Nexus 5X met Tapatalk
@WugFresh
Love your NRT on the Nmmexus 6. Glad you're here. Makes life a lot easier
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
imadiu said:
I couldn't install busybox as mentioned in the instructions provided for "rooting", it's the last step (confirmation for root). It prompted me to change installation directory but system/bin doesn't work as well. And i can't boot recovery as well after the whole rooting process. It just shows me a dead android there
edit: i may have download stock recovery as well, as prompted by your toolkit after rooting.
#2 edit: reflashed twrp to solve my problems, but you may want to mention something to prevent something like that from happening again. Or maybe i'm just dumb
#3 edit: so sorry, it seems that the busybox provided was outdated, update it from playstore and installation will be good to go
Click to expand...
Click to collapse
I am having BusyBox issues also.
mmartenn said:
I am having BusyBox issues also.
Click to expand...
Click to collapse
If you tried to install busybox right after you root your phone, as what the Root toolkit tells you to, it will not work like mine. That's because it's outdated. So just go to play store and update that app first before you reinstall any other app. I presume you rooted your device right after you unlock your bootloader which factory resets your device.
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
coolineho said:
I have issue gaining write access to /system, busybox can't install to system/bin or system/xbin, had to install busybox through recovery.
also no /system write access through adb shell, it says system file read only
Click to expand...
Click to collapse
Same problem here. Any solutions?
riceknight said:
Same problem here. Any solutions?
Click to expand...
Click to collapse
Not yet, still waiting ;(
I'm also facing the same issue, can't install busy box. It force closes after it fails to install. I tried updating to 124.1 but that didn't work, I also uninstalled and installed again from the playstore but that didn't work.
I also can't reboot into TWRP, unless I reboot through the NRT updater.
If I try to reboot normally without the updater, then I get the red warning message saying my phone is corrupt, followed by the green android robot with a red warning triangle coining out of it's stomach.
I'm running MDB08L
What I'm doing wrong?
Thanks
Sent from my Nexus 5X using Tapatalk
Install notes:
In options menu disable installing busybox, install busybox from play store after root process.
After root, Flashboot Flash Recovery in Advanced Utilities.
I have had no problems after using these steps.
I followed the steps above and busybox still wouldn't install so I found a 1.24.1 flashable zip flashed it and it worked . just another option to try if all others are not working
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Tank87 said:
Does the "Restore: Flash Stock + Unroot" option completely wipe any trace of unlocking, rooting so that the phone could be sent to Google for repair. (I'm just asking, in case my screen breaks)
Click to expand...
Click to collapse
Yup, just did mine to send it back to google for warranty replacement of intermittent power button.
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
skulldreamz said:
Guys here is a flashable zip. It's busybox 1.24.1 permissive. It's works 100% for me many times. If anyone wants 1.24.1 SElinux just let me know and I'll upload it
https://www.dropbox.com/s/e8tpfd4d8qcsqo5/Busybox-1.24.1.zip?dl=0
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried flashing this file (through twrp right?). It doesn't look like it worked through TWRP I got an "Updated process ended with error=1, error flashing 1.24.1.zip", and busybox is still not present on the phone when I restarted it. I tried downloading it from the play store directly and it still gives me the "it looks like it was not installed successfully" error message. Should I be flashing this file some other way? Thanks in advance!
I have seen a lot of issues with soft bricking using SuperSU-Me and I have figured out the issue once and for all. Kingroot has been upset over the recent reputation attacks of their software and have disabled functionality of switching between Su applications. Just follow my steps and you'll be alright.
You're going to need a few files to get started, grab them from the attachment links at the bottom of this post.
1) Extract the mrw folder from "Replace_Kinguser_with_SuperSU-v2.4_2.zip" and place it onto the root of your INTERNAL STORAGE
2) Install the PROVIDED KINGROOT APK
3) Once step 1&2 are complete, navigate to the play store and download "Terminal Emulator"
4)Open Terminal Emulator and type "su" without quotations and grant root access.
5) Next, type sh /storage/sdcard0/mrw/root.sh
6) The process will take a minute and have a few error messages, DO NOT BE WORRIED
7) Open the Supersu app that was just installed and update binary, this should have no issues as the other methods have proven faulty.
8)Reboot and enjoy
Reason I did this was so I can use Flashfire to hopefully install Xposed, I'll let you know how it goes!
does not work... the kingroot app you provided Fails to root device.
cocokasper said:
does not work... the kingroot app you provided Fails to root device.
Click to expand...
Click to collapse
Try again, many have rooted without issue.
Sent from my 5054W using XDA-Developers mobile app
root
where exactly for the mrw folder in /root or / or /home?
questions already been answered :}
Works
thankyou this worked perfectly, am i to understand that kingroot is completely uninstalled ?
Dude, you are the ****ing man! Worked perfectly and was finally able to get SuperSu to download the binaries, thanks!!!
links not working
Are these downloads still active? They won't download, could be my device but I thought I'd make sure and ask
root worked for me.
brad2192 said:
I have seen a lot of issues with soft bricking using SuperSU-Me and I have figured out the issue once and for all. Kingroot has been upset over the recent reputation attacks of their software and have disabled functionality of switching between Su applications. Just follow my steps and you'll be alright.
You're going to need a few files to get started, grab them from the attachment links at the bottom of this post.
1) Extract the mrw folder from "Replace_Kinguser_with_SuperSU-v2.4_2.zip" and place it onto the root of your INTERNAL STORAGE
2) Install the PROVIDED KINGROOT APK
3) Once step 1&2 are complete, navigate to the play store and download "Terminal Emulator"
4)Open Terminal Emulator and type "su" without quotations and grant root access.
5) Next, type sh /storage/sdcard0/mrw/root.sh
6) The process will take a minute and have a few error messages, DO NOT BE WORRIED
7) Open the Supersu app that was just installed and update binary, this should have no issues as the other methods have proven faulty.
8)Reboot and enjoy
Reason I did this was so I can use Flashfire to hopefully install Xposed, I'll let you know how it goes!
Click to expand...
Click to collapse
thank you for your help. great work
I cant find the root of internal storage can you explain how to do so? Just realized.I have 5045n is there one for it. Or a tut on how
brad2192 said:
I have seen a lot of issues with soft bricking using SuperSU-Me and I have figured out the issue once and for all. Kingroot has been upset over the recent reputation attacks of their software and have disabled functionality of switching between Su applications. Just follow my steps and you'll be alright.
You're going to need a few files to get started, grab them from the attachment links at the bottom of this post.
1) Extract the mrw folder from "Replace_Kinguser_with_SuperSU-v2.4_2.zip" and place it onto the root of your INTERNAL STORAGE
2) Install the PROVIDED KINGROOT APK
3) Once step 1&2 are complete, navigate to the play store and download "Terminal Emulator"
4)Open Terminal Emulator and type "su" without quotations and grant root access.
5) Next, type sh /storage/sdcard0/mrw/root.sh
6) The process will take a minute and have a few error messages, DO NOT BE WORRIED
7) Open the Supersu app that was just installed and update binary, this should have no issues as the other methods have proven faulty.
8)Reboot and enjoy
Reason I did this was so I can use Flashfire to hopefully install Xposed, I'll let you know how it goes!
Click to expand...
Click to collapse
Took me 3 or 4 tries to root with KingRoot 4.1 on an Alcatel OT Elevate, reboots constantly while rooting. Will update you if I am successful replacing KingRoot with SuperSU
UPDATE:
1. I haven't rebooted yet. . . KingRoot is in its death throes before reboot, what remains is a KingRoot app icon in App Drawer, KingRoot folder, and config file on the root of internal storage.
2. SuperSU has primary control of root management, but. . .
second line in terminal (after running script):
Failure [DELETE_FAILED_INTERNAL_ERROR]
UPDATE: Ignore this error, upon reboot what remains of KingRoot will be removed, as in deleted. It is like KingRoot simply vanished (which it did). That includes that annoying icon in your phone's App Drawer. Failure [DELETE_FAILED_INTERNAL_ERROR] is the script leaving behind the KingRoot app/icon in App Drawer, and the folder at root on internal storage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. I did a search using ES File Explorer in the /system/app folder. . . no searches found anything with the word "king" or "kinguser" in them, "Kingroot" folder still at root of internal storage. I am looking manually also in that /system/app & system/data folder in emulated storage 0. I see no Kinguser.apk, and nothing in data folder in emulated sdcard0. I have not rebooted the Alcatel OT Elevate yet after running the script.
UPDATE:
I no longer have concerns about bricking an Alcatel OT Elevate. There is like a 0.01% chance of a brick occuring using this method. If this was a perfect world I'd have said 0.00% chance, but I am telling you your phone will not brick.
UPDATE: I rebooted into safe mode, and still no sign of KingRoot, so I figured while I was at it I might as well boot normal boot. So, after normal boot I check the Elevate's system files and sure as rain is wet no sign of KingRoot. So, this script says "f%#@ you" to KingRoot and kicks it's ass, then kills it, and buries it in a very deep grave. R.I.P. KingRoot, thanks for the root, but you will so NOT be missed.
After Reboot:
Normal Boot, obviously:
To KingRoot:
You thought you had us Alcatel owners and others beat, but we are victorious!!! @Mr. W0lf Long live the King!!! King W0lf has a nice ring to it. Ya know?
PS.
Great thanks to King Chainfire as well!!! @Chainfire Long live Chainfire!!! SuperSU is THE shiznit.
LONG LIVE THE KING!!!
LONG LIVE THE KING!!!
LONG LIVE THE KING!!!
@brad2192 Thanks for the post
cocokasper said:
does not work... the kingroot app you provided Fails to root device.
Click to expand...
Click to collapse
Does work, just have to keep trying with the provided KingRoot .apk Got it to work on an Alcatel OneTouch Elevate. No issues.
So everything goes well until it switches to SuperSU. It then says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Help would be appreciated.
Jsjs51 said:
So everything goes well until it switches to SuperSU. It then says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Help would be appreciated.
Click to expand...
Click to collapse
I've got the same issue. Ever figure this out?
I was trying a few other mods that took me to installing apps to toggle root but needed special SU and all that jazz...I was not very comfortable with installing another app just to toggle it.
So I tried a terminal command way and it worked well, but remembering the commands and typing it in all the time sucked so I found an updater script that will work just the same.
Only bug is reverting back might take two flashes because of the mounting another folder. I might try and solve it when I have time but works flashing it twice.
The code I used makes it easy to know if it's working....look at theses screenshots of the recovery log
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PokeFix.zip recovery messages:
renaming files bin = Root off
renaming files xbin = Root off
nothing to rename = already done
PokeFix-revert.zip recovery messages:
reverting files bin = Root on
reverting files xbin = Root on
nothing to revert = already done
Click to expand...
Click to collapse
How this works:
The script will look at the folders bin and xbin where the su files are located so simply remaning them suBU will kill root and apps that look for root...the other script renames it back to su from suBU so rooted again on boot! Simple and clean!
To confirm you can flash them and get the nothing to message just to make sure!
If you have root in other folders and this does not work let me know and I will try and make special zips.
Hope this helps you CATCH 'EM ALL and use android Pay of course.
DJDARKKNIGHT96
TeamBlackOut
Link to files:
Gimmie Pokemon and Android pay on CM
Gimmie Pokemon and Android pay on DU/SuperSU comming soon hopefully but this thread seems to work with systemless root http://forum.xda-developers.com/apps/supersu/suhide-t3450396/post68424603
@djdarkknight96 Nice job David!!! Awesome thinking
Sent from my Nexus 6P using XDA Labs
Seems this is the place I need to be for PoGo fix.
LG G2 d800. Custom LolPop ROM. Apparently I am no longer rooted, but the LP cust ROM must be causing the PoGo "not compatible". Have tried a few suggestions to no avail. Cant access TWRP anymore either. Any ideas?
davizzyus said:
Seems this is the place I need to be for PoGo fix.
LG G2 d800. Custom LolPop ROM. Apparently I am no longer rooted, but the LP cust ROM must be causing the PoGo "not compatible". Have tried a few suggestions to no avail. Cant access TWRP anymore either. Any ideas?
Click to expand...
Click to collapse
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done
djdarkknight96 said:
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done
Click to expand...
Click to collapse
Okay, used Kingroot, but It's acting kind of funny. I think it's rooted. At least it passed root checker app twice. Then tried to use Flashify to flash TWRP img. 2.8.6 which was on there as my recent recovery image. Tapped boot into recovery and the LG logo with the boot certificate error came up. I thought I was screwed, but hit power button, and it did a regular boot into Lolli.
I'm nervous about messing with it. Last thing I want is another brick. Is there a way to check for sure that TWRP is on there successfully?
And if it is, and if I am rooted, You're saying that entering all of that code into terminal command will work and allow Pogo? Sounds too good to be true. I'm sure I'll find another new and unusual way to brick that I haven't done yet...
---------- Post added at 07:05 PM ---------- Previous post was at 07:00 PM ----------
djdarkknight96 said:
Oh man no TWRP access, you need recovery or you could root then use a terminal app and do these commands to find and hide the files they check for.
I got that from G+ so no credit to me for that, and it inspired my script.
Reboot after done
Click to expand...
Click to collapse
Does this do the same as if I went into the file through ES File Explorer and delete the su out of xbin? That trick worked for me over the weekend after I flashed CM13 and MM. I think I read somewhere it only works on CM13.
davizzyus said:
Okay, used Kingroot, but It's acting kind of funny. I think it's rooted. At least it passed root checker app twice. Then tried to use Flashify to flash TWRP img. 2.8.6 which was on there as my recent recovery image. Tapped boot into recovery and the LG logo with the boot certificate error came up. I thought I was screwed, but hit power button, and it did a regular boot into Lolli.
I'm nervous about messing with it. Last thing I want is another brick. Is there a way to check for sure that TWRP is on there successfully?
And if it is, and if I am rooted, You're saying that entering all of that code into terminal command will work and allow Pogo? Sounds too good to be true. I'm sure I'll find another new and unusual way to brick that I haven't done yet...
---------- Post added at 07:05 PM ---------- Previous post was at 07:00 PM ----------
Does this do the same as if I went into the file through ES File Explorer and delete the su out of xbin? That trick worked for me over the weekend after I flashed CM13 and MM. I think I read somewhere it only works on CM13.
Click to expand...
Click to collapse
If you boot recovery then it's safe now. Yes that script worked on non systemless root but I got lazy and made zips to do the same thing in recovery. While Android is running I wouldn't delete Root files..Just a bad feeling. I go to recovery for all system files just for piece of mind lol
djdarkknight96 said:
If you boot recovery then it's safe now. Yes that script worked on non systemless root but I got lazy and made zips to do the same thing in recovery. While Android is running I wouldn't delete Root files..Just a bad feeling. I go to recovery for all system files just for piece of mind lol
Click to expand...
Click to collapse
Someone suggested renaming the files, instead of deleting them. Also, I don't want MM. I prefer LP. Do you know if I can flash CM 13 and run Lollipop on it?
I'm still really new to all this.
davizzyus said:
Someone suggested renaming the files, instead of deleting them. Also, I don't want MM. I prefer LP. Do you know if I can flash CM 13 and run Lollipop on it?
I'm still really new to all this.
Click to expand...
Click to collapse
My script does rename them inside the zip, I just got the idea from that pic on G+. CM13 is Marshmallow though lollipop would be CM12....I recommend whatever runs good on your device. I use CM13 but I'm a Nexus user.
Yeah, that's what I thought. I just wasn't a fan of MM when I used it for a day last weekend, plus PoGo would freeze for a second or two every time I caught one. Anyway, thanks for your feedback. Maybe someone will come up with a workaround, or maybe those Niantic F"ers Will come to their senses and stop their idiocy of blocking innocent root users.
Hi @djdarkknight96, could please help me on my HTC Desire 620? I successfully flashed the PokerFix.zip file, however after rebooting, Android Pay still identifying the device as rooted, unlocked bootloader or running a custom ROM...any ideas? Many thanks in advance.
ptreber said:
Hi @djdarkknight96, could please help me on my HTC Desire 620? I successfully flashed the PokerFix.zip file, however after rebooting, Android Pay still identifying the device as rooted, unlocked bootloader or running a custom ROM...any ideas? Many thanks in advance.
Click to expand...
Click to collapse
I'm using Magisk now, this mod only worked on Cyanogen mod 13 but Magisk is great and gives root and safety net passes.
Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk
Do you need to reflash stock kernel before removing root/TWRP before flashing?
32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.
TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.
If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away
jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3
Finally I Get Root On S6 Verizon with nougat :laugh: :laugh:
Edit For those didn't work with them use this
https://forum.xda-developers.com/ve...al/rom-offical-nougat-pre-rooted-rom-t3718155
There Is a Proof In Attachments
My Rom DQD1
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
Edit :
A Video Proof And How To Do
In Description Of Video I add link to my rom
To Root You Will Need The Following Files :
G920V_ENG_ROOT_B4_ 7.0 , Root Files and Odin In The Attachments
First Extract G920V_ENG_ROOT_B4_ 7.zip
Flash G920V_ENG_ROOT_B4_ 7.0.tar with odin in AP
After Reboot make Sure You enabled usb debugging go to Settings and tap on About Phone. Tab Software Info Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it
Plug Your Device To Pc
Now Extract S6Root_Unroot_SU_2_79.zip
Plug your phone into the computer
Enter The Folder S6Root_Unroot_SU_2_79 And Double Click On root.bat
If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wait for minute your phone will reboot automatically
Your Phone Will reboot 2 time on 3 will boot
Every Time You will reboot your device it will reboot 2 time on 3 will boot because we have loocked bootloader
Dont Forget To hit Thanks Button
sorry For My Bad English
where is the proofs?
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.
NerdTronik said:
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.
Click to expand...
Click to collapse
You Are Right I will Post ScreenShot
NerdTronik said:
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.
Click to expand...
Click to collapse
I Added Proof In Attachments Check them
Ok, I have a problem with the adb, I tried many times but it still freezing and my cellphone screen too, I searched in the internet many ways to mount the system partition as read and write but all failed. Im thinking that the problem is the nougat version, I have the J1 and Im downloading the D1. Pst, the drivers and the cables are ok, I used another adb codes and they worked.
Seems like it only works on Qd1, so if have updated QI1 or QJ1, got to flash back to Qd1 to get it to work
...
I flashed DQD1 via Odin and after that, I flashed the .tar, but it still freezing my screen, I tried first without flashing the .tar because after flashing the firmware, the custom logo appeared. But again, the adb process failed, itsn freezed like the other but was unable to copy the su.img
---------- Post added at 07:06 PM ---------- Previous post was at 06:13 PM ----------
I did the same process that you made, so, I don't know why this happen, can you please assist this?? The phone doesn't matter, I just want to prove if this really work. I'll be amazed if this really do.
I´m facing the same problem on my device as @NerdTronik , just frezes when try to remount system as rewritable.. No succes as yet and I'm on Qd1 with the same kernel version.. Dont know How you Got to succesfully Remounted the system..
Another one stuck scratching my head with the phone locking when the batch script gets to the first adb shell mount command. The flash to DQD1 (from here, all 4 files) went fine. Flashed the new boot image without issue, reboot reflects custom image. Enabled debugging, connected with ADB, but that mount would be the final thing that would occur. Hoping this is just something we need clarified in the instructions.
Ok for all of your problem tonight i will make a youtube video learn how to root with the proof of it ☺?
Thanks for the root! Tell me, after I get the root of what custom firmware I can put? I understand you only need the development of verizon?
I did a Google for the the boot image file name and came across this link:
http://www.techzai.com/eng-root-file-samsung-android-7-nougat/
NOTE: I accessed this via Google's cache, and with NoScript plugin in Firefox. The firewall I was accessing through blocked the site for a reason... unsure if that could be that it isn't safe, work just didn't want me going there during business, etc. Go at your own risk.
But one thing that was noted in those instructions was to not only enable USB Debugging, but to also enable OEM Unlock in the developer options.
The thread for the S7 (which I think would apply but we just need to use the later released S6 boot image) mentions disabling secure startup. https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Might have time to play around with this more during the coming weekend, but maybe @faw_wal or another member will get additional info before then.
Don't work in my phone
So has any one else been able to confirm this as a working method?
DonaldAnderson said:
So has any one else been able to confirm this as a working method?
Click to expand...
Click to collapse
@DonaldAnderson
I was made a video about method but from begin when i flash the reactivation lock was on and now it's locked if you want a video with a proof i can post it for you and tomorrow i will post the full video do you want a proof video now ?
faw_wal said:
Finally I Get Root On S6 Verizon with nougat :laugh: :laugh:
There Is a Proof In Attachments
My Rom DQD1
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
To Root You Will Need The Following Files :
G920V_ENG_ROOT_B4_ 7.0 , Root Files and Odin In The Attachments
First Extract G920V_ENG_ROOT_B4_ 7.zip
Flash G920V_ENG_ROOT_B4_ 7.0.tar with odin in AP
After Reboot make Sure You enabled usb debugging go to Settings and tap on About Phone. Tab Software Info Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it
Plug Your Device To Pc
Now Extract S6Root_Unroot_SU_2_79.zip
Plug your phone into the computer
Enter The Folder S6Root_Unroot_SU_2_79 And Double Click On root.bat
If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
wait for minute your phone will reboot automatically
Your Phone Will reboot 2 time on 3 will boot
Every Time You will reboot your device it will reboot 2 time on 3 will boot because we have loocked bootloader
Dont Forget To hit Thanks Button
sorry For My Bad English
Click to expand...
Click to collapse
Don't you think your omitting a step??, we all follow each step you pointed in the instructions and got the same problem, devices just freezes when execute the root.bat
faw_wal said:
@DonaldAnderson
I was made a video about method but from begin when i flash the reactivation lock was on and now it's locked if you want a video with a proof i can post it for you and tomorrow i will post the full video do you want a proof video now ?
Click to expand...
Click to collapse
I think that it will be nice, I'll be waiting for it in a few hours. We just want to solve the errors, exactly the mounting system partition process.
can you tell me how to do that? when i double click root.bat my homegreen freezy?
can you tell me how to do that? when i double click root.bat my homegreen freezy
motorec said:
Thanks for the root! Tell me, after I get the root of what custom firmware I can put? I understand you only need the development of verizon?
Click to expand...
Click to collapse
I was doing a research and found this thread with the same problem as us ,seems like its knox that blocking the system remount.https://forum.xda-developers.com/att-galaxy-s6/general/root-att-samsung-g920a-s6-g925a-s7edge-t3564637
DDwhite said:
I was doing a research and found this thread with the same problem as us ,seems like its knox that blocking the system remount.https://forum.xda-developers.com/at...ot-att-samsung-g920a-s6-g925a-s7edge-t3564637
Click to expand...
Click to collapse
Oh nice, it's just seems impossible until somebody find the method to write in the system partition, in the thread you posted here, there was a man saying that we need to flash or do something before run root.bat, he didn't checked before but, sounds like a development.
http://rootjunkysdl.com/files/?dir=Gates/DeBloater