Database Users

Stock MZ604 (Xoom Wi-Fi) recovery.img

Seeing as BeagleBoy (http://forum.xda-developers.com/showthread.php?t=1017398) was willing to sacrifice his recovery partition to give us clean boot.img and system.img files, I thought I'd dump my recovery partition from my Xoom Wi-Fi.
*DISCLAIMER* Do not use this to relock your XOOM. I bricked mine... :S
This shows the recovery image from the 3G/4G Xoom is different...
Code:
mac-mini:Xoom Howard$ diff mz600_img/MZ600_HRI39/recovery.img mz604_img/stock/recovery.img
Binary files mz600_img/MZ600_HRI39/recovery.img and mz604_img/stock/recovery.img differ
Code:
mac-mini:Xoom Howard$ cmp mz600_img/MZ600_HRI39/recovery.img mz604_img/stock/recovery.img
mz600_img/MZ600_HRI39/recovery.img mz604_img/stock/recovery.img differ: char 9, line 1
mac-mini:Xoom Howard$
I forgot how to do a binary compare showing how many differences and all that but that's sufficient I think?
Edit: The recovery image I have are from a Canadian Xoom Wi-Fi which is confirmed to be quite different from the US version. US image files for the Xoom can be found here: http://developer.motorola.com/products/software
Here's my recovery partition:

This mean we're able to relock our wifi only Xooms?
Sent from my EvoKneivel

Nope. I think I may have bricked my XOOM in the process.

OP, can you please put a Disclaimer that the files do not work and may brick your xoom. The last thing we need is more people bricking their Xooms and having to return it to the store.

ericdabbs said:
OP, can you please put a Disclaimer that the files do not work and may brick your xoom. The last thing we need is more people bricking their Xooms and having to return it to the store.
Click to expand...
Click to collapse
Done. And to make things worse, I can't find my receipt...

Scourge1024 said:
Done. And to make things worse, I can't find my receipt...
Click to expand...
Click to collapse
Scourge,
Your an absolute renegade, thank you for sacrificing your baby for the benifit of the community. I really hope you find your receipt.

Thanks. I have 3 alternatives...
1. "Borrow" my friend's receipt.
2. Buy another Xoom.
2a. Exchange bricked Xoom with new receipt and sell spare on Kijiji at small loss.
2b. Eat the $600 loss and sell my body to afford another.
I'd only really feel comfortable returning that stuff if there's no serial number, MAC address or other unique identifier on the receipt though.

Will the stock SBF be able to fix it when it comes out?

Scourge1024 said:
This shows the recovery image from the 3G/4G Xoom is different...
Click to expand...
Click to collapse
Just wanted to point out that these would pretty much be different by definition, because they would have different kernels/configuration details due to them being different models.
(It would be interesting to see exactly how they differ, I might go download and unpack them and compare.)

ydaraishy said:
Just wanted to point out that these would pretty much be different by definition, because they would have different kernels/configuration details due to them being different models.
(It would be interesting to see exactly how they differ, I might go download and unpack them and compare.)
Click to expand...
Click to collapse
Well, I thought there could have been a possibility of them being similar. The recovery boot doesn't need to know about all the hardware differences between the two.

Scourge1024 said:
Well, I thought there could have been a possibility of them being similar. The recovery boot doesn't need to know about all the hardware differences between the two.
Click to expand...
Click to collapse
Similar, sure, but there's definitely going to be differences. Remember the boot.img and the recovery.img have the same kernel, ie., the system's kernel, so for efficiency purposes it's not going to have all the CDMA-specific stuff in the Wi-Fi only model.
(If you're curious, I've diffed the ramdisks and can show you the differences, but not the kernel images -- they're compressed and I'm unfamiliar with linux kernel image compression, and I'm not sure what good decompression will do)

Scourge1024 said:
Well, I thought there could have been a possibility of them being similar. The recovery boot doesn't need to know about all the hardware differences between the two.
Click to expand...
Click to collapse
I highly doubt you're bricked bro. Catch me in freenode #xoom and we'll take a look.

I'm just about to grab a power nap. Why don't you think I'm bricked? I can't scroll through the options on the boot screen and in Fastboot and RSD modes, my computer can't see the Xoom at all. How could I have fixed it?
Anyway, I took advantage of an exchange and confirmed that I got the same MD5 for the recovery partition as with the one I extracted from the old Xoom.

heres an easier guide and works only on wifi model http://www.xoomforums.com/forum/mot...99-how-restore-wifi-only-system-boot-img.html

Did you ever get it fixed? As long as you fan get fastboot you're not bricked.

pat4714 said:
heres an easier guide and works only on wifi model http://www.xoomforums.com/forum/mot...99-how-restore-wifi-only-system-boot-img.html
Click to expand...
Click to collapse
has anyone done something like this? i assume this is the closest to a factory reset we can get? I'm not looking to relock, just would like to start over from scratch....

xoppaw said:
has anyone done something like this? i assume this is the closest to a factory reset we can get? I'm not looking to relock, just would like to start over from scratch....
Click to expand...
Click to collapse
Just grab BeagleBoy's boot and system images. I know he extracted them right (virgin copies). The link you provided doesn't site the source or how the images were extracted. But, they could also be his images someone rehosted. I'd go right to the original source though...
http://forum.xda-developers.com/showthread.php?t=1017398
If someone has even once remounted their system folder, it's no longer a virgin copy. Even if they hadn't pushed any files onto it.
Or, you can grab my Canadian Xoom Wi-Fi files here:
http://forum.xda-developers.com/showthread.php?t=1041453

Is there actually a difference between the two? and which would be best for a uk wifi?

Well I had to use the Canadian Image files to recover my uk WiFi Xoom after I got into a boot loop flashing a theme
Sent from my Desire HD using XDA Premium App

Courtesy call. Stock Wi-Fi MZ604 images are up where the MZ600 ones are.

[Advice] if you have a uk wifi xoom flash the us image files.

Hello all uk wifi xoomers
Have you noticed the motoblur applications when you go to manage applications> all?
Have you noticed your still on 3.0.1
Well flash the us image files.
I bit the bullet and did it.
got the 3.1 update and is so much faster and the browser works so much better/faster
The whole os seems to be faster as well
Also no more motoblur crap.
Also means when the next update comes out you will get it rather then waiting
I recommend it to any uk xoomer.
Only works on wifi do not try on 3g
Sent from my Xoom

Have to agree, wasn't sure what I was doing when I tried it, but just unlocking the bootloader, flashing the US files and re-locking the bootloader took all of 20 mins, and the device seems to fly now.

iammodo said:
Hello all uk xoomers
Have you noticed the motoblur applications when you go to manage applications> all?
Have you noticed your still on 3.0.1
Well flash the us image files.
I bit the bullet and did it.
got the 3.1 update and is so much faster and the browser works so much better/faster
The whole os seems to be faster as well
Also no more motoblur crap.
Also means when the next update comes out you will get it rather then waiting
I recommend it to any uk xoomer.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
If you do this on a UMTS 3G Xoom you will most likely lose 3G (or have boot issues) and not be able to revert successfully to stock because Moto hasn't released those images yet.
There are already threads about people complaining about this.

Changed post due to only being able to do this on wifi Xoom
Sent from my phone

VaKo said:
Have to agree, wasn't sure what I was doing when I tried it, but just unlocking the bootloader, flashing the US files and re-locking the bootloader took all of 20 mins, and the device seems to fly now.
Click to expand...
Click to collapse
After unlocking the bootloader, do you need to root in order to flash the US files?
Which thread did you use to go by cause i'm not 100% about doing this to my xoom. I have rooted my nexus one though a while ago and am quite rusty to all of this again. ADB is such a nervous step for me!

I used this guide
http://forum.xda-developers.com/showthread.php?t=1052644
I did it from stock.
didn't have root or anything like that
Very easy quick process.
Sent from my Xoom using XDA Premium App

seakins said:
After unlocking the bootloader, do you need to root in order to flash the US files?
Which thread did you use to go by cause i'm not 100% about doing this to my xoom. I have rooted my nexus one though a while ago and am quite rusty to all of this again. ADB is such a nervous step for me!
Click to expand...
Click to collapse
Here is what I did, started with a stock unrooted device:
adb reboot bootloader (brings up fastboot)
fastboot oem unlock (follow on-screen instructions, will reboot, skip everything and enable debug mode again)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w (needed to clear the userdata, otherwise it might softbrick or something due to differences between the US and UK software)
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All done, although afaik you can't go back to the UK software after doing this, and if you try this on a UK 3G Xoom you will be the proud owner of a £600 paperweight.
Basic guide to setting up adb and unlocking the bootloader here, and the images are here. Read every page of the thread iammodo linked to, and understand that as soon as you enter the first flash command for boot.img, you cannot stop until you have finished the entire process.

VaKo said:
Here is what I did, started with a stock unrooted device:
adb reboot bootloader (brings up fastboot)
fastboot oem unlock (follow on-screen instructions, will reboot, skip everything and enable debug mode again)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w (needed to clear the userdata, otherwise it might softbrick or something due to differences between the US and UK software)
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All done, although afaik you can't go back to the UK software after doing this, and if you try this on a UK 3G Xoom you will be the proud owner of a £600 paperweight.
Basic guide to setting up adb and unlocking the bootloader here, and the images are here. Read every page of the thread iammodo linked to, and understand that as soon as you enter the first flash command for boot.img, you cannot stop until you have finished the entire process.
Click to expand...
Click to collapse
Nice - all we need now is a video guide
I think some people will still be hesitant due to no return to UK image - a shame really that Moto haven't pushed it out there.

VaKo said:
Here is what I did, started with a stock unrooted device:
adb reboot bootloader (brings up fastboot)
fastboot oem unlock (follow on-screen instructions, will reboot, skip everything and enable debug mode again)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w (needed to clear the userdata, otherwise it might softbrick or something due to differences between the US and UK software)
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All done, although afaik you can't go back to the UK software after doing this, and if you try this on a UK 3G Xoom you will be the proud owner of a £600 paperweight.
Click to expand...
Click to collapse
Thanks for the how-to-do guide, really spelt it out!
I totally appreciate the importance of reading the pages and pages of info. Spent a full 2 weeks reading before i rooted my nexus one. Shame, i think my nexus is feeling left out! Might flash something on that again before the xoom to remind me of what i'm doing!

seakins said:
Thanks for the how-to-do guide, really spelt it out!
I totally appreciate the importance of reading the pages and pages of info. Spent a full 2 weeks reading before i rooted my nexus one. Shame, i think my nexus is feeling left out! Might flash something on that again before the xoom to remind me of what i'm doing!
Click to expand...
Click to collapse
Cm7 is always a good one to remind you how to do things
Sent from my Xoom using XDA Premium App

iammodo said:
Hello all uk wifi xoomers
Have you noticed the motoblur applications when you go to manage applications> all?
Have you noticed your still on 3.0.1
Well flash the us image files.
I bit the bullet and did it.
got the 3.1 update and is so much faster and the browser works so much better/faster
The whole os seems to be faster as well
Also no more motoblur crap.
Also means when the next update comes out you will get it rather then waiting
I recommend it to any uk xoomer.
Only works on wifi do not try on 3g
Sent from my Xoom
Click to expand...
Click to collapse
The only "motoblur crap" I see on my device is "MotoBlur Services", taking up 32k. There's also a "Motorola location proxy service".
So, deffo no ill effects by flashing with the US image with regards to App Market and other location specific things?

mrgimper said:
The only "motoblur crap" I see on my device is "MotoBlur Services", taking up 32k. There's also a "Motorola location proxy service".
So, deffo no ill effects by flashing with the US image with regards to App Market and other location specific things?
Click to expand...
Click to collapse
I have been able to restore all my apps without any problems. It is the same UK market I believe as I don't have access to US only apps like Google books. There is a shortcut to it but it is not installed and cannot be found on market.
I was hesitant at first but took the dive and I am very happy I did. It is definitely much smoother and faster. Flash 10.3 works flawlessly now. I can play Videos smoothly that I haven't been able to before. Gallery displays pictures correctly. I keep finding improvements everywhere.

blueberet said:
I have been able to restore all my apps without any problems. It is the same UK market I believe as I don't have access to US only apps like Google books. There is a shortcut to it but it is not installed and cannot be found on market.
Click to expand...
Click to collapse
Very strange, but Google Books actually really is installed. When you root your device and install Titanium Backup, you can see it is 'frozen'. As soon as you 'unfreeze' it, it will function correctly and you will see it in the app drawer.

seakins said:
Thanks for the how-to-do guide, really spelt it out!
Click to expand...
Click to collapse
No worries, I spent a few days trying to figure it out myself so thought I'd share the wealth.

mbroeders said:
Very strange, but Google Books actually really is installed. When you root your device and install Titanium Backup, you can see it is 'frozen'. As soon as you 'unfreeze' it, it will function correctly and you will see it in the app drawer.
Click to expand...
Click to collapse
Anyway to unfreeze it without root?
Sent from my Xoom using XDA Premium App

Finally bit the bullet and flashed the US firmware. Used the instructions in this thread and no probs.
Moments after my xoom rebooted, the 3.1 update was ready to install
All installed and happy

I'm really tempted to do this but is there any way to flash the US system image and not lose data? I really don't want to have to mess around getting all my apps/games back.
Sent from my XOOM using XDA Premium App

baggy247 said:
I'm really tempted to do this but is there any way to flash the US system image and not lose data? I really don't want to have to mess around getting all my apps/games back.
Sent from my XOOM using XDA Premium App
Click to expand...
Click to collapse
No, you have to wipe data or you will brick it.

when I changed my xoom for another xoom because the first was broken I re-installed appbrain and logged back in with my gmail account and all the apps were listed to download very quickly and easily through appbrain
dont know if that's any help to you...

baggy247 said:
I'm really tempted to do this but is there any way to flash the US system image and not lose data? I really don't want to have to mess around getting all my apps/games back.
Click to expand...
Click to collapse
The market should auto-install all your old apps, but you'll need to root and use something like titanium backup to carry over the app settings. No idea how you do this, but I've been told that this is one of the reasons for rooting.

[SOLVED] Boot loader Won't unlock

hi. so I just bought my a500 used in the forums never rooted or unlocked already on the ice ota. I tried to unlock the bootloader' but everything just freezes while flashing. I am just stock rooted for now' but I really want to do some good dev work since my a2 has a locked boot loader. thanks/for any help and sorry if this had been covered. I may seem like it but I am not a complete noob.
Sent from my A500 using xda premium

lkrasner said:
hi. so I just bought my a500 used in the forums never rooted or unlocked already on the ice ota. I tried to unlock the bootloader' but everything just freezes while flashing. I am just stock rooted for now' but I really want to do some good dev work since my a2 has a locked boot loader. thanks/for any help and sorry if this had been covered. I may seem like it but I am not a complete noob.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Which OS are you on? ICS? HC?
Which "one step" app are you using to change out bootloaders?
MD

Moscow Desire said:
Which OS are you on? ICS? HC?
Which "one step" app are you using to change out bootloaders?
MD
Click to expand...
Click to collapse
I am on stock rooted is. it came stock ics and I just rooted it. I have tried pretty much all the tools available in windows, and done it manually with no flash in ubuntu. I can give u the. exact nvflash error later, but it falls I think on the step of actually flashing the new bootloader
Sent from my A500 using xda premium

lkrasner said:
I am on stock rooted is. it came stock ics and I just rooted it. I have tried pretty much all the tools available in windows, and done it manually with no flash in ubuntu. I can give u the. exact nvflash error later, but it falls I think on the step of actually flashing the new bootloader
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Well, if you can't use the tools, (you don't need to give the NVFlash error, I already know what it is), then first try the following. (no matter how silly they sound.
1. Different PC
2. Different USB port. (mine has 4)
3. A good USB cable. Using one that comes with the printer or camera, or an el-cheapo won't work. Data pins aren't always the same. I use my HTC cable.
4. Make sure anti-virus and such is off.
If that doesn't work, only recourse is to roll back to 3.0, preferably by RUU. Problem is, you need an HC UID number to run the ruu. That should set your partitions in place. It's possible you might be able to run an HC 3.2 full update, grab the UID, then run the RUU.
After that, do the NVFlash to get the bootloader/CWM.
At least if it were me, that's the route I would take. Never did it before, but seems sound.
A Pity you bought it already with ICS.
MD

Moscow Desire said:
Well, if you can't use the tools, (you don't need to give the NVFlash error, I already know what it is), then first try the following. (no matter how silly they sound.
1. Different PC
2. Different USB port. (mine has 4)
3. A good USB cable. Using one that comes with the printer or camera, or an el-cheapo won't work. Data pins aren't always the same. I use my HTC cable.
4. Make sure anti-virus and such is off.
If that doesn't work, only recourse is to roll back to 3.0, preferably by RUU. Problem is, you need an HC UID number to run the ruu. That should set your partitions in place. It's possible you might be able to run an HC 3.2 full update, grab the UID, then run the RUU.
After that, do the NVFlash to get the bootloader/CWM.
At least if it were me, that's the route I would take. Never did it before, but seems sound.
A Pity you bought it already with ICS.
MD
Click to expand...
Click to collapse
Alright, thanks.
I feel like such a N00B right now, LOL. This is like when I first bought my Atrix 2.
I bought it used on the forums and figured I was good, I don't have to even update it and stuff since it is on ics, and the bootloader is unlocked, so I will have aokp on it by the end of the night I get it. I guess I was wrong....
Anyways, I tried other ports, and I was using the good motorola cable, but tried the one that came with i as well, so I guess I have to go back to HC. Why would that help? is the idea that I can then just unlock it some other way? If so, how might I go about getting the UID.
Also, is it worth trying to flash the honeycomb bootloader? any better chance there? cause with that I could just flash the new one with a zip or fastboot. also, Is there any way to just put the new one on by simply putting it on the partition using cat or something. I know I did that on my a2 with recovery, but it would brick with the bl.
Thanks for your help.

Thanks everyone, I got it, here's what I did. As usually I massively screwed things up in the process, but I got it:
So first, I tried to flash again in a few different ways, no success, no harm.
Then I downloaded a HC 3.1.2 or something full rom and put it on my sdcard and rebooted and applied it. BRICK. boot verification failed. So that clearly didn't work, and I realized that is because I had an HC rom with ICS bl.
Long story short I tried to get back with an ics update.zip with no luck, so I tried using a stock rom EUU, but it got to the part where it was looking for the tablet with adb debugging so I cancelled it, since obviously that was not going to do anything. Then I tried a few more zips, with no luck at all and somehow ended up in fastboot, which makes no sense since nothing flashed (or at least I though). From there I tried flashing cwm so I could recover, but it just kept saying "not supported in lock mode" so I gave up on that.
Now comes the accidental fix part. I tried the other exe in the EUU just to see what it did, and it appeared the same, so I just kept hitting continue, and when it got to the usb debugging part, I must have hit minimize instead of close. about 30 minutes and me being really pissed that I somehow hardbricked later I realized there were now 2 windows of the EUU thing open. One said that it could not find my device, and to manually put it in apx mode. WOW, so I was just too impatient before.
Long story shorty again, that worked and it was back on stock honeycomb, and I flashed the HC unlocked BL with no issues, but that did me no good, so I put aokp on my sdcard and flashed the ICS BL with no problem at all this time. I rebooted into recovery and flashed aokp, watched the boot animation that reminded me it was made by a 7 year old girl for a few while the dalvik cache built, and then I was good to go screw with the unusually large number of settings included and flash gapps.
So, yeah, basically I am an impatient moron, but hey! it worked.
Now I just have to find a good OC'd kernel that will work with aokp and I an good to go.
Just a heads up, I plan on building JB aokp and releasing it, so get ready for some serious unicorn swagger in a few months when I finally decide to do it.

I like that process. Flash everything till something works :laugh::laugh::laugh:
At least it works for me sometimes
Glad you got it going.
Listen, edit your post and link to the EUU files you were successful with. Might help some others.
MD

Fix for JSS15J Update failure!

So it appears that some people (myself included) are having issues with their new Nexus 7. Specifically, where it is failing to install the second OTA update, which brings the tablet to version JSS15J. The first update (which is almost instant) works, but the second 50+MB one fails after rebooting into stock recovery.
It is failing because the file "/system/app/PrebuiltGmsCore.apk" is failing the sha1 checksum check. Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. I tried various standard work arounds but came up with no fix to get the OTA update, as is, to install. Then I decided to see if that was the only issue present and develop a work around.
I'm pleased to say that:
1) The PrebuiltGmsCore.apk file is the only one that breaks the OTA update. Everything else is fine.
2) I was successful in fixing this by creating a custom OTA update zip and installing it on my tablet.
3) I'm providing this modified update.zip for people to load on their tablets if they are having the same issue.
A couple of notes first...
Obviously, flash this at your own risk.
You NEED TO HAVE A CUSTOM RECOVERY for it to work. TWRP has already been ported over, so install that first.
Once you are in custom recovery, flash this file just like any other update.
Lastly, you should only download/install this if you are having the problem where the second OTA update fails. If you are currently running JSS15J, this update will fail (as it should).
This is 98% stock OTA update. All I did was some minor tweaks to fix the issue. Specifically:
1) I removed both the check for the PrebuiltGmsCore.apk file as well as the patching of it (since this fails).
2) I took the full JSS15J version of PrebuiltGmsCore.apk and built it directly into the update.
3) I removed the parts of the OTA update that mess with custom recovery. It will not install the /system/boot-from-recovery.p or /system/etc/install-recovery.sh files.
Once you install this, your tablet should be running identically to one that didn't suffer this issue.
Outside of using this, the only other option (AFAIK) is to wait until Google releases the full factory images and flash everything manually.
A big thanks to ATGAdmin for providing the stock JSS15J system dump that let me extract the updated PrebuiltGmsCore.apk file.
So without further ado, here is the update:
http://core.routed.com/JSS15J-Update.zip
Enjoy, and let me know if you have any questions.

Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app

