Hey guys! So I just saw that the 7.1 preview is coming to our Shamu next month, and it includes the seamless updates the Pixel and Pixel XL are getting! What does this mean as far as our phones partitions? Are they going to be changed from what we're used to? And does this mean it could update itself and potentially brick because of mods we may have? Thanks!
Will i think that you wont get an update if you were in mod as you cant get it now if you rooted or on a customized rom anyway are you sure that we will get it can you show me your sources
My understanding is that the update partition functionality is tied to the hardware, so it won't work on the N6 - I have no specific reference on that (you can look for it as well as I can), it's just what I remember from what I've read. And I'm not worried about the risk of bricking my N6 - it would be unrealistically reckless of Google to issue an update which would break our phones.
But I'll keep my TWRP backups safely on my laptop just in case...
Edit: "are you sure that we will get it can you show me your sources"
Ah, untrusting junior members. He sounds almost like me...
http://forum.xda-developers.com/nexus-6/general/nexus-6-nougat-7-1-preview-t3483997
It may be possible to implement seamless updates through repartitioning of internal storage, but to do it would leave about 11GB left for user files after all is said and done. Not a pretty picture, thus we're not getting seamless updates. Not only that, on a site full of tinkerers and developers, seamless updates would be useless because of our penchant for customizing Android.
My only comment would be is why would we even need it,and why would they waste time implementing it since our device is eol?? And yes I know we will get security updates for awhile but those won't be that big in size.
If there is indeed code for the seamless partition in the N6 build (I wouldn't recognise it if it bit me on the ankle...) isn't it just because Google are trying to keep the code as standard across devices as possible? In my programming life I've seen many programs with code which is active for some purposes and just ignored when non-applicable. It may be a bit of an overhead in the code size, but a few KB here or there don't matter much these days.
So your question "why would they waste time implementing it" - I would say "For the N6, they aren't".
dahawthorne said:
If there is indeed code for the seamless partition in the N6 build (I wouldn't recognise it if it bit me on the ankle...) isn't it just because Google are trying to keep the code as standard across devices as possible? In my programming life I've seen many programs with code which is active for some purposes and just ignored when non-applicable. It may be a bit of an overhead in the code size, but a few KB here or there don't matter much these days.
So your question "why would they waste time implementing it" - I would say "For the N6, they aren't".
Click to expand...
Click to collapse
Correct I've said this already in another thread, but I still don't think we will get it because our major updates are done, and Google has already said only pixel devices + would be getting it
holeindalip said:
Correct I've said this already in another thread, but I still don't think we will get it because our major updates are done, and Google has already said only pixel devices + would be getting it
Click to expand...
Click to collapse
Yea it's definitely all too hazy at this point, I saw a video of I think it was a 5x or a 6p running the new beta, and in the software update area, it said something about seamless updates, like, the developer preview allowed seamless updates on the older Nexus. That's about the time last night I decided to make this thread! lol honestly, my thoughts on this are what's in the op as well as this....... is this going to make manual fastboot flashing more of a pain? like, a crap load of new partitions to worry about on top of the like, 7 partitions Nexus devices already have? And also, mods would be so much harder to use knowing that when the system chooses to update and swaps your system, all your mods would be completely gone!
It was already mentioned that it won't update when modded much like they don't know with root and a non stock system, BUT if your second system partition is unmodified, then it could potentially update that and swap you to that one ._.
Confusing I know, too early to say for sure, but I thought this thread would get interesting.
EDIT: I just downloaded the 7.1 beta for the 6p and looked inside it, the img files all look normal, nothing out of the ordinary. bootloader,boot, radio, system, recovery, userdata, cache, and vendor.
H4X0R46 said:
Yea it's definitely all too hazy at this point, I saw a video of I think it was a 5x or a 6p running the new beta, and in the software update area, it said something about seamless updates, like, the developer preview allowed seamless updates on the older Nexus. That's about the time last night I decided to make this thread! lol honestly, my thoughts on this are what's in the op as well as this....... is this going to make manual fastboot flashing more of a pain? like, a crap load of new partitions to worry about on top of the like, 7 partitions Nexus devices already have? And also, mods would be so much harder to use knowing that when the system chooses to update and swaps your system, all your mods would be completely gone!
It was already mentioned that it won't update when modded much like they don't know with root and a non stock system, BUT if your second system partition is unmodified, then it could potentially update that and swap you to that one ._.
Confusing I know, too early to say for sure, but I thought this thread would get interesting.
EDIT: I just downloaded the 7.1 beta for the 6p and looked inside it, the img files all look normal, nothing out of the ordinary. bootloader,boot, radio, system, recovery, userdata, cache, and vendor.
Click to expand...
Click to collapse
Copy that, yea the factory images won't change much because you are still only flashing one set of partitions
I can only see this as a positive though for people who don't know wth they are doing and like 10 unsuccessful boots will auto boot the other set of partitions,and the seamless update part
Edit: here's the other thread
http://forum.xda-developers.com/nexus-6/general/update-signs-t3455461/post68963916
holeindalip said:
Copy that, yea the factory images won't change much because you are still only flashing one set of partitions
I can only see this as a positive though for people who don't know wth they are doing and like 10 unsuccessful boots will auto boot the other set of partitions,and the seamless update part
Edit: here's the other thread
http://forum.xda-developers.com/nexus-6/general/update-signs-t3455461/post68963916
Click to expand...
Click to collapse
Oh I remember that thread! When the Pixel and Pixel XL factory images are released, I'm gonna download them and check em out. I wonder how much more complicated that makes flashing.
H4X0R46 said:
Oh I remember that thread! When the Pixel and Pixel XL factory images are released, I'm gonna download them and check em out. I wonder how much more complicated that makes flashing.
Click to expand...
Click to collapse
Just edit the flash-all.bat it will tell all
holeindalip said:
Just edit the flash-all.bat it will tell all
Click to expand...
Click to collapse
Oh yea! I forget that that is even a thing, I never once used it lol
H4X0R46 said:
Oh yea! I forget that that is even a thing, I never once used it lol
Click to expand...
Click to collapse
Lol i don't think it's ever worked for the 6, but it tells all for when you get old and don't feel like looking it up on Google or XDA if you forget the commands
holeindalip said:
Lol i don't think it's ever worked for the 6, but it tells all for when you get old and don't feel like looking it up on Google or XDA if you forget the commands
Click to expand...
Click to collapse
It's supposed to work if you have a relatively recent version of Fastboot from the Android SDK but I have also never tried it and prefer to manually flash each image file separately.
alryder said:
It's supposed to work if you have a relatively recent version of Fastboot from the Android SDK but I have also never tried it and prefer to manually flash each image file separately.
Click to expand...
Click to collapse
Mine flashes bootloader and radio then errors out, never tried it again. I always flash individual after that
holeindalip said:
Mine flashes bootloader and radio then errors out, never tried it again. I always flash individual after that
Click to expand...
Click to collapse
I used wugfresh toolkit one time and it gave me that error like, 3 times in a row! Being the noob I was at the time, I FREAKED! Haha no clue what to do! I since started flashing all my partitions manually!
holeindalip said:
Just edit the flash-all.bat it will tell all
Click to expand...
Click to collapse
Just downloaded an image for marlin, and HOLY CRAP! This is a mess o.o Also, the flash-all.bat file just runs the -w update command, doesn't really say which commands are entered other than that! But this looks like a headache to flash manually!
Have a look!
http://imgur.com/a/yJaFq
Also, a pic of the batch file contents! http://imgur.com/a/Fx9Co
H4X0R46 said:
Just downloaded an image for marlin, and HOLY CRAP! This is a mess o.o Also, the flash-all.bat file just runs the -w update command, doesn't really say which commands are entered other than that! But this looks like a headache to flash manually!
Have a look!
http://imgur.com/a/yJaFq
Also, a pic of the batch file contents! http://imgur.com/a/Fx9Co
Click to expand...
Click to collapse
Interesting, the flash-all.bat is the same as ours for the 6
total lack of friday night drinking humor here.......
Pkt_Lnt said:
You *really* want to try flashing 64 bit firmware on a 32 bit phone?
"Cleanup on aisle N6 please". :cyclops:
Click to expand...
Click to collapse
Wth are you talking about about?? If you would of read anything in this thread you would've seen nobody in this thread said anything about flashing a 64bit os on a 32 bit processor
Related
I recently received my nexus 6 a couple days ago and I LOVE it. The problem I am having at the moment is that I can't seem to get it to go decrypt. I downloaded the tool kit and my devices build isn't present. As a result, the tool kit it won't allow me to run the decrypt option on the fastboot window.
It's anyone running into this. My build is a LNX***.
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Didgeridoohan said:
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Click to expand...
Click to collapse
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
KappaAce2010 said:
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
You just need a custom kernel and a wipe.
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Circaflex said:
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Click to expand...
Click to collapse
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
KappaAce2010 said:
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Didgeridoohan said:
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Click to expand...
Click to collapse
I already plan on doing this anyway. Just time is conflicting with me at the moment.
rootSU said:
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
Click to expand...
Click to collapse
Well it happened, it's not going anywhere. Either way thanks guys for the advice. I should figure out everything tonight.
Nexus 6....man I missed being rooted.
Everything is a go. Fully decrypted and loving it. Thanks again.
I'm working on a (100% legit legal and 100% ORIGINAL works) way to flash to our /system partition for kitkat.
I've put my turbo through physical abuse. And it finally croaked weeks after "the drop".
I would need someone who has flashed a /system img via mofo to run USBlyzer on the correct port during the flashing process and then save and upload the log file. I will guide as needed. Remote desktop would allow me to quickly setup and start the process.
No longer having a phone that even turns on, I've resorted to using as USBlyzer as my debugging info by comparing my output to the known correct output. However, I have only logged the beginning of an upload. I need a complete, in order log.
I can help in about 12 hours
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?
5.1:
How it works: Nobody has a clue because the 4.4 loophole is patched.
4.4
How it works: (I'm just making an example don't pick apart my math or partition sizes)
system.img = 3.5gb
cache partition = 1.5gb
So with a modified fastboot, you will write to the cache partition, but send more than 1.5gb of data, since the /system partition is next in order anything you send now will actually write to /system and not the /cache partition.
There are a few quirks I've seen, fastboot sends the "download" command 2x back to back, while the first "download" command hardly sends anything. This has something I assume to be "fake writing" Not quite sure. Its like it writes a tiny amount of data to /cache, sends the second "download" command to now write to /system. I've noticed that the data sent to /cache is actually a clone of a portion of the data sent to /system. Also there is 3gb of ram on the device, so after that gets filled up, the flash command is sent, then it goes back to download commands.
At the end it erases /cache because its full of garbage.
koftheworld said:
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
Click to expand...
Click to collapse
SaschaElble said:
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?
Click to expand...
Click to collapse
Fair enough that is exactly why I stayed on kk.
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
Does anyone have any info on the lolipop .img s
SaschaElble said:
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
Click to expand...
Click to collapse
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
TheSt33v said:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
Click to expand...
Click to collapse
just use a vm...
Michaelmansour1997 said:
just use a vm...
Click to expand...
Click to collapse
Good idea. I'd be willing to do that.
Okay,
Download USBlyzer
Turn on device in fastboot mode
Open USBlyzer
On the left hand side of USBlyzer, watch, while you plug in the device
checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)
click "start capture" in USBlyzer
Open mofo and flash your rom as usual.
When mofo is done, go back to USBlyzer and save the capture log where you will remember.
That log data contains your device serial and UID for your turbo... Thanks for helping the turbo community!
TheSt33v said:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
Click to expand...
Click to collapse
That should work
Michaelmansour1997 said:
just use a vm...
Click to expand...
Click to collapse
SaschaElble said:
Okay,
Download USBlyzer
Turn on device in fastboot mode
Open USBlyzer
On the left hand side of USBlyzer, watch, while you plug in the device
checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)
click "start capture" in USBlyzer
Open mofo and flash your rom as usual.
When mofo is done, go back to USBlyzer and save the capture log where you will remember.
Enjoy uploading 5-8gb of log data since you don't trust me being on your computer. Oh and since we are talking trust, that log data contains your device serial and UID for your turbo... SO actually you might not even want to do that either. Thanks for helping the turbo community!
Click to expand...
Click to collapse
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
TheSt33v said:
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
Click to expand...
Click to collapse
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.
The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
SaschaElble said:
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.
The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
Click to expand...
Click to collapse
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again .
I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
TheSt33v said:
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again .
I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
Click to expand...
Click to collapse
lol. I will for sure! But I won't get banned again. Not if everyone plays by the same rules they expect me to.
Anyone is free to contact me at (Edit: I was such an idiot. 5 years later... wow. ) If you want an easy two click way to get onto my channel on IRC follow the link in my signature.
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
Michaelmansour1997 said:
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
Click to expand...
Click to collapse
I would buy the bricked one, or you can let me see if I can fix it remotely.
NEW:
My vouching thread for those who I request access to their device remotely or gain knowledge of sensitive information:
http://forum.xda-developers.com/general/off-topic/saschaelble-vouching-thread-want-help-t3150299
Do you have a hangouts
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
Project Fi Nexus 6 rooted here on 5.1.1 LVY48E
I keep getting a notice that a system update has been downloaded (29.1) megs..a tad annoying
Would like to run the update, but can't because of TWRP... Also would like to try 6.0 if it is out, just don't want to lose root, and or have to have my phone reset...
I have Wug's nexus root toolkit too
How do I update to the latest L and or/ M???
Looking for some friendly advice....
Thanks!
Forgot to mention that I have tried flashing the update manually to no avail..
Drumrjoe
You can't update your rooted phone with Ota update, only way is to flash the factory image, download latest Nexus 6 factory image from Google and flash it with the tool kit, if you don't know how to flash a factory image, you should see the main thread
And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?
aiiee said:
And I believe , given the need for a modified boot when rooting Marshmallow, you lose the OTA anyway, no?
Click to expand...
Click to collapse
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..
drumrjoe said:
Thanks for the help! Been using the toolkit to try and flash stock + unroot...
It doesn't seem to be working for me... First tried to update to last version of lollipop.. runs the batch updater after downloading the factory image and extracting.. batch window closes after awhile I wait after no change to phone or toolkit and nothing has changed on phone... tried this with marshmallow too... same thing....
At a loss..
Click to expand...
Click to collapse
Just do it manually using fastboot. Or since you have TWRP, find a pre-rooted rom.zip you can flash from there.
Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.
istperson said:
Lately half the threads are about a toolkit not working. There should be a sticky about this: Don't use toolkits on Nexus phones! Those who don't feel secure enough to enter three lines in a command line/terminal really shouldn't use toolkits either. It gives a feeling of false security for a price of being totally at loss if anything goes wrong. And things do go wrong.
Click to expand...
Click to collapse
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.
zelendel said:
We try to advise people not to use rootkits or kits of any kind. It does nothing but hinder their efforts if something goes wrong. In the end it is people being lazy and then bricks happen and they have no idea what to do.
Click to expand...
Click to collapse
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,
danarama said:
I think many of us here agree with that. To avoid bashing, we have to say "use them if you like, but learn to use fastboot manually first". But all the work we collectively put in to that as a majority is easily undone when just one person replies "use a toolkit". It almost always ends up in a debate that is so long that when it reaches it's conclusion, the OP ended up using a toolkit anyway.,
Click to expand...
Click to collapse
I know. All we can do is advise and the lazy will still be lazy and then end up with issues. This is why you will see people post about issues and then the min they mention they have used a root kit all replies stop. There are many of us that refuse to help people that have used a root kit. It shows they should not be messing around with their devices if they dont have the time to learn to do things properly.
Duly noted -
But seriously, thanks for the info.. will be figuring this out!
Best all
DJ
Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA
drumrjoe said:
Update-
Sincere thanks to all that replied.. Did not know that the toolkit's were a nono-
I did use the command line to manually update and all is well. I am on LVY48I now and rooted.. Next is to reinstall the latest xposed for 5.1.1.
Also, tried finding a stock pre-rooted marshmallow, but didn't really have any luck with that... any pointers or links?
TIA
Click to expand...
Click to collapse
Not 100% sure of this but I believe that Marshmallow will not achieve root without some modification. At least I couldn't