Develop Bugs

[Q] Help me getting the max from my LG Nitro HD P930 ICS

Hi,
First, consider I am a beginner so I do not know the keywords you use. (like brick-unbrick-cm10-flash-rom-debugg-recovery mode...)
I want to benefit from my phone.
1- By rooting it. Please tell me what is the latest/tested/safest/compatible method to do so.
2- By having IF possible the latest android version after the latest/official update that is the 4.0.4 for my phone.
I really want a good guide that won't give me almost any errors because I will not know how to deal with them and if putting the latest android version will do so, I won't do it. But my main concern is rooting it.
[Edit]I did some research since I still got no replies so I found there is the Bin4ry method. Is this the one for me?
Thanks for a detailed answer for a beginner.
Your website is great
(I already created a topic before but I was given 2-3 different methods so I didn't know which one to choose so I hope this time you can help)
About my phone:
I have an LG Nitro HD P930 bought from the USA so they wrote on it at&t and updated with the LG tool to ICS 4.0.4.
Baseband version : APQ8060/MDM9200.
Kernel version : 3.0.8-perf
Build number : IMM76D
Software version : LG-P930-V20c-JUN-25-2012

Forum Rules
Specifically.. Rule #1 & 5
Does no one read stickies?
I really want you to take a look at the XDA Mantra.. I couldn't put it better myself:
I think what a lot of people forget is that this is not a "make my phone neat & kewl" place.
As implied by the name this is technically a Developers forum/community.
Now what does that mean? Well first off it means that there is an expectation that if you are here then you want to customize your device but rather than just installing something that someone packaged you want to understand how it works and maybe even enhance it yourself.
When I first came here with a Blue Angel it was a different environment. PDA Phones were not embraced by the general public because of the expense and complexity (I paid over $400 for my BA). A $400 phone 4 years ago was expensive, today the Tilt is $300 after rebates but with inflation & the rise in the cost of other devices and the fact that there are other sources out there giving them away for $150 our neat bit of kit has become popular with mainstream users.
Now we have a flood of new users who are asking not "How can I do this myself" but more like "Give me the quick fix" without caring to understand the process. See if you read the threads then you get to experience the learning process, you see how the issues were investigated and confirmed. Then you get to watch the different attempts at resolution and learn why some failed while others worked. That is called Development.
The NooB backlash is coming from users who have walked in the development shoes and is directed mainly at those who don't care for the journey but just want the end result or destination.
As a Development Forum we are just as much (if not more) about the journey. I've read so many comments like "I don't have time to read all of the threads" or "I don't care how it works, just that it does". These very statements are contrary to the heart & soul of XDA-Devs and that is why the backlash is so strong.
Let me be very clear on this: IF YOU DON'T CARE ABOUT UNDERSTANDING THE JOURNEY THEN YOU PROBABLY SHOULDN'T BE HERE IN THE FIRST PLACE.
XDA-Devs is about developers & hackers helping each other and working together to get the most out of our devices by understanding them better than most.
XDA-Devs is not about helping everyone who wants a "Kewl bit of kit" make their phone better than the guy next to him.
Now do we go kicking users off who never contribute anything, NO. We tolerate it to an extent. Where the toleration ends is when these users start diluting the usefulness of the forum by repeating the same questions over and over again.
You ask us to understand your position. Well if you want to benefit from our experience and time then I think it is only fair that you understand our position.
Click to expand...
Click to collapse
When I first got here from the Sony Ericsson dev forums of my previous phone (w810i) I knew absolutely nothing about android, or any smart phones.. However, I've been doing web/gfx design & coding for many years and I know how to learn fast. That being said, I didn't feel it necessary to make one thread and before I knew it I had rooted, and flashed a custom recov/ROM within 24 hours. Now yes, I had my share of problems but I was actually quite well versed because of it..
The moral is that you'd be answering the same question asked by the next guy if you did the same thing. Trial and error is how humans learn.
First, if you are a beginner as you said, what is the reason you think you need root? Most users probably don't even need it.
Second, and im sure this is going to be your next thread; you have official ICS which means locked boot loader. In layman's terms, no roms can be flashed without unbricking.
Either way, there's literally 5 or 6 rooting guides.. Did you even try?
This community frowns on people who continuously ask the same questions especially when the answer is on the front page of that very forum... It gets very frustrating to see the same question asked day after day by people who aren't even willing to try. And the fact that you've already asked once and now felt it necessary to make a whole new thread to do it again tells me rooting and modding isn't for you.
There's literally no negative result from a failed root attempt.. However, succeeding will void your warranty, and if you don't know how to find resources on your own you'll probably end up with a bricked phone (won't boot and/or worse... )
Questions are fine, not bothering to do any research or trial/error is not.
Sent from my LG-P930 using Tapatalk 2
---------- Post added at 11:39 AM ---------- Previous post was at 10:44 AM ----------
Judging by your +Thanks I take it you see what I'm saying, however looking back I just want to add that I'm not trying to make you look stupid or single you out.. and I apologize if it came off that way.
To answer your question better: typically the latest guide with the most recent replies is the one people are using. Just open the thread and read the last few pages to see if anyone has linked a newer guide or better method.
Afterward I'm assuming you'll want to try jb at some time which will mean you'll have to unbrick. There's a newer unbrick guide that is specifically designed to help with people who've flashed the official ICS and licked their bootloader. I suggest that one. Too hard to link on the fly so you'll have to do some recon
Good luck and thanks for taking the time to read my thoughts.
Sent from my LG-P930 using Tapatalk 2