shredder47 said:
Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes.
And I bought mine from Best Buy, which seems to be a common denominator with both of those issues.
However, I just checked, and I have that wallpaper now after installing this update.

Yeah sounds like that's the common denominator... I'm out right now but I'll try this out when I get home, thanks man!
Sent from my Nexus 4 using xda app-developers app

Thanks so much! This worked for me after trying other options failed. Mine was from Best Buy also.

Oh, one other quick note:
As I wanted to leave this as close to the stock OTA update as possible, this WILL remove root. Technically, the 'su' binary will remain, but it will lose it's suid permissions. It will also remove the daemon launcher (which is installed as the install-recovery.sh file).
So make sure to flash the root zip after installing this update.
One more thing:
While there aren't many mods out there yet that will mess with the update, eventually there will be. This custom update will check and verify that everything else (except that one file) is stock. So if you made any other modifications to any other system file (ie: build.prop, etc.), it will fail just like any other OTA. Your best bet is to install this before tweaking.

Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao

I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD

Nburnes said:
Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao
Click to expand...
Click to collapse
Awesome, glad to hear! And sure, that's perfectly fine with me.
It's on a 100Mb pipe, but the data center occasionally has some bad routing that makes certain destinations slow. Can't complain since I get a dedicated server for $59/month .

fosser2 said:
I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, I believe it to be a minority of tablets. Maybe just a bad batch that all happened to get sent to Best Buy. As time goes on and more people get them we'll see how wide spread it is. I'm curious to see what Google's official fix will be.

Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta

