Still waiting for Marshmallow... - Nexus 6 Q&A, Help & Troubleshooting

I still haven't received the OTA and Marshmallow update, and am starting to wonder if something is wrong with my device.
I'm in England, my N6 is unlocked, my SIM is "3".
Is anyone else here still waiting for Marshmallow? Or can anyone offer any advice, please?

Unlocked and 100% stock?

danarama said:
Unlocked and 100% stock?
Click to expand...
Click to collapse
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.

AidanBell said:
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.
Click to expand...
Click to collapse
You said your phone was unlocked. I am asking if it is 100% stock? Stock means unmodified.

danarama said:
You said your phone was unlocked. I am asking if it is 100% stock? Stock means unmodified.
Click to expand...
Click to collapse
I do apologise. Your signature about XDA mantras was so huge that I actually missed your question above it!!
The answer is yes, it's 100% stock, unmodified. The only thing that may be pertinent is that I'm on the Marshmallow developers preview. I've had all three previews; numbers two and three came across over the air perfectly. There's just no sign now of the official build.

AidanBell said:
I do apologise. Your signature about XDA mantras was so huge that I actually missed your question above it!!
The answer is yes, it's 100% stock, unmodified. The only thing that may be pertinent is that I'm on the Marshmallow developers preview. I've had all three previews; numbers two and three came across over the air perfectly. There's just no sign now of the official build.
Click to expand...
Click to collapse
Preview doesn't get official build OTA's
You'll have to flash the stock system and boot.img of the official build

danarama said:
Preview doesn't get official build OTA's
You'll have to flash the stock system and boot.img of the official build
Click to expand...
Click to collapse
Oh, I never knew that. Thank you very much.

This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?

AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
The same way you got the dev preview on there I guess.
See the first post at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 In step 5, use Method 2

AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
Did you actually buy your phone with M Preview?

AidanBell said:
This is a pig for me, then, as I don't have much experience in flashing and was hoping very much not to have too. However, that appears to be my only option, therefore can anyone please point me in the direction of a step-by-step guide for flashing Marshmallow onto a Nexus 6 (including making sure I choose the right version in the first place!)?
Click to expand...
Click to collapse
Just fastboot flash the system and boot images.
Go to Nexus 6 General > Sticky roll-up thread > adb and fastboot. What is it?
This will tell you how to set up fastboot and what it is (and how to use it.). Then flash the system.img and boot.img

AidanBell said:
I'm sorry, I don't understand your response. The answer to my question was not mentioned in the opening posts of the thread I posted in, which is why I posted!! Are you saying I missed a thread? In which case my apologies, and I would be grateful to know which thread that is. Otherwise I don't understand what you're trying to tell me.
Click to expand...
Click to collapse
Nah, that's his big sig, The message is one line, the sig is many lines and huge font

aiiee said:
Nah, that's his big sig, The message is one line, the sig is many lines and huge font
Click to expand...
Click to collapse
Huge for a good reason

danarama said:
Huge for a good reason
Click to expand...
Click to collapse

Many thanks for the help and comments, guys.
Yes, I bought the phone from the Phones Show Chat forum. So it was the previous owner who flashed the first preview build, not me.
I guess I have no choice, then, but to have a go at flashing the official build.
I'm not a complete newbie or an idiot, I'm confident that I can do it, but I would have preferred a step-by-step guide that doesn't presume any prior knowledge or experience. The one recommended by Jj14 still assumes a little too much for my liking. If I step a single foot off the correct path, I'll have no idea how to recover. If anyone can recommend another, safer, version I'd be most grateful.

AidanBell said:
I'm not a complete newbie or an idiot, I'm confident that I can do it, but I would have preferred a step-by-step guide that doesn't presume any prior knowledge or experience. The one recommended by Jj14 still assumes a little too much for my liking. If I step a single foot off the correct path, I'll have no idea how to recover. If anyone can recommend another, safer, version I'd be most grateful.
Click to expand...
Click to collapse
You can find the factory images here: https://developers.google.com/android/nexus/images?hl=en#shamu
There are the instructions how to flash it, but ignore the last step of locking the bootloader. If something goes wrong, and can't boot it, you can have a nice brick in your hands.
Save all your data! The flashing process will wipe it completely.
There's not magic needed, just fastboot. Turn your phone off, press down and power, until the "Fastboot flash mode" screen comes up. Then follow the instructions.
A couple of things explained:
1. The bootloader for the M preview and MRA58K were the same, but the MRA58N one might be new. I didn't try it.
2. if you unpack the "flash all" zip file, you can do the flashing by hand yourself, you can skip userdata if you don't want your device fully wiped, but then you must do a factory reset.
And if something is not clear, please feel free to ask anything. It's better to be sure than being modest and have a nice brick.
Edit: The bootloaders are the same bit for bit as the preview.
And the three official packages 58k, 58n, and 58r have the same radios.
58n is the security patch it is noted in the AOSP source too, and nobody knows what 58r is, but it can be for Verizon. But I'm not sure.