First, thanks for replying.
First, I am not the kind of person you are talking about. In fact, I feel sad for creating this thread now after your reply.
I want to learn but I find it hard to find the resources. Give me a good source of 10 pages and I am ready to read it to learn.
For example now, I saw different methods one of them sparkyroot one of them the bin4ry method and others but I don't know with which one should I proceed with. I don't know which one is compatible with my phone. I don't know if any user having my phone is facing problems after rooting since every popular thread have a minimum of 200 pages.
I posted this thread because I am scared of "trying" like you said and making an error while rooting and having my phone bricked and it is not a simple error I will get but a major one since I am modifying the root of my phone so I do care if my phone will face any error. I don't want to pay for a new phone or searching for someone to repair it.
I am still 16 years old, trying to learn, but it is so hard for me to find the tools on Android, none of my friends know anything about these stuffs and there are no tech guys in my place if I have questions. In two years I will be in university studying in CCE and this is to show you I like the programming stuffs but I need help starting. I do like exploring and learning like I do on my laptop and on my Ipad but the guides here are harder to find. When I first wanted to jailbreak my Ipad, I 've read a lot of step by step guides and found redmondpie.com which gives answers and guides to almost everything but I don't know where to start for Android since there are tons of models, forums, threads, methods etc.
As I said in the title, I want to make the max out of my phone so I want to be able to have the latest updates since the last one is ICS, getting rid of the useless apps, managing the startup apps, adding the coolest and most useful tweaks like I try to do on my jailbroken Ipad. To sum up, doing EVERYTHING none of the people around me know how to do and being able to have kind of a unique phone full of nice tweaks.
I hope you really understood what type of person I am.
So back to my problem,
I didn't know "There's literally no negative result from a failed root attempt".
I read that the sparkyroot uses an "old exploit"
I read that that the bin4ry method is new but I didn't find my model listed in it, in fact, I was more confused when I new there are models of my models like when I read v20c and v20e etc so I didn't know if I will have my phone bricked while using a bad method.
I don't know which ROMs are compatible with my device and my main problem is : I can't find answers for MY device since there are tons of guides and devices on Android unlike on IOS where you find the same guides, problems and solutions (I am not saying IOS is better in fact I like Android for its open OS based on Linux if I read well).
So I came here searching for not only the answers but the latest answers in which errors are fixed and which will not create problems with my device.
I knew XDA is one of the best communities for Android users but I can't seem to find easy guides for beginning and developing my knowledge.
I thanked your answer because you took time replying me but I need any help for starting. For example I found here a really good explanation of ROM http://droidlessons.com/what-are-roms-for-android/ and I really liked the "What kind of benefits can a custom ROM give me?" but I am scared of "2. Custom ROMs may have bugs that cause your device to have issues" and this is why I am posting this thread to know more of ROMs particular to my model version, and it is not as simple as that to find answers for my phone's questions I mentionned on the thread.

Proceeding
Yes.. I also don't like the people who want the answer directly without caring about all the effort the dev made and what they are really doing so I understand why you first posted your reply.
I will not do anything before wednesday (I have exams :s )
But first if I want to root, the latest method is the bin4ry one if I searched well.
I ve read about superoneclick http://androidjinn.com/how-to-root-lg-nitro-hd-the-easy-way.html but I told the guy who posted the thread about my first thread I posted on XDA so he told me to try the sparkyroot method here http://forum.xda-developers.com/showthread.php?t=2044645 but then someone told me "TPSparkyRoot is based on an old exploit and works on v18f(4.0.3) only. Thats just for rooting if you want to install CWM, you mush "unbrick" your phone."
So, should I proceed with the bin4ry method? (I am scared having errors as I told you so is this the one I should try?)
After having my phone rooted, to have JB on it, you told me I should unbrick it (did I understand you well?) To do this, I've read "Just rooting, you shouldn't lose your data.... following an unbrick guide on the other hand, you will." does this mean like a "format" for my android? I do not mind doing so because in that way I will have a new phone wiped from all the things I installed on it.
So, I should backup all of my data first.
But which unbrick guide should I follow, the latest one on the LG Nitro HD section is this http://forum.xda-developers.com/showthread.php?t=1597488
So again the same question, is this the one for me? Should I do it after rooting my phone? And do you know known bugs?
I am detailing you my answer to show you I am searching but I still need help.
Thanks.