paranoid android85 said:
Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.

phonic said:
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.
Click to expand...
Click to collapse
I brick my nexus. Can someone upload nandroid backup please?

phonic said:
... Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. ...
Click to expand...
Click to collapse
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?

Bob Smith42 said:
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?
Click to expand...
Click to collapse
I'm not really sure. After looking at the first OTA update that oldblue910 posted, it definitely indicates that it was modified by that. If so, it had to have initially passed that first check. Why some units fail the second check makes little sense to me. The lack of the official wallpaper is also weird.
Additionally, that first OTA clearly shows that these devices were rushed. The fact that they were sent out with developer keys is just really bad QA.
My device, hardware wise, seems to be perfect. So I don't want to roll the dice and try to get another one, especially if the only issue is some minor software glitch that I already corrected. I haven't had a chance to really play with it yet, as I've been spending my time backing up/restoring files, so I'll see how it goes.

Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta

stab244 said:
Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, you should reapply the root zip.
The OTA update does two things in this regard. It removes the two 'recovery recovery' files, and it also removes the suid bit from the su binary. The TWRP su fix will reapply the suid bit to 'su' (thus making it actually work), but it doesn't put back the SuperSU daemon launcher (/system/etc/install-recovery.sh). By applying the root zip again, it will fix both of these.
I thought about removing the part of the update that deletes this file, but again I wanted to keep it as stock as possible. Also, for people who hadn't rooted yet but do have a custom recovery, it would help keep it custom and not require them to manually remove those files that would (stock) reset the recovery back.

