yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Themes and Apps] gee one:
I don't think those are "image" files. They are ARM binaries that will run on the phone. imgdata is just structured data.

file bootloader*
bootloader.aboot.img: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
bootloader.cmnlib.img: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
bootloader-flag-clear.txt: data
bootloader-flag.txt: ASCII text, with no line terminators
bootloader.hyp.img: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, stripped
bootloader.imgdata.img: data
bootloader.keymaster.img: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
bootloader.pmic.img: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, stripped
bootloader.rpm.img: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
bootloader.sbl1.img: data
bootloader.sdi.img: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, stripped
bootloader.sec.img: data
bootloader.tz.img: ELF 64-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped

The only file that is different between the last 3 bootloaders is aboot, which appears to be the actual bootloader program that gives you the fastboot menu and also boots recovery and system images.

md5sum
767f62f046598bf8bbcee328bd12cf11 mtc19z/ota/bootloader.aboot.img
502c9b975894c3199d4c3103aa4aac20 mtc19v/ota/bootloader.aboot.img
edc2482db47d21e272fc3d4455d87a98 mtc20f/ota/bootloader.aboot.img

The rest of the files seem to be bitwise identical.

Getting rid of the warning images defeats some of the security features. I suspect that there is a hash/signature check so that we can't be "tricked" into thinking that our phone is secure if someone loads a cracked ROM. That being said, I think we need someone with expertise in bootloaders to figure out what the new aboot is doing.

Here is some background info in the verified boot:

https://source.android.com/security/verifiedboot/verified-boot.html

Lastly, there are some security patches to the bootloader- I haven't poured over all of this yet to see which relates to the image data. Scroll down towards the bottom to get to the patch details.

https://source.android.com/security/bulletin/2016-08-01.html
[Nexus 5X Themes and Apps] gpvecchi:
I checked both bootloaders with hex editor: I found that imgdata starts at a different address, but it has even different bytes. Previous imgdata.img matches perfectly with imgdata part in old bootloader.

EDIT: I looked at the imgdata in latest OTA file and it's the same of the stock one provided by Bitdomo, so I assume we can use the same imgdata as before.