Continued thanks.
Still very nervous and somewhat out of my depth, but here goes nothing.
And ... fell at the first hurdle!
Can someone please tell me which version I need; "MRA58K", "MRA58N" or "MRA58R"?

Always the newest. MRA58K was the first Marshmallow factory image. MRA58N is the 1st November securty update, and so far nobody knows what 58R is. People are guessing here:
http://forum.xda-developers.com/nexus-6/help/mra58r-build-t3242328

I found this excellent step-by-step guide, and followed it carefully. Result ... I now have official Marshmallow.
http://www.digitaltrends.com/mobile/how-to-install-android-factory-image
So, I recommend that page to anyone else who, like me, needs a guiding hand. And I thank very much everyone in this thread for your help and encouragement.
Cheers,
Aidan

I'm stuck on LVY48I ( 5.1.1 )
don't know why it's too long to get the update !!
My Nexus totally stock.

Related

[Q] Root M7 but Maintain HTC ROM (Lollipop 5.0.2/Sense 6.0)

Hi everyone. I'm new to the forum; this is my first post.
I have an M7 on a stock HTC/AT&T ROM running Lollipop 5.0.2 with Sense 6.0.
I would like to root the device so that I can do things like eliminate ads, remove bloatware, run more advanced software, etc., but I do not want to loose things like Beats Audio/Boom Sound. So I'm thinking I just want to stick with the stock AT&T/HTC M7 ROM.
I have seen reference to the Sunshine App, but unless someone can tell me it does something absolutely magical for the one-use $25 payment they expect, I'm fine doing it the free way. I got the impression about Sunshine that it doesn't actually get you all the way to root. If it got me all the way and saved my data/apps, too, I'd be all over it.
Can someone please give me the full path of steps I need to go through to get this done? I'm not a dumb guy. Pretty computer savvy, actually, but there is a lot of jargon and intermediate steps that seem to be involved in all of this. Some of the videos I'm seeing are quite dated at this point, and I have to wonder if they are relevant to an AT&T M7 on Lollipop a this point. But I thrive on step-by-step tutorials, so if you guys point me to the right videos or written tutorials, I should be fine.
Any suggestion on the best way to backup my device would be appreciated, too. I understand I'm going to get all my data and programs wiped somewhere along the path.
Thank you!
djMot said:
Hi everyone. I'm new to the forum; this is my first post.
I have an M7 on a stock HTC/AT&T ROM running Lollipop 5.0.2 with Sense 6.0.
I would like to root the device so that I can do things like eliminate ads, remove bloatware, run more advanced software, etc., but I do not want to loose things like Beats Audio/Boom Sound. So I'm thinking I just want to stick with the stock AT&T/HTC M7 ROM.
I have seen reference to the Sunshine App, but unless someone can tell me it does something absolutely magical for the one-use $25 payment they expect, I'm fine doing it the free way. I got the impression about Sunshine that it doesn't actually get you all the way to root. If it got me all the way and saved my data/apps, too, I'd be all over it.
Can someone please give me the full path of steps I need to go through to get this done? I'm not a dumb guy. Pretty computer savvy, actually, but there is a lot of jargon and intermediate steps that seem to be involved in all of this. Some of the videos I'm seeing are quite dated at this point, and I have to wonder if they are relevant to an AT&T M7 on Lollipop a this point. But I thrive on step-by-step tutorials, so if you guys point me to the right videos or written tutorials, I should be fine.
Any suggestion on the best way to backup my device would be appreciated, too. I understand I'm going to get all my data and programs wiped somewhere along the path.
Thank you!
Click to expand...
Click to collapse
just posted this for someone else
Flash TWRP 2.8.5.0
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
/ enter recovery
Exit recovery choose yes to Root
when the phone boots up go to the SuperSU Icon in the app drawer
it will ask to update / choose TWRP
after it reboots your rooted
clsA said:
just posted this for someone else
Flash TWRP 2.8.5.0
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
/ enter recovery
Exit recovery choose yes to Root
when the phone boots up go to the SuperSU Icon in the app drawer
it will ask to update / choose TWRP
after it reboots your rooted
Click to expand...
Click to collapse
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
djMot said:
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
Click to expand...
Click to collapse
Yeah, that's not going to happen
Read the FAQ >> http://forum.xda-developers.com/showthread.php?t=2228274
and the So you came at XDA-Developers to find help
If your still stuck after that then ask questions.
Hint: I described all the steps in post 2 above
djMot said:
Thanks, but I think you are making a few too many assumptions that I understand what your saying.
I don't think I can just flash twrp before unlocking the bootloader, am I right? And I have no clue how to flash twrp, how to set up to do that, and what to have where. I can do the steps if I know what they are. So I really am looking for a pretty explicit set of steps. You've given me some steps, yes, and thank you for that(!!), but I think you're coming from a position of already knowing exactly what you are doing and all the ramifications of each and every step you would take, so by the time it gets to me it just sounds like the cliffs notes and I'm still wondering what the novel is about.
And, yes, I get that some of you here answer these kinds of noobie questions a lot, and it just gets tedious repeating yourselves. Unfortunately for us noobies who come looking to the experts for the straight-up how-to, the responses all seem like "just do this, do that" without any discussion of how to do this and how to do that. I've read several "how do I root my phone" threads here, but the answers all seem just a little to Greekish to me, and to others too I would imagine. The video tutorials here were recorded back when the M7 was brand new and there's no indication at all whether updates along the way to present day have altered the process, or whether there is a safer, better way after all this time. I have no idea if they are relevant today.
I get that I'm asking a lot for such an old device, but I would really appreciate a little of a tutorial approach.
Thanks very much.
Click to expand...
Click to collapse
Hi,
I know its 2019, four years since you posted this request, but I just pulled my HTC One M7 AT&T after 3 years and had the exact same query and needed a way to ensure that steps mentioned in posts like these in 2015 are still relevant/applicable on our device running Android 5.0.2 with HTC Sense 6.
I was looking to have a device specific tutorial to finally make the plunge to install a custom ROM (someone ported Android 10 to this device!) , but remember there being some complexities back in the day to do this on our device. Were you able to get around this? Look forward to your response.
Thanks & regards,
Deepesh

