Easiest way to upgrade to 5.1 and keep root without wiping - Nexus 6 Q&A, Help & Troubleshooting

I know, I know - this is a noob question, guides have already been posted, etc - but information is scattered all over the place, and the internet is littered with "what worked for me" type guides, and I'm just looking for a quick response.
Here's the 2 guides I have found so far:
EDIT: It looks like i can't post outside links, but have found 2 guides. Both are on reddit, and one ends in:
/nexus6/comments/2ywu1m/guide_to_flashing_51_factory_image_without_wiping/
The other:
/nexus6/comments/3028i9/guide_how_to_update_to_51_and_keep_root/
Both of these are very different methods, it seems. My phone is unlocked, rooted, encrypted, and has 5.0.1. It would seem like the easiest thing to do would be to unroot, apply the OTA update, the re-root using CF-Auto-Root - but a forum post said that didn't work, it needs to be re-flashed.
I'm just looking for which of these methods would be best for me at this point. I want to keep root, and not lose my phone's configuration in the simplest way, preferably just using the OTA update, without re-flashing.
Thank you, and I apologize for asking a question that has already been answered. The problem is there are too many different answers, and I'm not sure which one to go with.
EDIT: I've also noticed, that if I have to re-flash, there are 3 different images for nexus 6 5.1: LMY47D, LMY47E, and LMY47I - this is the first time I've seen this when looking to flash a phone. How do I know which is the most up-to-date, and which one to go with?

XDA-Nexus-User said:
I know, I know - this is a noob question, guides have already been posted, etc - but information is scattered all over the place, and the internet is littered with "what worked for me" type guides, and I'm just looking for a quick response.
Here's the 2 guides I have found so far:
EDIT: It looks like i can't post outside links, but have found 2 guides. Both are on reddit, and one ends in:
/nexus6/comments/2ywu1m/guide_to_flashing_51_factory_image_without_wiping/
The other:
/nexus6/comments/3028i9/guide_how_to_update_to_51_and_keep_root/
Both of these are very different methods, it seems. My phone is unlocked, rooted, encrypted, and has 5.0.1. It would seem like the easiest thing to do would be to unroot, apply the OTA update, the re-root using CF-Auto-Root - but a forum post said that didn't work, it needs to be re-flashed.
I'm just looking for which of these methods would be best for me at this point. I want to keep root, and not lose my phone's configuration in the simplest way, preferably just using the OTA update, without re-flashing.
Thank you, and I apologize for asking a question that has already been answered. The problem is there are too many different answers, and I'm not sure which one to go with.
Click to expand...
Click to collapse
Just download the factory image of your choice and use fastboot to flash everything individually except userdata. You won't be wiped and all you'll have to do is re-root. Or just pick a ROM from development forums.
---------- Post added at 05:07 PM ---------- Previous post was at 05:01 PM ----------
Follow the steps in Method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
As I said, flash everything except userdata. Also skip the factory reset at the end.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
LMY47I is the newest AFAIK.
---------- Post added at 05:15 PM ---------- Previous post was at 05:09 PM ----------
Also, questions go in the Q&A forum, not in general. I've asked the mods to move it there.