Wow.. Loaded question.
Truepeace said:
First, I am not the kind of person you are talking about. In fact, I feel sad for creating this thread now after your reply.
I want to learn but I find it hard to find the resources. Give me a good source of 10 pages and I am ready to read it to learn.
For example now, I saw different methods one of them sparkyroot one of them the bin4ry method and others but I don't know with which one should I proceed with. I don't know which one is compatible with my phone. I don't know if any user having my phone is facing problems after rooting since every popular thread have a minimum of 200 pages.
I posted this thread because I am scared of "trying" like you said and making an error while rooting and having my phone bricked and it is not a simple error I will get but a major one since I am modifying the root of my phone so I do care if my phone will face any error. I don't want to pay for a new phone or searching for someone to repair it.
I am still 16 years old, trying to learn, but it is so hard for me to find the tools on Android, none of my friends know anything about these stuffs and there are no tech guys in my place if I have questions. In two years I will be in university studying in CCE and this is to show you I like the programming stuffs but I need help starting. I do like exploring and learning like I do on my laptop and on my Ipad but the guides here are harder to find. When I first wanted to jailbreak my Ipad, I 've read a lot of step by step guides and found redmondpie.com which gives answers and guides to almost everything but I don't know where to start for Android since there are tons of models, forums, threads, methods etc.
As I said in the title, I want to make the max out of my phone so I want to be able to have the latest updates since the last one is ICS, getting rid of the useless apps, managing the startup apps, adding the coolest and most useful tweaks like I try to do on my jailbroken Ipad. To sum up, doing EVERYTHING none of the people around me know how to do and being able to have kind of a unique phone full of nice tweaks.
I hope you really understood what type of person I am.
So back to my problem,
I didn't know "There's literally no negative result from a failed root attempt".
I read that the sparkyroot uses an "old exploit"
I read that that the bin4ry method is new but I didn't find my model listed in it, in fact, I was more confused when I new there are models of my models like when I read v20c and v20e etc so I didn't know if I will have my phone bricked while using a bad method.
I don't know which ROMs are compatible with my device and my main problem is : I can't find answers for MY device since there are tons of guides and devices on Android unlike on IOS where you find the same guides, problems and solutions (I am not saying IOS is better in fact I like Android for its open OS based on Linux if I read well).
Click to expand...
Click to collapse
Not sure exactly what you mean.. If you searched you'd have found on the very first page of this very sub-forum:
Root LG Nitro HD on ICS
In post # 4 you can see that the method linked worked.. and this was posted this month.. Not sure why you have so much trouble finding this info.. It's right here, and if you notice; if that fellow had bothered to search, he'd have found the same info that the first response provided. It's literally all right here. XDA is usually the one-stop-shop for all required info and resources, so long as you're willing to look.
Nevertheless, I've tried both of these methods, and both worked first try for me. However, you usually only have to do this once, and Ive done it both on GB when I first got it, and then again on ics 4.0.4 when I updated like a moron without reading... This was a great example of a "lesson learned" for me.. and trust me, I am better for it.
I don't understand what you're "scared" of... Basically, as long as you follow the guides properly you'll never have a problem..
However, if you are flashing custom ports, or beta release roms that are known to be unstable (it will always say); then your worst "fear" would be having to follow the Unbrick Guide, which shouldn't take more than 30-45 mins tops after the first run-through in which you obtain all the required files. Unless you do something stupid -- usually caused by not following/reading guides properly.. again, most of the time human-error is the only culprit of bricks -- your phone will never be "broken beyond repair."
Warnings are typically clearly stated -- I can't stress this enough: READ READ READ (replies, comments, reports, bugs.. all listed in the same thread as the guide itself).
So I came here searching for not only the answers but the latest answers in which errors are fixed and which will not create problems with my device.
I knew XDA is one of the best communities for Android users but I can't seem to find easy guides for beginning and developing my knowledge.
I thanked your answer because you took time replying me but I need any help for starting. For example I found here a really good explanation of ROM http://droidlessons.com/what-are-roms-for-android/ and I really liked the "What kind of benefits can a custom ROM give me?" but I am scared of "2. Custom ROMs may have bugs that cause your device to have issues" and this is why I am posting this thread to know more of ROMs particular to my model version, and it is not as simple as that to find answers for my phone's questions I mentionned on the thread.
Click to expand...
Click to collapse
Again, "bugs" and "issues" usually means random reboots, or force closing of apps... Nothing serious. Flashing CM nightly (trusted dev) is very safe IMO.. Flashing custom ports is probably the most risky. but again, nothing an unbrick cant fix in 45 mins or so.
Truepeace said:
Yes.. I also don't like the people who want the answer directly without caring about all the effort the dev made and what they are really doing so I understand why you first posted your reply.
I will not do anything before wednesday (I have exams :s )
But first if I want to root, the latest method is the bin4ry one if I searched well.
I ve read about superoneclick http://androidjinn.com/how-to-root-lg-nitro-hd-the-easy-way.html but I told the guy who posted the thread about my first thread I posted on XDA so he told me to try the sparkyroot method here http://forum.xda-developers.com/showthread.php?t=2044645 but then someone told me "TPSparkyRoot is based on an old exploit and works on v18f(4.0.3) only. Thats just for rooting if you want to install CWM, you mush "unbrick" your phone."
So, should I proceed with the bin4ry method? (I am scared having errors as I told you so is this the one I should try?)
Click to expand...
Click to collapse
It was more a general look at the rules. Not specifically saying you're like that, I just think he worded it well so I thought I'd share.
Anyways, from my experience as long as you have the drivers properly installed and don't let your antivirus delete the zergrush or other exploit file (because it will), superoneclick has always worked first try for me. However some people report having to try multiple times so just keep trying.
As I said, all rooting guides use pretty much the same exact tools, just worded differently or a different app that does the same thing.
After having my phone rooted, to have JB on it, you told me I should unbrick it (did I understand you well?) To do this, I've read "Just rooting, you shouldn't lose your data.... following an unbrick guide on the other hand, you will." does this mean like a "format" for my android? I do not mind doing so because in that way I will have a new phone wiped from all the things I installed on it.
So, I should backup all of my data first.
Click to expand...
Click to collapse
Yes, the official ICS update locks the bootloader so you have to follow the same guide you would if you had "bricked" your phone.
Flashing any ROMs or doing pretty much any modding requires a full wipe. Simply back up your data (I suggest helium).
After you flash a custom recovery (CWM), you can do what's known as a Nandroid backup, which (basically) backs up every last detail of your current running ROM including settings for all installed apps, games, etc. as well as settings for the OS itself, wifi info, etc. -- Let me put it this way, if you restore a nandroid backup, it's as if you never wiped/flashed anything else. This is the best benefit of flashing a custom recov. (IMO) besides flashing roms of course.
Rooting is very non-intrusive.. Unless you have apps that require root, you wouldn't even notice. There's no risk of errors or bricked via root itself, however.. Root means "admin" or "full" access. You will have access to things that are normally hidden/protected from accidental changes.. Similar to the control panel in windows.
As with any computer, If you go deleting things or editing important options like a moron after obtaining root then yes, you will have problems. That's the whole point of why phones don't come with root access.. People who aren't smart enough to figure it out most likely aren't smart enough to handle it.. (Ie. General public).
But which unbrick guide should I follow, the latest one on the LG Nitro HD section is this http://forum.xda-developers.com/showthread.php?t=1597488
So again the same question, is this the one for me? Should I do it after rooting my phone? And do you know known bugs?
Click to expand...
Click to collapse
I'm not sure what you mean by bugs.. It works 100%. Its user error that is the problem.
Google "how to unlock p930 bootloader".. Its clear as day
I am detailing you my answer to show you I am searching but I still need help.
Thanks.
Click to expand...
Click to collapse
That's the point.. Read the mantra more closely. The whole point is to try.. You learn by trying.. If you're afraid to get a little dirty sometimes, then this stuff probably isn't for you.
One last tip: Read guides fully before starting and make sure all files are still available/alive. This ensures you don't get stuck half way through. You'll thank me later.
Edit:
PS: mattman was kind enough to make an updated repo for us.. It's on this same sub-forum:
[May 05, 2013] Repository
This contains an updated list of almost all important resources. Just read the guide you're interested in, and like I already said; go to the last page and read every post from the last 3-5 pages if necessary. Most of the time, this is where the latest bugs, and newest updated info is located in any thread.. Its very simple. Did you read my post or just skim through it?
PPS: HO!NO! has been kind enough to offer a mirror of all the required files for unbricking, as well as many other useful resources. If you look around you'll find everything you need right here.
Heres the guide you want for rooting official ICS:
Note: Disregard the word "Bell" in the title.. It'd be the same for any provider, so long as you're running a p930 (even then, it probably works for the 935, 936, and su640, etc.)
[GUIDE] How to ROOT Bell official v20e firmware
Here's the guide you want to use for both rooting, and unlocking bootloader if you're going to want to flash a custom recovery and/or roms:
Note: I highly recommend.. Clockworkmod Recovery is extremely useful, and nothing beats CM10.1 RC2 + Wind Kernel 2.01 as far as battery life is concerned, and the features JB offers over ICS are simply amazing.. (as long as bluetooth isn't a deal-breaker for you -- this should be fixed soon though.. we're getting very close.)
[GUIDE] Rooting and Unbricking p930/p935/p936
FYI: I found all of this info in a matter of seconds.. This is why it's so frustrating when people ask this every day.. lmao
Good luck.
Sent from my LG-P930 using Tapatalk 2

[Q] issues with dev response & tool kit