In my opinion (but I'm not an expert) I think that new structure just have imgdata at a different address. And that sounds correct as imgtool gives bad descriptor for image 5.

EDIT 2: It seems that all the scripts flash the imgdata.img to the address f9824900, so it seems all correct, but as gee one says there is some other part of the bootloader that prevents the images to be displayed correctly.

So, images have to be stored even somewhere else...

Stupid idea: couldn't be the bootloader that prevents the correct flashing of modded imgdata? Is there any way to flash it via fastboot/adb?
[Nexus 5X Themes and Apps] sfhub:
Is it possible the image data is now hashed and there is a failsafe "corrupt" image embedded in the bootloader code to be used if the themed image data fails hash?
[Nexus 5X Themes and Apps] mlord:
I suspect the reason aboot is much larger, it that the images are now hardcoded inside aboot, ignoring the imagedata partitions entirely. Easy to test: just replace all of the images with something different, and see if the original images still show up at boot time.
[Nexus 5X Themes and Apps] sfhub:
That is basically what I suggested. I am just unsure if it is the corrupt message only or all of them.

This was what happened to Gee One when he flashed the images at the old (wrong) location.

Which is why I suggested at least the corrupt message was embedded in code.

I believe it was also confirmed the images are still there but at a different location. It could be they are ignored and everything is embedded in code, or it could be there is a failsafe corrupt message to be used if the images fail some check (probably hash check)

As Gee One mentioned above, flashing the images at the wrong location did have some change in behavior, loss of android dude.
[Nexus 5X Themes and Apps] gee one:
I think the next step is to look for the fallback images in the new aboot. I'm a bit busy for the next few days, but it shouldn't be too hard to look for a few binary patterns from the red screen in aboot, in case anyone else want to take a stab at it. Looking at some of the other diffs between the new aboot and the old aboot might be helpful too.
[Nexus 5X Themes and Apps] gpvecchi:
As I said, the addresses of the imgdata are the same as before. I'm afraid that what has been said of the N bootloader is true even with latest M aboot. If something is modified, there will be the red alert (built-in in aboot) and the modded part will not be loaded! I'm afraid for what regards modded system (custom Roms)
[Nexus 5X Themes and Apps] gee one:
I did a little poking around in the new aboot and this doesn't look too encouraging:

strings aboot_mtc19v.img | grep IMGDATA
IMGDATA!
Loaded IMGDATA at 0x%X

strings aboot_mtc20f.img | grep IMGDATA
IMGDATA!
Loaded IMGDATA at 0x%X
IMGDATA corrupted

It seems that there is some signature/hash checking to detect if the image data is corrupted.
[Nexus 5X Themes and Apps] xabier-bo:
Could you say which is the latest "working" bootloader?

PS. A bit surprised about these changes on google's criteria... If you unlock and flash a new imgdata, you are supposed to know what are you doing. And if you are just a bit "techy", maybe don't feel comfortable being warned every time...
[Nexus 5X Themes and Apps] xabier-bo:
Just in case another one is looking for: the last one I've found is bhz10p
[Nexus 5X Themes and Apps] gee one:
From a security perspective, I think the situation they are preventing is a malicious actor installing a rom on a stock phone without the user being aware. Think of an evil maid scenario or a phone "lost" for a few hours, that comes back with a malicious rom that looks just like the stock rom, except for a few extra seconds at boot.

I think most people here have an unlocked bootloader and choose to customize their phone, so this is not the target audience that is protected by this change.

I'll throw this out there and say that it is possible to have a locked bootloader and a custom rom and still be able to flash new ROMs, radios and bootloaders. It's a little more work, but it is possible.
[Nexus 5X Themes and Apps] xabier-bo:
Thanks gee one,

These days I am reading Charles Cumming and Stella Rimington ;-D, and I also thought of possible scenarios where this change could make sense, but may be it's a matter of days or weeks for any clever developer around here to find a "solution"...

Just for curiosity (and learning), any thread where to learn how to root Nexus 5X with a locked bootloader?
[Nexus 5X Themes and Apps] gee one:
You can unlock the bootloader, root the phone, then lock the bootloader. Data are wiped only when unlockiing. The tricky part is updating recovery, vendor, and the bootloader when the bootloader is locked. You can use an insecure recovery that will allow you to flash any unsigned zip, or you can use a more secure recovery and sign all the zips that you want to flash. It's extra work and there are probably bigger security holes in other areas.
[Nexus 5X Themes and Apps] xabier-bo:
A new way to explore (for me)... thanks!
[Nexus 5X Themes and Apps] PiousInquisitor:
Make sure you do your homework on locking the bootloader after making changes to your phone.

Locking with TWRP installed will definitely cause you issues. I don't know about rooting, flashing stock recovery, then locking. But, I wouldn't do it till I knew for sure it wouldn't cause issues.
[Nexus 5X Themes and Apps] Moto G User:
Android 7.0 Nougat not working anymore

Just flashed this zip after i installed android N but the warning is still there Any update possible?

Thanks
[Nexus 5X Themes and Apps] kojak1989:
[MENTION=4325732]bitdomo[/MENTION]

Can you update your tool because it fails to compile bhz10r.
[Nexus 5X Themes and Apps] ebowen 747:
I just fastboot flash bhz10p bootloader, works like before no problem. New bootloader checks for tamper.
[Nexus 5X Themes and Apps] semenoof:
I have updated to Android 7.0 Nougat.

Just flashed this zip after i installed android N but the warning is still there Any update possible?
[Nexus 5X Themes and Apps] xabier-bo:
Just flash bhz10p bootloader
[Nexus 5X Themes and Apps] Midomad:
Link to bhz10p bootloader?
[Nexus 5X Themes and Apps] xabier-bo:
https://www.androidfilehost.com/?fid=24588232905720818
[Nexus 5X Themes and Apps] agentdr8:
In one of the previous factory builds.
[Nexus 5X Themes and Apps] Midomad:
Appreciated,but error when trying to download i don't want to download the whole factory image, will search more.

Edit:working now :)