XDA-Nexus-User said:
EDIT: I've also noticed, that if I have to re-flash, there are 3 different images for nexus 6 5.1: LMY47D, LMY47E, and LMY47I - this is the first time I've seen this when looking to flash a phone. How do I know which is the most up-to-date, and which one to go with?
Click to expand...
Click to collapse
Verizon phones ship with E. AT&T is currently pushing D (and Sprint). T-Mobile is pushing M.
With that said, (unless you're on TMO), I've tried D, E, and I, and I could not really see any difference. E has the 98R radio, which some users have had better results with. All of the others have the 95R radio. You will have to try both and decide which works best for you.

cam30era said:
Verizon phones ship with E. AT&T is currently pushing D (and Sprint). T-Mobile is pushing M.
With that said, (unless you're on TMO), I've tried D, E, and I, and I could not really see any difference. E has the 98R radio, which some users have had better results with. All of the others have the 95R radio. You will have to try both and decide which works best for you.
Click to expand...
Click to collapse
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?

XDA-Nexus-User said:
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?
Click to expand...
Click to collapse
M was issued as an OTA for T-Mobile users. That being said, @simms22 will confirm that LMY47I works just fine on T-Mobile.

whatever carrier you are on, everything will work regardless of which letter update you chose.

XDA-Nexus-User said:
Well I have T-Mobile, so I'd like to stick with what they are pushing, if for no other reason than to conform to thier OTA push and their unique radio frequencies.
However, the options are "E" "D" and "I" on the Google website. However, you mentioned M. Did you mean one of the others, or is there some unique image not available on the developers.google.com website? Which one off that site would be the default for T-Mobile?
Click to expand...
Click to collapse
Available only via OTA, which means you have to go back to 100% stock first. Here >http://forum.xda-developers.com/nexus-6/general/t-mobile-rolling-lmy47m-5-1-t3059371

im on I, and am on tmobile, with the 95r radio, and everything works, including volte

@simms22: "everything works" is great, but this isn't what I'm looking for, I want to be picky. I'm going to quote @PunishedSnake from @cam30era's link:
PunishedSnake: "M was built 4 days after I so yes it would have all that I has and then tmobile specific stuff"
PunishedSnake: "It's in build.prop
---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?

XDA-Nexus-User said:
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?
Click to expand...
Click to collapse
Letters don't appear to represent sequential release. I is most recent, and represents r3.
If M was going to be released with a factory image, it would normally have been within 48 hours of the OTA. It's been 3 weeks. You can keep waiting, and waiting.....

XDA-Nexus-User said:
@simms22: "everything works" is great, but this isn't what I'm looking for, I want to be picky. I'm going to quote @PunishedSnake from @cam30era's link:
PunishedSnake: "M was built 4 days after I so yes it would have all that I has and then tmobile specific stuff"
PunishedSnake: "It's in build.prop
---------- Post added at 09:31 AM ---------- Previous post was at 09:30 AM ----------
M is greater than I..... "
Honestly, I'd rather wait for google to put M up on their developer's site rather than touch anything at this point. Does anyone think this might happen?
Click to expand...
Click to collapse
you can do whatever youd like, everyone has their own priorities. me, i did it the easiest way, i dirty flashed 5.1 over 5.0.2, kept all my data, all my setup, and everything else. took about 90 seconds

cam30era said:
Letters don't appear to represent sequential release. I is most recent, and represents r3.
If M was going to be released with a factory image, it would normally have been within 48 hours of the OTA. It's been 3 weeks. You can keep waiting, and waiting.....
Click to expand...
Click to collapse
Ok, wow. Never so much confusion is updating a Nexus device...
Some people say M is newer than I, some say otherwise? Either way, doubtful M will be released on google's site, and doublful it has anything I doesn't, so I'll just proceed with the original "Method 2" described in my original reply.
So all I have to do is follow the steps, except make sure not to type: fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img?

To add fuel to the fire, 5.1.1 is expected soon as well. This will, perhaps, unify all builds into one. This is based on the SDK being updated to 5.1.1 a few days ago.
---------- Post added at 07:09 PM ---------- Previous post was at 07:05 PM ----------
XDA-Nexus-User said:
Ok, wow. Never so much confusion is updating a Nexus device...
Some people say M is newer than I, some say otherwise? Either way, doubtful M will be released on google's site, and doublful it has anything I doesn't, so I'll just proceed with the original "Method 2" described in my original reply.
So all I have to do is follow the steps, except make sure not to type: fastboot flash userdata C:/image-shamu-XXXXXX/userdata.img?
Click to expand...
Click to collapse
Yes, correct.

Thank you everyone! Followed @Evolution_Freak's "Method 2" link, re-rooted, and everything seems good. I'm not good at using forums and this was my first time making a thread or being this confused at the particulars of flashing a nexus, but your explanations and information have been very helpful.

XDA-Nexus-User said:
Thank you everyone! Followed @Evolution_Freak's "Method 2" link, re-rooted, and everything seems good. I'm not good at using forums and this was my first time making a thread or being this confused at the particulars of flashing a nexus, but your explanations and information have been very helpful.
Click to expand...
Click to collapse
Glad you got it sorted and glad to have helped in any way.

Please give an example of a build where for example
A R build was older than an I build.
M is 4 days newer than I although I don't know why google hasn't posted the M build. Hopefully the next update brings all N6 to the same build

simms22 said:
im on I, and am on tmobile, with the 95r radio, and everything works, including volte
Click to expand...
Click to collapse
Hate to break this to you, but the I image has a serious problem for certain people on T-Mobile. It completely breaks group messaging using the default messenger, forcing them to use a different messaging program.
I told a friend to use the I Image as I had been told repeatedly everything would work fine. He uses group messaging heavily for work, while I never use it. I caused him some serious problems.
Not trying to rag on you specifically @simms, but I am just warning people in general that not everything works perfectly on T-Mobile without the M build. I tested this myself.

XDA-Nexus-User said:
Hate to break this to you, but the I image has a serious problem for certain people on T-Mobile. It completely breaks group messaging using the default messenger, forcing them to use a different messaging program.
I told a friend to use the I Image as I had been told repeatedly everything would work fine. He uses group messaging heavily for work, while I never use it. I caused him some serious problems.
Not trying to rag on you specifically @simms, but I am just warning people in general that not everything works perfectly on T-Mobile without the M build. I tested this myself.
Click to expand...
Click to collapse
i use the Google messenger app, and arent having any issues with sms, and group sms. no issues here to report.

simms22 said:
i use the Google messenger app, and arent having any issues with sms, and group sms. no issues here to report.
Click to expand...
Click to collapse
Are you verifying that other people receive the SMS message? It does not give an error of any kind.
When I tested it, was in a room with 4 different people, and the message appeared to go through. However, only 1 person on the list I started the group message with would actually receive it.

Related

TRYING TO ROOT IT!| Help rooting 4.3 ML2 on the SGH-i537

XDA:DevDB Information
Rooting with the community the 4.3 ML2 on the SGH-i537, a ROM for the Samsung Galaxy S 4 Active
Contributors
TransformixS4
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Testing
Created 2014-02-28
Last Updated 2014-03-30
Good Job man !
Good luck with this , i hate at&t we ****ed up with locked boot loader
What exactly is the "Odin ML2?" Is that the leaked version that we already have root for? The one we don't have root for is the OTA version, which has nothing to do with Odin. Yet another pointless thread.
Miami_Son said:
What exactly is the "Odin ML2?" Is that the leaked version that we already have root for? The one we don't have root for is the OTA version, which has nothing to do with Odin. Yet another pointless thread.
Click to expand...
Click to collapse
The ota is ML2. He is on the right track. Good work op.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Miami_Son said:
What exactly is the "Odin ML2?" Is that the leaked version that we already have root for? The one we don't have root for is the OTA version, which has nothing to do with Odin. Yet another pointless thread.
Click to expand...
Click to collapse
First off there's no need to be a ****. You are correct that we don't have root for ML2, or the OTA version as you refer to it. The point of this thread is to figure out a way to get root which I think everybody would appreciate, so no need to give the guy grief.
Secondly, while most people received the update to ML2 as an OTA, there were 2 users here who were able to find and post complete Odin packages for ML2 (see this thread and this one), so yes, this thread has everything to do with Odin and rooting ML2. There are summaries of all the official AT&T firmwares in this thread with links to most of the important stuff. Please at least do a search before invalidating somebody who is trying to help the community.
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
TransformixS4 said:
PROJECT: TRYING TO ROOT THE ML2 UPDATE!
Hi Guys!
So I will try to root the Odin ML2.
I will try to upload it on Sunday/Monday.....
Click to expand...
Click to collapse
Thanks for taking the lead on trying to figure out root, I think a good starting point might be a list of all the root methods that others have tried and failed so we don't get people duplicating work that we already know doesn't work. I'll take a crack at putting that list together this weekend. It's nice to have a dev working with the i537.
The only thing I'm trying to invalidate is the need for yet another thread about this. There's several already (like this one: http://forum.xda-developers.com/showthread.php?t=2576460) that could have been used to keep everything consolidated instead of spread all over the forum. I also had a difficult time understanding just what the OP is saying as the grammar is not the best. This post seems more like an exercise in cheerleading than a serious attempt. Regardless, since there is so much confusion regarding the OTA and the leaked versions of ML2 I think it only prudent to be clear when posting anything about either one. This thread was definitely not clear.
Devo7v said:
First off there's no need to be a ****. You are correct that we don't have root for ML2, or the OTA version as you refer to it. The point of this thread is to figure out a way to get root which I think everybody would appreciate, so no need to give the guy grief.
Secondly, while most people received the update to ML2 as an OTA, there were 2 users here who were able to find and post complete Odin packages for ML2 (see this thread and this one), so yes, this thread has everything to do with Odin and rooting ML2. There are summaries of all the official AT&T firmwares in this thread with links to most of the important stuff. Please at least do a search before invalidating somebody who is trying to help the community.
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
Thanks for taking the lead on trying to figure out root, I think a good starting point might be a list of all the root methods that others have tried and failed so we don't get people duplicating work that we already know doesn't work. I'll take a crack at putting that list together this weekend. It's nice to have a dev working with the i537.
Click to expand...
Click to collapse
Well said! :highfive:
TransformixS4 said:
PROJECT: TRYING TO ROOT THE ML2 UPDATE!
Hi Guys!
So I will try to root the Odin ML2.
I will try to upload it on Sunday/Monday.
The thing will be rooting the odin and making it a Pre-Rooted firmware.
People, Listen, Don't hurt my feelings as if you will I will abound this project just like I did with my old Rom on GT-i9300 which turned it into a S4, As Henrylife copied my Rom :/ ... But that is old news...
I will be using my old laptop with a Ubuntu ( I need Linux) USB stick, So I might delay it a few times because there isn't enough memory and the computer is old and half broken.
REMEMBER: TOGETHER WE ARE BETTER AND SMARTER! ARE SMALL COMMUNITY IS REALLY BIG MINDS! SO I WILL NEED YOUR HELP NOT ONLY MINE!
I need your help:
'Enter Device Model' - For Example: I537?
'Enter Sales Code' - ATT?
'Enter PDA Version' - For example: I537UCUBML2?.
'Enter Phone Version' - Version of Modem. For example:I537UCUBML2?.
'Enter CSC Version' - For exampleUCUBML2?.
tell me if this is right.
Ok, Wish us luck.
-TransformixS4
XDA:DevDB Information
Rooting with the community the 4.3 ML2 on the SGH-i537, a ROM for the Samsung Galaxy S 4 Active
Contributors
TransformixS4
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Testing
Created 2014-02-28
Last Updated 2014-02-28
Click to expand...
Click to collapse
Let me know what I can do to help out on my end. Really want to get this rolling so we can move forward with 4.3 compatible SS Roms. However, should we wait a little while for news on the 4.4.2 KK that would be pushed out? I feel like we might end up pouring efforts into 4.3 ML2 and boom, KK gets pushed. Either way I'll try to help in any way possible.
Miami_Son said:
The only thing I'm trying to invalidate is the need for yet another thread about this. There's several already (like this one: http://forum.xda-developers.com/showthread.php?t=2576460) that could have been used to keep everything consolidated instead of spread all over the forum. I also had a difficult time understanding just what the OP is saying as the grammar is not the best. This post seems more like an exercise in cheerleading than a serious attempt. Regardless, since there is so much confusion regarding the OTA and the leaked versions of ML2 I think it only prudent to be clear when posting anything about either one. This thread was definitely not clear.
Click to expand...
Click to collapse
Ok, so I'm not going to argue with you because as I've seen in other threads you really get worked up. By I will try to clarify what the OP is trying to do because there are probably others that are unclear on what he is trying to do.
The other root threads for ML2 focus on using existing root methods to try to root ML2, the purpose of this thread is to develop a completely new root method. The idea is to take the ML2 Odin files and decompile them. Once the files are decompiled he's going to try to inject root into it, and recompile it so we can flash it to our phones.
If this works it would be a lot more simple for the end user than most of the other root methods (except for Active Root, obviously). Additionally if he is able to achieve this, it might be a good idea to try to replace the ML2 bootloader with the MI2 bootloader since it would allow users to be able to downgrade to MF1 and MF2 or MF3 if we ever figure out a way to get that back on the phone. Basically it seems like the most "open" bootloader.
I think this is a definitely a worthwhile effort since it is probably our only chance of getting root on ML2 and a worthwhile thread since it consolidates all the information for this specific root method in one thread. Let me know if there's anything I can do to help.
I personally think that this is a better approach and, depending how it is written, this could survive 4.4 update, seeing how past root approaches were more or less overlays or hijacks, if you will, with it written into the package, it would seem to me, have a better probability to survive.
Also, on another note, no need to disparage someone who is willing to try, a lot of the Roms and roots, on XDA, were written by someone, whose main language is not English.
Sent Via Smoke Signals
I have an i537 already on ML2 here that I don't use at the moment. We can use it to test installs as long as devs here would help me if I have trouble restoring it (should something go wrong with a bad install).
Thread cleaned, keep it respectful.
captaincado said:
Also, on another note, no need to disparage someone who is willing to try, a lot of the Roms and roots, on XDA, were written by someone, whose main language is not English.
Click to expand...
Click to collapse
Actually, the OP is from New York. When relating things of a technical nature it is very important to be clear and precise. These forums are littered with posts from people who either could not follow directions or who followed directions that were unclear and ended up causing a problem with their phones. If the OP has difficulty with English then perhaps he should enlist the aid of someone better suited to be providing technical explanations or directions for us to follow. That's not a knock on the OP's ability to pull this off, just on his ability to present it clearly and understandably. I was a magazine technical editor for many years, so I might be a little sensitive in this area. I've seen a lot of posts by people who were brilliant at figuring stuff out in here, but when it came time to put the actions into words there was much confusion about the processes they were explaining. It is very difficult to write technical material for a broad audience of varying technical abilities. When writing technically, one should always assume that the readers are less savvy and tailor the information to their level, not that of the writer's. So many problems in here would be minimized if developers would remember that the majority of people need to be walked through things step by step instead of assuming that they already know all about the process. Just my $.02.
Oh, I know he is from N.Y. I was being general in nature, the English as a second language part, been too much of deriding in here, when sentence structure isn't to someone's standards, which translators don't do.
As far as the OP is concerned, yes it could have been a little more concise, but he was only saying what he was trying to do, which a lot of people understood, when it's time for the finished product, that's where it should be concise.
Just IMO.
Sent Via Smoke Signals...
Hello all. I'm new to smart phones and the Galaxy s4 active is the first one I have ever owned. I have had it for a couple weeks now and I knew nothing about rooting when i got it, so when I was prompted to update I didn't give it second thought. Now I know about rooting and that I can't do it because of the update Wishing you guys the best of luck with this. I will help out any way I can, as long as any changes I make to my phone can be undone in case it doesn't work. Thanks for the effort.
TransformixS4 said:
PROJECT: TRYING TO ROOT THE ML2 UPDATE!
Hi Guys!
So I will try to root the Odin ML2.
I will try to upload it on Sunday/Monday.
The thing will be rooting the odin and making it a Pre-Rooted firmware.
People, Listen, Don't hurt my feelings as if you will I will abound this project just like I did with my old Rom on GT-i9300 which turned it into a S4, As Henrylife copied my Rom :/ ... But that is old news...
I will be using my old laptop with a Ubuntu ( I need Linux) USB stick, So I might delay it a few times because there isn't enough memory and the computer is old and half broken.
REMEMBER: TOGETHER WE ARE BETTER AND SMARTER! ARE SMALL COMMUNITY IS REALLY BIG MINDS! SO I WILL NEED YOUR HELP NOT ONLY MINE!
I need your help:
'Enter Device Model' - For Example: I537?
'Enter Sales Code' - ATT?
'Enter PDA Version' - For example: I537UCUBML2?.
'Enter Phone Version' - Version of Modem. For example:I537UCUBML2?.
'Enter CSC Version' - For exampleUCUBML2?.
tell me if this is right.
Ok, Wish us luck.
-TransformixS4
XDA:DevDB Information
Rooting with the community the 4.3 ML2 on the SGH-i537, a ROM for the Samsung Galaxy S 4 Active
Contributors
TransformixS4
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Testing
Created 2014-02-28
Last Updated 2014-02-28
Click to expand...
Click to collapse
Any luck so far? Can you give a update as to where you are at with this? Please and thank you...
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Devo7v said:
First off there's no need to be a ****.
Click to expand...
Click to collapse
Devo7v said:
Ok, so I'm not going to argue with you because as I've seen in other threads you really get worked up.
Click to expand...
Click to collapse
:good: straight to it
Astrus said:
I have had it for a couple weeks now and I knew nothing about rooting when i got it, so when I was prompted to update I didn't give it second thought..
Click to expand...
Click to collapse
I did a factory reset to my 4.3 (through Samsung while unrooted) and it downgraded to 4.2.2. I don't know if yours can do the same now that it's rooted, or even if it's meant to do that (when I factory reset my tablet it reset to a blank ROM of the same version it was on), but that could be worth a try.
---
OP: You could dual boot your regular computer if you wanted a better performing linux machine, but I'm sure you know that.
I have the i9295 but I think it would be good the S4A as a whole if we could get more root users. If you need help with anything that needs to be done on a linux computer that yours is struggling to do, let me know. I'm happy to help!
@ tiskael
Oh I never did root my phone, that's what I was saying. I didn't even know what it was at first. So now I know about it and want to root but since I updated, I can't. So you think if I do a factory reset I can get root? I am willing to try and go back to 4.2.2 and then just update when there is a root method for ml2 4.3. How would I do a factory reset? Sorry, like I said, I'm knew to all this.
Astrus said:
Oh I never did root my phone, that's what I was saying. I didn't even know what it was at first. So now I know about it and want to root but since I updated, I can't. So you think if I do a factory reset I can get root? I am willing to try and go back to 4.2.2 and then just update when there is a root method for ml2 4.3. How would I do a factory reset? Sorry, like I said, I'm knew to all this.
Click to expand...
Click to collapse
Oh, right, I misread your original post, sorry. You *may* be sent back to the version your device shipped with - I was on my i9295, I wasn't on my Bauhn tablet though. A factory reset does mean that it's set back to the way it was in the factory, so it should do. It would be worth a try if you really want to root your phone, but I would definitely advise backing everything up either way. A ML2 root is being worked on at the moment but some other nice XDA users.
How to factory reset: http://support.vodafone.com.au/articles/FAQ/Restoring-factory-settings-on-the-Samsung-Galaxy-S4
tiskael said:
Oh, right, I misread your original post, sorry. You *may* be sent back to the version your device shipped with - I was on my i9295, I wasn't on my Bauhn tablet though. A factory reset does mean that it's set back to the way it was in the factory, so it should do. It would be worth a try if you really want to root your phone, but I would definitely advise backing everything up either way. A ML2 root is being worked on at the moment but some other nice XDA users.[/url]
Click to expand...
Click to collapse
Thank you. I am tempted to do the factory reset, but then again I think I will wait for the ML2 root. I could also help in the testing of the method, as long as I have instructions on what to do if something went wrong. Thanks again.
use other sotfware
I think you should use other sotfware to root

[Q] HTC One (M7) Bluetooth audio issue other end cannot hear

Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Bob the Swede said:
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Click to expand...
Click to collapse
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Thank you!
alray said:
Hello Bob, welcome to xda!
Bluetooth call audio was fixed in version 6.01 of NewSenseSIX rom. Your actual version is RC 4.2 which mean "Release Candidate" version 4.2. RC versions are not fully stable, but stable enough for average users to test them. Latest stable version of NewSenseSIX for verizon htc one is 8.0. Updating your rom to latest version should fix your issue.
You might also want to update your firmware to the latest version for more stability. (will be mentioned in the rom thread if required)
You'll have to use twrp recovery version 2.7.0.8 or newer like said in the rom thread
http://forum.xda-developers.com/showthread.php?t=2693502
keep in mind that Verizon variant of the M7 have different partition layout than the internation version(M7_UL), so only use stuff (rom/recovery/tools) that is compatible for Verizon M7 (M7VZW)
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
if you need help how to flash the rom and recovery just ask here and we will help you.
Click to expand...
Click to collapse
Thank you so much! Now I get what is what I might need help finding the right place or thread showing me how to flash the ROM etc. I will look around too of course now that I know what the problem is.
I need help...
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
The link posted by @alray above comes with the download and instructions for flashing TWRP. And the second link takes you directly to the rom.
The only way it could be easier is if he comes to your house and flashes it all for you
Hahaha, I'm sorry, that's embarrassing.
Bob the Swede said:
Hahaha, I'm sorry, that's embarrassing.
Click to expand...
Click to collapse
just take your time and read a lot ..it's all pretty simple once you get a grasp on whats going on
Bob the Swede said:
I am not confident enough to try this on my own and I don;t want to brick my phone.
Can anyone show me the necessary steps needed to do update from RC 4.2 to 8.0..? I have SuperSU v2.14, and TWRP 2.7.0.1.
Click to expand...
Click to collapse
you will first need to upgrade your firmware like said in the rom thread. Click on the link in that thread "Latest Radios and Firmware are REQUIRED and can be found here"
follow instruction to flash the latest firmware in that thread
then flash twrp 2.8.0.1 (also linked in the rom thread just above "Latest Radios and Firmware..." link.
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then push the rom to your phone (either using adb push/adb sideload/usb otg) and install it using twrp.
like cisa said above, if you follow the instructions in that thread andtake your time, everything will be good.
THANK YOU!!!
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Bob the Swede said:
I did it! Thanks to you guys! alray and clsA
I am now on RC8.0 and it is AWESOME! BT works great along with all the extra stuff included.
Click to expand...
Click to collapse
:highfive:

Custom Roms

I saw in another post that the kernel source got released, Im new to this, I was reading a post about how to create custom roms and all that, and i was wondering , we do need root access to get the system files and all that to begin working on a rom ?
What i wanted to do was basically a full stock lollipop rom, but with the Axon Software ( Camera, Dolby Digital, and a few other things ).
I dont have any background expirience creating roms, but whats leading me to this is , loving the phone but hating the toggles, and a few other software bugs ive encountered.
I have some programming knowledge, and I will make this my little side project if theres any chance for it to be done. If anyone has some background and wanna help/teach me, ill be thankfull.
This is the link I been following.
http://forum.xda-developers.com/showthread.php?t=1801690
I have no programming knowledge, but I'll gladly provide moral support and encouragement in this endeavor! A stock lollipop rom with ZTE features would be spectacular.
StaticMoot said:
I have no programming knowledge, but I'll gladly provide moral support and encouragement in this endeavor! A stock lollipop rom with ZTE features would be spectacular.
Click to expand...
Click to collapse
I know right ? Well, If by any chance it can be done, ill keep trying. I guess first we need root.
I would like to support this and I have some java and c++ programming experience. The only problem is that there hasn't been any word on root methods or bootloader unlock methods. Supposedly ZTE phones come bootloader unlocked already, but I haven't been able to prove this since we can't access the bootloader via fastboot :/ if we can at least get root that would be a good start.
Marshmallow on Axon Elite?
Hi all,
I came across this poat while checking for new ROMS. If this checks out I would happily go for the Elite as the price point and features are value for money. For those of you who do have it can you confirm that this is actually a Marshmallow ROM.
Moderator Edit : Links Removed
Thanks all
Danaim said:
Hi all,
I came across this poat while checking for new ROMS. If this checks out I would happily go for the Elite as the price point and features are value for money. For those of you who do have it can you confirm that this is actually a Marshmallow ROM.
Moderator Edit : Links Removed
Thanks all
Click to expand...
Click to collapse
What's up with all of the surveys?
That's what I thought but beyond that has anyone managed to actually get the ROM and verify it to be working?
I am on the cross roads for a new phone.
---------- Post added at 07:27 AM ---------- Previous post was at 07:24 AM ----------
Sub-Negro said:
What's up with all of the surveys?
Click to expand...
Click to collapse
That's what I thought but beyond that has anyone managed to actually get the ROM and verify it to be working?
I am on the cross roads for a new phone. Also would like to know the XDA source mentioned as am sure it won't have ads to download.
Danaim said:
That's what I thought but beyond that has anyone managed to actually get the ROM and verify it to be working?
I am on the cross roads for a new phone.
---------- Post added at 07:27 AM ---------- Previous post was at 07:24 AM ----------
That's what I thought but beyond that has anyone managed to actually get the ROM and verify it to be working?
I am on the cross roads for a new phone. Also would like to know the XDA source mentioned as am sure it won't have ads to download.
Click to expand...
Click to collapse
I am on the Lux model and it's full of Chinese software that I can't even read and I have no access to google apps.
Sub-Negro said:
I am on the Lux model and it's full of Chinese software that I can't even read and I have no access to google apps.
Click to expand...
Click to collapse
I was hoping to get the Elite and be able to flash it as the phone had a lot of potential!
You need to install Google Play Services and Google Services Framework. You will need to sideload these apk's. You will need to Google them.
Please, how can i upgrade my ZTE AXON Elite to Android 6.0? Is it posisible? Thanks
Marshmallow isn't available for this device yet.
When will a custom ROM appear for the Axon Pro?I hate all these chinese stuff and i would like to have the option to reset the phone and redo all the Gmail account,without the phone asking me for the last gmail account.I bought the phone from a friend and i did a reset later that day and it kept asking me for the old account.It sayd that the phone was reset and needs the old account and i couldn't go forward because it kept connecting to google and asked for the old account.I had to use my friends account again to use the phone.I want a simple rom,without this stupid connection to google and other chinese stuff.Any idea when a rom will be available?
No clue but now that you have your friends Google account you should be able to delete it and add your own.
I'm surprised that there isn't any custom roms for this phone yet,i mean its a phone with 4gb of ram,810 Snapdragon so its pretty powerful.
[/COLOR]
raduch said:
When will a custom ROM appear for the Axon Pro?I hate all these chinese stuff and i would like to have the option to reset the phone and redo all the Gmail account,without the phone asking me for the last gmail account.I bought the phone from a friend and i did a reset later that day and it kept asking me for the old account.It sayd that the phone was reset and needs the old account and i couldn't go forward because it kept connecting to google and asked for the old account.I had to use my friends account again to use the phone.I want a simple rom,without this stupid connection to google and other chinese stuff.Any idea when a rom will be available?
Click to expand...
Click to collapse
Why didn't you just do a factory reset? Also, Chinese stuff?
Jonathan.Parker2005 said:
[/COLOR]
Why didn't you just do a factory reset? Also, Chinese stuff?
Click to expand...
Click to collapse
I did a factory reset and it keeps saying that the phone was reset and i need to enter the gmail account that was previously entered.I also tried entering 15-20 time in a row ,because a lot of people say on forums that on note 4 and other phones if you enter the wrong account,the phone will reset and it will let you enter another account.On ZTE this doesn't work .
Jonathan.Parker2005 said:
[/COLOR]
Why didn't you just do a factory reset? Also, Chinese stuff?
Click to expand...
Click to collapse
He probably has a Chinese model. I have the Lux so I know exactly what he is talking about.
Sub-Negro said:
He probably has a Chinese model. I have the Lux so I know exactly what he is talking about.[/QUOTEA friend of mine is a ballet dancer and he bought it when he was on tour in Shanghai,so i think it's the chinese model.
Click to expand...
Click to collapse
Nothing new for the AXON PRO?

[ROM][Stable]Stock Debloated 1.23.1550.3 MetroPCS

This Is My First Shot at making something for this device,so please bear with me.
This Is A Custom Stock ROM that has been debloated and slimmed down a bit to my personal liking.
ive used SuperR's Kitchen on Ubuntu to bring this to you guys.
i used Captain_Throwbacks Metro Base ROM as a starting point.
i will include my list of apps that i have removed in the second post.
i would suggest a factory reset and dalvik/ART wipe
as always,if your device explodes or stops working,i assume no responsibility for any damages or data loss.
flash at your own risk.
if anyone has any suggestions and/or input,please feel free.
im no developer,just taking a shot at this.
the goal is to remove as much bloatware as possible,whilst maintaining stability.
:highfive:
i added /data/app support as well as busybox & deodexed the ROM.
im currently uploading my first build to google drive and will share links shortly.
bear with me as i dont have the best internet connection.
DeZiREv5K
OP Updated with newer build.
Code:
6-14-16 build changelog
--Removed HTC Launcher(replaced with google now launcher)
--updated play store to latest version
--updated HTC Service pack to latest and integrated back into ROM(no longer needs Seperate download)
--attempted to add back the official metropcs device unlock app(Thanks [user=3100103]@sandix[/user] !)
6-16-16 build changelog
---removed google play launcher & replaced with nova launcher(issue with installment on first boot)
6-19-16 build changelog
-- changed ZIP compression method(v3 was too large)
This is A Flashable Zip,should flash in TWRP.
Special Thanks to the following folks:
@sandix for the continuous hard work in the forums here
@Captain_Throwback for his stock rooted metroPCS ROM.
@SuperR. for his Excellent Kitchen!!!
@nightbreed813 for his thread layout & list of modifications to his ROM
This Is My Bloat_Custom File that i edited by hand to suppliment in the kitchen.
these are all the apps/folders that were removed prior to building.
Code:
system/app/BasicDream*
system/app/Calculator*
system/app/CalculatorWidget*
system/app/Chrome*
system/app/Cloudex*
system/app/CloudPrint*
system/app/Drive*
system/app/DriveActivator*
system/app/Exchange3Google*
system/app/FaceLock*
system/app/Font_Helvetica*
system/app/Font_XinGothic*
system/app/Font_Yuen*
system/app/Gmail2*
system/app/GoogleTTS*
system/app/Hangouts*
system/app/HoloSpiralWallpaper*
system/app/HtcCarGps*
system/app/HtcBackupReset*
system/app/LiveWallpapaers*
system/app/HtcLogLevel*
system/app/HTC_Connect*
system/app/HTCZero*
system/app/IMEMurasuIndic*
system/app/IMEMurasuViet*
system/app/IME_TP_Basic*
system/app/IME_TP_ValueAdd*
system/app/Kidmode-google*
system/app/Maps*
system/app/MPCS_Blockit*
system/app/MPCS_Metro411*
system/app/MPCS_MyMetro*
system/app/NoiseField*
system/app/PhaseBeam*
system/app/Photos*
system/app/PrintStudio*
system/app/talkback*
system/app/YouTube*
system/priv-app/HtcDotMatrix*
system/priv-app/HtcFileManager*
system/priv-app/HtcDLNAMiddleLayer*
system/priv-app/MPCS_MetroAppStore*
system/priv-app/iCloudTransfer*
system/priv-app/MPCS_MetroZONE*
system/priv-app/MPCS_RSU*
system/priv-app/LMIRescue*
system/priv-app/Velvet*
system/priv-app/LMIRescueSecurity*
system/priv-app/HtcSoundrecorder*
system/priv-app/Twitter*
system/priv-app/MirrorLink_MirrorLinkService*
system/priv-app/MPCS_Lookout*
system/priv-app/PolarisOffice*
system/priv-app/Mail*
system/priv-app/HTCSpeakCyberon*
system/priv-app/Facebook*
system/media/audio/notifications*
system/media/audio/ringtones*
system/media/audio/alarms*
TO DO List:
edit updater script to change out rom title
check what works and what does not
(Possibly) remove More files/Free up more space
upload newer build as first one fail with status 7 in recovery.(assert error)
Check my build and compare to yours to see what can be removed. I'm sure you will find a lot more that can be done.
when will a working link be available? very excited for this rom
talking_llama said:
when will a working link be available? very excited for this rom
Click to expand...
Click to collapse
i already uploaded a newer build,will update OP with working link.
@sandix ,thank you very much i definitely will do that!
worked for me, thank you!
sweet. finally a flashable rom for our metro variant. was debating on trying nightbreed's rom, as someone mentioned in that thread that they tried it and it worked. didn't want to kill the phone though as it is a daily driver. will report after using.
Ipoke Smot said:
sweet. finally a flashable rom for our metro variant. was debating on trying nightbreed's rom, as someone mentioned in that thread that they tried it and it worked. didn't want to kill the phone though as it is a daily driver. will report after using.
Click to expand...
Click to collapse
Let me know how it works out.also,if you have any suggestions feel free to throw them out here.
so i assume i have to install TWRP and flash this?
corrado85 said:
so i assume i have to install TWRP and flash this?
Click to expand...
Click to collapse
Yeah it's required
Just looking at channel log I'm assuming this is still relevant. I'm on V3 and with some frustration (I don't have Wi-Fi and had to trick my 6yr old laptop to boot up) I got it running well.
As someone who has hard bricked smart phones since the xv6800, this is a first good go. Inspires me to start cooking my own roms.
Suggestion: A file browser would have made it so much smoother. No one with half a brain will ***** about es file explorer or root browser being cooked in. Fortunately bad habits inspired me to always backup original stock. Most people would've been screwed there. Dirty flash. Pdanet. Got it all up and going.
Keep up the good work. Look forward to any tweakings you find out of my league
Sincerely,
Satisfied end user
Sent from my HTC Desire 626s using Tapatalk
trekie4ever said:
Just looking at channel log I'm assuming this is still relevant. I'm on V3 and with some frustration (I don't have Wi-Fi and had to trick my 6yr old laptop to boot up) I got it running well.
As someone who has hard bricked smart phones since the xv6800, this is a first good go. Inspires me to start cooking my own roms.
Suggestion: A file browser would have made it so much smoother. No one with half a brain will ***** about es file explorer or root browser being cooked in. Fortunately bad habits inspired me to always backup original stock. Most people would've been screwed there. Dirty flash. Pdanet. Got it all up and going.
Keep up the good work. Look forward to any tweakings you find out of my league
Sincerely,
Satisfied end user
Sent from my HTC Desire 626s using Tapatalk
Click to expand...
Click to collapse
Thank you for the input,much appreciated.also,i updated OP with a newer build that uses nova launcher as default and puts back a few apks that got cutout by mistake.
My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks
sgeto said:
My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks
Click to expand...
Click to collapse
This ROM is based off of the original Stock MetroPCS USA variant,i didnt add anything that would potentially affect your simlock status.ive only removed stuff that was already there.
If youre not in the US and youre not using MetroPCS Variant of the phone,you shouldnt be flashing this ROM to be 100% honest.flashing incompatable firmwares across devices can sometimes lead to bricks.whats your Carrier and device?
sgeto said:
My phone got simlocked after trying this ROM. It's still locked even after restoring the nanodroid backup I made prior to flasing this ROM.
I'm not in the US sooo I am not using sprint.
Any advice?
Thanks
Click to expand...
Click to collapse
https://www.mediafire.com/?451vq4nmp7paz2a
i2andog said:
https://www.mediafire.com/?451vq4nmp7paz2a
Click to expand...
Click to collapse
That APK will just crash,as the required lib files etc to accompany the APK are missing.
GotHeart said:
This ROM is based off of the original Stock MetroPCS USA variant,i didnt add anything that would potentially affect your simlock status.ive only removed stuff that was already there.
If youre not in the US and youre not using MetroPCS Variant of the phone,you shouldnt be flashing this ROM to be 100% honest.flashing incompatable firmwares across devices can sometimes lead to bricks.whats your Carrier and device?
Click to expand...
Click to collapse
I agree. It's very unusual.
I got this phone from a local phone shop. The owner seem to have unlocked the phone with some kind of service. I contacted my carrier who wrote down a couple of numbers from inside the phone (including the original phone number) and boom, I was able to use the phone with my number.
I have a theory about the error. Maybe you could see if that makes sense:
Maybe the phone isn't locked. But after a factory reset it keeps trying to "activate" the phone using the methods given by sprint.
There's this one step during the initial setup (right after factory resetting the phone) where it tries to register the phone, and fails. This step takes at least tem minutes and returns an error that locks up the phone.
I think the phone assumes that it's locked because it's not able to "reach" sprint servers and denies all incoming and outgoing calls/messages because of this.
If you know a way out of this please let me know.
Another user also provided me with an app that seems to be solving the issue. But it's not marshmallow compatible. Any ideas on that one as well?
Thanks a lot. And great debloating work you did there
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
GotHeart said:
That APK will just crash,as the required lib files etc to accompany the APK are missing.
Click to expand...
Click to collapse
Please tell me more about this app. Cam it solve my issue?
Thx
sgeto said:
I agree. It's very unusual.
I got this phone from a local phone shop. The owner seem to have unlocked the phone with some kind of service. I contacted my carrier who wrote down a couple of numbers from inside the phone (including the original phone number) and boom, I was able to use the phone with my number.
I have a theory about the error. Maybe you could see if that makes sense:
Maybe the phone isn't locked. But after a factory reset it keeps trying to "activate" the phone using the methods given by sprint.
There's this one step during the initial setup (right after factory resetting the phone) where it tries to register the phone, and fails. This step takes at least tem minutes and returns an error that locks up the phone.
I think the phone assumes that it's locked because it's not able to "reach" sprint servers and denies all incoming and outgoing calls/messages because of this.
If you know a way out of this please let me know.
Another user also provided me with an app that seems to be solving the issue. But it's not marshmallow compatible. Any ideas on that one as well?
Thanks a lot. And great debloating work you did there
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
Please tell me more about this app. Cam it solve my issue?
Thx
Click to expand...
Click to collapse
Again,what is your Carrier?if youre using anything other than MetroPCS USA,you should not use this ROM.thats #1.#2 is if youre using sprint,you should get the RUU to return the phone to factory software,and i assume youre using sprint because our Metro devices havent gotten MM yet,and you mentioned it.
And yes,CDMA/Sprint phones will not work correctly if theyre not provisioned from the carrier correctly.so if the activation is failing,then youre not going to be able to use the device to send messages etc until its activated correctly.
Suggestion,try using nightbreeds MM ROM thats for those kinds of carriers.
GotHeart said:
Again,what is your Carrier?if youre using anything other than MetroPCS USA,you should not use this ROM.thats #1.#2 is if youre using sprint,you should get the RUU to return the phone to factory software,and i assume youre using sprint because our Metro devices havent gotten MM yet,and you mentioned it.
And yes,CDMA/Sprint phones will not work correctly if theyre not provisioned from the carrier correctly.so if the activation is failing,then youre not going to be able to use the device to send messages etc until its activated correctly.
Suggestion,try using nightbreeds MM ROM thats for those kinds of carriers.
Click to expand...
Click to collapse
Oh lesson learned. I'm from Yemen and my carrier is YemenMobile (CDMA). I don't know why but I assumed that the phone won't mind the ROM since it was kinda unlocked. SORRY.
The phone was saying Sprint when I bought it. I think I'm going to get back to factory and see if that does the trick. :-/
My extended apologies

How to root Pixel / XL on 7.1?

I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
sturmeh said:
I'm wondering what the process for the Pixel devices is, and if anyone has had any success with existing tools/SuperSU.
It's running 7.1 if that's relevant.
Click to expand...
Click to collapse
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
mattzeller said:
The same way you root other phones, flash custom recovery and supersu.
Sent from my SCH-R220
Click to expand...
Click to collapse
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
sturmeh said:
I guess I have to wait for custom recoveries that support this phone then? I can't see a build for TWRP that supports sailfish.
Click to expand...
Click to collapse
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
eatsleep said:
You'll first need to unlock the bootloader and then wait for chainfire's magic. It is possible to root through fastboot also so there is a good chance that you'll get root before a custom recovery.
Due to seamless updates, things have changed a bit so it'll take some time to be figured out
Click to expand...
Click to collapse
Buy it directly from Google and the bootloader won't be locked, only if you buy it through a carrier like Verizon will the bootloader be locked
Sent from my SCH-R220
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
fkofilee said:
Will be interesting if you can do it CF... Looking forward to release - Ill send a donation your way when done
Click to expand...
Click to collapse
The worst possible thing you could write...
ldeveraux said:
The worst possible thing you could write...
Click to expand...
Click to collapse
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
fkofilee said:
Hmmm... Does it matter ive donated like 3 or 4 times to him already over the years xd
Either way looking forward to it
Click to expand...
Click to collapse
If your intent was truly altruistic, you wouldn't feel the "burden" of stating it publicly. So no, it doesn't matter.
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Confirmation number: 57C48888US937054E
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Appreciate all you do Chainfire, seriously. Can't wait for you to work your magic
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
hutzdani said:
Ah its so funny to what people write after all these years of people spending their own time to work out back doors and exploits to enable root / Xposed / Custom bootloaders / Kernels / Recoveries.
People can't just wait and see and if the devs ask for help or testers just be part of it, throwing a few dollars at them is not going to push things forward . . . let them do what they want to do its their project / baby and it will happen when it does.
Support the devs after the fact dont try and attempt to influence them into it with beer money.
Click to expand...
Click to collapse
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Ker~Man said:
Some of y'all are ridiculous! The guy made a harmless statement and didn't mean anything negative by it. And what do all of the analytical geekers do? Just that... Analyze his comment to the bone and find all sorts of self-serving intent within it. Blows my mind...
Click to expand...
Click to collapse
Totally agree. Thanks for speaking up!
Chainfire said:
This is the first device with Android's new partition layout. Having looked at the firmwares and at running devices (remotely), I have some ideas on how to do it.
However, it will be a while before I have SuperSU fixed up. The changes will be quite a bit of work and testing, and doing so remotely will make that take significantly longer. So I'm just going to wait for my own device, but as they aren't available in my country, it has to be shipped from another country and go through customs. I don't expect my device to arrive for another week or two.
In the meantime, it's always possible someone else releases root for it.
I saw @jcase and @Dees_Troy have been playing with TWRP, to me it seems wholly possible to fix that up (mostly) as well. But even if TWRP is released tomorrow, using the existing SuperSU ZIP will not work on it, due to all the breaking changes in Android 7.1.
Click to expand...
Click to collapse
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Sent from my Pixel XL using Tapatalk
tveith said:
Oh shut up. What a stupid thing to say. People are excited about dev work, and if they suggest a donation, what do you care? Why is it any of your business? If the dev has a problem with people providing positive feedback and offering donations, they will make it known.
---------- Post added at 10:10 PM ---------- Previous post was at 10:08 PM ----------
Totally agree. Thanks for speaking up!
Click to expand...
Click to collapse
What ever but tour the same guys who's going to be asking for OTAs and asking devs to do this that and the other as fast as humanly possible.
If you want it that bad do it your self or sit and wait like a good little child.
No dev is going to rush something because of some people in a forum get a grip, like I said it's their time and it will be ready when it's ready.
You might think I'm going off on one but read the rules page for Christ's sakes.
sionicion said:
Hey I've unlocked my bootloader, but with the different partition layout and file based encryption (assuming this device uses that), is there any chance I'll have to erase my data and start over for root?
Because I got the 128GB model and I'm ready to start filling up with apps and keep a big portion of my Google Play music library to save on data and everything but I don't want to do it if there's a real possibility I'll have to erase everything if to achieve root.
I guess it is possible to use a custom recovery (once they come out) to backup, but that'll be a huge backup if I start keeping all my music to the device.
Click to expand...
Click to collapse
The chance you'll have to erase is always present when rooting. Even when your device is fully prepared something may go wrong. At least you have already unlocked your bootloader, which reduces that chance.
File-based encryption will probably not be a reason to for wiping, though. It works fine in the dev version of SuperSU with Android 7.0 on a 5X.
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
mrnovanova said:
Hey guys. Found this on the interwebs and was wondering how valid it is. http://www.technobuzz.net/root-google-pixel-xl/
Seeing as it calls for twrp which is not yet available, would flashfire work?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks interesting, but without twrp you sure are taking a big chance if something goes wrong.
Sent from my Pixel using Tapatalk

Categories

Resources