I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?

xene97 said:
I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?
Click to expand...
Click to collapse
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.

phonic said:
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.
Click to expand...
Click to collapse
Thanks for the clarification!

[STOCK] VERIZON Nexus 6 [5.1][LMY47E] Firmware Image

For anyone interested here is the firmware image for Verizon Nexus 6 [5.1] [ LMY47E].
VRZ_XT1103_5.1_SHAMU_LMY47E_release-keys_subsidy-default_CFC.xml.zip
http://www.filefactory.com/file/12c...Y47E_release-keys_subsidy-default_CFC.xml.zip
Nexus 6 Firmware Folder
http://www.filefactory.com/folder/74e3c3d68254b075
This where I upload my stuff so sorry if I offend anyone for doing so.

So the difference in between whats out there and this is? I'm curious as the build is different.

coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Not sure what's actually different but the build number is different, LMY47D vs LMY47E.

Could this be flashed with twrp without losing custom recovery?
Sent from my Nexus 6 using XDA Free mobile app

Hopefully we will find out if there are any significant changes or additions. I really hope that I do not need to follow a Verizon firmware through the life of this phone. I hope that there is nothing meaningful in the E version.

Not positive as I am just downloading it, but pretty sure it is the factory image for the Nexus 6 for VZW so I imagine it will remove root and probably custom recovery.
But the nice thing about the Nexus 6 is that you are NOT tied to your carrier's firmware/ROM's for it. Unlike previous phones, there are only two versions, US and International. So we don't have to worry if 'x ROM' is for the T-Mobile version, the Sprint version, etc., etc.