Lol.
[Nexus 5X Themes and Apps] xabier-bo:
It's working for me.

Yes I had the whole factory image as well, but googling for bootloader bullhead bhz10p you will get different links.

This one, was the one I used ;)
[Nexus 5X Themes and Apps] Necrodaemon:
Someone has the fix for bootloader-bullhead-bhz11e.img in NRD90S?
[Nexus 5X Themes and Apps] Midomad:
No,not yet.
[Nexus 5X Themes and Apps] xabier-bo:
bhz10p will do the work ;)
[Nexus 5X Themes and Apps] Midomad:
Sure,his talking about the one from september images!
[Nexus 5X Themes and Apps] Necrodaemon:
Exactly, i ask is about of new bootloader
[Nexus 5X Themes and Apps] mishko:
[MENTION=3360838]PhoenixTank[/MENTION]

Your zips were excellent! Any plans on making ones for Nougat (NBD90x)?
[Nexus 5X Themes and Apps] Mailphone.andrea:
Can you made for nogat (nbd90w)?

Tnks
[Nexus 5X Themes and Apps] Midomad:
I think this discountinued.

The last message from OP was on 11 fev,so his not active anymore!

Try to flash an older bootloader.
[Nexus 5X Themes and Apps] xkym:
What needs to be done to get this working again?

The imgdata.img flashing goes to a long but valid /dev/block/platform/.../imgdata - symlink is active to the relevant mmc blk device.

When pulling this after using the "flash-me.zip" - using dd - extracting the imgdata.img shows the stuff that was modified in the tool.

So the boot images are there, but the phone is now looking at another location?
[Nexus 5X Themes and Apps] semenoof:
Is there solution for the last bootloader 11 whithout downgrading it? How to hide the message "...your device can't check for the corruption..." Have any ideas?
[Nexus 5X Themes and Apps] Midomad:
No.
[Nexus 5X Themes and Apps] banana guy 67:
Can I use this for the bootloader BHZ11l and if yes do I flash the IMG or the zip
[Nexus 5X Themes and Apps] xabier-bo:
Not working in newer bootloaders...

But you can flash and older one (bhz10p)
[Nexus 5X Themes and Apps] xkym:
Not sure if anyone has looked at it closer yet - /imgdata is indeed updated, if you restart and pull the imgdata partition back off the phone it will have the changes you have applied.

So the phone is ignoring this area and pulling these logos from another location.
[Nexus 5X Themes and Apps] FLH_Sky:
Is there an update for the latest bootloader BHZ21C of Android 8.0?
[Nexus 5X Themes and Apps] osm0sis:
I can confirm a new-imgdata.img generated by the tool in this thread appears to get ignored on the latest bootloader, showing all images even though I've replaced them with all black in the new-imgdata.img.

[MENTION=4325732]bitdomo[/MENTION] [MENTION=5448769]makers_mark[/MENTION] any ideas? Here's the current imgdata.img.

Edit: I see the bootloader.img always contained imgdata.img with it, but maybe the imgdata partition isn't used anymore and they're also being split from the flashed bootloader.img into sbl or something... I'll keep hunting around.

Edit 2: Damn, sbl1 doesn't contain it either, I also checked DDR and aboot, and no other partitions are big enough to hold it that aren't already empty. No idea where the new bootloader is pulling them from, unless they are encoding them differently again elsewhere.. but then why would the latest bootloader.img still contain them as they are in imgdata..? :confused:

Edit 3: It's been a few weeks and no response, so I'm unsubscribing for now. Please @ mention me if you end up figuring anything out. :good:
[Nexus 5X Themes and Apps] htc_unenthusiast:
Can you point me to instructions on flashing the bootloader? I have the version you mentioned but I usually only flash kernel and user space builds.

