What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
lukemovement1 said:
Not long go the pixel 5 and its been a while since I've played with flashing device partitions. Can anyone give me some pointers on the below?
Is the recovery now the boot partition and the boot partition boot_a?
Is their a way of rooting lineage os without having to modify the boot.img? (idk about amazon)
Do I need to re-root with magisk after each update?
Click to expand...
Click to collapse
Unfortunately you might have asked this in the wrong forum, thus no replies. Look here in Guides https://forum.xda-developers.com/t/guide-root-pixel-5-android-11-r.4187609/
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
Fastboot says that the recovery doesn't exists?
lukemovement1 said:
Fastboot says that the recovery doesn't exists?
Click to expand...
Click to collapse
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
lukemovement1 said:
What on earth makes you think I need a guide to rooting my device?
Made the question a bit simpler to avoid confusion
Click to expand...
Click to collapse
Ay, Ay, Ay,,,
To be fair, he was only trying to help, a simple this isn't helpful goes a long way. Being sour though, gets everyone absolutely nowhere.
And you did ask "Is their a way of rooting lineage os without having to modify the boot.img" -- I believe he was guiding you to that thread to possibly ask there as you may get a faster response. I think the question was just taken incorrectly is simply all. No harm, no foul.
bobby janow said:
You did originally ask about rooting so I thought I'd help out a little. What I don't understand is your animosity towards an attempt at posting a possible helpful link. Maybe a simple.. let me clarify my request since it might not have been clear. Oh well good luck.
Click to expand...
Click to collapse
You make more friends with lemonade, or something like that, you were trying to help, so good job in my eyes.
xunholyx said:
Hmmmm, your edit removed the actual question and I don't remember exactly what it was.
Click to expand...
Click to collapse
I'll help.
"Is their a way of rooting lineage os without having to modify the boot.img"
xunholyx said:
I'm not sure what you mean.
fastboot reboot recovery won't work. It never has afaik
fastboot boot *twrp.img name* should work if you are trying the test build of TWRP
adb reboot recovery always works
You can't boot to recovery from bootloader with fastboot commands, but you can boot to it with adb commands while booted to /system
Click to expand...
Click to collapse
I believe he was propbly doing a list of the partition table, and I haven't looked myself, but recovry is missing and instead of doing some research into this, he was simply asking for a simple answer, I feel this is the point of the Q & A forum, so good job to OP.. Personaly I feel this needed a simple answer, as someone coming from like a htc one m8 or htc 10 (like myself) what the hell happened to recovery.img -- a fair question in my eyes, everyone.
AsItLies said:
I'm guessing, as there's really not enough information to know for sure, but is this possibly a google treble question?
prior to treble, yes->recovery partition
with treble->no recovery partition, but another 'slot' for recovery.
cheers
Click to expand...
Click to collapse
Appreciate the info, thank you.
fadedave said:
Recovery and boot have merged into one partition, (on a/b devices at least) and you ship your boot and reco partitions in a unified boot image now which you can flash with fastboot flash boot x.img.
Click to expand...
Click to collapse
Thank you!
Guys, this is how it should work. This is the point of the Q&A thread, ask a question, get an answer, no need for anyone to get upset or to be sour. A question was asked, an answer was kindly given.
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info, asking a question is a battle and half the ROMs and images don't work
lukemovement1 said:
asking a question is a battle
Click to expand...
Click to collapse
That's because you're making it a battle. As mentioned above, you were partly to blame for the initial misunderstanding. If people don't fully understand your question, instead of being upright rude, maybe rephrase or add more clarification as @andybones said.
lukemovement1 said:
half the ROMs and images don't work
Click to expand...
Click to collapse
There are 3 roms in this forum for Pixel 5. They all work and all are regularly updated. You are complaining about the time, sweat and money that developers put in to bring custom roms to us for free. If you don't like something about it, post a feedback or don't use it rather than be disrespectful.
lukemovement1 said:
Kinda lost all faith in this forum tbh. Loads of incorrect and missing info
Click to expand...
Click to collapse
Then leave, or contribute to providing the correct and missing info, rather than, again, complain about free info people bring together in their spare time. None of us here are paid to bring info and provide code. We all do it in our spare time and share our knowledge because we want to make a positive community.
Your total disrespect, negativity and entitlement is not welcome here.
Touché
If you post was removed, it's because I decided to do some house-cleaning -- no one did anything wrong.
And I fixed the title to the thread, so that it's easier on those seeing it and understand what the "simple question" actually is.
Not sure why people get all salty over a simple question...
There is no /recovery partition on Pixel devices. Recovery coresides with the kernel in /boot. Previously, with Android 10, it was possible to install a custom recovery alongside a rooted kernel (such as using Magisk) but Android 11 broke this.
The best and most foolproof option in my opinion is to only temporarily boot a custom recovery to perform modifications. This is what I do every time I get an update on my Pixel 5 - I download the OTA, boot TWRP, install the OTA, reboot to system, let the update finish, boot TWRP again, and flash Magisk.
lukemovement1 said:
What happened to the recovery partition?
Before posting your reply, just to be clear, I do not need a guide on rooting my device or flashing a recovery. This has already been done! So please don't spam links at me for things I can find with a 5 minute search on google because I have don't this already <3
Click to expand...
Click to collapse
agree , the people don't want to help,
Related
Guys, I don't have the original image and the only image I have on my SDcard is eclair 2.0-1.2
I am just upset with the OP for providing insufficient instructions and I am very unaware of the previous setup required before doing it so.
I am in recovery mode and my G1 keeps rebooting over and over since I wipe the factory default.
I apologize for not using the search button because I don't see any answers, or maybe I just want direct answer.
Sorry, I have to ask this, how do I recover the image on my G1? I have it connected to my PC but it's currently in recovery mode right now.
Please provide me detailed step to step what I need to do. Thank you for your time and effort, this is upsetting me big time.
misdirection said:
I am just upset with the OP for providing insufficient instructions
I am in recovery mode and my G1 keeps rebooting over and over since I wipe the factory default.
I apologize for not using the search button because I don't see any answers, or maybe I just want direct answer.
Sorry, I have to ask this, how do I recover the image on my G1? I have it connected to my PC but it's currently in recovery mode right now.
Please provide me detailed step to step what I need to do. Thank you for your time and effort, this is upsetting me big time.
Click to expand...
Click to collapse
LMAO dude this is pure richness right here, you are posting in wrong section you know. And that title of yours isnt following forum rules. Were you rasied under rock or something? There are tons of guides that will tell you what to do, plus even vid guides. All directions are all here for your use.
-Best Regards Ace
Ps. if your in rec mode then your not bricked
Brick=cant turn on G1 pr G1 is stuck @ Splash screen
Gotta give props for the thread title ... is very attracting ... lol
Stop blaming the guys making the ROMS for your own F-up.
Learn to read the instructions.
ALL of them.
Don't blame them for the fact you didn't read THIS :
first you will need these things haykuro spl,ext3/linux-swap if you dont have it and if you do wipe them clean
The please provide links for those kinds of software.
I am really upset that no one will help me
Oh lordy!
Havent laughed this hard in aaaaages!
If nothing else you make for some great entertainment value
misdirection said:
Guys, I don't have the original image and the only image I have on my SDcard is eclair 2.0-1.2
I am just upset with the OP for providing insufficient instructions and I am very unaware of the previous setup required before doing it so.
Click to expand...
Click to collapse
You should be upset at yourself for not reading the clear instructions that are inherent in nearly every ROM update procedure. READ the instructions.
I am in recovery mode and my G1 keeps rebooting over and over since I wipe the factory default.
I apologize for not using the search button because I don't see any answers, or maybe I just want direct answer.
Click to expand...
Click to collapse
Searching forums before diving blindly into processes like these will certainly save you frustration and a bricked device. Again, blaming someone else for your laziness isn't exactly the route you should take.
Sorry, I have to ask this, how do I recover the image on my G1? I have it connected to my PC but it's currently in recovery mode right now.
Please provide me detailed step to step what I need to do. Thank you for your time and effort, this is upsetting me big time.
Click to expand...
Click to collapse
Search the forums.
shadowch31 said:
Oh lordy!
Havent laughed this hard in aaaaages!
If nothing else you make for some great entertainment value
Click to expand...
Click to collapse
I know this place is ***** great, this guy got me laughin here
just return the phone and get an apple iphone
Okay..
How do I put the files into SD card even when my phone is in boot mode?
misdirection said:
Guys, I don't have the original image and the only image I have on my SDcard is eclair 2.0-1.2
I am just upset with the OP for providing insufficient instructions and I am very unaware of the previous setup required before doing it so.
I am in recovery mode and my G1 keeps rebooting over and over since I wipe the factory default.
I apologize for not using the search button because I don't see any answers, or maybe I just want direct answer.
Sorry, I have to ask this, how do I recover the image on my G1? I have it connected to my PC but it's currently in recovery mode right now.
Please provide me detailed step to step what I need to do. Thank you for your time and effort, this is upsetting me big time.
Click to expand...
Click to collapse
1. Read the rules
2. Read the Forum
3. Search on the Forum
4. Post in good place
ums_enable in console
or on amon_ra usb toggle on the main screen
quit hating ppl help noob out, which version of recovery r u using ? or is it stock recovery? Which rom r u trying to flash? If u r using stock recovery u should b serching for something like Fastboot or adb, if u using cyan's or RA's recovery that just find different room to flash.It would b nice to know Phones specs...SPL, Radio, REcovery etc. just like what i got in my sig.
For future references post in Q&A thread or where is the ROM u flashed is, Provide some info if u need help.
I am using standard recovery. I tried Droid Explorer and no luck.
misdirection said:
How do I put the files into SD card even when my phone is in boot mode?
Click to expand...
Click to collapse
Since you're too cocky and too ignorant to do most of the things on here, I suggest you put your phone back to stock as soon as you figure out how to flash images. Get the "recovery image" from here http://developer.htc.com/google-io-device.html, then go ahead and get a card reader, drop the file on the reader, rename it update.zip, boot into recovery, alt+s to flash it, alt+w to wipe, then reboot.
misdirection said:
I am using standard recovery. I tried Droid Explorer and no luck.
Click to expand...
Click to collapse
ok then go here and set up adb after u done follow the link in my sig to flash RA 1.5.2 recovery. After u get RA recovery find the rom u need to flash id suggest Cyans rom or WG and make sure ur SPL and RAdio is uptodate.
Good luck.
Can you atleast change the title?
Such language on a sunday.
HAHA too bad this dump won't allow the wrecking crew to 'assist' this here fella...
Ace42 said:
Can you atleast change the title?
Such language on a sunday.
Click to expand...
Click to collapse
I know right! but hey give him a break i bet almost every1 of u ****ed something up eh ;-) .... personally i so "bricked" my phone twice.....lost root at least 5 times fing around with the roms and scripts....
Brutal,
Me and Ace42 spent around 2 pages in manups thread trying to help only to be told '**** You' we have given him all the links to help him yet still he does not listen and proceeds to be rude and obvoxious.
I think he is looking more for someone to do it all for him rather than using the information already given out to help himself.
All I can say is good luck, your gonna need it!
I own the G1 and it took a good while to root my phone. In the process I only made it to cup cake and now I'm stuck. Dream_Devphone DRC83 debug deal is what I'm using and when I try to reset, I get the android on skateboard scenery and after pressing the power and camera key. Please help me to resolve this problem. Your kindness would be greatly appreciated. I would also like to go beyond all the roms in order to learn about the android world. Please help me.
Djaysay1 said:
I own the G1 and it took a good while to root my phone. In the process I only made it to cup cake and now I'm stuck. Dream_Devphone DRC83 debug deal is what I'm using and when I try to reset, I get the android on skateboard scenery and after pressing the power and camera key. Please help me to resolve this problem. Your kindness would be greatly appreciated. I would also like to go beyond all the roms in order to learn about the android world. Please help me.
Click to expand...
Click to collapse
Hmmmm... what development does this have?
Djaysay1 said:
I own the G1 and it took a good while to root my phone. In the process I only made it to cup cake and now I'm stuck. Dream_Devphone DRC83 debug deal is what I'm using and when I try to reset, I get the android on skateboard scenery and after pressing the power and camera key. Please help me to resolve this problem. Your kindness would be greatly appreciated. I would also like to go beyond all the roms in order to learn about the android world. Please help me.
Click to expand...
Click to collapse
you should search for
g1 root
and if you can't get enough info with that
then give up
you don't have what it takes.
now... where did I leave my marshmallows?
Go to the theunlockr.com. They have good tutorials. Good luck dude.
Follow the steps...
Follow the steps on this site to root your phone...you say you got back to cupcake (1.5) right...ok, then you are going in the right direction. I used these to root my phone a while back. The link actually starts @ donut and goes back, but you can find the cupcake instructions on there also. Remember to be patient...it will happen eventually. Hope that helps.
http://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/
If your phone is truly rooted, just flash a donut or eclair rom? I don't really understand the issue here...
There are a million how-to's here and everywhere else.
It's a complicated process so there is no "easy" answer. I almost gave up a few times in the process but I made it. If I can do it you can too. This is the wrong forum to get help from. I think you want the G1 Q&A forum.
Welcome to XDA-Devs. Search is your friend
Search for Amon Ra's recovery, and flash that. From there, you can easily partition your SD card, and flash ROMs. Also, since you are on the G1, search for and read the thread about flashing the Danger SPL if you want to be able to run some of the bigger ROMs like hero, and some of the eclair roms.
Firerat said:
you should search for
g1 root
and if you can't get enough info with that
then give up
you don't have what it takes.
now... where did I leave my marshmallows?
Click to expand...
Click to collapse
I usually wouldn't step in and say anything, as we were all noobs once. BUT that's pretty damn funny.
Firerat said:
you should search for
g1 root
and if you can't get enough info with that
then give up
you don't have what it takes.
now... where did I leave my marshmallows?
Click to expand...
Click to collapse
Or he could just jump into a blackhole...
djaysay1 said:
i get the android on skateboard scenery and after pressing the power and camera key. Please help me to resolve this problem.
Click to expand...
Click to collapse
what problem???!?!?
lbcoder said:
what problem???!?!?
Click to expand...
Click to collapse
yes that's what is supposed to happen man.. and I appreciate all the guys trying to keep the thread on topic. we were all noobs, and have all posted in places we shouldn't have, but we all learned didn't we? usually I flame people that post in wrong sections but... I took pity on this kid.when you have an expensive device and THINK you've broken it, you do anything to. make it right again, right?
Djaysay1 said:
I own the G1 and it took a good while to root my phone. In the process I only made it to cup cake and now I'm stuck. Dream_Devphone DRC83 debug deal is what I'm using and when I try to reset, I get the android on skateboard scenery and after pressing the power and camera key. Please help me to resolve this problem. Your kindness would be greatly appreciated. I would also like to go beyond all the roms in order to learn about the android world. Please help me.
Click to expand...
Click to collapse
you should have a recovery image installed, if not,install amon ra's. then boot into RECOVERY BY HOLDING HOME AND POWER. DON'T BOOT USING CAMERA AND POWER, THAT PUTS YOU INTO FASTBOOT. YOU FLASH ROMS IN RECOVERY OK? anyways, once you boot into recovery, wipe your phone and flash a Rom and you are all set ok?
oshizzle1991 said:
you should have a recovery image installed, if not,install amon ra's. then boot into RECOVERY BY HOLDING HOME AND POWER. DON'T BOOT USING CAMERA AND POWER, THAT PUTS YOU INTO FASTBOOT. YOU FLASH ROMS IN RECOVERY OK? anyways, once you boot into recovery, wipe your phone and flash a Rom and you are all set ok?
Click to expand...
Click to collapse
its not as easy as that though,,
we have no idea what radio, spl , recovery this guy has.
we can't tell him what to do,
well we can, we can tell him to search and read, he will learn...
read his post, he says he wants to learn.
plenty of stuff to read, no need for questions, they have all been asked and answered countless times.
if he truly wants to learn 'the android world' then he should not be lazy and read, read read.
then play play play
Firerat said:
its not as easy as that though,,
we have no idea what radio, spl , recovery this guy has.
we can't tell him what to do,
well we can, we can tell him to search and read, he will learn...
read his post, he says he wants to learn.
plenty of stuff to read, no need for questions, they have all been asked and answered countless times.
if he truly wants to learn 'the android world' then he should not be lazy and read, read read.
then play play play
Click to expand...
Click to collapse
Have you considered he is very new to all of this an is not sure where to read? Or do you just immediately treat people that ask questions like this? If you do not want to help why even post?
@ op go to www.theunlockr.com they have video and written step by steps on how to root pretty much every phone, roms will require you have a new radio or spl, these can be a little more risque to do as opposed to flashing a rom and calling it done, again unlockr will have tutorials on how to do that as well.
Good luck and i hope this helps.
oshizzle1991 said:
you should have a recovery image installed, if not,install amon ra's. then boot into RECOVERY BY HOLDING HOME AND POWER. DON'T BOOT USING CAMERA AND POWER, THAT PUTS YOU INTO FASTBOOT. YOU FLASH ROMS IN RECOVERY OK? anyways, once you boot into recovery, wipe your phone and flash a Rom and you are all set ok?
Click to expand...
Click to collapse
So.... you want him to install a recovery... by using ... recovery? in order to fix a.... BROKEN RECOVERY??? Wow, your illogic appears unbounded.
And what's this nonsense about not flashing in fastboot? Last I checked, flashing roms was **THE THING** that fastboot does!!!
http://developer.htc.com/adp.html#s5
Firerat said:
we have no idea what radio
Click to expand...
Click to collapse
Not particularly relevant
spl
Click to expand...
Click to collapse
Droids on skateboards.... gonna be one of 0.95.3000(eng), 10.95.3000(hspl), or 1.33.2005(douchspl), and which of those it is doesn't matter.
recovery this guy has.
Click to expand...
Click to collapse
The droids on skateboards say that its not relevant.
we can't tell him what to do
Click to expand...
Click to collapse
droids on boards!!!!
The next step is obvious: flash stuff!
lbcoder said:
Not particularly relevant
Droids on skateboards.... gonna be one of 0.95.3000(eng), 10.95.3000(hspl), or 1.33.2005(douchspl), and which of those it is doesn't matter.
The droids on skateboards say that its not relevant.
droids on boards!!!!
The next step is obvious: flash stuff!
Click to expand...
Click to collapse
like the eris port, that will work on eng yes?
ionic7 said:
Have you considered he is very new to all of this an is not sure where to read? Or do you just immediately treat people that ask questions like this? If you do not want to help why even post?
@ op go to www.theunlockr.com they have video and written step by steps on how to root pretty much every phone, roms will require you have a new radio or spl, these can be a little more risque to do as opposed to flashing a rom and calling it done, again unlockr will have tutorials on how to do that as well.
Good luck and i hope this helps.
Click to expand...
Click to collapse
If he's "not sure what to read", then he needs to do further research. Why are we the bad guys when people just go barrelling though steps and when they realized they missed a step and now they have a fancy new paperweight, they freak out and ignore the rules of the Development section, which, if I remember correctly, is for development, and not for questions. There is a specific section for questions, aptly titled the Q&A section.
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.
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
dbzturtle said:
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
blueyes said:
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
dbzturtle said:
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
Click to expand...
Click to collapse
Fastboot flash twrp, and then flash 2.52superuser.sip in recovery. Look up wugfresh Nexus root toolkit, it'll explain the process.
Sent from my Nexus 6 using Tapatalk
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
dahawthorne said:
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
Click to expand...
Click to collapse
The problem with using toolkits when they are "idiot-proof" is that if you go into the process as an idiot, you leave the process still an idiot, so if something goes wrong with the device at a later date, the user has not got the skills to fix it, which becomes a problem on these forums as rather than telling someone how to fix it, we also have to teach the skills that should already have been learned.
Toolkits are great if you know what they're doing but if you dont, use fastboot the first time to get an understanding of it and also to ensure you know it is working on your computer correctly. It's easier to troubleshoot PC configurations when the device is fully working rather than waiting until it is "broken"
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
dahawthorne said:
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
Click to expand...
Click to collapse
It's not really the long way round. Once everything is installed, its as quick if not quicker. And as I said, you need all this installed for ongoing maintenance anyway so may as well do this whilst your device is working.
You can't brick your device by flashing to the wrong partition so there are no floods of posts from people doing things manually at all. .if you flash to the wrong partition,.just flash to the right partition. It's not rocket science either. If you flash a radio, flash it to the radio partition. If you flash system, flash it to the system partition. ...and if you type something wrong, it won't do anything at all.
Fastboot is well documented (by me and others) in the general forum. People should feel free to nude toolkits once they have learned it, but noobs should definitely learn it and use it the first time for the reasons I have already mentioned.
To root is so simple.
1. In fastboot, use
"fastboot oem unlock"
2. In fastboot, flash a custom twrp recovery image
"fastboot flash recovery twrp.img "
3. If marshamallow, flash a custom boot.img to allow it to be rooted
"fastboot flash boot boot.img"
4. Copy SuperSU to sdcard
5. Flash SuperSU zip from recovery
Once these steps have been carried out, you've used fastboot, know how it works and also have proof your computer has working fastboot. That ticks essential boxes.that every root user needs to have ticked. Once they're ticked, use toolkits to your hearts desire.
The worst thing about noobs using toolkits is when we need them to use fastboot when helping with their issues, they don't know what it is and we have to teach them that. We also need to troubleshoot setting it up which can be extremely hard if their device is bricked or in a state of needing repair. 10 minutes learning now can help prevent hours of wasting our time later. Surely it's only being courteous to learn these things ?
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
getmoneygreen said:
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
Click to expand...
Click to collapse
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
I am an Android Noob! My first Android devices were the Nexus Player and the Nexus 6. (I came from iPhones and Apple TV) It did not take me long at all to learn how to use fastboot and adb. I manually flashed my Nexus 6 and Nexus Player to 6.0 before the OTAs were rolling out no problem. I have root on both of my devices.
My point is, if I can learn how to do this in a matter of a day (I have not had my Nexus 6 a full month yet) You can learn how to do it as well. There are tons of guides out there on how to do all of this. Google is your friend. You will feel awesome and have a sense of accomplishment if you take the time to learn this stuff. It is easy to learn, not hard at all! I come from a pretty extensive tech background so I was a step ahead, but anyone can do / learn this stuff.
There are toolkits that can do this stuff for you pretty much. I have not downloaded or used one myself. I don't trust someone else's code with my device. That's just me though. I like to feel in control when I flash stuff.
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
dahawthorne said:
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
Click to expand...
Click to collapse
Radio may boot but won't connect to a network.
Boot is the kernel so it won't boot without it (bootloop)
Both can be fixed by flashing the correct image to the correct partition.
The images in the factory image are appropriately labelled too, so it would be difficult to flash to the wrong partition without realizing it was wrong.. Eg
"fastboot flash radio boot.img" looks wrong when you have radio.img too.
Thanks, danarama. I suppose that's the point I was trying to make at the top - that if you're a bit of a thicko then you could flash to the wrong partition, which a predefined script won't. As long as it's recoverable, no problem, but I remember the pumping heart and breathlessness as I watched my devices on several occasions sitting with the boot animation for 10-15 minutes and thinking "What the hell do I do now?"
I know I'm hijacking this thread (sorry...) but is there anything you can think of that would definitely hard-brick my device if I'm being thick or careless? I've never managed it, and maybe as Android progresses it's becoming harder to hard-brick, but is there ever a time when I need to think "There's no way back from this one"?
danarama said:
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
Click to expand...
Click to collapse
Thank for the heads up really appreciate that. BTW what is the default password for twrp
getmoneygreen said:
Thank for the heads up really appreciate that. BTW what is the default password for twrp
Click to expand...
Click to collapse
Not sure, Im not encrypted. But its documented somewhere by twrp dev. Maybe on their site or in their thread
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.