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.
Related
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Finally! I'm going to flash this on both my flo and mako. Then, along with my hammerhead, I'll have KitKats everywhere!
Was going to post this too. Just my luck that they release it the day that I'll be out all night and won't be able to update until the weekend. Maybe I'll get the OTA before then.
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Zaphodspeaks said:
For Both Flo/Deb
https://developers.google.com/android/nexus/images#razorkrt16o
It looks like they are currently uploading the Flo version at this time of posting, but both Stock 4.4 Images are up..
I looked around to see if anyone who have already posted this.. if so please feel free to merge or delete this Post
Click to expand...
Click to collapse
The Wifi version doesnt look like its been fully uploaded..
Deb however looks like its all there.. Check in an hour to see if the upload is complete..
The F5 key on my keyboard has taken a turn for the worst! lol
Blockberd said:
Looks like the file for flo is corrupt. It is always only 835 bytes. MD5 hash seems to be taken from the version on the server... So don't even waste time in x-checking them just yet.
The update for mako seems to be fine, though.
Click to expand...
Click to collapse
Maybe not completed the upload yet?
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
ElGato65 said:
Maybe not completed the upload yet?
Click to expand...
Click to collapse
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Noticed this as well -- no image.
Blockberd said:
Hm. Would be interesting. I can open the file without any problem. It contains flash-all.bat, flash-all.sh and flash-base.sh.
Click to expand...
Click to collapse
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
They don't work like OTAs because they don't patch the file you have in place, but rather replace the /system partition with the new one. The difference being if you installed some extra files into /system, they would be preserved during an OTA update, but would be gone after a factory image.
jbwray said:
It is a complete file, with no image, just the install scripts.
Seems like it's almost a place holder -- could just be a flat-out mistake.
Can someone tell me if these images are complete resets? Or do they work just like the OTA update would?
Thanks.
Click to expand...
Click to collapse
Those factory images will reset your device to factory is flashed as told by Google. There are, however, ways to avoid that if you have a stock Android prior to the version you want to flash.
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
The question is if someone has closer contact to someone at Google to inform them about that...
Great tip, thanks.
sfhub said:
By default, they are complete resets but they can be modified to keep your user data with minimal effort by removing the -w flag.
Click to expand...
Click to collapse
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
jbwray said:
Awesome tip, thanks! Now that I have looked at the file, I think I have seen that before, but it really didn't register as I wasn't concentrating on doing an update like this... too antsy for 4.4
Click to expand...
Click to collapse
You could also go ahead and flash each .img file (except userdata) in bootload with fastboot to the device. That will be my way once the damn factory image is properly uploaded. ;D
sfhub said:
It isn't a problem with the upload.
It is a problem with WHAT was uploaded.
The file that was uploaded matches the sha1 hash code.
It unpacks fine.
Unfortunately it has nothing except the flash batch files/shell scripts.
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Well atleast the Binaries are up..
So it wont be long until we will be seeing new Custom Roms, and Kernels..
Those of us that were lucky to get the OTA dont need to worry about the factory images..
I created a TWRP clean stock backup of KRT16O if I need to go back to factory settings
This is NOT, I repeat NOT a flashable zip. Its a Zip of my TWRP backup, minus the Data partition..
Just unzip into your TWRP backup folder.. It will bring your Nexus 7 Flo directly to stock 4.4..(ROOTED) It is not an OTA.
Your SD Card will remain untouched
https://www.dropbox.com/s/mqczh3q59lydga9/2013-11-13--06-14-08 KRT16O.TWRP.zip
If any of you want to flash just the update to 4.4, HERE is a link, with directions HERE
sfhub said:
Also the batch file tries to flash bootloader 3.14, which is wrong. The bootloader should be 4.01. It does however try to flash the krt16o rom, which means someone edited the file, just didn't do a good job.
Click to expand...
Click to collapse
Apparently calling all bootloaders 3.14 is a mistake they have chosen to propagate from JSS15R when they called the 3.15 bootloader 3.14.
So basically the 4.01 bootloader is named bootloader 3.14 in the archive.
With the stock rom, can I just flash it using a custom recovery?
yanksrock1000 said:
With the stock rom, can I just flash it using a custom recovery?
Click to expand...
Click to collapse
You can flash the OTA (the OTA requires stock JSS15R to be installed) or the update.zip that scrosler put together using custom recovery.
You can't flash the factory image from google in this thread using custom recovery. It was meant to be flashed using fastboot and with your tablet in bootloader.
Update images now available.
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
jbwray said:
EDIT ** I looked at the wrong image... nothing has changed ** please delete.
Click to expand...
Click to collapse
I was in the middle of replying saying I must be blind (or some cache is getting in the way) because I couldn't find the alternate link/download
It's out guys!
https://developers.google.com/android/nexus/images
jarjar124 said:
It's out guys!
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks for the heads up!
if anyone is going to flash this, could you please benchmark it encrypted?
i saw a bench today where someone had fullspeed even encrypted. is this on 5.0.1?
Interesting that it is the exact same build as the other 5.0.1 updates. No major Shamu specific changes? Hopefully the new binaries provide significant improvements at least.
So I wondering, do we need to unroot the device in order to update using factory images, I had read sometime back how updates in Lolipop now checks all system files and if they are patched/altered the update will fail, but have not ready any issues updating the nexus 7 to 5.0.1 or the nexus 10 when they are root.
wolfnumba1 said:
So I wondering, do we need to unroot the device in order to update using factory images, I had read sometime back how updates in Lolipop now checks all system files and if they are patched/altered the update will fail, but have not ready any issues updating the nexus 7 to 5.0.1 or the nexus 10 when they are root.
Click to expand...
Click to collapse
No need to unroot to flash the new images..
Sent from my Nexus 4 using Tapatalk
ohhdavid said:
Interesting that it is the exact same build as the other 5.0.1 updates. No major Shamu specific changes? Hopefully the new binaries provide significant improvements at least.
Click to expand...
Click to collapse
There might be as there are new binaries I believe. I'll need to check when I'm home.
BRKotucs said:
No need to unroot to flash the new images..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Right that was only for flashing OTA update files right? Doing it through fastboot should just work, taking nandroid and then flashing after will post status
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
How did you disable the encryption in kernel, before I remember just using a modified boot image, dont know if that one will work for the new 5.0.1 factory image though, did you use the same boot image from this link to do this before updating?
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
---------- Post added at 06:59 AM ---------- Previous post was at 06:57 AM ----------
Silentsoul said:
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
Click to expand...
Click to collapse
So I was same, root with decrypted kernel and TWRP. I updated manually but forgot I had it decrypted, its encrypting right now, good thing I took a nandroid before so I am going to restore back to that image and try again with that modified boot image like I did before when I decrypted it and will let you know.
Silentsoul said:
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2954008
Sent from my Nexus 4 using Tapatalk
wolfnumba1 said:
How did you disable the encryption in kernel, before I remember just using a modified boot image, dont know if that one will work for the new 5.0.1 factory image though, did you use the same boot image from this link to do this before updating?
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Click to expand...
Click to collapse
Nope, I took 5.0.1 kernel, unpacked it, changed from force encrypt to encryptable and repacked. Will post it in that thread as soon as I'll get back to PC.
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
I have noticed the same thing on 5.0
I got the amazing speeds upon first boot after flashing then never again. 160/140 is similar to what i'm getting now. was that the same as encrypted?
Maybe it was all a placebo.
No force encryption boot img here:
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
XorZone said:
No force encryption boot img here:
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
Click to expand...
Click to collapse
Thanks!
wolfnumba1 said:
So I was same, root with decrypted kernel and TWRP. I updated manually but forgot I had it decrypted, its encrypting right now, good thing I took a nandroid before so I am going to restore back to that image and try again with that modified boot image like I did before when I decrypted it and will let you know.
Click to expand...
Click to collapse
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
What app are you using to measure?
joderme said:
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
Ill let you know, its updating now after flashing however I am going to reflash like I said before, I will check root status first though, I am sure the root is gone now.
Click to expand...
Click to collapse
joderme said:
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
What app are you using to measure?
Click to expand...
Click to collapse
1. cf-autoroot after flashing and 1 time booting works fine
2. androbench
Is the kernel the same? I'm curious if they changed it.
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
westernmg said:
Nexus Security Bulletin - January 2016
Download the Factory Images
MMB29P for Nexus 5x
Click to expand...
Click to collapse
Has someone captured the ota?
Nice find thanks
Now just need the modified boot.img for this newest build.
Does anyone can tell me if this month update restores the baseband menu (#*#*4636*#*#)with all the bands options?
Thank you!
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
ns2israel said:
it seems you need to this tread:
http://forum.xda-developers.com/nexus-5x/help/baseband-error-china-t3238867
good luck!
Click to expand...
Click to collapse
Thanks!
I actually successfully followed this method and manage to get this right again. I was just curious because I read on the google forums that this bug will be solved in a next update and was curious to know if it has been indeed addressed in this build.
Travisdroidx2 said:
Now just need the modified boot.img for this newest build.
Click to expand...
Click to collapse
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Got the OTA just now. Any chance it might fix the wifi problems I started getting with last month's update? Or does it strictly contain only boring security fixes?
Can you post a link to OTA
bg1906 said:
Actually since SuperSU 2.60 you don't need to worry about boot.img. Depends on your config though. Check out the thread below.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
I did see that after. However, I prefer system root still at this time. But I did see where you can run some commands to make the systemless to be system root.
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
I don't think its even possible to update with a custom recovery.
Tomyk89 said:
So I'm on the elementalX kernel, TWRP recovery, and rooted (stock) rom. Can i take the OTA that's prompting my phone without it overwriting any of that? I see that the OTA is only 11.4MB so I would assume that at most it would break ROOT.
Thanks in advance!
Click to expand...
Click to collapse
ulxerker said:
I don't think its even possible to update with a custom recovery.
Click to expand...
Click to collapse
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
dmudd said:
I have the latest TWRP recovery and I'm rooted and running ElementalX kernel. I updated yesterday successfully.
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You rock! I'll do this when I get home.
Tomyk89 said:
You rock! I'll do this when I get home.
Click to expand...
Click to collapse
No problem! Also, when I rebooted into system, my phone bootlooped once but didn't again after that. And you will also have to reflash the EX kernel.
Just FYI, I got all of this information from flar2 over in the EX kernel thread from this post.
tigid said:
Hey folks,
Has the OTA URL been made intentionally harder to capture? I got the OTA noon Jan 6th and immediately dumped logcat, but despite the log covering the entire morning there was no URL in there. The log seemed to reflect that the OTA has already been downloaded over WiFi previously, and the phone's UI simply gave the option to install, not to download.
Am I missing something here, or is the only way to capture now to be intercepting traffic and manually running an update check regularly in hopes you get lucky?
I feel like the Android update model is getting even worse, not better. Now not only do Google not publish the OTA links, enthusiasts have a hard time supporting the community too.
Click to expand...
Click to collapse
I didn't know there was a URL for the OTA and that it might show up in the logcat. Otherwise I would've checked for it. And doesn't logcat clear after each reboot? It would mean you would need to have adb ready and dump the log right after you start the download, but before the reboot which might be automatic. I know I've seen some logcat related stuff under dev options - at least for a longer buffer, not sure if you can make it persist across reboots.
I had not rebooted yet, the log covered from before 2AM that morning until noon when I received the notification. Unless the download occurred over ten hours before I was notified I would have expected to see the URL in the log.
Wow I have an update popped up!
Normally I have to manually do it!
Sent from my Nexus 5X using XDA Free mobile app
SINCE TWRP 3 THIS POST IS USELESS
Hi !
In this thread, you can find vendor.img from factory images in flashable zip format.
The zip will flash your vendor partition unconditionally (write_raw_image).
Flash it at your own risks
This is my first thread, be gentle plz
Thx to @BeansTown106 (Pure Nexus ROM) and Google
Update to MMB29Q vendor
Vendor from P and Q are the same in Nexus images...
gpvecchi said:
Vendor from P and Q are the same in Nexus images...
Click to expand...
Click to collapse
Not the same CRC (md5 or sha).
Can you explain plz ?
Blueblob said:
Not the same CRC (md5 or sha).
Can you explain plz ?
Click to expand...
Click to collapse
Sorry, my fault. I probably compared two times the same vendor.img. It's indeed different.
gpvecchi said:
Sorry, my fault. I probably compared two times the same vendor.img. It's indeed different.
Click to expand...
Click to collapse
We can do error, we are human.
Feedback is always a good thing.
I didn't compare img before your feedback, so next time I will do it, thx ?
Sent from my Nexus 5X using Tapatalk
What's so special about vendor.img so that we'll want to flash just this file?
ubcjack said:
What's so special about vendor.img so that we'll want to flash just this file?
Click to expand...
Click to collapse
Some people (myself included) are too lazy to download the factory image and extract the vendor.img and then flash it in fastboot and find it easier to flash in recovery.
Blueblob said:
Hi !
In this thread, you can find vendor.img from factory images in flashable zip format.
The zip will flash your vendor partition unconditionally (write_raw_image).
Flash it at your own risks
This is my first thread, be gentle plz
Thx to @BeansTown106 (Pure Nexus ROM) and Google
MDA89E vendor zip
MDB08I vendor zip
MDB08L vendor zip
MDB08M vendor zip
MMB29K vendor zip
MMB29P vendor zip
MMB29Q vendor zip
Click to expand...
Click to collapse
Sorry for this question, but what does the vendor file do exactly?
alwaysbelieve1 said:
Sorry for this question, but what does the vendor file do exactly?
Click to expand...
Click to collapse
The vendor partition contains proprietary drivers and such, if I understand correctly.
alwaysbelieve1 said:
Sorry for this question, but what does the vendor file do exactly?
Click to expand...
Click to collapse
Drivers and binaries from manufacturer (not open source).
Before 5X and 6P, it was mandatory to build Android (https://developers.google.com/android/nexus/drivers)
Now it's a dedicated partition.
Sent from my Nexus 5X using Tapatalk
added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up
Blueblob said:
MMB29Q vendor zip
Click to expand...
Click to collapse
When I booted the 2/4 nightly of CM13, I got the error about an "internal problem". Doing some searching, it said to flash the vendor.img that matched the build, which would be MMB29Q. When I flashed this zip, I still got the error. I pulled the vendor.img out of the stock image from google and flashed it with fastboot and now the error is gone. There is some sort of difference between this file and the google one.
psycho_asylum said:
When I booted the 2/4 nightly of CM13, I got the error about an "internal problem". Doing some searching, it said to flash the vendor.img that matched the build, which would be MMB29Q. When I flashed this zip, I still got the error. I pulled the vendor.img out of the stock image from google and flashed it with fastboot and now the error is gone. There is some sort of difference between this file and the google one.
Click to expand...
Click to collapse
Thx. Gonna check
Edit : Same CRC for vendor.img in my zip and zip from Google
Strange, maybe cache or something like that
Sent from my Nexus 5X using Tapatalk
Experienced same thing...
Looking for why
Haha ok, vendor partition needs to be mounted
You can do it in twrp
I'll will update files later
today's cm shows MMB29U in build.prop thus showing internal error message with Q
So...
My updater script doesn't work.
I'm investigating
Sent from my Nexus 5X using Tapatalk
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
No need to make a flashable zip anyway. We will able to flash vendor.img in twrp.
Sent from my Nexus 5X using Tapatalk
Is there any way to check which vendor image is installed?
Edit 1: Nevermind, found it under vendor/build.prop
Thanks for this, saves me from downloading a whole img.
Edit 2: Doesn't seem to work, even when I mount the vendor partition in twrp it doesn't seem to properly flash it. Any advice?
I gonna ask a mod to close my thread
I will find another way to contribute to community with my skills ?
Sent from my Nexus 5X using Tapatalk
Google just released May 2016 factory images for Nexus devices.
Factory Images for Nexus Devices
Android Security Bulletin—May 2016
Anyone flashed it?
OTA zip file link?
Sent from my Nexus 5X using XDA-Developers mobile app
We probably need to wait a little bit for OTA zip.
following for ota link
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
miksontije said:
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
Click to expand...
Click to collapse
Hopefully it's a good update. Sometimes they're hit-or-miss.
mxrider97 said:
Anyone flashed it?
Click to expand...
Click to collapse
Flashed it yesterday, haven't noticed anything new. However, I also haven't noticed anything bad or broken; which is just as important.
Sent from my Nexus 5X using Tapatalk
Flashed using the factory images and nothing is broken. It did trigger a Google Camera update and it has been improved a bit more. Faster startup and snappier response when changing between portrait and landscape mode. Battery life stayed the same.
waiting for ota zip :good:
I updated using fastboot. Rooted and everything is working fine. Even Android Pay with the latest SuperSU.
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Just installed! You have any advice about a compatible kernel?
Andr006 said:
Just installed! You have any advice about a compatible kernel?
Click to expand...
Click to collapse
I like EX Kernel. It has not been update with the new patches but will still work well.
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
I update all the images with fastboot then just use WugFresh to root and add TWRP.
65coupei6 said:
I update all the images with fastboot then just use WugFresh to root and add TWRP.
Click to expand...
Click to collapse
This worked in the end, thanks for your help tip!
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
if you boot using stock kernel (boot.img) android will replace whatever recovery you have flashed with stock recovery.
to prevent this from happening, PRIOR to first boot after flashing update, flash twrp in fastboot, scroll down in fastboot menu and boot into recovery/twrp, and apply supersu update.zip
after that you'll be rooted again and boot.img will no longer try and replace your recovery with stock recovery.
OTA posted:
http://forum.xda-developers.com/showpost.php?p=66781159&postcount=124