Well no worries this all but confirms vzw is rootable and unlockable

Anyone Flash this yet?
Has anyone flashed this yet...very interested how you went about it and what the results are.....thx

Is there a rooted version??

Parsing the image filename
coldconfession13 said:
So the difference in between whats out there and this is? I'm curious as the build is different.
Click to expand...
Click to collapse
Also waiting another few hours for download to complete. In the mean time, just parsing all the attributes of the file name:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
release-keys: signed by Google
subsidy-default: Includes parameters that resets the SIM Lock on the radio to "default" status, which we assume is factory-unlocked.
CFC: any idea what means?
I would assume this also gives us an image for the /oem partition

Judging by the name this was made on the same day as the image on Google's website, so it is very unlikely that there are major changes.

Nexus 6 subsidy lock config
@autoprime:
1. Does the contents of the included slcf_rev_b_default_v1.0.nvm look like plain QMI commands to you?
2. Do you still have a user-friendly one-click tool that can send DFS commands to a device in diag mode?

How to Flash
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
edit...
duh.... ok sorry... my bad for not looking into the zip.... I see the flash all .bat

mahst68 said:
Maybe a dumb question... but can this be TWRP flashed (I thinking no) or is there some other method? I was thinking this was a standard recovery image that could be flashed in stock recovery?? Other than that, I am not sure... if anyone has success flashing let me know!
Click to expand...
Click to collapse
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).

