New factory 5.1 image just posted
https://developers.google.com/android/nexus/images
I also saw this have you tried it yet?
arodhr13 said:
I also saw this have you tried it yet?
Click to expand...
Click to collapse
Na i'll wait for developer to post a twrp flashable version. Interested to see what they fixed though.
Yeah me to.
thats the same version number as is on the Verizon version...
cmh714 said:
thats the same version number as is on the Verizon version...
Click to expand...
Click to collapse
Did anyone ever figure out what the changes between D and E are?
at the very least the radios are different....95 in the D image and 98 in the E image.
So I have a Motorola Nexus 6 that I just flashed the OTA for (LMY47D). Did I screw up not waiting for this version since I use this on Verizon?
Huh I sideloaded the OTA so I guess to get the new radio I need to unlock the bootloader and flash just the radio?
I'm flashing the new radio now. (t-mobile)
---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------
Gage_Hero said:
Huh I sideloaded the OTA so I guess to get the new radio I need to unlock the bootloader and flash just the radio?
Click to expand...
Click to collapse
Yup, assuming that is the only change.
phoenixus said:
So I have a Motorola Nexus 6 that I just flashed the OTA for (LMY47D). Did I screw up not waiting for this version since I use this on Verizon?
Click to expand...
Click to collapse
no, not really....the 47D radio works fine on VZW.....some have reported that the 47E works better, others have said its the same.....YMMV
I havent flashed the 98 radio yet but more than likely will
---------- Post added at 09:27 AM ---------- Previous post was at 09:18 AM ----------
The E version from Google is 16MB smaller than the VZW version as well....
I didn't notice any change from the radio that was in 5.01, just sideloaded on Sunday but the few data tests show LTE to be worse than before.... wifi on the other hand did improve. I guess I'll just wait and see what others have to say about radio 98 as opposed to 95...
cmh714 said:
at the very least the radios are different....95 in the D image and 98 in the E image.
Click to expand...
Click to collapse
boot.img, recovery.img and system.img are also different, according to 'diff'.
Will give this a whirl later this evening...
mijkz said:
boot.img, recovery.img and system.img are also different, according to 'diff'.
Will give this a whirl later this evening...
Click to expand...
Click to collapse
So if those are all different, there must be an OTA out there or on the way also?
phoenixus said:
So I have a Motorola Nexus 6 that I just flashed the OTA for (LMY47D). Did I screw up not waiting for this version since I use this on Verizon?
Click to expand...
Click to collapse
No, you didn't screw up. That "was" (LMY47D) the latest factory image posted for the Nexus 6, this is "now" (LMY47E) the latest factory image for the Nexus 6. Just flash the newer one now....if you want.
phoenixus if you did a side load like me, to use the factory image, you need to unlock the bootloader... just be aware this will wipe the device so save anything you want to keep to your PC first..... picture, songs, etc......
mijkz said:
boot.img, recovery.img and system.img are also different, according to 'diff'.
Will give this a whirl later this evening...
Click to expand...
Click to collapse
OK, so I've flashed LMY47E on my stock 5.1 (rooted and TWRP) and it's working fine (3 UK network):
Rebooted to bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img (maybe not necessary for such a minor update)
fastboot reboot
Warning: this sets recovery back to stock (even if you don't flash recovery.img) so you have to then:
fastboot flash recovery openrecovery-twrp-2.8.5.0-shamu
IMMEDIATELY reboot into recovery by scrolling to the recovery option in the bootloader and pressing the power button
flash SuperSU
Reboot and you're done.
Anyone figure out what the changes are?
From Android Police :
People, this is the firmware variant that shipping on devices purchased from Verizon. Pre-orders have shipped and people are beginning to receive them today. If you own a Nexus 6 that wasn't purchased from Verizon, you won't be getting LMY47E over the air or anything else. The two branches will be merged with the next OTA, presumably.
There is, for all intents and purposes, no reason to use this over LMY47D, unless you're using your phone on Verizon and/or want the newer radio. And even if you are using Verizon, LMY47D works fine.
So I am slightly confused.... in this thread, everyone talks about flashing the factory images with fastboot.... in this thread http://forum.xda-developers.com/nexus-6/general/stock-verizon-nexus-6-firmware-image-t3053052/page9 they are all talking about mfastboot. I am going to guess booting into recovery and issuing adb commands that have been repeated here a few times (after unlocking the bootloader of course) will get the job done correct?
Related
And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip
What state does the phone have to be in to fastboot? I get waiting for device in normal phone OS and in recovery.
I can adb reboot to recovery, so I know everything is set up PC wise.
From bootloader I get "cannot load _______.img : no error"
---------- Post added at 01:10 PM ---------- Previous post was at 01:04 PM ----------
Got it I think. Your command in the OP has it ending in .img not .zip
EDIT....still getting binary not installed. I've got to go to work, but idk why this is the first phone I've ever struggled with so many things. Could be because we still don't have ANY working official images.
---------- Post added at 01:13 PM ---------- Previous post was at 01:10 PM ----------
Got it. Had to unzip the file and flash the image like you said.... I read wrong my bad.
Thanks
graffixnyc said:
And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip
Click to expand...
Click to collapse
Is the boot.img for Lollipop based on the .5 or .6 release?
BrokenWall said:
Is the boot.img for Lollipop based on the .5 or .6 release?
Click to expand...
Click to collapse
It's boot img agnostic.. meaning you boot this boot.img, it actually takes the current boot.img on the device and injects root into it. So it uses whatever boot.img is currently on the device. So if you are on the .5 kernel it should work, if you're on the .6 kernel it works
graffixnyc said:
It's boot img agnostic.. meaning you boot this boot.img, it actually takes the current boot.img on the device and injects root into it. So it uses whatever boot.img is currently on the device. So if you are on the .5 kernel it should work, if you're on the .6 kernel it works
Click to expand...
Click to collapse
Awesome, and I will make sure I give Chainfire some money, I will probably just pickup SU Pro
Didn't want to run into boot loop because it was meant for a particular kernel
Is it just for xt1095 or will also work with 1092?
Sent from my XT1092 using Tapatalk
blinkin said:
Is it just for xt1095 or will also work with 1092?
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It was made for the 1095. You can give it a try and let us know. If it fails it doesn't screw up anything (I don't think, since in testing it failed for me many times before he got the bugs worked out) Theoretically it should work as I said it's boot.img
graffixnyc said:
It was made for the 1095. You can give it a try and let us know. If it fails it doesn't screw up anything (I don't think, since in testing it failed for me many times before he got the bugs worked out) Theoretically it should work as I said it's boot.img
Click to expand...
Click to collapse
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all
beelzebu said:
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all
Click to expand...
Click to collapse
Can confirm on XT1097. Man this is amazing!
Anyone has flashed twrp?
Anyway thank you all!
Thanks.
Is there a step-by-step for this? I never rooted any of my Note series phones, so it's been a while.
1. unlock bootloader from moto site (follow instructions there) ALL OF YOUR DATA WILL BE WIPED - BACKUP EVERYTHING FROM INTERNAL STORAGE
2. ensure that you have fastboot / mfastboot / android SDK installed and setup (including PATH)
3. enable usb debugging on your phone
4. ensure that you have the appropriate drivers for your device installed
5. reboot to bootloader
6. check to make sure you have the correct drivers installed
7. type fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
8. phone will reboot.
All of this is in the OP. good luck
Disclaimer
you alone are responsible for the health of your device, if you are at any point worried about causing damage, do not proceed. I will not buy you a new phone if you break yours.
byt3b0mb said:
1. unlock bootloader from moto site (follow instructions there) ALL OF YOUR DATA WILL BE WIPED - BACKUP EVERYTHING FROM INTERNAL STORAGE
2. ensure that you have fastboot / mfastboot / android SDK installed and setup (including PATH)
3. enable usb debugging on your phone
4. ensure that you have the appropriate drivers for your device installed
5. reboot to bootloader
6. check to make sure you have the correct drivers installed
7. type fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
8. phone will reboot.
All of this is in the OP. good luck
Disclaimer
you alone are responsible for the health of your device, if you are at any point worried about causing damage, do not proceed. I will not buy you a new phone if you break yours.
Click to expand...
Click to collapse
Muchas gracias! Here we go. I saw others had success with XT1097, so I'm going for it.
Working on XT1092 with XT1095 5.0 firmware
Any Canadians with a Telus model try this out? I believe Telus Moto X (2014) is XT1097 as well.
graffixnyc said:
And HERE it Is!!!! I'm too tired to make a long thread.. I need to sleep hahah I'll make a proper thread tomorrow if he doesn't..
quickist way... be bootloader unlocked and then boot the image in the image folder of the zip
Unzip the zip to your computer.
fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
Make sure it's fastboot boot.. not fastboot flash.
It will reboot, reboot again and then you're good
Now go buy chainfire a beer
http://download.chainfire.eu/596/CF-Root/CF-Auto-Root/CF-Auto-Root-victara-victaratmo-xt1095.zip
This is not a flashable zip
Click to expand...
Click to collapse
Thank u... It is working perfectly
We now need to wait for Exposed and the fun begins with a lollipop taste....
beelzebu said:
Running Lollipop on XT1097, and rooted with this. Everything going good.
Thx u all
Click to expand...
Click to collapse
You just ran these steps and good to go? no problems with modem/radio and or imei? I also have an xt1097 but I'm afraid to brick my beloved X in the process haha
JoaoGuiPan said:
You just ran these steps and good to go? no problems with modem/radio and or imei? I also have an xt1097 but I'm afraid to brick my beloved X in the process haha
Click to expand...
Click to collapse
Just need to backup modem fsb and pds and then flash tmo factory images, after that sideload de OTA, refresh your modem an from there you are good to go.
blyndfyre said:
Any Canadians with a Telus model try this out? I believe Telus Moto X (2014) is XT1097 as well.
Click to expand...
Click to collapse
Did you get lollipop running on your telus moto x? If so what process did you follow.
Jesus, will non unlocked ever get root?
5.0.1 Build LRX22C OTA to 5.1 Build LMY47M "T-Mobile"
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
Your bootloader MUST be unlocked already, if not, these instructions do not apply to you so don't do them, it won't work.
These are the steps I did that worked for me. No guarantees that it will work for you, or if it wipes or bricks your phone.
Basically, you're downgrading your phone to 5.0.1 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None. Set OEM Unlock in Developer Options on just in case.
2. Reboot phone to bootloader (adb reboot-bootloader), or Power+Vol Down while the phone is off.
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
Green Android with Red Exclamation mark is stock recovery. Press Power + Vol Up to activate the menus. I sometimes have to press them a lot to get it to show.
If your PC does not recognize ADB Sideload mode, unplug your phone and plug it back in, it should work. If not check Device Manager and reload ADB drivers.
nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
Click to expand...
Click to collapse
Thank You! THANK YOU! THANK YOU! lol thanks for sharing
How do i install this again what are the requirements
Looks like I'm reverting back to 5.01 to get this one.
Just installed it. Thank you!
iGoogleNexus said:
Just installed it. Thank you!
Click to expand...
Click to collapse
Good job, mine is still optimizing apps, super slow, 160 of 202.
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
simms22 said:
someone want to pull the radio out of it? i did, and flashed it, twice, but i keep getting an older radio version???
Click to expand...
Click to collapse
Radio is 95R, it's the same in the D system image.
nxt said:
http://android.clients.google.com/p...ed-shamu-ota-LMY47M-from-LRX22C-fullradio.zip
5.01 to 5.1 M build OTA
I have LMY47D/E 5.1 on my phone.
Here are instructions on how to flash it without wiping.
You must be bootloader unlocked already, if not, these instructions do not apply to you so don't do them.
Basically, you're downgrading your phone to 5.01 then running the OTA. NO WIPE!!!
1. Turn off all security code/pattern lock/pin, set it to None.
2. Reboot phone to bootloader (adb reboot-bootloader)
3. Download the LRX22C system Image, and extract all the zips.
4. Run the following fastboot commands:
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
5. Restart bootloader (Not sure if it's necessary but I did it anyways)
6. Go to Recovery Mode from the bootloader.
7. Sideload this OTA from the stock Recovery.
8. Look at your phone and command window on pc, make sure everything is 100% or Success/Finish. If no Errors, then reboot phone and you should be golden!
FYI, Radio is 95R, the E (Verizon build) is 98R
Click to expand...
Click to collapse
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
the.emilio said:
I tried this earlier using the exact same steps, but when I select recovery, it just goes to an android with a spinning blue icon in its belly. And it just sits there. Any ideas?
Click to expand...
Click to collapse
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
nxt said:
It's suppose to be an android with his belly open with a red ! mark on it. Then you have to do a Power + Up to get to the menus
That blue spinning one is something else. That's a flashing icon when it does a real OTA.
Click to expand...
Click to collapse
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
I just finish side loading it......
mr pnut said:
I just finish side loading it......
Click to expand...
Click to collapse
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
the.emilio said:
Yeah I know what it should look like but its not. Then when I hold power and press up it says formatting /data. Weird. Been trying to figure out what it means for like the last 3 hours lol
Click to expand...
Click to collapse
Same not sure. Ended flashimg all the img, 47E
jay661972 said:
Are you in 5.1 bootloader?
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
Same not sure. Ended flashimg all the img, 47E
Click to expand...
Click to collapse
Yes sir.......
Sorry too far OT delete
kaos2569 said:
Hi guys,
I reverted back to LRX22C with WUG's-no root or custom recovery and tried to ADB sideload the update and I get the error shown in the attached photo.
I did rename the file to "update.zip". Any help on this error message?
Thank you.
UPDATE ** Figured out why I was getting the error. I had the "No Encryption" option checked when I reverted so the update wouldn't take without the stock factory image. Flashed the stock image and it went through no problems at all. Now the question of the day is if I can get root and a custom recovery back on this damn thing!
Click to expand...
Click to collapse
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
LGSilva said:
I had the same problem then I remembered I was using Franco Kernel.
Just boot back to recovery and run fastboot flash boot boot.img where boot.img is from the 5.01 factory image file.
Then continue to recovery/OTA sideload procedure.
@nxt Maybe add an optional step to flash boot.img if anyone is using a custom kernel in the instructions?
Click to expand...
Click to collapse
What if u already stuch with 5.1 47E bootloader, flash the one from op but when about tonto recovery, got the same woth the other guy, android with the spinning thing and not exclamation.
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
lainemac said:
Anyone know what the difference is between the M and E builds? Is it just the radio that's different or something? Also, I just flashed the E build for the second time(redownloaded it) and notice that it came with the 98R radio instead of 95R(which I'm pretty sure came with it before.)
Click to expand...
Click to collapse
98R and E build is for Verizon phones. The D builds are for all other non Verizon nexus 6 phones. I went back to 95R because 98R was giving me calling issues.
For Moto X Pure Edition(XT1095) ONLY
There has been a bit of confusion on how to do this, or the instructions are deep inside the other threads. So this is just to make it easier to find
Despite what people are saying on Reddit DO NOT DOWNGRADE TO Android 4.4.4, IT IS A HUGE RISK AND COULD POSSIBLY HARD BRICK YOUR DEVICE
IF YOU ARE ON 23-11-14 SKIP TO PART B ON THE #3 POST BELOW
PART A
Motorola released the new Android 5.1 OTA (23.16.3) and of course as of right now the original soak test users(23.1.28) have been left out. Now unfortunately in order to install the new OTA you must downgrade back to Android 5.0 ,which requires you to unlock your bootloader( Now, because you have the XT1095 Pure Edition this will NOT void your warranty). However you can relock the bootloader AFTER downgrading.
Proof that it doesn't void warranty found here >>>>> http://forum.xda-developers.com/moto-x-2014/general/unlocking-bootloader-moto-x-pure-t3004779
-The Guide to do this can be found on Motorola's site here >>>>> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
The guide is at the bottom below downloads.... Make Sure you follow those instructions carefully as I am NOT RESPONSIBLE for you bricking your device!
DO NOT FLASH bootloader (motoboot) and partition table (gpt) Thanks JulesJam
-Android 5.0, link found here >>>>>> http://www.graffixnyc.com/motox.php
MAKE SURE YOU DOWNGRADE TO Android 5.0: 22.21.11(Full Image) NOT 22.11.5 or 22.11.6 AS THOSE ARE OLD SOAK TEST VERSIONS
-After you downgrade to Android 5.0 you can then upgrade to the new OTA found here >>>>> http://www.graffixnyc.com/motox.php
CONGRATS you are now on the latest version of Android 5.1(23.16.3)
I will be updating this guide as I receive feedback so please be patient and keep the thread clear so users can get help as needed
THANKS
PART B
IF YOU ARE ON SOAK TEST(23.1.28) PLEASE GO TO PART A ABOVE AS THIS WILL NOT WORK FOR YOU
So as it turns out you can actually upgrade from the 5.1 soak test(23-11-14) directly to the new OTA(23.16.3). All you need to do is download the ZIP below and boot into recovery and select install/update from SD and locate the file on your phone.
https://drive.google.com/file/d/0B4wdtquycD9rMGtGZUVMc19VV0k/view
What about your data on the phone?
Do you wind up losing it ?
phonepersonality said:
What about your data on the phone?
Do you wind up losing it ?
Click to expand...
Click to collapse
Yes, unlocking the boot loader requires your phone to be wiped, after that you will be able to install each subsequent update with needing to wipe
jrdnkasparek said:
After you downgrade to Android 4.4.4 you then have to update to Android 5.0, link found here >>>>>> https://onedrive.live.com/?cid=227F163CB35629DA&id=227f163cb35629da!28119&authkey=!AMWPTB3ICDtezYs
MAKE SURE YOU UPDATE TO 22.21.11 NOT 22.11.5 or 22.11.6 AS THOSE ARE OLD SOAK TEST VERSIONS
Click to expand...
Click to collapse
People on the 60.16 bootloader have bricked doing that. I would NOT do that if you are on the 60.16 bootloader. Instead, do not downgrade to 4.4.4 - simply downgrade to the 5.0 images (system, kernel, modems, baseband, recover) by flashing them.
---------- Post added at 08:07 PM ---------- Previous post was at 08:04 PM ----------
jrdnkasparek said:
After you downgrade to Android 4.4.4
Click to expand...
Click to collapse
There is ABSOLUTELY NO REASON TO DOWNGRADE ALL THE WAY TO 4.4.4 AND IT IS DANGEROUS TO DO THIS AND THEN TAKE THE 5.0 OTA AFTER YOU HAVE BEEN ON 5.1!!!
The safer thing to do is to simply flash the full 5.0 images (except for the bootloader (motoboot) and partition table (gpt)). Why on earth would you flash back to 4.4.4 when the 5.0 stock images are available for your device? It makes no sense at all and people with XT1095's have bricked when they were on 5.1 then flashed back to 4.4.4 and took the 5.0 OTA.
It just makes no sense to do it this way.
JulesJam said:
People on the 60.16 bootloader have bricked doing that. I would NOT do that if you are on the 60.16 bootloader. Instead, do not downgrade to 4.4.4 - simply downgrade to the 5.0 images (system, kernel, modems, baseband, recover) by flashing them.
---------- Post added at 08:07 PM ---------- Previous post was at 08:04 PM ----------
There is ABSOLUTELY NO REASON TO DOWNGRADE ALL THE WAY TO 4.4.4 AND IT IS DANGEROUS TO DO THIS AND THEN TAKE THE 5.0 OTA AFTER YOU HAVE BEEN ON 5.1!!!
The safer thing to do is to simply flash the full 5.0 images (except for the bootloader (motoboot) and partition table (gpt)). Why on earth would you flash back to 4.4.4 when the 5.0 stock images are available for your device? It makes no sense at all and people with XT1095's have bricked when they were on 5.1 then flashed back to 4.4.4 and took the 5.0 OTA.
It just makes no sense to do it this way.
Click to expand...
Click to collapse
This is just what I was told in the other threads and on Reddit. I will Edit Thanks!
jrdnkasparek said:
This is just what I was told in the other threads and on Reddit. I will Edit Thanks!
Click to expand...
Click to collapse
Ok well I will bump my thread about the OTA again. Just flash back to 5.0 directly (not the BL (motoboot) or the PT (gpt) though - leave those alone).
JulesJam said:
Ok well I will bump my thread about the OTA again. Just flash back to 5.0 directly (not the BL (motoboot) or the PT (gpt) though - leave those alone).
Click to expand...
Click to collapse
Do you have a download link I could post, only one I can find is the OTA from 4.4.4 > 5.0
NVM found it!
jrdnkasparek said:
Do you have a download link I could post, only one I can find is the OTA from 4.4.4 > 5.0
NVM found it!
Click to expand...
Click to collapse
Patrick has been hosting them - everyone should download them b/c he can pull them down at any time if he doesn't want to host them any longer.
http://www.graffixnyc.com/motox.php
So, if I'm on stock v5.0 rooted with TWRP and unlocked bootloader, I could simply unroot and flash back to stock recovery and then sideload the OTA, correct? Haven't seen a clear answer on this.
the orange bandit said:
So, if I'm on stock v5.0 rooted with TWRP and unlocked bootloader, I could simply unroot and flash back to stock recovery and then sideload the OTA, correct? Haven't seen a clear answer on this.
Click to expand...
Click to collapse
Here is a tutorial for the MX13, works same for MX14 but obviously, you use the MX14 files. And I would flash stock system before I did it.
How to SIDE LOAD an OTA.ZIP via this process
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
Do you have to install the radios as well?
https://onedrive.live.com/?cid=804EF0BE56E7A96F&id=804ef0be56e7a96f!3262
phamine said:
Do you have to install the radios as well?
https://onedrive.live.com/?cid=804EF0BE56E7A96F&id=804ef0be56e7a96f!3262
Click to expand...
Click to collapse
What have you done to your device? Just rooted 5.0 and installed a custom recovery? Or did you take the 5.1 soak OTA? Did you flash any different radios?
What you need to do depends on what you have done.
Noob question here... The 5.0 factory image file has the system.img file separated in several sparsechunk files. How can I flash those, or put them back together into 1 file?
And... another question, do I need to use motorola's fastboot commands or is it ok with normal android ones?
Thanks a lot!!
gabrielss said:
Noob question here... The 5.0 factory image file has the system.img file separated in several sparsechunk files. How can I flash those
Click to expand...
Click to collapse
Regular fastboot.
fastboot flash system system_sparsechunk1.img
do each one until they are done.
---------- Post added at 05:25 AM ---------- Previous post was at 05:25 AM ----------
gabrielss said:
And... another question, do I need to use motorola's fastboot commands or is it ok with normal android ones?
Click to expand...
Click to collapse
sparsechunks can be flashed with regular fastboot. A single file system.img needs to be flashed with mfastboot.
JulesJam said:
What have you done to your device? Just rooted 5.0 and installed a custom recovery? Or did you take the 5.1 soak OTA? Did you flash any different radios?
What you need to do depends on what you have done.
Click to expand...
Click to collapse
I was on the the 5.1 soak.
I downgraded to 5.0 based on the guide and the below commands
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
$ fastboot erase userdata
$ fastboot erase cache
Then I just sideloaded the 5.1 OTA in the guide.
Baseband version
MSM8974bp_4235210.110.09.11R
VICTARA_TMO_CUST
phamine said:
$ fastboot flash system system.img
Click to expand...
Click to collapse
Did you use mfastboot b/c regular fastboot won't boot a single file system.img.
JulesJam said:
Did you use mfastboot b/c regular fastboot won't boot a single file system.img.
Click to expand...
Click to collapse
Yes. I installed each sparsechunk.
Is the radio version the current 5.1 OTA radio?
phamine said:
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
If you did this using the stock 5.0 images, then you are back on the 5.0 radios.
Is up on Google developer website. MMB29V
https://dl.google.com/dl/android/aosp/shamu-mmb29v-factory-0b4a53f0.tgz
Edit: No change in bootloader or radio.
Thank you for upload. my work blocks google dl but not drive for some reason XD
Has anyone been able to get the checksum to verify? the MD5 for me doesn't match from the link provided or the Google image page.
just tried as well off the Google image page..MD5 does not match :|
I just downloaded from the stock images page also and the MD5 matches for me.
They just changed the MD5 code to match the factory image I downloaded. The new one matches my image.
How does one go about flashing this?
Flash all files through fastboot, except userdata.img?
murtaza02 said:
How does one go about flashing this?
Flash all files through fastboot, except userdata.img?
Click to expand...
Click to collapse
What build are you on now?
holeindalip said:
What build are you on now?
Click to expand...
Click to collapse
The February one. MMB29Q.
Unlocked bootloader
Not rooted.
Sent from my Nexus 6
murtaza02 said:
The February one. MMB29Q.
Unlocked bootloader
Not rooted.
Sent from my Nexus 6
Click to expand...
Click to collapse
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
cam30era said:
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
Click to expand...
Click to collapse
Will do and report back.
Stupid question, but does Google post changelogs?
Other than the security patch, could anything else have changed?
Sent from my Nexus 6
@murtaza02,
Not a stupid question, at all. Go here for answer > http://source.android.com/security/bulletin/2016-03-01.html
cam30era said:
@murtaza02,
Not a stupid question, at all. Go here for answer > http://source.android.com/security/bulletin/2016-03-01.html
Click to expand...
Click to collapse
That's some pretty detailed stuff!
Thanks man.
The factory image just finished downloading, I will report back in about 10 minutes.
Sent from my Nexus 6
---------- Post added at 07:17 PM ---------- Previous post was at 07:02 PM ----------
@cam30era
Thanks so much!
It worked. I flashed it and wiped cache in stock recovery. It's Optimizing apps now, and should be done soon!
cam30era said:
Just flash the system.img and boot.img. No other files changed. (FWIW, not even sure that there's a change in boot.img, but just in case....)
Click to expand...
Click to collapse
That's what I was getting too just wanted to make sure he was at least on 6.0
@holeindalip @cam30era
The build date on the Kernel version changed. ( Kernel is boot.img right? )
When I was on MMB29Q, it showed Dec 10 2015
After MMB29V flash, it shows Jan 20 2016
murtaza02 said:
@holeindalip @cam30era
The build date on the Kernel version changed. ( Kernel is boot.img right? )
When I was on MMB29Q, it showed Dec 10 2015
After MMB29V flash, it shows Jan 20 2016
Click to expand...
Click to collapse
Kernel is included in boot.IMG with other files.
I compared md5 between mmb29q and mmb29v and boot, system and recovery seem different.
Noob question here:Is recovery different because I have twrp installed or shall I flash it too?
wrydgj said:
I compared md5 between mmb29q and mmb29v and boot, system and recovery seem different.
Noob question here:Is recovery different because I have twrp installed or shall I flash it too?
Click to expand...
Click to collapse
I think that boot.img should be flashed. I don't think that it will override your TWRP recovery.
harpin14789 said:
I think that boot.img should be flashed. I don't think that it will override your TWRP recovery.
Click to expand...
Click to collapse
I asked about recovery.img, I know that boot.img has to be flashed. Nevermind, I flashed both of them, just in case, and twrp after all flashes[emoji6]
Sent from my shamu using Tapatalk
What I find funny is that some of the patches are not even included in the update but in the updated binaries.
Also there were changes to the kernel. A few of the issues were kernel issues.
Go to the Google site guys...build is up...looks like one to rule them all
Here is a link to the OTA https://developers.google.com/android/ota#sailfish
Or if you want the factory image
https://developers.google.com/android/images#sailfish
Interesting there aren't separate builds...
Do they post a changelog anywhere? Curious what changes are in store.
pjd2011 said:
Interesting there aren't separate builds...
Click to expand...
Click to collapse
More interesting... it looks like the 6P will have a separate build for Verizon this month...
Waiting for non verizon build like the one from November
This build NMF26O seems to have a newer baseband than the Canadian update (NPF26J). Hopefully LTE issues sorted for those who have it.
I haven't finished extracting it...is the bootloader the same or has it changed?
Doing everything from my phone while the wife does the Christmas shopping
bwthor20 said:
Do they post a changelog anywhere? Curious what changes are in store.
Click to expand...
Click to collapse
http://android-developers.blogspot.com/2016/12/welcoming-android-711-nougat.html?m=1
Sent from my Pixel using Tapatalk
do i need to flash every OTA or just the last one? currently on 7.1.0 (Europe, NDE63U, Nov 2016)
google is not really informative at this point
I'm getting the December OTA as I type this. I have a 32GB Pixel with locked bootloader, from the Google Store.
EDIT: Now I'm getting it on my N5x as well. I haven't seen an OTA roll out this swiftly before.
OTA just popped up... Verizon pixel 128gb
Do those of us on Verizon have to worry about thisessing up unlocked bootloader if it's already unlocked??
Also curious if this patched the bootloader exploit used
has anyone flashed the factory image or side loaded the OTA for a non-VZ device yet?
spunks3 said:
has anyone flashed the factory image or side loaded the OTA for a non-VZ device yet?
Click to expand...
Click to collapse
Flashed factory img, carrier tmobile purch from BB
jay661972 said:
Flashed factory img, carrier tmobile purch from BB
Click to expand...
Click to collapse
very nice, which commands did you use to flash?
I'm currently rooted with TWRP alpha2 and SuperSU SR5. I'd like to update without losing data.
My system is on Sot B so I'm thinking:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_b system.img
fastboot flash vendor vendor.img
and then to get TWRP back:
fastboot boot twrp.img
- TWRP install twrp.zip
Reboot into recovery
- TWRP install supersu.zip
Does the above sound accurate?
spunks3 said:
very nice, which commands did you use to flash?
I'm currently rooted with TWRP alpha2 and SuperSU SR5. I'd like to update without losing data.
My system is on Sot B so I'm thinking:
and then to get TWRP back:
fastboot boot twrp.img
- TWRP install twrp.zip
Reboot into recovery
- TWRP install supersu.zip
Does the above sound accurate?
Click to expand...
Click to collapse
I use the flash-all file, i edit the file first to remove the -w so i can dont have to wipe the data
Cant answer the TWRP, not sure if it works with the new update
aholeinthewor1d said:
Do those of us on Verizon have to worry about thisessing up unlocked bootloader if it's already unlocked??
Also curious if this patched the bootloader exploit used
Click to expand...
Click to collapse
I just sideloaded the OTA onto my VZW Pixel with unlocked bootloader. My bootloader remains unlocked and I flashed twrp and SuperSU SR5. So far everything is working fine.
According to the dePixel8 website (http://theroot.ninja/depixel8.html) "dePixel8 is patched in Android 7.1.1 and newer, do not ask for future support or any kind of support."
So if you take this OTA from the phone (on an unlocked bootloader) you may well be locked out for good (unless someone finds another exploit).
stranula said:
I just sideloaded the OTA onto my VZW Pixel with unlocked bootloader. My bootloader remains unlocked and I flashed twrp and SuperSU SR5. So far everything is working fine.
According to the dePixel8 website (http://theroot.ninja/depixel8.html) "dePixel8 is patched in Android 7.1.1 and newer, do not ask for future support or any kind of support."
So if you take this OTA from the phone (on an unlocked bootloader) you may well be locked out for good (unless someone finds another exploit).
Click to expand...
Click to collapse
Thanks for the reply. I did some more reading and realized it's safe to install the OTA since I'm already unlocked. The update can't relock it. I already installed it via OTA and everything is ok
sorry, big time newb here. How do I flash the update if I have Verizon pixel with bootloader unlocked and with twrp installed? OTA doesn't work and I don't want to lose data....please help