Any input is appreciated!
[Nexus 5X Themes and Apps] sebastianrameshs s:
HI, I am new to this concept. I want to know some information about spalsh. image in developing boards. Can anyone explain how to make this application (tool ) for creating splash.image to flash on the custom board.
[Nexus 6P Q&A, Help & Troubleshooting] geoff5093:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
[Nexus 6P Q&A, Help & Troubleshooting] MrDSL:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
[Nexus 6P Q&A, Help & Troubleshooting] bitpushr:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
[Nexus 6P Q&A, Help & Troubleshooting] Mikey:
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding :) Hello [MENTION=450224]bitpushr[/MENTION]
[Nexus 6P Q&A, Help & Troubleshooting] krabman:
Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...
[Nexus 6P Q&A, Help & Troubleshooting] geoff5093:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
[Nexus 6P Q&A, Help & Troubleshooting] MrDSL:
Chainfire has one and I believe there is one in the development forum.
[Nexus 6P Q&A, Help & Troubleshooting] geoff5093:
I was looking at his thread, but I only see one for the 08K image.

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

The one in the dev section also appears to only be for 08K: http://xdaforums.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013

I just wanted to confirm that these need to be the same, so I'll wait for an update.
[Nexus 6P Q&A, Help & Troubleshooting] MrDSL:
I thought Build MBD08K was the latest..

I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img
[Nexus 6P Q&A, Help & Troubleshooting] mysongranhills:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.

I have working root, decrypted with TWRP installed.
[Nexus 6P Q&A, Help & Troubleshooting] bitpushr:
Awesome!! ????
[Nexus 6P Q&A, Help & Troubleshooting] rsmolen:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:

1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)

2. Download and install OTA

3. Reflash modified MDB08K boot.img from Chainfire

4. Reflash TWRP recovery

5. Install SuperSU 2.52 using TWRP

Has anyone tried this method?
[Nexus 6P Q&A, Help & Troubleshooting] mysongranhills:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
[Nexus 6P Q&A, Help & Troubleshooting] geoff5093:
In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.
[Nexus 6P Q&A, Help & Troubleshooting] rsmolen:
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.
[Android Apps and Games] Nilanchal24:
Hi,

I deleted my splanner and my sdmaid backup copy doesnot have odex files.

To reinstall i need the odex file too.

Any rooted user, please attach SecCalendar_SPen.odex file from /system/apps folder of their note 2.

Regards
[Nexus 5X Q&A, Help & Troubleshooting] leontine:
Does anyone have this problem? I have the "old" ( first version) off Chromecast nexus 7 and 5 works perfect with it, the new 5x won't.

Any thoughts? It's on 2.4 ghz...

Edit: Solved see below!
[Nexus 5X Q&A, Help & Troubleshooting] dpwhitty11:
Covering all bases here... Do you have the Chromecast app installed? :p
[Nexus 5X Q&A, Help & Troubleshooting] leontine:
Yep off courses don't find any devices

Verstuurd vanaf mijn Nexus 5X met Tapatalk
[Nexus 5X Q&A, Help & Troubleshooting] leontine:
And delete the app, start fresh and

.....BAM find it!!! Perhaps old settings still backup-ed?? Anyway working fine now

Verstuurd vanaf mijn Nexus 5X met Tapatalk
[Nexus 5X Q&A, Help & Troubleshooting] gerg004:
I had some issue's as well, turned out it was my new modem/router.

Have you had either replaced since the last time it worked? If you have you may need to log into your router and change the WiFi frequency. Mine was on 11, I changed to 1 and its been working since. Hope that helps
[Nexus 6P Accessories] itch808:
I hear all these talks about cases blocking mics and the autofocus laser. My Project Fi Nexus 6p just shipped today and I'm wondering if it's worth getting a case through google with the Fi 50% discount code.