Did It!!!
DA6030 said:
I believe you will need the Motorola Fastboot tool (mfastboot) to flash this in the motoboot mode. You can get it from the MotoDev site, or search on the forums. Note that this is NOT the same as the standard fastboot that ships with the Android SDK (which will also work with the Nexus 6, but not with this particular zip file).
Click to expand...
Click to collapse
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!

mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!! Booted up everything real nice.... download myverizon and voicemail as soon as I went through initial setup.... rooting now!!! :good:
bootloader remained unlocked the whole time!!!!
Click to expand...
Click to collapse
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?

elreydenj said:
Does the firmware seem configured for VZW? VZW ringtones and boot animation and the like? Or does it appear like something that Google will drop on us in the near future? I wonder if it will ever hit the factory images page?
Click to expand...
Click to collapse
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:

mahst68 said:
only thing Verizon really are the 2 app downloads.... everything else is the same... not boot animations nothing. Root and TWRP setup worked fine as well.... Not going to relock bootloader though... I know the horror stories of Hard Bricks.... Not going to take off force encrypt either.... was having trouble with the phone wanting to go bootloopy with the regular image from google when I made it force before... I will let everyone know bugs and post some pictures as well once I set it up fully!! :highfive:
Click to expand...
Click to collapse
Question: I think I may have been under the same circumstances as you. I am rooted, with TWRP, and bootloader unlocked. I am however, running a custom rom (5.0.1 encrypted). I won't be relocking the bootloader. What steps (if you are able to provide them) should I take to achieve 5.1 with bootloader still locked and then root and install TWRP. (Please keep in mind I a have not had a Nexus device since the very first one).
Edit: I am on VZW network but Google Play Store Nexus 6.
TIA