With all due respect mskips work: Tool kit.. I am perturbed at the lack of response and consideration. I donated, sent 3-5 emails, finally got a response 3-4 weeks later. stating he was working on it, 1-2 weeks..( unless I misunderstood him.) I understand, he has a life apart from xda , but if he doesnt respond via pm's... and hardly responds via email- Then the conclusion I come to is seek another method of rooting: hence chainfires cf autoroot.
However, Going back to my initial point- if our build number isnt listed, you must go through this somewhat complicated procedure of sending a boot image. side note here: I am wondering if your build is 4.1.2, are we able to use the latest build shown on the kit, or it also has to be synched with the precise build number ( mine is jzo54k ). are there enough differences to present/cause a problem?
I did try the cf-autoroot last night- and unless I did something wrong-
although I did accomplish root( verified with rootchecker, and I used odin to push twrp. I was unable to flash zip files, I had this image show up with android on his back with some symbols above- prompting me to reboot, or wipe cache, etc. No options to go to sd or internal memory. I am not sure if another function was missing( busybox, or ??? ) but I had no issues pushing twrp, and supersu kept failing with a notice. I am sure thousands have done this successfully- but I dont know what the difference was between cf's rooting method and ability to flash zips and the tool kit which I had previously used on another note 2 that had a diff build number ( which WAS listed on builds in mskips kit.)
This is a loaded comment/question post- but seeking many answers- without any help yet. frustrated -not the thread is closed..strange..
and I am grateful for the great work of chainfire and mskip- but chainfire
deserves all the kudos for being a great communicator- and developer.
Just a much better way of molding your reputation.: I hope this post is in correct section- if not, my sincerest apology!

just happened to be scanning thru
so i'm adding my $.02
i think the longer a dev as been around, the less tolerant they can be of same question
the typical info has been around
we are expected to perform a certain level of due diligence
after we have explored all avenues and googled a topic to death and still cant find the answer..then perhaps you can try asking away
you can't expect an answer though..with or without a donation
it's part of the reason i chose not to take any donation however well intention...just so I dont feel like i'm owned or owed
rooting for a new locked bootloader device like the att s4 is ground breaking...requiring original work or research
once that has been done, more work is built on it
for the gn2...with so many options available to root it...one just have to read a bit..the tool kit is a collection of many options..but it's not the only method
no malice intended..just my 2c
read as much as you can and you will be able to answer your own questions

taking with grain of salt...
qkster said:
just happened to be scanning thru
so i'm adding my $.02
i think the longer a dev as been around, the less tolerant they can be of same question
the typical info has been around
we are expected to perform a certain level of due diligence
after we have explored all avenues and googled a topic to death and still cant find the answer..then perhaps you can try asking away
you can't expect an answer though..with or without a donation
it's part of the reason i chose not to take any donation however well intention...just so I dont feel like i'm owned or owed
rooting for a new locked bootloader device like the att s4 is ground breaking...requiring original work or research
once that has been done, more work is built on it
for the gn2...with so many options available to root it...one just have to read a bit..the tool kit is a collection of many options..but it's not the only method
no malice intended..just my 2c
read as much as you can and you will be able to answer your own questions
Click to expand...
Click to collapse
I get what your saying- and I have done plenty of research..respectfully- I have seen some answers- not all..hence my question/venting... and also- contradictions here and there... but. like you said. there is no obligation implied by donations- and they have become jaded by the overwhelming number of repetitive questions. I guess I expected more...patience is a virtue we all dont have in the same amounts.:highfive:

Is root possible for SAMSUNG-SM-N910A on 5.1.1 build number LMY47X.N910AUCU2DOI3 ?

I have been searching for a few days and can't seem to find any available method to root this build number. It's my own fault for accepting the most recent update, I should have known better. If anyone knows of a root method for this build I would love to know how to do it.

from where have you downloaded N910AUCU2DOI3

Latest update from AT&T through system update.

At this time there is none. There likely will never be permanent root for this device, either. Best hope is for a future update of KingRoot to come that gives a very buggy temp-root.

naverone said:
I have been searching for a few days and can't seem to find any available method to root this build number. It's my own fault for accepting the most recent update, I should have known better. If anyone knows of a root method for this build I would love to know how to do it.
Click to expand...
Click to collapse
i rooted the SM-N910A NOTE4 using root king and it said root successful then after reboot it bricked itself anda screen came out saying warning at&t has detected ilegal custom software on your device please turn of your device and head to the nearest at&t support center. Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK. Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it. For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
---------- Post added at 07:11 PM ---------- Previous post was at 06:51 PM ----------
teddyherrera1 said:
i rooted the SM-N910A NOTE4 using root king and it said root successful then after reboot it bricked itself anda screen came out saying warning at&t has detected ilegal custom software on your device please turn of your device and head to the nearest at&t support center. Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK. Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it. For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
Click to expand...
Click to collapse
forgot to tell you the two U.S. carriers that put locks on their bootloaders is AT&T and VERIZON so i wouldnt recommend root unless you unlock bootloader or else your phone will continueously stay in boot mode without letting you exit. that i believe is a bootloop good luck

teddyherrera1 said:
Honestly you have two choices from what i understand There is 2 U.S. carriers that put what they call a boot lock on their device bootloaders. there is a way to remove the boot lock. google it or ask XDA to assist you . GOOD LUCK.
Click to expand...
Click to collapse
You CANNOT unlock our bootloader and DO NOT ask XDA. Googling it will not result in anything useful either.
Our bootloader is still not able to be unlocked and thus Googling for an answer will only bring up scams, false information, or just no results.
teddyherrera1 said:
Me personally posted many threads requesting help being that im a noobie and dont know jack sh... about unlocking rooting anything and nobody ever bothered to help me or maybe they just too busy devoloping what ever the case was i had my phone for atleast 2 weeks and i did research during that whole time in different forums like android central etc. and finally figured how to do it.
Click to expand...
Click to collapse
Not sure if you're referring to unlocking the bootloader still or about fixing the soft brick caused by Kingroot. Either way, the reason why no one answered you here on XDA is because both questions are asked at least every other week by people who either can't use the search function or just don't even try to. We here in the XDA community are more than happy to help noobs, but if we see the EXACT same questions being asked over and over again, then we will begin to ignore them since the answers are readily available already.
teddyherrera1 said:
For get about going to AT&T they will tell you your warranty is void and that your phone is permanantly hard bricked and all they do is lie to you so you can purchase a new device. I finally restored my device by installing official firmware that you can download free from sammobil.com via odin 3.10.6 they will give you a complete guide. and the correct download links for the proper tools needed to complete the job NOTE: this worked for me its not a hundred percent sure that it will work for you. Please note and understand that you can do this at YOUR OWNE RISK I will not take responsibility for any damage that you may do to your device by using this method and there is a possibility if you dont do it right you can hard brick your phone PERMANENTLY!!!!!!! proceed at your owne risk if you try to blame me for damages to your phone i will laugh at you HARD!!!
Click to expand...
Click to collapse
Yes, for our phones- since there is no possibility to root and thus no risk of doing very serious software damage- Odin is usually the cure-all for most problems. You can find the latest available Odin file in our phone's thread, and use Google to find tutorials on how to use Odin itself.

How I root Samsung Galaxy note 4 SM n910a 4.4.4

spexwood said:
You CANNOT unlock our bootloader and DO NOT ask XDA. Googling it will not result in anything useful either.
Our bootloader is still not able to be unlocked and thus Googling for an answer will only bring up scams, false information, or just no results.
Not sure if you're referring to unlocking the bootloader still or about fixing the soft brick caused by Kingroot. Either way, the reason why no one answered you here on XDA is because both questions are asked at least every other week by people who either can't use the search function or just don't even try to. We here in the XDA community are more than happy to help noobs, but if we see the EXACT same questions being asked over and over again, then we will begin to ignore them since the answers are readily available already.
Yes, for our phones- since there is no possibility to root and thus no risk of doing very serious software damage- Odin is usually the cure-all for most problems. You can find the latest available Odin file in our phone's thread, and use Google to find tutorials on how to use Odin itself.
Click to expand...
Click to collapse
"Our bootloader" ... "our phones" You make it sound as if you're a rep or employee of AT&T. And if so then wth is so wrong with simply allowing people root access to the phones they bought n own? I understand stupid people with powerful tools make powerful stupid mistakes. But smart people who can fix their own few mistakes would still greatly appreciate being allowed to adjust the phone to drastically increase efficency, or at least remove the bloated optimization cap.
Or those who want root so that they can utilize a form of genuine location and privacy protection. To choose whether or not the app they haven't used in weeks still needs to run in the background all the time or still check your location.
Idk... I'll step off my soap box now. Maybe I'll just say screw it and swap the note 4 for another rootable note 3. Since my straight talk phone service is reliant on the AT&T tower near me for any service.

Spooters said:
"Our bootloader" ... "our phones" You make it sound as if you're a rep or employee of AT&T. And if so then wth is so wrong with simply allowing people root access to the phones they bought n own? I understand stupid people with powerful tools make powerful stupid mistakes. But smart people who can fix their own few mistakes would still greatly appreciate being allowed to adjust the phone to drastically increase efficency, or at least remove the bloated optimization cap.
Or those who want root so that they can utilize a form of genuine location and privacy protection. To choose whether or not the app they haven't used in weeks still needs to run in the background all the time or still check your location.
Idk... I'll step off my soap box now. Maybe I'll just say screw it and swap the note 4 for another rootable note 3. Since my straight talk phone service is reliant on the AT&T tower near me for any service.
Click to expand...
Click to collapse
1) That post was made back in 2016. That was over 2 years ago!!! Why did you necro such an old thread? The last post made here was Dec 5, 2016.
2) I no longer have the n910a. Got rid of it a long time ago
3) I do not, nor never have worked for ATT nor am affiliated with them in any way.
4) When I used the word "our" I was referring to the fact that I too owned the n910a. So "our phone" obviously meant "my n910a and everyone else's" and same for the "our bootloader"
5) At the time of my post, root was not available for rhe n910a AT ALL. (If I recall, a temporary root eventually became available though, but it reset everytime you restarted your phone). On a daily basis, people were asking whether root was available or not and people were getting sick of answering the same question over and over again when the answer fould easily be found through a simple search here on XDA.
There were also scams going on at the time BECAUSE this was such a popular topic. Websites claimed to give walkthroughs on how to root your n910a, but all they really did was brick your phone. Kingroot was one of them.