The microfiber case looks the most unique but there were initial concerns of it coming off the back (http://xdaforums.com/nexus-6p/accessories/google-6p-carbon-quartz-case-t3213838). The Adopted case is the cheapest but doesn't look like much. What have you done?
[Nexus 6P Accessories] joderme:
I got the adapted and I like it a lot, however, I should have gotten the carbon. I got the frosted case thinking that it would be more see through on a graphite phone. It just doesn't look right. It is a bit slick, however, it fits the phone nicely and feels nice as well.
[Nexus 6P Accessories] donald121:
I got the $35 (carbon/quartz) case.

Look: so so, doesn't look as good as in the pictures

Protection: great, is pretty thick TPU

Feel: make the phone feel bigger

$35 no worth it, with your 50% off, yes it worth it.

One of the reason I got this case is it has the "NEXUS" logo instead some other case brand logo, but if the case is damaged I would not get another one. I would get a clear case.
[Nexus 6P Accessories] jprev:
Just as a note, I think the code only applies to the ADAPTED case.
[Nexus 6P Accessories] Ovrclck:
Correct.
[Nexus 6P Accessories] cloney:
Does anyone have a 50% code that they havent used or clicked on the link from the email? Would greatly appreciate it if you can share!
[Nexus 6P Accessories] LuckyDragan:
I'm returning the carbon Adopted microfibre case for my N6P. The fit was really snug and the ports/hole cutouts were all fine, but I couldn't justify spending nearly $40 CAD for essentially a TPU case with what amounts to a paper-thin microfibre sticker on the rear. Aside from future peeling concerns, I think the pattern and logo would also start peeling off after hundreds of time rubbing the inside of my jean pocket. Then the case wouldn't become anything special.

I'd rather spend 1/3 of the price on a Diztronic TPU case and customize it myself with a DBrand or Slickwrap skin (e.g. with the rainbow "X" logo).

Another option I'm considering is the Crash Guard by Evolutive Labs paired with a Slickwrap Natural Leather skin on the back.
[Nexus 6P Accessories] ChrisJ:
Beware of the Folio case. Mine is currently stuck on the phone. I'm not alone either it would appear (from the google product support forums). It looks likely that I'm going to have to return the phone for another.

There's either a batch issue or a design issue.
[Nexus 6P Accessories] AndreaCristiano:
I have the Nexus official case in Carbon and it's great. Love the way it looks love the feel especially the felt back and it is very protective. Totally worth it. The adopted case is nice but I feel it's not as protective
[Nexus 6P Accessories] rdelfin:
You can count me as one of the 'Loving it!!'-camp. This case is exactly what it's portrayed as: the most intrinsically designed case for the 6P... The rest, as much as they try to be the same, they're still aftermarket products. Yes, I agree 35 dlls is not acceptable, but that's another issue apart from how good this case goes.
[Nexus 6P Accessories] dowlf:
I'm another fan of the official case. I also have the Adopted, but the official case is the one on my phone right now and probably will stay that way.
[Nexus 6P Accessories] rborg:
I'm hoping I never have to take mine out again. Once was enough. It's jammed in there for good.
[Galaxy S III Q&A, Help & Troubleshooting] athunder:
Hi, need some advice on restoring my S3 back to stock.

What I've done so far...

Used this guide http://xdaforums.com/galaxy-s3/general/galaxy-s3-i9300-basics-best-performance-t3111802 to install CyanogenMod V11.0(Android 4.4.4)

I have had battery issues and also changed to a new phone, so now would like to restore the S3 back to its original state.

I have followed this guide http://xdaforums.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081

But so far had no success.

The ROM that thread links to doesn't work for me so have tried to download 2 others

I9300OXAEMG4

I9300OXAGMK6

Having run Odin it gives the following messages:

Added!!

Enter CS for MD5..

Check MD5.. Do not unplug the cable..

Please wait..

KIES_HOME_I9300XXEMG4_I9300OXAEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.

Checking MD5 finished Sucessfully..

Leave CS..

Odin v.3 engine (ID:4)..

File analysis..

SetupConnection..

Initialzation..

Get PIT for mapping..

Firmware update start..

boot.img

Normally just seems to hang at this point, or eventually display failed message.

This is first time I have ever used a Custom ROM on a phone so I am very much a novice at this.

Apologies if this seems a stupid question or if I'm asking the wrong place, just have no idea what I'm doing wrong!
[Galaxy S III Q&A, Help & Troubleshooting] Stevica Smederevac:
For a start,try diffrent cable and other usb ports on pc.
[Galaxy S III Q&A, Help & Troubleshooting] athunder:
Sorted!

Seems it may have been drivers?

Had Kies installed but when i loaded it up and tried to connect my phone, i got some files/setup appear that didn't happen before, tried with Odin again and worked.

Thanks for the suggestion Stevica