Will do... I am still setting up the phone. Once I complete it and make sure it works fine for a little bit then I'll post. Don't want to cause any issues that might lead to someone bricking their phone

Initial observations
DA6030 said:
LMY47E: Newer than LMY47D, which is explicitly called 5.1.0 on the Nexus Factory Image page (not the usual numbering convention, which would be 5.1; possibly foreshadowing that they know 5.1.1 is hot on its heels)
Click to expand...
Click to collapse
System partition looks complete, but I won't have time to do a diff between the two until next week. But by then, we might have an official changelog.
DA6030 said:
subsidy-default: Implies there's something within this file that sets the SIM Lock parameters on the radio? Extracting that could be very interesting to AT&T and Sprint customers.
Click to expand...
Click to collapse
I don't have an AT&T device to test, but applying this file certainly attempts to set the SIM lock to it's default factory-unlocked state. But it's also possible the radio firmware could reject the unlock commands if it has been previously locked by a carrier. Only way to know is to test.
DA6030 said:
I would assume this also gives us an image for the /oem partition
Click to expand...
Click to collapse
There is an oem partition file within the zip, but it's literally just the string "Hi, Fly Guy". Just open oem.img with a text editor to see it. I cannot imagine that is a valid ext img file, so I'm shocked that it was able to be flashed. If so, that would suggest that the Verizon devices will ship with no unique customizations (e.g., bootanimation, ringtones, that cannot be removed without root), and has a sense of humor.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
mahst68 said:
As described, used mfastboot... flashed each individual image file based on the steps in the flashfile.xml!!!
Click to expand...
Click to collapse
@mahst68, did you flash only the image files, or also the subsidy_lock_config file (slcf....nvm)? What mfastboot command did you use to send the slcf? What was the response did you get back from that command? And when you flashed the oem.img what response did you get back?