How many people took the 5.1.1 and are stuck with the "locked" bootloader

If you didn't know the 5.1.1 update comes with a "locked" bootloader (G920T) that does not allow you to flash custom recoveries. I would like to know what your status is if you don't mind because I think the more people who are stuck like me the more developers will say we need to come up with a fix for flashing custom recoveries issue.
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
mikeyinid said:
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Click to expand...
Click to collapse
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
se1000 said:
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
Click to expand...
Click to collapse
What I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
ethanscooter said:
Accidently* wasn't really paying while typing and what I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
Click to expand...
Click to collapse
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
ethanscooter said:
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
Click to expand...
Click to collapse
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
se1000 said:
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
Click to expand...
Click to collapse
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
mikeyinid said:
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
Click to expand...
Click to collapse
I understand it isn't locked but what I mean is for the time being it feels like it is locked considering we can't root or install a custom recovery or downgrade.
ethanscooter said:
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
Click to expand...
Click to collapse
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
se1000 said:
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
Click to expand...
Click to collapse
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
ethanscooter said:
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
Click to expand...
Click to collapse
You have 2 threads in the QA section that are on this same subject.
Look, if you want to have a rooted, custom recovery, custom kernel device, don't be the first to update. That's just how things go.
From the Moderator
Redundant Thread ......... So........
..............THREAD CLOSED...........

