Quote:
Originally Posted by Cannon Fodder View Post
that would be really useful.
And although I understood the analogy, I still don't get the technical aspects of why you can have 1,000 devices that are all the same but they each need a different file. I'm used to building Windows computers, and you can use the same image repeatedly for multiple copies of the same type of computer.

I'm also wondering: why can't anything be installed straight from the SD card or even USB when a device is bricked? How does Asus do it when they fix people's motherboards?
Think of it like a cryptographic key. Each tablet's NVFlash blobs has a certain signature. To compare it to the Windows situation, assume that you have a legal, non-volume licence key for Windows, only that when you installed it the first time, the key was permanently bound to the motherboard.

Assume that it is a string of lower-case letters (good chance that it has numbers, capital letters, and all sorts of fun stuff). A two-character signature has a space of 26*26, which is already over 625 keys. That number scales hella fast when you add more characters.

Asus will fix your tablet by either replacing your motherboard completely (more likely), or they may have the NVFlash keys for your device by its serial number. However, since your bootloader is unlocked, and they will have your serial number on file as "unlocked", they may just refuse to repair it outright. Surely, they will refuse it for a warranty repair, though I don't know if they will even repair your device for money.
Anonymous founding contributor to Team CodeFire.

Samsung Galaxy S4 SGH-i337 - BroodPlank AOSP 4.4, Jeboo CWM 6.0.4.7.
HTC Desire HD - CodeFire CyanogenMod 11, official tester, 4ext 1.0.0.6 RC1.
HTC Raider 4G - Sold.
Samsung Galaxy S i9000 - Stock rooted 2.3.6 XWJW8, CWM 2.5.1.2.
Asus Transformer Pad TF300T - CyanogenMod 11, TWRP 2.6.3.1.