So my 64GB GRAY Nexus 6 arrived on 5.0 and it wants to update to 5.0.1. I enabled USB debugging and OEM unlock and I am going to unlock it then make a nandroid of 5.0. Not sure why I am doing that but I thought I would.
Is there any reason to upgrade to 5.0.1 before flashing to 5.1? I thought I would let the OTA happen, then make another nandroid. Then flash to 5.1. Then make another nandroid.
JulesJam said:
So my 64GB GRAY Nexus 6 arrived on 5.0 and it wants to update to 5.0.1. I enabled USB debugging and OEM unlock and I am going to unlock it then make a nandroid of 5.0. Not sure why I am doing that but I thought I would.
Is there any reason to upgrade to 5.0.1 before flashing to 5.1? I thought I would let the OTA happen, then make another nandroid. Then flash to 5.1. Then make another nandroid.
Click to expand...
Click to collapse
If you want to upgrade to 5.1 via the OTA, you have to be on 5.0.1.
cam30era said:
If you want to upgrade to 5.1 via the OTA, you have to be on 5.0.1.
Click to expand...
Click to collapse
OK that is an upside to taking the 5.0.1 OTA. lol! I was going to flash to 5.1 though b/c I am on Verizon with a non-Verizon branded device and I wasn't sure how the OTAs work if you are using a non-Verizon N6 on Verizon.
Right now I have activated the phone through WiFi w/o a Verizon SIM card in it.
Any downsides for me to take the 5.0.1 OTA? I don't think there are but I wasn't sure if I was missing something.
JulesJam said:
OK that is an upside to taking the 5.0.1 OTA. lol! I was going to flash to 5.1 though b/c I am on Verizon with a non-Verizon branded device and I wasn't sure how the OTAs work if you are using a non-Verizon N6 on Verizon.
Right now I have activated the phone through WiFi w/o a Verizon SIM card in it.
Any downsides for me to take the 5.0.1 OTA? I don't think there are but I wasn't sure if I was missing something.
Click to expand...
Click to collapse
Nothing I'm aware of.
JulesJam said:
OK that is an upside to taking the 5.0.1 OTA. lol! I was going to flash to 5.1 though b/c I am on Verizon with a non-Verizon branded device and I wasn't sure how the OTAs work if you are using a non-Verizon N6 on Verizon.
Right now I have activated the phone through WiFi w/o a Verizon SIM card in it.
Any downsides for me to take the 5.0.1 OTA? I don't think there are but I wasn't sure if I was missing something.
Click to expand...
Click to collapse
It's may be easier to just use the factory images to get 5.1 rather than do the 5.0.1 OTA update and then adb sideload the 5.1 OTA update. Whatever you do, don't relock the device until everything is working and booting .
mwalt2 said:
It's may be easier to just use the factory images to get 5.1 rather than do the 5.0.1 OTA update and then adb sideload the 5.1 OTA update. Whatever you do, don't relock the device until everything is working and booting .
Click to expand...
Click to collapse
thanks, I am going to use the factory images to get to 5.1 but wasn't sure if there were any issues with the 5.0.1 OTA. And I definitely would never relock my bootloader ever!!
Related
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
If all you want to do is update, you could install Custom ROM although you will lose Motorola's Active Display, Always Listening etc...
If you want complete stock and have to reflash TWRP and root your phone, you will need to flash the stock firmware using fastboot or a utility.
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Alecegonce101 said:
Well I too have a Dev Edition but is SIM-Unlocked so it isn't Verizon.
Click to expand...
Click to collapse
Um, all VZW Moto Xs are SIM-unlocked.
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
I hope it wasn't the pre-camera 4.2.2....or you might be in a tough spot now.... Risking a brick. ?
---------- Post added at 10:09 AM ---------- Previous post was at 10:08 AM ----------
Unless the first firmware was also pre camera... Then you're OK.
dukeoid said:
I have new Verizon Moto X Dev Edition. Messed up. Thought it was already on 4.4.2. Not, it's on 4.2.2. Unlocked bootloader and installed twrp and rooted. Wanting to update it to 4.4.2. Thinking from reading that I need to get back to stock recovery for OTA update if that is possible over wifi since phone is not activated yet. Can't find 4.2.2 stock recovery and not sure if that is what I need to do anyway. Is that what I need to do and/or is there a better way? Thanks
Click to expand...
Click to collapse
dukeoid said:
Finally found 4.2.2 . When trying RSD fail at gpt bin, also fails there with manual flashing. Any ideas?
Edit...Finally got it. Different version of 4.2.2 did it.
Click to expand...
Click to collapse
Taking OTA's is incremental, so if you are the initial shipping 4.2.2 you need to take the first 4.2.2 w/camera OTA, then the 4.4 OTA, then the 4.4.2 OTA... a real time waster and pain in the rear.
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
Since you have a Dev Edition, why not just go to 4.4.4? it has a few bug fixes, and is stable. For me and many others its no worse than 4.4.2 as far as performance and battery.
Once you arrive on the ROM you want, you can flash TWRP and root.
KidJoe said:
Best way... Grab the SBF for the version you want to be on, and flash it... i.e. you mention going to 4.4.2, so... grab the 4.4.2 SBF and flash it.
t.
Click to expand...
Click to collapse
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
Yup! ?
As long as it's not a lower version.
dukeoid said:
OTA'ed to 4.4.2. But for future reference you can skip versions and SBF to the one you want??
Click to expand...
Click to collapse
OTA = Incremental. Only patches the changed/updated parts.
SBF/FXZ = "all inclusive" or "image files".. and overwrites entire partitions/parts.
So yes. You can just flash the newer SBF file. (As @Darth said... as long as the SBF you are flashing is NEWER than the version on your phone... i.e. NEVER DOWNGRADE)
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
pokedroid said:
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
Click to expand...
Click to collapse
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
ac3theone said:
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
Click to expand...
Click to collapse
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
rootSU said:
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
Click to expand...
Click to collapse
I just installed it as an update.zip using adb. No unlock required.
pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
FYI, AT&T have no control over the update process. The update comes directly from Google, for all carriers. As long as you didn't install M or I, you're fine. There is nothing that AT&T could do to prevent anyone getting the update. Except maybe sending a memo out to a staff saying "you'll receive an update from Google. Please, please, please don't accept it"
pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
ac3theone said:
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
Click to expand...
Click to collapse
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
rootSU said:
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
Click to expand...
Click to collapse
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
ac3theone said:
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
Click to expand...
Click to collapse
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
rootSU said:
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
Click to expand...
Click to collapse
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
pokedroid said:
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
Click to expand...
Click to collapse
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
rootSU said:
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
Click to expand...
Click to collapse
Oh, I was thinking the boot loader status would show "relocked" when in fastboot
Will an ota push to put the n6 on a verizon build like LMY47E if its currently on LMY47M and I put a vzw sim in it? Everything works now, just curious if it'll come automatically or if i need to load it manually.
Restola said:
Will an ota push to put the n6 on a verizon build like LMY47E if its currently on LMY47M and I put a vzw sim in it? Everything works now, just curious if it'll come automatically or if i need to load it manually.
Click to expand...
Click to collapse
Probably not. If you're not on E, when Verizon finally releases the OTA, you won't get it.
Thanks. Decided to unlock and flash lmy47e to avoid any issues.
Hi,
Can you please tell me how did you flash lmy47e?
I tried doing that with wugs toolkit, but it just hangs.
Thanks.
NeoMorpheus1337 said:
Hi,
Can you please tell me how did you flash lmy47e?
I tried doing that with wugs toolkit, but it just hangs.
Thanks.
Click to expand...
Click to collapse
Properly, without a toolkit.
Images are here:
https://developers.google.com/android/nexus/images
You need to use fastboot.
All guides and info threads are in general > Sticky roll-up
Mine just came in today (64 GB Cloud White). Very impressed so far. I'm going to unlock, root, ROM. I'm not a noon in this area - been doing it since the OG Droid days. Not going to do it with a toolkit.
Anyway, it came with 5.0 (build number LNX97M) but I have a notification for a system update. Shows it's the update for 5.0.1, but I imagine the 5.1 update will follow shortly. Can these updates be unlocked/rooted? I assume so, but I like to be certain first. Thanks in advance for your help.
Rodeojones said:
Mine just came in today (64 GB Cloud White). Very impressed so far. I'm going to unlock, root, ROM. I'm not a noon in this area - been doing it since the OG Droid days. Not going to do it with a toolkit.
Anyway, it came with 5.0 (build number LNX97M) but I have a notification for a system update. Shows it's the update for 5.0.1, but I imagine the 5.1 update will follow shortly. Can these updates be unlocked/rooted? I assume so, but I like to be certain first. Thanks in advance for your help.
Click to expand...
Click to collapse
all nexus updates can easily be bootloader unlocked and rooted. google makes any nexus device easy to be bootloader unlicked and rooted, that who put in the option of fastboot oem unlock
simms22 said:
all nexus updates can easily be bootloader unlocked and rooted. google makes any nexus device easy to be bootloader unlicked and rooted, that who put in the option of fastboot oem unlock
Click to expand...
Click to collapse
Thanks. I figured as much, but wanted to be certain. Haven't had a Nexus since the Galaxy Nexus, so I'm used to being extra cautious about these things. I'll go ahead with the OTAs then unlock and root.
Rodeojones said:
Thanks. I figured as much, but wanted to be certain. Haven't had a Nexus since the Galaxy Nexus, so I'm used to being extra cautious about these things. I'll go ahead with the OTAs then unlock and root.
Click to expand...
Click to collapse
you'll get an update for 5.1 after updating to 5.0.1, then later on, you'll get an update for 5.1.1. or, you can also flash and use M
My wife is using my old Turbo which was originally Mofo rooted and it's currently on the First Encounter 5.1 stock image since she doesn't care about root. We tried to do the recent OTA update and it failed. Is there anyway to get it to update without wiping everything and doing a return to stock install of some sort?
Bump, I nobody else still has a mofo rooted Turbo? I suppose a factory reset is needed.
someguyatx said:
Bump, I nobody else still has a mofo rooted Turbo? I suppose a factory reset is needed.
Click to expand...
Click to collapse
I'm not sure, but the problem could be that it's still on the 4.4.4 bootloader. The update script checks just about everything that it can to make sure that you're on stock SU4TL-44 before it decides that it's safe to upgrade. If that's the case, you'll need to flash the SU4TL-44 bootloader. If you want to be 100% sure that the phone will update correctly, restore it to SU4TL-44 using section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
While you're there, you should unlock if you want to do so. Once you get to SU4TL-49 if you haven't unlocked already, you'll be locked up tight. Permanently.
Thanks I saw this the other day and forgot to hit reply. I also forgot that the mofo exploit retained the 4.4.4 bootloader which explains why it didn't update. I haven't modded my current Turbo so I am giving it to the wife and moving all of her stuff over. I got myself a M8 in the meantime while I mess with the mofo rooted Turbo.
Do you happen to know if I just need to flash the SU4TL-44 stock firmware in stock recovery to return to stock?
someguyatx said:
Thanks I saw this the other day and forgot to hit reply. I also forgot that the mofo exploit retained the 4.4.4 bootloader which explains why it didn't update. I haven't modded my current Turbo so I am giving it to the wife and moving all of her stuff over. I got myself a M8 in the meantime while I mess with the mofo rooted Turbo.
Do you happen to know if I just need to flash the SU4TL-44 stock firmware in stock recovery to return to stock?
Click to expand...
Click to collapse
EDIT: I misread what you said. No, you can't flash anything other than official OTAs using the stock recovery. Follow the guide. It's the best way to do it and it's pretty easy.
Thanks I will be working on this weekend