New N6 shipped with developer build?

Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
csdaytona said:
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
no access at all?
simms22 said:
no access at all?
Click to expand...
Click to collapse
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
csdaytona said:
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
Click to expand...
Click to collapse
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
simms22 said:
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
Click to expand...
Click to collapse
OK what is it and why is it frowned upon?
csdaytona said:
OK what is it and why is it frowned upon?
Click to expand...
Click to collapse
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
simms22 said:
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
Click to expand...
Click to collapse
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
|Jason8| said:
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
First time doing this, but it's OK to jump straight to 6.0?
csdaytona said:
First time doing this, but it's OK to jump straight to 6.0?
Click to expand...
Click to collapse
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
if you can get to a computer..
you can unlock your bootloader with "fastboot oem unlock"
then fastboot flash twrp recovery
then flash a custom kernel wiyh the latest supersu in your new recovery.
and then boot up with root, an unlocked bootloader, and a custom recovery
|Jason8| said:
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
Click to expand...
Click to collapse
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
csdaytona said:
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
Click to expand...
Click to collapse
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
csdaytona said:
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
simms22 said:
no access at all?
Click to expand...
Click to collapse
csdaytona said:
Not at the moment.
Click to expand...
Click to collapse
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Click to expand...
Click to collapse
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
scryan said:
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
I linked him to that already. No need to be a **** about it. He was looking for an easy way to do it now, when he doesn't have a computer. **** got crazy, so he asked if it would be easier with a computer, which the answer is yes.
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
csdaytona said:
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
Click to expand...
Click to collapse
No problem man. I wish you luck!
If you do plan on modding it/rooting it/romming it in the future, DEFINITELY unlock your bootloader before you set up the phone or that'll wipe it, too.
|Jason8| said:
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
Click to expand...
Click to collapse
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
scryan said:
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
scryan said:
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
Click to expand...
Click to collapse
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
simms22 said:
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
Click to expand...
Click to collapse
At that point its a legitamate question. This is a very different situation that is not well covered here, and requires a unique solution not many would come up with.
But "I absolutely have no computer nor laptop access" is pretty different then "I can access one TOMORROW. Sheesh, having something 1 day away is pretty far from it not being a possibility.
And I think you would agree it would be a significantly better idea to wait that day then to proceed with the method you gave (not that it was bad of you to give it... but you tried to differentiate and he held out to avoid being told to do it the hard way)
|Jason8| said:
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
Click to expand...
Click to collapse
We are told time and time again that their are no bad questions. Truth is there are more bad questions then good ones.
Him asking about a build that provides few google hits is very legitimate.
Him asking about doing it without a computer because he doesn't have one is legitimate.
It only becomes an issue when he doesn't get the answer he wants, and all of a sudden he does have computer access.
And given that he is going to proceed in a computer... It becomes nothing more then "How do I update my phone?", which is VERY well documented.
I not only gave him the link to the information he needed, AND even corrected the information pointing out that the flashall script fails and that he would need to use the second method listed in the instructions I linked him to (since I know he will likely have limited time to fail and figure out whats wrong)
"That's the exact opposite of what you're saying you strive to do. I don't get it."
Then let me explain.
Would you skip your homework, ignore your textbook, then show up to class asking your teacher to explain it again? We are here to help... but how or why should I care more about it then he does? With no attempt made to learn, how much should I care to teach him?
Its a pretty big **** you to all those who have spend countless hours documenting this stuff to help new people to ignore their work and tell someone to do it again.

Flashing back to stock

