Mine is a totally unresponsive device - can't access boot loader - no buttons working - nothing.
As long as you have the proper boot loader working, it's not bricked, and can be made to work again - easily.
I have flashed a flo rom on my hammerhead before....no issues. I have flashed nexus 4 kernel before..... No issues. So please relax. Your're wrong here. Recovery has its own kernel. Nexus devices have a boot loader. Tough to brick. Know your information before posting and misleading others
I feel like you're arguing just to argue. You said the only way to brick the N5 is by flashing a ROM from another device on it. Yet you go on to say you flashed a flo ROM with no adverse effects. Suspect. N5 actually has two bootloaders. I can't say I believe you about N4 kernel on N5 as I remember now for sure. He did brick flashing a N4 kernel. Find one, flash it and PM me screen shot your N5 on a N4 kernel. Recovery having its own kernel doesn't have to do with what I'm talking about. Obviously they're tough to brick, but go ahead and flash a kernel from a phone that's not a nexus LOL.
Flashing proprietary blobs has nothing to do with a hard brick.
To answer all of these, long ago, flashing kernel or rom was being done by accessing the relevant partition per number (i.e. emmc0blk1) which is obviously different for each device. However, nowadays, MOST of the kernel access the partition per name (/dev/block/platform/(platform_name)/by-name/(name_of_the_partition) which is kind of a failsafe. That way, even dumb people flashing nexus 4 kernel on their nexus 5 would overwrite only the kernel partition, where as flashing by partition number would overwrite the aboot (mmcblk0p6) partition of the said nexus 5 with a nexus 4 boot (mmcblk0p6) partition, killing the bootloader.
Also, not sure by what you meant by "Nexus devices have a boot loader.". All devices have bootloader otherwise they'd all be paperweight. I think you should make some reading before flashing your 400$ device with anything.
|Thread Tools||Search this Thread|