Automatic OTA after depixel8, TWRP, and root?

On Friday (1/6) I opened my freshly purchased pixel XL and was happy to see it was still on 7.1. Given the status of many of the how to threads for the XL (Op not fully updated), I struggled to unlock the bootloader. I left the SIM card in and activated the phone. I even punched in my wifi password and got to the "checking for updates screen" before I started to read everything. I eventually got through it an unlocked the bootloader, slapped TWRP on it and flashed root. So far so good...
Then I started to read through the pain of updating manually to 7.1.1. No thanks. Kind of annoyed, I went about my merry way and just decided I'd hassle through it when something really important mandated it.
Fast forward to today, I noticed a bunch of apps had updated over night and something just seemed odd. So I checked the phone build number and it was updated to 7.1.1. Horrified, I installed quickboot and rebooted to recovery without issue, including SuperSU providing it root....whew!
My question - How did I get the OTA without losing TWRP and root? From what I've read, if you side load the OTA updates, you have to flash it again. I'm on the latest TWRP (RC1) and I've updated SuperSU binaries the easy way.
EDIT- By the way, this is the Verizon version (can't beat $15/m no trade in).

Because sideloading an OTA is a different update. You took the incremental OTA, which is a lot smaller and doesn't include installing to partitions that will break root. When you sideload the OTA, it's a "full OTA" and includes much more.
I would strongly suggest you disable automatic system updates and only manually update from here on out. It's far more risky taking incremental OTA's while rooted and modified than sideloading an OTA yourself when you can control it and flash everything you need to not bootloop.
Consider yourself lucky that you took it and didn't bootloop. But you are even more lucky that you got a 7.1 from Verizon! Nice.

xnatex21 said:
On Friday (1/6) I opened my freshly purchased pixel XL and was happy to see it was still on 7.1. Given the status of many of the how to threads for the XL (Op not fully updated), I struggled to unlock the bootloader. I left the SIM card in and activated the phone. I even punched in my wifi password and got to the "checking for updates screen" before I started to read everything. I eventually got through it an unlocked the bootloader, slapped TWRP on it and flashed root. So far so good...
Then I started to read through the pain of updating manually to 7.1.1. No thanks. Kind of annoyed, I went about my merry way and just decided I'd hassle through it when something really important mandated it.
Fast forward to today, I noticed a bunch of apps had updated over night and something just seemed odd. So I checked the phone build number and it was updated to 7.1.1. Horrified, I installed quickboot and rebooted to recovery without issue, including SuperSU providing it root....whew!
My question - How did I get the OTA without losing TWRP and root? From what I've read, if you side load the OTA updates, you have to flash it again. I'm on the latest TWRP (RC1) and I've updated SuperSU binaries the easy way.
EDIT- By the way, this is the Verizon version (can't beat $15/m no trade in).
Click to expand...
Click to collapse
What pain of updating to 7.1.1.

xnatex21 said:
On Friday (1/6) I opened my freshly purchased pixel XL and was happy to see it was still on 7.1. Given the status of many of the how to threads for the XL (Op not fully updated), I struggled to unlock the bootloader. I left the SIM card in and activated the phone. I even punched in my wifi password and got to the "checking for updates screen" before I started to read everything. I eventually got through it an unlocked the bootloader, slapped TWRP on it and flashed root. So far so good...
Then I started to read through the pain of updating manually to 7.1.1. No thanks. Kind of annoyed, I went about my merry way and just decided I'd hassle through it when something really important mandated it.
Fast forward to today, I noticed a bunch of apps had updated over night and something just seemed odd. So I checked the phone build number and it was updated to 7.1.1. Horrified, I installed quickboot and rebooted to recovery without issue, including SuperSU providing it root....whew!
My question - How did I get the OTA without losing TWRP and root? From what I've read, if you side load the OTA updates, you have to flash it again. I'm on the latest TWRP (RC1) and I've updated SuperSU binaries the easy way.
EDIT- By the way, this is the Verizon version (can't beat $15/m no trade in).
Click to expand...
Click to collapse
I bought the verizon version a while back, unlocked the bootloader. Here is the thing now, when you unlock the bootloader, you'll be good. You can download the google factory images, and flash your phone to the latest version, then you can reflash twrp and super su again. You'll not use the ability to add TWRP everytime because restoring or flashing the images, vendor, even stock recovery does not lock the bootloader. You can also have a custom rom for a piece of mind flashed, I am currently on pure-nexus, which is great and stable for me. I understand if you want to stay fully stock. Did I make any sense to you?

toknitup420 said:
What pain of updating to 7.1.1.
Click to expand...
Click to collapse
Exactly. It doesn't get much easier than double clicking a flashall.bat.

toknitup420 said:
What pain of updating to 7.1.1.
Click to expand...
Click to collapse
spotmark said:
Exactly. It doesn't get much easier than double clicking a flashall.bat.
Click to expand...
Click to collapse
I guess I'm just used to downloading a rom and gapps on my phone, clicking reboot to recovery, wipe/flash/wipe (or just dirty flash). Involving a PC, downloading the latest twrp, supersu, rom and whatever the tool of the day, is a pain comparatively...not to mention having to read pages and pages of threads because the OP isn't up to date and one step that is buried is critical. I understand this may come across as ungrateful. It isn't meant that way. I appreciate the many thankless hours people are putting into this. But from a user point of view, jumping through the hoops and risking bricking a $800 phone because the steps aren't short and simple, doesn't have the same value as when it is easy.

xnatex21 said:
I guess I'm just used to downloading a rom and gapps on my phone, clicking reboot to recovery, wipe/flash/wipe (or just dirty flash). Involving a PC, downloading the latest twrp, supersu, rom and whatever the tool of the day, is a pain comparatively...not to mention having to read pages and pages of threads because the OP isn't up to date and one step that is buried is critical. I understand this may come across as ungrateful. It isn't meant that way. I appreciate the many thankless hours people are putting into this. But from a user point of view, jumping through the hoops and risking bricking a $800 phone because the steps aren't short and simple, doesn't have the same value as when it is easy.
Click to expand...
Click to collapse
It will change. This phone is very different, it's not as open during the boot process as it used to be. Going to take some time to pull it all together. You won't brick it. You may soft brick it but a factory image and flashall.bat will pretty much always save you.

xnatex21 said:
I guess I'm just used to downloading a rom and gapps on my phone, clicking reboot to recovery, wipe/flash/wipe (or just dirty flash). Involving a PC, downloading the latest twrp, supersu, rom and whatever the tool of the day, is a pain comparatively...not to mention having to read pages and pages of threads because the OP isn't up to date and one step that is buried is critical. I understand this may come across as ungrateful. It isn't meant that way. I appreciate the many thankless hours people are putting into this. But from a user point of view, jumping through the hoops and risking bricking a $800 phone because the steps aren't short and simple, doesn't have the same value as when it is easy.
Click to expand...
Click to collapse
The Pixels are a little trickier than Nexus devices of the past in terms of flashing stuff, but you'd almost have to TRY to brick the phone. As long as you keep your bootloader always unlocked, you will always have a way to restore it.
In the future, if you keep your stock recovery, you can sideload OTA's through ADB by downloading the OTA from the Google site, and then using adb sideload ota.zip inside recovery with sideload selected. Alternatively, you can download the entire factory image for the new version, use Notepad to edit the flash-all.bat to remove "-w" from the file - it's in the middle of a flash command - and it will prevent it from wiping your device. But it will wipe out all your system modifications, if you made any.
I hit a "no command" recovery bootloop once when I tried manually updating, and didn't think I'd be able to get out of it because even flash-all.bat was not working (insufficient space error) for no good reason, and no article online has the proper new manual fastboot flash commands for Nougat devices using seamless updates. I think I know the commands now, but the SkipSoft Unified Toolkit is a GREAT tool (simplifies a lot of modification processes for a lot of devices) and automatically flashed the entire factory image for me, fixing the device.

xnatex21 said:
I guess I'm just used to downloading a rom and gapps on my phone, clicking reboot to recovery, wipe/flash/wipe (or just dirty flash). Involving a PC, downloading the latest twrp, supersu, rom and whatever the tool of the day, is a pain comparatively...not to mention having to read pages and pages of threads because the OP isn't up to date and one step that is buried is critical. I understand this may come across as ungrateful. It isn't meant that way. I appreciate the many thankless hours people are putting into this. But from a user point of view, jumping through the hoops and risking bricking a $800 phone because the steps aren't short and simple, doesn't have the same value as when it is easy.
Click to expand...
Click to collapse
Updating this phone is easy as hell. You sound like someone who isn't willing to put in the effort to learn how to properly do this stuff. Using fastboot is extremely easy. To sit there and say jump through hoops is ridiculous. You won't brick you're 800$ device if you know what you're doing. And there's plenty of guides out there on how to use fastboot that a complete noob can understand. This stuff isnt meant to be short and simple. Don't modify you're device if you don't want to learn how to properly do it.

toknitup420 said:
Updating this phone is easy as hell. You sound like someone who isn't willing to put in the effort to learn how to properly do this stuff. Using fastboot is extremely easy. To sit there and say jump through hoops is ridiculous. You won't brick you're 800$ device if you know what you're doing. And there's plenty of guides out there on how to use fastboot that a complete noob can understand. This stuff isnt meant to be short and simple. Don't modify you're device if you don't want to learn how to properly do it.
Click to expand...
Click to collapse
Nice troll or you didn't read and understand what I wrote. Maybe typing it again will help you, the "noob" at comprehension. Looking at your username, I'm probably wasting my time though.
It's not easy compared to download, wipe, flash, wipe. Are you really questioning this?
The guides on XDA are riddled with one off steps buried pages into the thread. I know people are working on this in their spare time so updating a guide is grunt work compared to coding and compiling. But for someone who just got the phone and can't even set it up for fear of losing the ability to unlock their bootloader without reading every page of every thread, it's a bit much.
Did anyone make me do any of this? Of course not. But thanks for your permission to not do it going forward.
To everyone else who replied in this thread respectfully, thank you.

xnatex21 said:
Nice troll or you didn't read and understand what I wrote. Maybe typing it again will help you, the "noob" at comprehension. Looking at your username, I'm probably wasting my time though.
It's not easy compared to download, wipe, flash, wipe. Are you really questioning this?
The guides on XDA are riddled with one off steps buried pages into the thread. I know people are working on this in their spare time so updating a guide is grunt work compared to coding and compiling. But for someone who just got the phone and can't even set it up for fear of losing the ability to unlock their bootloader without reading every page of every thread, it's a bit much.
Did anyone make me do any of this? Of course not. But thanks for your permission to not do it going forward.
To everyone else who replied in this thread respectfully, thank you.
Click to expand...
Click to collapse
Troll? Seriously? Because you're a lazy user who doesn't want to put in the time and effort to properly mod you're device. Can't wait to see you're thread about help I'm soft bricked and don't know what to do. I only wanted you to take the time to learn everything so you don't mess up you're phone. But apparently you think it's too much of a pain. Enjoy you're future bricked phone.

Sadly this is what it's like on many xda threads.
One must read hundreds or in many cases thousands of posts to find out what could have been summed up on the op's original message with a simple 1-10 steps.
And if you call anyone out on it you get the backlash that you received in this thread. It's just the way it is here. Some nice helpful folks and many that just look for a fight.

This thread turned into a mess. All anyone with a Verizon model needs to know is that if you are on 7.1 you can unlock your bootloader. If you are already on 7.1.1 you can't unlock your bootloader and likely will never be able to.
Once you unlocked it you have nothing to worry about. It will ONLY get locked again if you yourself lock it via fastboot with the appropriate command. If you are not rooted and do not have twrp installed you will still get OTA notifications and be able to install just like you normally would. Your bootloader being unlocked has nothing to do with OTA updates.
I do agree with the previous post though. There's no denying that the pixel is different so things aren't as simple and we have some extra steps in order to keep root and twrp and also install updates. To whoever responded to him saying he was lazy is just looking for drama. Ignore it

rfranken said:
Sadly this is what it's like on many xda threads.
One must read hundreds or in many cases thousands of posts to find out what could have been summed up on the op's original message with a simple 1-10 steps.
And if you call anyone out on it you get the backlash that you received in this thread. It's just the way it is here. Some nice helpful folks and many that just look for a fight.
Click to expand...
Click to collapse
what's sad is you guys feel you shouldn't have to read like the people who has been around for years when there was no one to ask. Just should ask and get spoon feed help I just don't get it. I can build kernels from source Roms I do mad mods to my personal setup how did I learn by spending weeks of my time reading and learning. Guess I should have just come here begging for help instead right? And @toknitup420 works we me he can do pretty much everything I can do and people wonder why we don't post our work on XDA cause of users like in this thread. It's a shame entitled users are ruining XDA or users that think their entitled.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
xnatex21 said:
Nice troll or you didn't read and understand what I wrote. Maybe typing it again will help you, the "noob" at comprehension. Looking at your username, I'm probably wasting my time though.
It's not easy compared to download, wipe, flash, wipe. Are you really questioning this?
The guides on XDA are riddled with one off steps buried pages into the thread. I know people are working on this in their spare time so updating a guide is grunt work compared to coding and compiling. But for someone who just got the phone and can't even set it up for fear of losing the ability to unlock their bootloader without reading every page of every thread, it's a bit much.
Did anyone make me do any of this? Of course not. But thanks for your permission to not do it going forward.
To everyone else who replied in this thread respectfully, thank you.
Click to expand...
Click to collapse
By his username WTH does that mean? Smh

He has 420 in his username. Google it if you don't know the reference. Or do we need to "spoon feed" it to you?

Tigerstown said:
what's sad is you guys feel you shouldn't have to read like the people who has been around for years when there was no one to ask. Just should ask and get spoon feed help I just don't get it. I can build kernels from source Roms I do mad mods to my personal setup how did I learn by spending weeks of my time reading and learning. Guess I should have just come here begging for help instead right? And @toknitup420 works we me he can do pretty much everything I can do and people wonder why we don't post our work on XDA cause of users like in this thread. It's a shame entitled users are ruining XDA or users that think their entitled.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
By his username WTH does that mean? Smh
Click to expand...
Click to collapse
First off why don't you read before you make a post like this. Nothing bad or disrespectful was posted. The other person was simply talking about the pixel being more complicated then other devices and stuff like that. It was no indication of him being too lazy to read threads. Then your "boy" felt the need to comment and start useless drama twisting the other guys words. You sit here and say "this is why I left XDA" yet you are the one who just went out of your way to continue the pointless drama that started because neither you nor your friend can read. YOU and YOUR post are the reason people get fed up with this place. You are contributing to drama your friend started on a forum for a device you clearly don't even own. Didn't you say you left XDA? So why are you posting here? I'm sure you're "mad skills" would be more useful somewhere else. Seriously grow up and at least read and know the story before you comment.

aholeinthewor1d said:
First off why don't you read before you make a post like this. Nothing bad or disrespectful was posted. The other person was simply talking about the pixel being more complicated then other devices and stuff like that. It was no indication of him being too lazy to read threads. Then your "boy" felt the need to comment and start useless drama twisting the other guys words. You sit here and say "this is why I left XDA" yet you are the one who just went out of your way to continue the pointless drama that started because neither you nor your friend can read. YOU and YOUR post are the reason people get fed up with this place. You are contributing to drama your friend started on a forum for a device you clearly don't even own. Didn't you say you left XDA? So why are you posting here? I'm sure you're "mad skills" would be more useful somewhere else. Seriously grow up and at least read and know the story before you comment.
Click to expand...
Click to collapse
when did I say I left XDA? Your right I can't read get a clue I wonder how I program CNC machines everyday when I can't read. I didn't read the post I replied clearly.
---------- Post added at 01:05 AM ---------- Previous post was at 01:02 AM ----------
rfranken said:
He has 420 in his username. Google it if you don't know the reference. Or do we need to "spoon feed" it to you?
Click to expand...
Click to collapse
Yeah spoon feed it to me please!! Google it your funny I'm a grown man I partake in it myself as it's legal..Once again I still don't see the point of why his username has anything to do with it. You sound very butt hurt are you a snowflake?

Tigerstown said:
when did I say I left XDA? Your right I can't read get a clue I wonder how I program CNC machines everyday when I can't read. I didn't read the post I replied clearly.
---------- Post added at 01:05 AM ---------- Previous post was at 01:02 AM ----------
Yeah spoon feed it to me please!! Google it your funny I'm a grown man I partake in it myself as it's legal..Once again I still don't see the point of why his username has anything to do with it. You sound very butt hurt are you a snowflake?
Click to expand...
Click to collapse
Notice how every post you feel the need to try and brag? We just met you and we already know you build kernels, do "mad mods" to your phone, and you program CNC machines.. You both were looking for drama where the was none is the bottom line. So why not end it

aholeinthewor1d said:
First off why don't you read before you make a post like this. Nothing bad or disrespectful was posted. The other person was simply talking about the pixel being more complicated then other devices and stuff like that. It was no indication of him being too lazy to read threads. Then your "boy" felt the need to comment and start useless drama twisting the other guys words. You sit here and say "this is why I left XDA" yet you are the one who just went out of your way to continue the pointless drama that started because neither you nor your friend can read. YOU and YOUR post are the reason people get fed up with this place. You are contributing to drama your friend started on a forum for a device you clearly don't even own. Didn't you say you left XDA? So why are you posting here? I'm sure you're "mad skills" would be more useful somewhere else. Seriously grow up and at least read and know the story before you comment.
Click to expand...
Click to collapse
Wait I clearly don't own a pixel XL that's too funny you don't even know me yet you know what phone I own... I left XDA you said but I'm the one that can't read wow

This isn't a pixel XL :good:

google pixel xl build #NKG47L

HI,
I purchased a google pixel xl, the bootloader is currently locked I would like to unlock and root if possible. the phone is running android 7.1.2 build NKG47L. Ive searched youtube, and xda for means of rooting, etc but im not having any luck on finding what would help me.. so some help would be greatly appreciated

https://forum.xda-developers.com/pixel-xl/how-to/index-google-pixel-xl-t3466185

Hopefully you don't have the Verizon version of the Pixel XL.. If you do unlocking the bootloader is impossible. If you don't then flashing and rooting the Pixel XL is possible but unusually difficult. The instructions seem to change from month to month and you need to use a specially modified version of Magisk because the official one doesn't work on the Pixel. If you go the SuperSu route they do have an official version for the Pixel. I've been flashing for years and it pretty much took me an entire day to successfully flash a custom recovery, a custom rom, a custom kernel, root with Magisk and get the phone to pass safety net. I've never owned a phone that was such a headache to flash on. Good luck.

jhs39 said:
Hopefully you don't have the Verizon version of the Pixel XL.. If you do unlocking the bootloader is impossible. If you don't then flashing and rooting the Pixel XL is possible but unusually difficult. The instructions seem to change from month to month and you need to use a specially modified version of Magisk because the official one doesn't work on the Pixel. If you go the SuperSu route they do have an official version for the Pixel. I've been flashing for years and it pretty much took me an entire day to successfully flash a custom recovery, a custom rom, a custom kernel, root with Magisk and get the phone to pass safety net. I've never owned a phone that was such a headache to flash on. Good luck.
Click to expand...
Click to collapse
Because you are having a hard time doesn't mean everyone will. Literally every chance you get you have to post the exact same narrative about how hard this is. It's like you are trying to poison other people's experiences because you find this so difficult. Let OP form their own opinion because frankly there are tons of users having zero issues rooting romming and etc..
Good Lord.

pcriz said:
Because you are having a hard time doesn't mean everyone will. Literally every chance you get you have to post the exact same narrative about how hard this is. It's like you are trying to poison other people's experiences because you find this so difficult. Let OP form their own opinion because frankly there are tons of users having zero issues rooting romming and etc..
Good Lord.
Click to expand...
Click to collapse
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.

jhs39 said:
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
Click to expand...
Click to collapse
Not claiming it's easy. Just saying it gets repetitive to see you in how many threads griping about how this is such an insurmountable task.
And of course you see people with issues. Why do I need to comment that I'm not having issues. Heck when someone does comment that they aren't having issues you refute that because you are having a hard time.
You say I should be more constructive, lol please please please read my post history and maybe you will see how many people I have made efforts to help. I've been helping people in the forum, I've been helping people on Reddit, I've been helping people on discord, irc, etc etc. I've turned down money for helping people. How many people have you helped? How have you paid forward any help you have gotten on the pixel? Hell I even told you why you couldn't flash twrp after you downgraded from the O beta. So please don't tell me about being constructive bro.
"Flashing on Android for years" means nil my friend. Maybe if you took the time to understand the device it wouldn't be so difficult.
Do you even know why you couldn't flash twrp? It's because the OTAs flash to the opposite slot so when you got the ota for Android N from O N flashed in the other slot.
TWRP patches both boot.imgs but now your inactive boot.img is incompatible with twrp so it hangs up.
Super simple fix, now that you know there are two slots. You figure out how to swap slots at the bootloader. Then you learn how to flash all and flash all in both slots
Then you get a light that goes off because you took the time to read how twrp works in it's thread and realize you don't even need to flash all. You could simply flash the boot img in both slots. Because if you know what twrp patches then you know exactly what files you need.
I've been flashing for years also but I'm humble enough to know I should read before crying to people that are doing it without issue.
As far as the magisk "issue", well if anyone took the time to go to the magisk thread they would see the device isn't officially supported. Who's fault is it you didn't do that?
What was stopping you from searching the magisk thread before you started? I mean obviously you ignored where it stated it's not supported.
You can lead a horse to water my man. Can't make him drink.

jhs39 said:
I think anyone who claims it's easy to flash on this phone is being unrealistic and dishonest. Most posts I read from flashers on XDA involving this phone are from people who had trouble flashing or were unsuccessful and are stuck somewhere and looking for a way to recover. Problems getting TWRP to work are very common. Problems with people who don't realize they can't use a non-modified version of Magisk are very common. It doesn't help that there isn't a good clear up to date flashing guide for the phone anywhere on XDA or that you have to go from thread to thread to find the files you need to flash or that the download shortcuts and discussion for the Pixel XL modified version of Magisk are actually buried in the Resurrection Remix thread where nobody would​ logically think to look for them.
I'm not the one who made it hard to flash on this phone--Google did, and people like you don't help matters. If you are such an expert on flashing on this phone do something more constructive than criticizing me for being honest--create a thread that includes clear and up to date instructions for how to flash on the Pixel XL and which includes shortcuts for all the files a person would typically need. And keep the instructions up to date when a Google security patch changes the flashing procedure or files needed.
You claim its easy to flash on this phone. If it's so easy for you then share your expertise with everybody else. If you are unwilling to do that you are just wasting everybody's time by being wildly dishonest about the difficulties people very frequently face when they try to flash on the Pixel XL.
I have been flashing on Android phones for years and I stand by what I said--I've never encountered a phone that was such a headache to flash on.
Click to expand...
Click to collapse
It's "extremely easy" to flash on this phone. It's the hacking and deving thats hard. Give me a zip that works and a functioning Twrp, it will be like taking candy from a baby. Yeah, and Google's not helping any of us.

Well THAT escalated quickly...
Sent from my SM-N910V using Tapatalk

Thanks for the help. I have been able to get the phone rooted, etc but I can't get TWRP recovery to stick. But do I have to reflash TWRP recovery after I flash SU files for root?

yamaha_wins said:
Thanks for the help. I have been able to get the phone rooted, etc but I can't get TWRP recovery to stick. But do I have to reflash TWRP recovery after I flash SU files for root?
Click to expand...
Click to collapse
I had to boot into my rom once, go back into fastboot TWRP and then flash the TWRP zip again in order to get it to stick.

@jhs39 and @pcriz, you're both correct in this matter and hopefully you all can just agree to disagree. I agree with you both, if you're a flasher like most of us and I too have been flashing for years. In fact about 90% of the phones I've owned have all been flashed and I average about two phones per year. That said I'm not expert and do find some things harder here and there but I'm techie enough to work through it with help from members of this forum. @pcriz I've used many of your instructions and assistants on this thread so thank you! I too believe flashing on the pixel has been very difficult mainly because the device changed the way things usually worked (slots etc.). I can't remember the last time it took me hours to flash a simple ROM. After I learned a little bit of what was going on with TWRP and the whole slot A/B configurations I was able to at least troubleshoot my own issues and get things working a little better. I would say anyone having issues need to take the time to really read and understand the device because they don't function the say as before. The instructions do change because Google changes things up. Manufactures don't want us flashing any more and with security being a top priority flashing is quickly being discouraged.
I've gotten to the point now where I just want to get my pixel which is no longer my daily driver (my S8 plus is) to stock but even that isn't working. I've tried numerous times to flash an image and it fails every single time. Why????? I have come to love a stock experience even though I still love the customization you get with a custom ROM. If I were to pick right now I'll just stick with stock; if I can ever get the phone to flash the stupid image so I can try Android O lol.