Hey guys. I'm sorry to ask the same question again (like others do) but i'm really confused. Today my pixel xl will arrive. I will unlock the bootloader, flash twrp and put a custom rom on it. I thought about lineageos 15.1. In the rom thread are advices that you have to be on 8.1. before everything will work smoothly. So my work process will be - wait for 8.1 OTA and then start all the processes.
But in some thread there's a warning that rooting will be difficult and in some others that there's no problem.
I really don't know what's the best way to do all this before something goes wrong. Can anybody help me out?
Related
Hi folks.
Been lurking for a while, but this is my first post.
I've been looking into rooting my SM-G870W (Galaxy S5 Active, Canadian, Telus) for a while now. It's currently updated to Android 6.0.1.
I've read a lot of different information and I've held off on actually trying it because of several posters saying they've bricked their phone or had no luck.
To the best of my knowledge and research, there is no "plug and play" app or program that will root automatically. Is this accurate?
I have read of manual recommendations or guides that say they work.
This site, being the foremost authority as far as I'm concerned, is my last step in research.
Can anyone please advise if this is possible for this phone and version?
If so, is there an existing guide that is reputable that I could follow?
I thank you in advance.
A little late to post. But I am having no luck rooting my SM-870W on Telus. I used Odin and the CF-Auto-Root-kltecanactive-kltevlactive-smg870w for Marshmallow 6.0.1
I just end up with "Recovery is SeAndroid enforcing"
I then have to flash back the stock rom
Tomorrow when I have time, I am going to downgrade back to Lollipop to root it. If successful, then I will use Flashfire to update to Marshmallow 6.0.1 and see how that goes.
Well so far I successfully downgraded my phone back to Lollipop and rerooted it. . Tomorrow or next week will try updating with flashfire
I tried again to root marshmallow using flashfire, and it boot looped. So just going to stay on Lollipop and keep rooted. Will probably upgrade phone soon anyway. I don't know how others on youtube etc say they have done it, but it's not working for me.
Thanks for posting
I too have the same model phone and I'm running into the exact same issue you are. Thanks for posting which lets me know I'm not the only one facing this problem
windrider42 said:
I tried again to root marshmallow using flashfire, and it boot looped. So just going to stay on Lollipop and keep rooted. Will probably upgrade phone soon anyway. I don't know how others on youtube etc say they have done it, but it's not working for me.
Click to expand...
Click to collapse
Hello. I'm pretty terrible at all this rooting stuff (or at least, I only do it once for each android phone I get, and then don't really look into it or stay up to date on all of it afterwards, I just use a few pluses that come along with being rooted).... Anyways, I really do need some help this time, as the confusion has really gotten to me, and I've lacked being able to find some simple answers (probably because they are just THAT simple) on google/reddit/on this forum.
Anyways, I've rooted my phone awhile back, lost it when my verizon pixel auto updated to 7.1.1 (idk how or why, pretty sure I had that disabled with root even, very frustrated) and even attempted to regain root by flashing SU with TWRP, but for some reason SU said I didn't have root still, and eventually just gave up in frustration. But now, my verizon pixel has been shutting off at ~40% battery power, and I read in the google forums that this was patched in the 7.1.2 update for pixels, and it was a software glitch rather than a malfunctioning/bad battery... So now I really want to upgrade to 7.1.2 from 7.1.1 not only to fix the battery/software issue, but also because I really want root.
I have an unlocked bootloader from when i first got my pixel and did this stuff, but now im unrooted on 7.1.1 because of that update awhile back, and want to update to 7.1.2 and root, but I've heard theres issues with rooting on the verizon because of bootloader, but that shoulden't be an issue since I unlocked it already (right? at least, I think? please let me know).
My only question (since i think i'll be able to follow this guide once I get the answer to this) is in the post he says: "Works with 7.1.2 (NJH47F, Aug 2017)".......... but since i have the verizon pixel (small version, not XL), should i be downloading this version: 7.1.2 (NHG47Q, Aug 2017, Verizon).... Or would it just be acceptable to allow my phone to auto download the update i have on it right now? Or must I download the NON verizon version as stated in the post and flash that one? Thanks for the help guys!
Thanks for any help!
-Synk
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
jhs39 said:
If your bootloader is actually unlocked then no update that you flash can lock it. The people that were having problems on Verizon had phones where the OEM Unlock option was there and then after a Verizon update was greyed out. But those people didn't have unlocked bootloaders. Once the bootloader on the phone is unlocked Verizon can't lock it again.
The Pixel phone isn't really a good one to root once and then forget about it because sometimes the instructions change--people needed to flash a boot signature file one month to maintain root but didn't need to do it anymore the following month. Sometimes a particular version of SU stops working after an update and you have to download a newer version. The Pixel isn't like a Nexus where flashing and rooting was simple and easy.
I don't know of any reason you wouldn't be able to root after flashing a Verizon image as long as your bootloader is unlocked but someone with experience rooting a Verizon phone would be better able to answer that.
Click to expand...
Click to collapse
Thank you so much for the explanation. Truly, it's actually crazy how I was unable to find all of this neatly, nicely, and simply stated. Great to hear, I'm going to go on rooting, here's to hoping I don't blow it up.
Hey everyone!
I wanted to root my Pixel 2 XL but I noticed that Oreo 8.1 is rolling out today. (Some of my friends already got the update, apparently). I wanted to know if I were to root my phone on 8.0, would I continue to have root when I update to 8.1 or would I have to redo the process again from the start?
Thank you in advance!
You have to be 100% stock to install an update from ota. You won't be able to install the update it will just fail as you would have a modified system.
rjbad1100 said:
Hey everyone! I wanted to root my Pixel 2 XL but I noticed that Oreo 8.1 is rolling out today. (Some of my friends already got the update, apparently). I wanted to know if I were to root my phone on 8.0, would I continue to have root when I update to 8.1 or would I have to redo the process again from the start? Thank you in advance!
Click to expand...
Click to collapse
At this point I would just wait if I were you. Let your device take 8.1 and then use one of the rooting tutorials. Otherwise (as you suspect) you will be doing things twice. I just got my device Saturday afternoon and couldn't wait, knowing this week we would be getting some kind of an update and I would have to re-apply. Unlocking and Critical Unlocking would be the first step if you haven't taken care of that yet. Just spend some time reading up on the method and correct sequence, downloading and placing the files you will need so that when the time comes you will be ready.
If you haven't unlocked the bootloader, now would be a good time.
Thanks everyone! Very quick and helpful responses
Hi all, sorry if I ask questions already made and answers many times, but while reading well here and there in this forum, I have ideas a bit 'confused.
I own the device in question, currently stock Samsung with Marshmallow 6. I would like to unlock it, get root permissions, install a recovery (maybe the twrp) and maybe flash a new Rom like the LineageOS.
Can some "holy" summarize the steps?
Because I do not understand if I have the bootloader locked or not, if just I do the operation of the "autoroot chainfire" and then flash rom (everything from Odin) or if you need anything else. I would not brick the device...
Thanks and sorry for my english...!!!!
Hi all,
I know this may seem like a n00b question, but I hope you can point me in the right direction. I have a A320FL with Android 6.0.1 - build june 28 2017, and I blocked the auto update feature, because back then I read about the advanced locking technique and want to root my phone. Since then I looked at these forums, but found it quite difficult to gather all the information to get confident enough to flash/root my phone. In the past I rooted/flashed my Sony Z1c regularly and that was easy. But for some reason flashing the A320 seems much more difficult, with more chances for it to go wrong.
I'd like to have the following:
- Android Oreo stock, twrp, rooted and Xposed (optional if possible)
I found this thread about rooting and twrp and xposed, but it's an older manual for Android 7 and I don't know if it will also work with Oreo.
Other threads talk about unlock and the security path, but I'm not sure if it applies to my situation, or not? (since I have an older installation, perhaps the advanced locking technique isn't implemented)
Any help is appreciated. Thanks.
hatsikidee said:
Hi all,
I know this may seem like a n00b question, but I hope you can point me in the right direction. I have a A320FL with Android 6.0.1 - build june 28 2017, and I blocked the auto update feature, because back then I read about the advanced locking technique and want to root my phone. Since then I looked at these forums, but found it quite difficult to gather all the information to get confident enough to flash/root my phone. In the past I rooted/flashed my Sony Z1c regularly and that was easy. But for some reason flashing the A320 seems much more difficult, with more chances for it to go wrong.
I'd like to have the following:
- Android Oreo stock, twrp, rooted and Xposed (optional if possible)
I found this thread about rooting and twrp and xposed, but it's an older manual for Android 7 and I don't know if it will also work with Oreo.
Other threads talk about unlock and the security path, but I'm not sure if it applies to my situation, or not? (since I have an older installation, perhaps the advanced locking technique isn't implemented)
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
You should just be able to enable OEM unlock, flash TWRP, format data in TWRP, flash no-verity- noencrypt zip, and you should be fine I think.
Okay, and then flash the last stock rom and then Magisk for root?
hatsikidee said:
Okay, and then flash the last stock rom and then Magisk for root?
Click to expand...
Click to collapse
If you want to be on the latest update, then do it before you root. But yes, then you flash magisk after the rom after you got TWRP.. Make sure you boot up once or more before you flash magisk.