Related
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
Hey guys, this is my first HTC device. I've been reading through the threads here and in the intl forum and I just wanted to get a little info in one place as to what we can flash for this device. I sent mine off to someone with a Java Card, so now that I'm good to go, I wanted to see what all I (and other VZW users) can do at this early stage in the game. I know that until there is an easier way to S-Off/root/etc than sending your device to someone it is still kinda rocky as to development on this particular device, but I've heard mixed reviews on what ROMs/kernels are good to flash.
I assume that as long as I've got a custom recovery, flashing ROMs on this device would be the same as the other devices I've used... just pick the file in TWRP and flash, right?
As far as ROMs go, I've read that ViperOne works, along with InsertCoin with nothing extra.. just flash and go apparently. As for other ROMs, a little editing and some files from the stock VZW ROM should make them work, right? What files exactly would be needed?
Basically, if you've flashed anything, post your results here. What works, what doesn't, anything I should do before I start flashing myself. Any good threads I should read before I jump in. Thanks guys!
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
jtommyj said:
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
Click to expand...
Click to collapse
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
lordcheeto03 said:
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
Click to expand...
Click to collapse
Well first thing you need to have a custom recovery flashed.
Then you would need to backup your stock system. If you are in a soft brick then volume up and power being held at the same time should get you out of it.
There should not be a need to refresh firmware since the original firmware is all we have. I do believe an Ruu is being worked on currently.
Final word- if you're unsure,don't!!
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
notedroidbrokedroid said:
I just want to make sure that everything is crystal clear. I have spent weeks and many, many hours pouring over numerous, differing guides on how to root the 910V and run a custom 6.0+ ROM - all of them missing different vital chunks of information. Correct me if I am wrong:
You have to temp-root the device and quickly run an unlocking script written by an unknown source before the phone completely locks up and reboots itself. Then if you're lucky and the script is successful after 17 attempts and 4 battery re-charges, the stock 5.1.1 ROM will refuse to boot and you'll only be able to access the stock recovery with an "unlocked" flag on it. Then you'll go to install TWRP, try and flash a custom MM ROM only to find that wifi, camera, and all sensors don't work on any MM ROM without flashing the updated CPD1 bootloader firmware (this is not explicitly mentioned in multiple different guides for rooting and unlocking, including the official): Example here and here. Oh, and good luck using the thread search tool to find replies that mention this wifi issue in any of the 500 pages of replies that follow the official rooting and unlocking guide! The search tool has been broken for weeks and you'll get: "Sorry, we encountered an error processing your request. Please go back and retry or wait a minute. The Administrators have been notified of this error". Clearly Admins either aren't being contacted or don't care.
Then if you are repeatedly unsuccessful in flashing the updated bootloader firmware using the BPA1-CPD1 Hybrid Lollipop ROM developed by hsbadr in this guide, you might try and flash the stock 6.0+ bootloader firmware found here, (because you can't find anything with the broken search tool, it seems like a logical thing to do, and there are absolutely NO write-ups that mention extremely simple things - (like whether or not the updated stock VZW bootloader firmware will re-lock the bootloader.) However, if you do this, the bootloader re-locks itself, the phone bricks itself into a boot loop, and you have to factory flash VZW's MM ROM. If you manage to do that without completely losing your sanity, then you have to flash VZW's 5.1.1 ROM while on 6.0.1 firmware, which will take 6+ tries to get working and might not work at all. Then you have to boot into 5.1.1, re-temp root, quickly re-run the shady bootloader unlocker script before the phone force-restarts, go back to having an unbootable ROM, re-flash TWRP, then flash a custom 6.0+ ROM.
Am I understanding all of this right? I just want to make sure that I am not unaware of something, because god forbid anyone ever be unaware of something, lest this YOU DIDN'T READ!!! YOU DIDN'T READ!!!!! mantra get thrown around - as if any of you could seriously have the audacity to claim that these cluttered, fragmented guides on 15 different links represent some sort of fool-proof cohesive and coherent guide in your warped minds.
So am I missing anything? Some crucial step that I still might be unaware of? No? Great. Rant done. TL;DR: This process is waaaaaay too complicated for most people. I put myself in this category as a professional engineer that's rooted and flashed custom ROMs on many different phones.
Click to expand...
Click to collapse
The processes were easy enough...and some like me had temp root on first or second try. If you've spent weeks and weeks trying to figure this all out, I'm not sure anyone can help you. There are people in these threads that have answered every question you've brought up, and helped people get through. I know you must be some kind of troll with your "one post" and claiming you've been rooting blah blah blah....engineer...blah blah blah, you should be embarrassed by your lack of understanding and ability to root and unlock. Go read some of the dopey posts by people who can't follow instructions or put a sentence together, yet were successful! I guess what I'm saying is stfu and go away.
Sent from my SM-N910V using XDA-Developers mobile app
gcounts said:
The processes were easy enough...and some like me had temp root on first or second try.
Click to expand...
Click to collapse
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
gcounts said:
you should be embarrassed by your lack of understanding and ability to root and unlock.
Click to expand...
Click to collapse
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
notedroidbrokedroid said:
You can follow all of the links I posted and verify that the information I have claimed is missing, is indeed missing. I have pointed out what is missing from where and concisely explained exactly why the process for this particular phone is dangerous without said information.
Congrats on your effortless unlock and custom ROM flash. Your anecdotal success and unsubstantiated claims regarding the successes of others does not make the process objectively "easy", nor straightforward. I have flashed custom ROMs onto many devices, and this one is the most complicated, convoluted, and frustrating of them all.
Ahhh, the "YOU DIDN'T READ!!!!" mantra begins! I don't know if you're aware of this, but failure is how things are learned. It's how more cohesive, better written guides surface, and it's how people like you enjoy a successful root and custom ROM. There are lots and lots of people who have ruined phones from attempting this process. I'd be willing to bet money that the people who developed these hacks certainly went through a couple.
Click to expand...
Click to collapse
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
douger1957 said:
You know what? The people that wrote the guides did so out of the goodness of their hearts as have all of the people here that have helped others to root their phones. There's nothing like you coming in here and slapping those people in the face.
Perhaps they're not the best writers. I think it unlikely that writing is what they do for a living. But you know what? If you'd taken the time to read the entire threads, you would have seen every possible way to **** up and how to deal with it. But no. Assholes like you think there should be a one touch root because you're too ****ing lazy to learn a little bit about your phone. Sorry, bub. It didn't happen with this phone. It took almost 18 months to discover and develop the exploits that allowed us without developer editions to root our phones.
I should apologize. I should be sorry that you're too ****ing stupid to read through hundreds of posts on how to unlock a bootloader and root your phone.
Have you sent any money to the guys that developed the exploit? How much are you paying for any of what's here on this forum? STFU.
Click to expand...
Click to collapse
- Has anybody bothered to state that 40% of the battery charge disappears every time you run Kingoroot? Nope. Nowhere in the guides.
- Has anybody mentioned that the CPD1 VZW bootloader firmware is also locked and will not boot a ROM flagged as custom? Nope! Nowhere. You heard it here first!
- Has anyone examined the content of the BPA1-CPD1 hybrid 5.1.1 ROM to determine whether it contains OEM VZW firmware or a custom firmware revision developed by someone on this forum? No. Nobody has done that.
You don't have to "write full-time" to have good written communication skills. I could write a very respectable COMPREHENSIVE guide on the process involved, but do you know what would happen to it? The admins would never sticky it and it would get buried under a thousand other threads. Somebody decided that there can be ONLY ONE ["Official"] guide, even though the current one is a stupid, incoherent mess that's maintained by an OP who refuses to amend or add anything to it.
And lazy? At least I perused the source code before I blindly copied a script claiming to unlock my bootloader. I doubt you have the slightest clue on either how to look at it or what malicious code looks like.
Lastly and most importantly, you're a fool for being content with giving your money to a phone manufacturer that rails you in the ass for wanting more control over it. After I brought my Note 4 back from the grave, I bought a Nexus. You think donating your change to the Devs is going to fix this problem long-term when you give Samsung $800 to continue doing this to you? I don't have enough crayons to further explain to you what an idiot you are.
Ok as this really is nothing more then a rant I will close this up with a few passing thoughts.
Things like this are not meant to be done by the average guy. This is a developers site. So yes you are expected to do lots of research before you do anything.
Next. No one in their right mind uses that root process. The battery drain is it connecting to the internet and downloading what ever it is they use to root the device after then get your imei and store it.
Also lets leave the name calling for the playground or the next name that will be called is banned.
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:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Edit: Opps sorry thought was OP3 thread :laugh:
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
This phone launched with nougat. You can't run marshmallow on it.
liam_davenport said:
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Click to expand...
Click to collapse
where do i find those? (i have searched but can only find cm14 for pixel?
toknitup420 said:
This phone launched with nougat. You can't run marshmallow on it.
Click to expand...
Click to collapse
this is what i was afraid of....
ncsuwolfs said:
where do i find those? (i have searched but can only find cm14 for pixel?
this is what i was afraid of....
Click to expand...
Click to collapse
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
There are no Marshmallow ROM's anywhere for this phone.
Never was, never will be.
Magisk isn't an Xposed replacement.
There is no replacement for Xposed.
Dammit, I miss my ~17 Xposed modules.
Most of which gave me options that you won't find on any custom Nougat ROM.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
It's a root option. As in you can run SuperSU or Magisk. Magisk has mods that can accomplish certain things that Xposed did but the majority of them don't work with the pixel so don't count on a suitable replacement.
jhs39 said:
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
Click to expand...
Click to collapse
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
CZ Eddie said:
Magisk isn't an Xposed replacement.
Click to expand...
Click to collapse
This isn't completely true. There are Magisk mods that overlap things that Xposed was capable of. So depending on what you are trying to do and IF mods even worked for the pixel. It could be a replacement for some.
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
jhs39 said:
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
Click to expand...
Click to collapse
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
pcriz said:
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
Click to expand...
Click to collapse
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
jhs39 said:
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
Click to expand...
Click to collapse
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Yeah for the pixel it's pretty straight forward, if you want to root use chainfire's zip it's 2.79 SR3, you're even advised on 2.82 that pixel users will not want to upgrade.
As far as the may bootloader situation, flash the april bootloader and you don't need to bother with the signing zip. Besides, I think dealing with knox was much worse
pcriz said:
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Click to expand...
Click to collapse
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
jhs39 said:
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
Click to expand...
Click to collapse
You went from saying "Magisk and SuperSU don't install properly or don't keep root" to talking about the changes to boot signing on newer bootloaders.
If you are going to share information at least try to be accurate. There is a whole slew of users in the development section running rooted ROMs just fine but if a new user reads your posts they will assume root is broken and flashing the pixel leads to boot loops.
You don't want to deal with the verified boot signer all you need to do is flash the april bootloader and reboot. It happens once. If that is too difficult then maybe those same people shouldn't bother flashing anything period.
No one said flashing and modding would be easy but flashing a bootloader ain't hard.
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
jhs39 said:
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
Click to expand...
Click to collapse
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
pcriz said:
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. QUOTE]
I answer these questions a lot and that is most certainly true.
Click to expand...
Click to collapse
pcriz said:
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
Click to expand...
Click to collapse
Actually that's absolutely not true. I came from a Nexus 6P. On the XDA threads for that phone there is an accurate, clear, up to date step by step guide on how to flash anything with that phone, including separate instructions for how to root, install a custom recovery, how to install a custom Rom and how to go back to stock. On the Pixels the threads are a complete free for all filled with confusing, contradictory and inaccurate information. I just read posts from earlier today from someone who is getting boot loops when flashing SuperSu. Not a single person responded by suggesting that he use the April bootloader. The suggested solution (which didn't work) was to flash the boot sig zip. How exactly is somebody supposed to research flashing on the Pixel when the XDA threads for this phone are a complete shambles? And since you are supposedly such an expert at flashing on this phone why don't you do something useful and help other people who are having problems instead of wasting everybody's time with your utterly pointless posts about how easy it is to flash on this phone and how people having trouble are idiots who didn't do their own research? You aren't simply part of the problem, dude--you are literally the personification of everything that is wrong with XDA.
jhs39 said:
.
Click to expand...
Click to collapse
This discussion ain't worth reading whatever it is you typed dude. I'm going to agree to disagree.
Sorry stable root is an unattainable unicorn for you. Sorry you're having such a difficult time. Sorry that making excuses for false information is a priority over finding out how it's actually done.
Happy flashing, best of luck to you sport.