Related
Anybody rooted this one yet?
Sent from my SM-G860P using XDA Free mobile app
cortacanya said:
Anybody rooted this one yet?
Sent from my SM-G860P using XDA Free mobile app
Click to expand...
Click to collapse
Towelroot should work. It works on the standard S5 and AT&T S5 active as well as Verizon variants.
CCallahan said:
Towelroot should work. It works on the standard S5 and AT&T S5 active as well as Verizon variants.
Click to expand...
Click to collapse
tries and just hung there
cortacanya said:
tries and just hung there
Click to expand...
Click to collapse
Correction-- app says
"phone isnt currently supported"
Sprint Galaxy S5 Sport
I am interested in this as well.
My searches have only turned up false leads.
Model: SM-G860P
Kernel Version: 3.4.0-2113914
Kernel Date:: July 11 2014
cortacanya said:
tries and just hung there
Click to expand...
Click to collapse
Go to device info in settings and look at the Kernel version. What date is listed?
**EDIT...NM, I see the kernel date listed in dallas532's sig as July 11. Towelroot will not work with Kernel dated after June 3rd.
You can put in a request to CF here to create a working CF Auto Root for your device. Just be sure to post the recovery.img file as listed in the OP if/when the source code is available.
CCallahan said:
Go to device info in settings and look at the Kernel version. What date is listed?
**EDIT...NM, I see the kernel date listed in dallas532's sig as July 11. Towelroot will not work with Kernel dated after June 3rd.
You can put in a request to CF here to create a working CF Auto Root for your device. Just be sure to post the recovery.img file as listed in the OP if/when the source code is available.
Click to expand...
Click to collapse
Request has been made!
I returned mine on launch day for a regular gold s5 because of the software differences. I tried all different ways I could think of to root and couldn't get a recovery to stick without soft bricking the phone.
Sent from my SM-G900P using XDA mobile app
s5 active 860p
i hope someone can help with root...i will donate to whoever makes this happen,or points me in right direction.
tomlirr324 said:
i hope someone can help with root...i will donate to whoever makes this happen,or points me in right direction.
Click to expand...
Click to collapse
Any updates on root for the S5 Sport? I really like this phone but there's no way I'm owning a phone w/o root & AdAway!! Thx
UPdownLoAD said:
Any updates on root for the S5 Sport? I really like this phone but there's no way I'm owning a phone w/o root & AdAway!! Thx
Click to expand...
Click to collapse
I am still awaiting a reply from anyone, I check on websites daily, made a request to CF, even downloaded vroot and tried...nothing yet
UPdownLoAD said:
Any updates on root for the S5 Sport? I really like this phone but there's no way I'm owning a phone w/o root & AdAway!! Thx
Click to expand...
Click to collapse
I feel the same way. I knew I should have purchased the regular S5. Damn it. I guess we're stuck. If anyone hears anything please post it here. I'll do the same. Thanks !
I'd be willing to trade my regular Sprint s5 for the sport if anyone is interested. Message me.
Yes, the GS5 Sport (Sprint SM-G860P) is rootable
cortacanya said:
Anybody rooted this one yet?
Sent from my SM-G860P using XDA Free mobile app
Click to expand...
Click to collapse
UPdownLoAD said:
Any updates on root for the S5 Sport? I really like this phone but there's no way I'm owning a phone w/o root & AdAway!! Thx
Click to expand...
Click to collapse
Good to see ya interested in this phone too, UPdownLoAD! I hope all went well with the Torque dev when I had to pop off of the grid right after rooting that (this one is A LOT easier...trust me).
I just bought this phone earlier this week and hadn't looked into its rootability. I figured that, since it is a Samsung phone on Sprint, it would have an unlocked bootloader (and it does). There are, however, zero support tools for these. This is not TowelRoot eligible due to the newer patched kernel and is not on the CF-Auto-Root list yet.
I took a little time during the LLWS today to get this thing rooted and confirmed before I go out of town on business for a week and it turned out just fine.
Solution: Simply employing the use of a custom recovery and using the "fix su binaries" and "prevent stock recovery flashing" options upon exiting after entering the recovery.
Ok, yes, there is no official release of CWM, TWRP or Philz for this device yet. I have a custom recovery that is in Chinese that I, personally, know how to decipher, but would not release it here*. Hopefully, there is an official recovery on the way or someone properly builds one in English. CWM used to have an automated recovery builder tool server-side, but I think it has been offline since March of this year. Again, I am about to head out on business soon and don't have a lot of time until on my flights to dig more into this, but wanted to give the certain thumbs up to anyone considering this phone but didn't know if it would have root.:good::good::good:
In summary: YES, the Sprint Samsung Galaxy S 5 Sport (SM-G860P) on the latest OTA build (NG3) is rootable just fine.
*Please do not ask me for the recovery that I have...Google is your friend (it's only in a single public location as of right now), but I did not want to be responsible for someone grabbing it and guessing what characters mean and borking their phone.
I need help.
VicFreeze said:
Good to see ya interested in this phone too, UPdownLoAD! I hope all went well with the Torque dev when I had to pop off of the grid right after rooting that (this one is A LOT easier...trust me).
I just bought this phone earlier this week and hadn't looked into its rootability. I figured that, since it is a Samsung phone on Sprint, it would have an unlocked bootloader (and it does). There are, however, zero support tools for these. This is not TowelRoot eligible due to the newer patched kernel and is not on the CF-Auto-Root list yet.
I took a little time during the LLWS today to get this thing rooted and confirmed before I go out of town on business for a week and it turned out just fine.
Solution: Simply employing the use of a custom recovery and using the "fix su binaries" and "prevent stock recovery flashing" options upon exiting after entering the recovery.
Ok, yes, there is no official release of CWM, TWRP or Philz for this device yet. I have a custom recovery that is in Chinese that I, personally, know how to decipher, but would not release it here*. Hopefully, there is an official recovery on the way or someone properly builds one in English. CWM used to have an automated recovery builder tool server-side, but I think it has been offline since March of this year. Again, I am about to head out on business soon and don't have a lot of time until on my flights to dig more into this, but wanted to give the certain thumbs up to anyone considering this phone but didn't know if it would have root.:good::good::good:
In summary: YES, the Sprint Samsung Galaxy S 5 Sport (SM-G860P) on the latest OTA build (NG3) is rootable just fine.
*Please do not ask me for the recovery that I have...Google is your friend (it's only in a single public location as of right now), but I did not want to be responsible for someone grabbing it and guessing what characters mean and borking their phone.
Click to expand...
Click to collapse
So I have tried to root my gs5 sport and have ran into a big problem. I think it is a big problem. My phone did not like the rooting that I tried and now is restarting over and over. I don't know what to do. Any help would be nice. Thanks
nate2mars said:
So I have tried to root my gs5 sport and have ran into a big problem. I think it is a big problem. My phone did not like the rooting that I tried and now is restarting over and over. I don't know what to do. Any help would be nice. Thanks
Click to expand...
Click to collapse
Most likely you'd need the Stock The file to Odin back to stock. But I'm not even sure those are available. Least I haven't seen anything mentioned about em.
Not sure what root method you tried, but there's been alot of talk going around for a week or so, that neither cf root, or towelroot methods don't work.
Next time (to be totally safe) it may be best to wait for a stock tar file to be available, before Taking a chance like this. Just a thought. Head to the SamMobile website and look up your devise to see if they got the Stock tar up. Still a pretty new device, so not sure if they'll be around yet. That sux tho.
Good luck!
Sent from my SM-G900P using Tapatalk
nate2mars said:
So I have tried to root my gs5 sport and have ran into a big problem. I think it is a big problem. My phone did not like the rooting that I tried and now is restarting over and over. I don't know what to do. Any help would be nice. Thanks
Click to expand...
Click to collapse
The NG2 and NG3 tars are out. Get NG3 and prepare to wipe the entire device if you Odin the whole tar. It would be more helpful to know what you actually did (the method) versus saying "I tried to root". Since there is no automated root specific to this device yet and TowelRoot would not cause a bootloop, you likely ran something you certainly should not have (if it wasn't made for this phone model, why would you do that?) You've likely hosed up the phone/system to the point where you have to run the full tar (versus just the boot/kernel or the modem to "fix" with your user & system data in tact).
Grab the NG3 tar from sammobile or samsung-firmwares and Odin back to stock.
FYI TO ALL: everything is running smoothly after running my Titanium Backup restore from my old GS5 and pushing in Xposed modules. Also have successfully applied the hotspot tweak to my telephony.db and SD card write access. Hopefully I get some time during flights with Wi-Fi to pump out a recovery worth wide-releasing sometime this week if no one else chimes in.
Sent from my SM-G860P using Tapatalk
I await patiently for some one to root and a custom recovery. I actually like this phone and prefer it over the regular but awesome GS5. I just wish for more support. I have rooted and customized every android phone I have gotten within a day of purchase, so it became habit and ritual. Now I sit here waiting patiently.
cortacanya said:
I await patiently for some one to root and a custom recovery. I actually like this phone and prefer it over the regular but awesome GS5. I just wish for more support. I have rooted and customized every android phone I have gotten within a day of purchase, so it became habit and ritual. Now I sit here waiting patiently.
Click to expand...
Click to collapse
Chainfire has posted Auto Root for the G860P:laugh:
cortacanya said:
Chainfire has posted Auto Root for the G860P:laugh:
Click to expand...
Click to collapse
Indeed. Here is a link to the CF-Auto-Root download:
http://download.chainfire.eu/460/CF...-Root-kltesprsports-kltesprsports-smg860p.zip
Just download, extract and flash the Tar with Odin using the PDA option. Let the device reboot into the temporary recovery and self-root.
Sent from my SM-G860P using Tapatalk Pro
I got my one plus one 64gb from a friend and it has ColorOs ver 1.2.0 installed on it. He said that the device is new and has never been used before but this seems odd to me as it should have come with CM11S pre installed. It has the "Global version" logo on the back package. Is there a simple guide/way that I can use to switch to CM11S or any other rom?
dilgit said:
I got my one plus one 64gb from a friend and it has ColorOs ver 1.2.0 installed on it. He said that the device is new and has never been used before but this seems odd to me as it should have come with CM11S pre installed. It has the "Global version" logo on the back package. Is there a simple guide/way that I can use to switch to CM11S or any other rom?
Click to expand...
Click to collapse
Do some research my friend this is xda all the info you need is right in front of you but you need to read. First off check if its been rooted or has a custom recovery. Please do not use a toolkit as they may cause issues down the line. Does it say CM on the back of the phone?
Main thing is everything is simple if you just read and take your time. From the way you asked your question not sure if you ever rooted before? Google the differences my friend Google it
playya said:
Do some research my friend this is xda all the info you need is right in front of you but you need to read. First off check if its been rooted or has a custom recovery. Please do not use a toolkit as they may cause issues down the line. Does it say CM on the back of the phone?
Main thing is everything is simple if you just read and take your time. From the way you asked your question not sure if you ever rooted before? Google the differences my friend Google it
Click to expand...
Click to collapse
Thanks. I've googled this as much as I can, but can't find a way to switch from ColorOs to CM11S. I'm really stuck and need you help. The device is recognised by windows 8.1 and I transferred the CM11 r33 zip file to the device. When I go into ColorOs recovery mode on the device, and try to install CM from there, it fails. When I go to fastboot mode and I try to unlock the bootloader on the device in order to go on and flash a recovery and than root... It fails. What can I do? I can't stay with the ColorOs...
Ok. Now I'm completely stuck, on bootloader logo, and no OS!! I can still enter recovery TWRP 2.8.0.1 or fastboot mod. I have unlocked the bootloader, rooted the device, wiped all and did not backup. When I tried to flash the latest CM11 it failed and there I am. No OS and device is not recognised by computer(win 8.1) so I cannot transfer files to the device anymore... What do I do now? How do I get this working once again? Thanks for your help!!
What's the full filename of the CM11S zip you flashed?
Also, if you got your phone from a friend, where on earth did the invite I gave you go to?
Transmitted via Bacon
timmaaa said:
What's the full filename of the CM11S zip you flashed?
Also, if you got your phone from a friend, where on earth did the invite I gave you go to?
Transmitted via Bacon
Click to expand...
Click to collapse
The device coming from your invite, should arrive today and I'm sure it will be with CM11S.
The stuck device I bought second hand from a friend.
I tried to flash cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Now its not possible to transfer new files to the device and the computer does not recognise the device
when it's in fastboot mod.
dilgit said:
The device coming from your invite, should arrive today and I'm sure it will be with CM11S.
The stuck device I bought second hand from a friend.
I tried to flash cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Now its not possible to transfer new files to the device and the computer does not recognise the device
when it's in fastboot mod.
Click to expand...
Click to collapse
The invite thread is only for people that don't have the device, and that's clear in the OP, which you said you read and agreed to.
Transmitted via Bacon
timmaaa said:
The invite thread is only for people that don't have the device, and that's clear in the OP, which you said you read and agreed to.
Transmitted via Bacon
Click to expand...
Click to collapse
Dear timmaaa... When you sent me the invite I did not have the device. While it was on it's way to me, I bought a used one for my daughter. Now that's the one that is currently stuck with no OS on it. The Device I ordered from One + with the invite you sent me, arrived today, has CM11 on board and works perfectly.
dilgit said:
Dear timmaaa... When you sent me the invite I did not have the device. While it was on it's way to me, I bought a used one for my daughter. Now that's the one that is currently stuck with no OS on it. The Device I ordered from One + with the invite you sent me, arrived today, has CM11 on board and works perfectly.
Click to expand...
Click to collapse
This isn't adding up to me, you told me you wanted another invite for your son.
Transmitted via Bacon
timmaaa said:
This isn't adding up to me, you told me you wanted another invite for your son.
Transmitted via Bacon
Click to expand...
Click to collapse
Correct. And you told me it's not possible. So I purchased another device. By the way, I figured out the issue I had with the instructions I found on this link: http://forum.xda-developers.com/showthread.php?t=2765455... Worked just fine to me... Now I'm on CM11 and my daughter will get a wonderful present... timmaaa, I'm sorry if I offended you. I use the device I got today thanks to you and good people on this forum and I'm grateful to you. I needed another device and purchased one on the free market. Thank you and sorry if I did something wrong.
I'm trying to install Cyanogenmod to my Nexus 5. (I installed it successfully to my Nexus 7 2012 and was very pleased with it.) I've been following the instructions on this page: http://wiki.cyanogenmod.org/w/Install_CM_for_hammerhead, but I can't get Clockworkmod to mount the /data partition. I get an error. It just says "Error mounting /data!" and nothing else.
I get numerous other errors when trying to do just about anything else. I've also tried reinstalling Clockworkmod.
This is kinda/sorta urgent, because I'm without a phone until I can get this resolved. [**Another update: Not as urgent as I thought because Lollipop does boot up after all. Still, I really like CM and I'd love a solution.]
Update: One thing I should have mentioned is that I'm using adb and fastboot in Linux Mint 17.1. I don't know how relevant that is, but I thought it was worth mentioning.
Get rid of Clockworkmod, it's outdated and was discontinued quite a while ago. Use TWRP 2.7.1.0.
BirchBarlow said:
Get rid of Clockworkmod, it's outdated and was discontinued quite a while ago. Use TWRP 2.7.1.0.
Click to expand...
Click to collapse
Well, that's interesting; I had no idea. Would the instructions on that page be more-or-less the same, but with TWRP?
Update: So far, seems to have worked. The phone is booting into Cyanogenmod right now for the first time. I'll report back if there are any problems, but so far everything looks fine.
To answer my own question (for anybody who may come across this via Google), the instructions on that page do actually work almost identically with TWRP. Also, TWRP 2.8 did not work for me, but the specific number listed by BirchBarlow did.
Again, to BirchBarlow, thank you very much!
adanedhel728 said:
Well, that's interesting; I had no idea. Would the instructions on that page be more-or-less the same, but with TWRP?
Update: So far, seems to have worked. The phone is booting into Cyanogenmod right now for the first time. I'll report back if there are any problems, but so far everything looks fine.
To answer my own question (for anybody who may come across this via Google), the instructions on that page do actually work almost identically with TWRP. Also, TWRP 2.8 did not work for me, but the specific number listed by BirchBarlow did.
Again, to BirchBarlow, thank you very much!
Click to expand...
Click to collapse
*headbang* I meant to say TWRP 2.8.1.0 (2.8.2.0 is faulty), but anyway you're welcome.
BirchBarlow said:
*headbang* I meant to say TWRP 2.8.1.0 (2.8.2.0 is faulty), but anyway you're welcome.
Click to expand...
Click to collapse
Haha, glad to know it.
i have my sch-1925 rooted with Kingroot. Now I am following these instructions:
androidbits how to install Android 6.0 Marshmallo CyanogenMod 13 [CM13] Rom on Verizon Samsung Galaxy Note 10.1 SCH-I925 [Simple Steps]
will not let me post the link you will have to google it
I have TWRP downloaded from Google Play and when I open that App and try to do the install inside the app I get an error message that says
Something went wrong
Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now? No Yes
Yes makes the app unresponsive.
Any Suggestions
MIKEOS98 said:
i have my sch-1925 rooted with Kingroot. Now I am following these instructions:
androidbits how to install Android 6.0 Marshmallo CyanogenMod 13 [CM13] Rom on Verizon Samsung Galaxy Note 10.1 SCH-I925 [Simple Steps]
will not let me post the link you will have to google it
I have TWRP downloaded from Google Play and when I open that App and try to do the install inside the app I get an error message that says
Something went wrong
Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now? No Yes
Yes makes the app unresponsive.
Any Suggestions
Click to expand...
Click to collapse
Hi,
I think that your problem is due to the fact that your Note 10.1 is a Verizon one, which means that the bootloader of your tablet is probably locked and will be difficult to unlock. You will not be able to install TWRP nor any other custom recovery without unlocking this bootloader
Sent from my GT-N8013 using XDA-Developers mobile app
DroidHiker63 said:
Hi,
I think that your problem is due to the fact that your Note 10.1 is a Verizon one, which means that the bootloader of your tablet is probably locked and will be difficult to unlock. You will not be able to install TWRP nor any other custom recovery without unlocking this bootloader
Sent from my GT-N8013 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah. I am in the same boat. Have been looking up and down to see what I can do but nothing so far.
Hmmm.... https://wiki.cyanogenmod.org/w/Install_CM_for_i925 ???
dimitriz75 said:
Yeah. I am in the same boat. Have been looking up and down to see what I can do but nothing so far.
Hmmm.... https://wiki.cyanogenmod.org/w/Install_CM_for_i925 ???
Click to expand...
Click to collapse
Maybe this could work, but honestly I don't know if it will.
I also owe a Moto X 2014 and I know that some peoples who owe the Verizon version managed to unlock their bootloaders with a tool called Sunshine, which they had to pay for (25$ ) but which worked well. I don't know if this could work with your Note 10 because it's an older device than the Moto X 2014, but maybe this could be a solution.
Sent from my GT-N8013 using XDA-Developers mobile app
DroidHiker63 said:
Maybe this could work, but honestly I don't know if it will.
I also owe a Moto X 2014 and I know that some peoples who owe the Verizon version managed to unlock their bootloaders with a tool called Sunshine, which they had to pay for (25$ ) but which worked well. I don't know if this could work with your Note 10 because it's an older device than the Moto X 2014, but maybe this could be a solution.
Sent from my GT-N8013 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nah, They only support Moto and HTC. I saw nothing about Samsung on their website.
Somebody in another thread said that it's possible through ADB. I am gonna give it a shot when I am back at work on Monday.
Stupid Verizon!, lol. They whine about having unlocked devices on their network as being a problem yet all the Xoom's we have at work can be bootunlocked without any problems.
They seriously about to loose our business account over this stuff as I gotta purchase 50+ tablets.
Adb
Any luck with adb?
MIKEOS98 said:
Any luck with adb?
Click to expand...
Click to collapse
Sorry, was dragged out on a business trip.
Will add to my calendar for Monday test.
Update on Monday!
dimitriz75 said:
Sorry, was dragged out on a business trip.
Will add to my calendar for Monday test.
Update on Monday!
Click to expand...
Click to collapse
Ok, I just tried but nothing
when I issue "adb reboot bootloader" it reboots but goes back to OS.
not sure I am a n00b at this., lol
I also set it to Download mode but adb doesnt see the tablet.
Hi everyone,
I have a the Google edition of Pixel, and have unlocked the bootloader successfully. I would like to root the device somethow, as well as get tether working. I am on Vzw's original unlimited data plan, and this phone has replaced my wife's Samsung Galaxy S3 phone on verizon. We held on to the S3 for so long as it is rooted and with the ROM we could tether using Vzw's tether and pay nothing extra.
What can I do to get back into a similar situation with this Google Pixel?
Thanks so much in advance.
statustray said:
Hi everyone,
I have a the Google edition of Pixel, and have unlocked the bootloader successfully. I would like to root the device somethow, as well as get tether working. I am on Vzw's original unlimited data plan, and this phone has replaced my wife's Samsung Galaxy S3 phone on verizon. We held on to the S3 for so long as it is rooted and with the ROM we could tether using Vzw's tether and pay nothing extra.
What can I do to get back into a similar situation with this Google Pixel?
Thanks so much in advance.
Click to expand...
Click to collapse
Install twrp and flash magisk for root. Any root tether app should be able to treat your tether data as standard data
KittyRgnarok said:
Install twrp and flash magisk for root. Any root tether app should be able to treat your tether data as standard data
Click to expand...
Click to collapse
Thanks KittyRgnarok,
Do you have a link for Twrp for Google Pixel and also one for majisk? It seems some threads are old, and I don't want to mess things up.
Thanks so much in advance.
statustray said:
Thanks KittyRgnarok,
Do you have a link for Twrp for Google Pixel and also one for majisk? It seems some threads are old, and I don't want to mess things up.
Thanks so much in advance.
Click to expand...
Click to collapse
Haha good on you for asking cuz quite a few people have gotten close to bricking their devices using the boot-to-root method from the day the phone released lmao. A quick Google search for "twrp sailfish" will bring u to the latest version of official twrp. As far as magisk just look up magisk on XDA and the official thread will have the dl link (don't download magisk from anywhere else)
There's a Magisk "Tethering Enabler" module which I recommend you try, after you're rooted.
KittyRgnarok said:
Haha good on you for asking cuz quite a few people have gotten close to bricking their devices using the boot-to-root method from the day the phone released lmao. A quick Google search for "twrp sailfish" will bring u to the latest version of official twrp. As far as magisk just look up magisk on XDA and the official thread will have the dl link (don't download magisk from anywhere else)
Click to expand...
Click to collapse
mike.s said:
There's a Magisk "Tethering Enabler" module which I recommend you try, after you're rooted.
Click to expand...
Click to collapse
Thanks fur the info KittyRgnarok and mike.s,
I will try to do that tomorrow. Got sidetracked by a few other honey dos. Will try my very best to get back on this tomorrow. I hope you don't mind me reaching tomorrow evening after I get off work.
TIA
statustray said:
Thanks fur the info KittyRgnarok and mike.s,
I will try to do that tomorrow. Got sidetracked by a few other honey dos. Will try my very best to get back on this tomorrow. I hope you don't mind me reaching tomorrow evening after I get off work.
TIA
Click to expand...
Click to collapse
No problem man and no worries. If you find yourself needing any help feel free to quote me in the thread or pm me.
KittyRgnarok said:
No problem man and no worries. If you find yourself needing any help feel free to quote me in the thread or pm me.
Click to expand...
Click to collapse
Hi KittRgnarok,
I have downloaded the following to my computer:
twrp-3.2.1-2-sailfish.img
twrp-pixel-installer-sailfish-3.1.1-2.zip
Magisk-v16.0.zip
My computer is a macbook pro so I don't believe I need any additional drivers as supposedly they are already available in the Mac OS. I was able to unlock my bootloader using a terminal session & adb.
How should I now proceed?
Thanks in advance.
statustray said:
Hi KittRgnarok,
I have downloaded the following to my computer:
twrp-3.2.1-2-sailfish.img
twrp-pixel-installer-sailfish-3.1.1-2.zip
Magisk-v16.0.zip
My computer is a macbook pro so I don't believe I need any additional drivers as supposedly they are already available in the Mac OS. I was able to unlock my bootloader using a terminal session & adb.
How should I now proceed?
Thanks in advance.
Click to expand...
Click to collapse
Correct MacBook shouldn't needed additional drivers. Put the magisk and twrp zip files on your phone. Then reboot into bootloader. From there use the command fastboot boot twrp-3.2.1-2-sailfish.img which should put you into ram version of twrp. From here decrypt your device and install the twrp installer zip file. Once that's done reboot into recovery and flash magisk and you should be good to go
I finally got it figured out I have installed TWRP, as well as Majisk. I've tested root using a root tester, and now I need to see about the module that mike.s was referring to- specifically "tethering enabler".
All this stuff is totally new to me, so I am creeping along at a slow pace... lol
statustray said:
I finally got it figured out I have installed TWRP, as well as Majisk. I've tested root using a root tester, and now I need to see about the module that mike.s was referring to- specifically "tethering enabler".
All this stuff is totally new to me, so I am creeping along at a slow pace... lol
Click to expand...
Click to collapse
In magisk manager there is a downloads tab and a modules tab. Go to the downloads tab and look for tether and you'll find it
KittyRgnarok said:
Correct MacBook shouldn't needed additional drivers. Put the magisk and twrp zip files on your phone. Then reboot into bootloader. From there use the command fastboot boot twrp-3.2.1-2-sailfish.img which should put you into ram version of twrp. From here decrypt your device and install the twrp installer zip file. Once that's done reboot into recovery and flash magisk and you should be good to go
Click to expand...
Click to collapse
You must've been posting as I was typing my message to you. I'm just now seeing that you provided some steps. Yes, I had figured that out and got it done. Life's good now.
I am doing some searching trying to figure out tethering, that's the last piece of the equation for now... hehehe..... On the old vzw unlimited data plan and I don't want to switch over to their new plans. If I can get this going, then my better half will be super happy, and then I will look into getting me a Google Pixel (but the XL version).
KittyRgnarok said:
In magisk manager there is a downloads tab and a modules tab. Go to the downloads tab and look for tether and you'll find it
Click to expand...
Click to collapse
Thanks so much KittyRgnarok,
You pointed me in the right direction and I really appreciate that. It worked with no problems as I tested it and all's well. I then demonstrated it to my better half and she is super happy!!
Now I will order me one as well, but I am going to get the Google Pixel XL. I see the screen is larger on the Pixel 2, but heard there's been some "screen issues"? For me the lack of a phone jack is not all that big of a deal as I never hookup a wired headset and only use the bluetooth. *Ahem* on my phone I've only used a wired headset once or twice years ago when my bluetooth messed up. Lol....
Thanks again for everything!
:good:
statustray said:
Thanks so much KittyRgnarok,
You pointed me in the right direction and I really appreciate that. It worked with no problems as I tested it and all's well. I then demonstrated it to my better half and she is super happy!!
Now I will order me one as well, but I am going to get the Google Pixel XL. I see the screen is larger on the Pixel 2, but heard there's been some "screen issues"? For me the lack of a phone jack is not all that big of a deal as I never hookup a wired headset and only use the bluetooth. *Ahem* on my phone I've only used a wired headset once or twice years ago when my bluetooth messed up. Lol....
Thanks again for everything!
:good:
Click to expand...
Click to collapse
Glad to hear both you and her are happy with the results . As far as the pixel 2 xl a lot of the screen issues were software side but there are also issues with burn in(which I've experienced a decent amount of on the og as well) I have a friend with the pixel 2 and I highly recommend it but be aware that it is modding hell if you intend to be messing with a lot of that. As far as staying on stock rom+magisk+Xposed though it works great.
Hi everyone
Can anyone please let me know if the files he downloaded is the same files i need to do the same procedure, i have a normal google pixel 32gb from verizon which i unlocked the bootloader on 7.1 then upgraded to 8.1
S7sadly said:
Can anyone please let me know if the files he downloaded is the same files i need to do the same procedure, i have a normal google pixel 32gb from verizon which i unlocked the bootloader on 7.1 then upgraded to 8.1
Click to expand...
Click to collapse
Same files.
Thank you
KittyRgnarok said:
Glad to hear both you and her are happy with the results . As far as the pixel 2 xl a lot of the screen issues were software side but there are also issues with burn in(which I've experienced a decent amount of on the og as well) I have a friend with the pixel 2 and I highly recommend it but be aware that it is modding hell if you intend to be messing with a lot of that. As far as staying on stock rom+magisk+Xposed though it works great.
Click to expand...
Click to collapse
Thanks for the heads up on the Pixel 2 issues. I will probably stay with stock like on my better half's phone, and just want to root and tether. Now the burn ins, that kind of worries me. Hmmmm... decisons, decision... hehe...
To prevent burn in you can get the magisk module that hides the navbar and toggle that occasionally as that's the only place I really notice it aside from the statusbar which idk a way to hide. I've also heard inverting colours often can help prevent it
KittyRgnarok said:
To prevent burn in you can get the magisk module that hides the navbar and toggle that occasionally as that's the only place I really notice it aside from the statusbar which idk a way to hide. I've also heard inverting colours often can help prevent it
Click to expand...
Click to collapse
Thanks for that information. I did not realize that. And sorry for the delay in responding. I didn't get on xda yesterday as I got back home late last night. I will certainly look for that magisk module you mentioned.
Oh and by the way, I just got me a Google Pixel XL today
Now I need to work the same magic on this one. I've already got it activated at the VZW Store near where I live. *Woohoo*