I looked for other threads on the issue and didn't really find any that helped.
I am currently on cm12.1 with twrp 2.8.7.1
I am downloading the latest stock build from the google developers site:
https://developers.google.com/android/nexus/images#shamu
Basically, I need to know how to go about it. Ideally I could flash it via twrp, but I've never had a phone where factory images were flashable like that.
Essentially what I want to end up with is stock, with twrp, xposed and gravitybox.
Can someone point me in the right direction?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Found this finally. I think it answers my question.
Forboding Angel said:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Found this finally. I think it answers my question.
Click to expand...
Click to collapse
Use method 2 (img`s), flash-all is broken.
Yeah, I figured that out after a bit haha
I could have probably written a new script for it, but that wouldn't really do anyone any good, so I just did it manually. Plus I didn't feel like figuring out how to tell a script to wait for bootloader restart. Thank you

Going from DRL6 to CRK1

Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!
Spectrah said:
Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!
Click to expand...
Click to collapse
Download CRK1 with the SamFirm tool
Flash it with patched ODIN 3.13.1
Spectrah said:
Hey there, I decided to try out the beta but I'm looking to revert to stock Oreo so I can get Pie through OTA. However I have no clue how to do it, I've read a couple threads referencing this but I can't seem to piece together what needs to be done.
Would someone be so kind to post step by step instructions on what I need to do? I'm pretty techy so just basic instructions would be a great help. Thanks and have a great day!
Click to expand...
Click to collapse
Download this firmware crk1 from here https://androidfilehost.com/?fid=11410963190603879881 extract the files and you'll see inside of the extracted folder more files that have .md5 on the end of them right click on the files and click rename and just delete the .md5 part only and leave it so it still has the .tar on the end then use the REGULAR NEWEST version of Odin NOT the patched one and then load the files in their respective places AP to AP, BL to BL etc. etc. Then just flash it to the phone while the phone is in download mode and after the successful flash boot into recovery mode and select factory reset so everything is the way it's supposed to be.... Finished!
I really appreciate the help! I'm a bit confused because Mr. Orange is saying use patched ODIN but MrMike is saying not patched version. I'm not sure which version to use then.
Spectrah said:
I really appreciate the help! I'm a bit confused because Mr. Orange is saying use patched ODIN but MrMike is saying not patched version. I'm not sure which version to use then.
Click to expand...
Click to collapse
The patched one may not work and you'll be forced to start over.. The newest version of odin is for the newer bootloader versions and the patched one isn't updated for the newer bootloader versions but you can try it if you want if it doesn't work then start over.
MrMike2182 said:
The patched one may not work and you'll be forced to start over.. The newest version of odin is for the newer bootloader versions and the patched one isn't updated for the newer bootloader versions but you can try it if you want if it doesn't work then start over.
Click to expand...
Click to collapse
Hmm, is there any advantage to using the parched version? It sounds like there's an official version that will get me the desired results from what you're saying.
Spectrah said:
Hmm, is there any advantage to using the parched version? It sounds like there's an official version that will get me the desired results from what you're saying.
Click to expand...
Click to collapse
The patched version is usually used to switch from N950U to N950U1 or the other way.. I would just use the official version if I were you because I ALREADY flashed from 5DRL7 back to N950USQS5CRK1 and it's working perfectly.. But if you want to mess with the patched version you can but like I said if it doesn't work then you have to start over.
MrMike2182 said:
The patched version is usually used to switch from N950U to N950U1 or the other way.. I would just use the official version if I were you because I ALREADY flashed from 5DRL7 back to N950USQS5CRK1 and it's working perfectly.. But if you want to mess with the patched version you can but like I said if it doesn't work then you have to start over.
Click to expand...
Click to collapse
I'm gonna use the patched version, thanks so much for all of your help!
Spectrah said:
I'm gonna use the patched version, thanks so much for all of your help!
Click to expand...
Click to collapse
Must be something wrong with you obviously.. You go and ask for help and then the person who gives you the most details on how to do it and you'd rather listen to someone who gave you a one line answer. LMAO. Actually this is probably my own fault because I should have known better that when someone asks for step by step instructions basically asking someone to hold their hand through the process that they're a problem..
I used the patched version and it works perfectly on the N950U.
Mr. Orange 645 said:
I used the patched version and it works perfectly on the N950U.
Click to expand...
Click to collapse
Well others in the other thread complained that it didn't work but that's why I said it may or may not work I didn't outright say it doesn't work.
MrMike2182 said:
Well others in the other thread complained that it didn't work but that's why I said it may or may not work I didn't outright say it doesn't work.
Click to expand...
Click to collapse
I never said you did. Is there a particular reason you're being so confrontational and taking things so personal? You just bit the OP's head off and called him "a problem," because he didn't take your advice exactly. I didn't even mention you, quote, or refer to you. I was just sharing my experience, yet you jump on and defend yourself. Try to realax a little and have fun.
Mr. Orange 645 said:
I never said you did. Is there a particular reason you're being so confrontational and taking things so personal? You just bit the OP's head off and called him "a problem," because he didn't take your advice exactly. I didn't even mention you, quote, or refer to you. I was just sharing my experience, yet you jump on and defend yourself. Try to realax a little and have fun.
Click to expand...
Click to collapse
That's because too many folks on here want someone to hold their hand through the entire process instead of actually spending the time to learn how to do it on their own and then when you go spend your time to give them the best answers so they don't waste their time running into possible problems that others have stated that they did and then person just decides to go do the opposite then it's like what did you even ask for help for then? I agree that I was a bit of a jerk but that's from constantly dealing with that on here.
MrMike2182 said:
Must be something wrong with you obviously.. You go and ask for help and then the person who gives you the most details on how to do it and you'd rather listen to someone who gave you a one line answer. LMAO. Actually this is probably my own fault because I should have known better that when someone asks for step by step instructions basically asking someone to hold their hand through the process that they're a problem..
Click to expand...
Click to collapse
Unfortunately that was a typo and I meant the non patched version. Obviously you went above and beyond in making sure I was prepared and I really appreciate that. Sorry about the confusion.

Categories

Resources