Download Brick Game For Android ((FREE))
Buddy Ssims
In Android, there used to be a permission with the name BRICK that could be used to potentially disable the device. Other than hearing it as an urban myth, I do not really know if this permission can really be used to brick a device.
It's still there in the android documentation and there is no indication that it is deprecated. It is a system level permission and so has to be signed with the same signature as the android version build. So an app developer cannot use it. It may be usable on an emulator but I'm not sure.
You should understand difference between a permission and actual API functionality supported by this permission. So far I do not see any API calls for bricking a device. You should understand also difference between soft bricking and hard bricking. For example damage boot portion of OS will be just soft bricking however physical burning some circuits can be considered as hard bricking. Since use of Android isn't limited to only phones and tablets, I can see some military use of this functionality, for example if you have Android based missiles launcher, using this functionality makes great sense. Another use case for example smart cards, I heard that some TV provider used smart cards which were hacked, so the TV provider just sent a "bricking" signal issued permanent damage of smart cards. I am currently interviewing by a company which deploy Android on smart cards, so certainly I will work with this functionality soon and can give you more details.
It's certainly possible to remote-brick a phone. In fact, you might be able to use Tasker in conjunction with Mobile Odin or similar to remotely softbrick a Samsung device by flashing bad firmware after a text message, or something. Of course these devices are also easy to unbrick; to brick them more permanently you'd need to flash a bad bootloader. Chainfire has said that Mobile Odin can but won't flash bootloaders, so perhaps it could just be modified.
Importantly, though, I wouldn't do this. All it does is guarantee that you can't get the phone back (you can't track it anymore) or that if you get it back, it won't work. You should just install tracking software instead. Remote bricking won't deter a thief who doesn't know about it, and while I see the revenge aspect it's not as good as catching them!
Starting today you can access this functionality through stock android and Google apps at Once you set it up, you will be able to remotely delete all your data from the device, and locate it on Google maps. Remote locking and changing the lock-screen are also listed as functionalities available (soon).
I've googled what happens when you hard brick a phone. All I get are noob posts telling how or how not to hard brick your phone. Most of the posts say that when you flash the wrong ROM, the phone may get hard bricked. My question is,
Usually, the only software-based hard brick that is possible is when you overwrite the bootloader. Without a (working) bootloader, the phone (a) cannot get to the point where it would load the operating system and/or (b) cannot have working software loaded onto it.
For it to be possible to hard brick a phone, some of the software that the phone has to run to boot and flash itself -- something from the point where it's a just-powered-on processor running address 0 to the point where the phone is writing a new image to flash -- needs to be itself in flash that the phone can write. Usually this is something like a secondary boot loader. If you erase that, then you can't reflash anymore. Hard bricked.
On a phone where you can write something new with only the aid of whatever software is in ROM that the phone can't write, whether or not it's by shorting a couple of pins and there's USB straight into the processor, you can't truly "hard brick" the phone. Unbricking would always be possible at least in theory, provided you can feed it the firmware in whatever format it needs.
So I was wondering if there was a method bricking my phone remotely in the event it was stolen? Something like remotely deleting the System32 equivalent of an Android phone. Or maybe a way to rig my battery to discharge its power supply to fry the hardware. It's probably too fantastical to be a real thing, but I would like to at least know if I have any options on the matter.
Howdy! So, like many others, I woke up with a system update pending for my V60 (firstly, amazing that LG kept their promise with updates for this phone, it's one of my favorite phones and I deeply miss LG's V series, having had a V10, V20, V30, V35, V50, and still using my V60). However, like many others, the update soft bricked my phone. It would only boot to black screen with flashing and disappearing navigation buttons, but no other controls or display. I didn't expect a full 13 update and all other updates have gone perfectly well, no issues at all, so I just went ahead and updated without doing a full backup (In the eternal words of Julia Roberts: "Big mistake. Big. HUGE!").
The way to fix the brick is to boot to qualcomm QDLoader 9008 mode and use FireHose to wipe the userdata partition and flash the engineering bootloader. Nothing else worked for me. I wanted to share a quick tutorial to help others fix their bricked V60 after the update.
Unfortunately this method WILL delete ALL of your data that is not on your SD card. I personally lost the last 6 months of photos and videos, which is pretty devastating but again 10000% my fault for not backing up. However, this update should not be something that bricks phones, so some blame has to be placed on LG/TMO for releasing an update that has bricked a good 50% of users' phones.
A brick (or bricked device) is a mobile device, game console, router, computer or other electronic device that is no longer functional due to corrupted firmware, a hardware problem, or other damage.[1] The term analogizes the device to a brick's modern technological usefulness.[2]
Installing firmware with errors, or for a different revision of the hardware, or installing firmware incompetently patched such as DVD firmware which only plays DVDs sold in a particular region, can also cause bricking.
Hard bricked devices generally show few or no signs of life. A hard bricked device does not power on or show any vendor logo; the screen remains turned off or blank. Some of the major reasons for hard bricking include installing firmware not intended for the device, severe physical damage, interrupting a firmware flashing procedure, or following a flashing procedure incorrectly.
Recovering from a hard brick is generally considered difficult and requires the use of a more direct programming interface to the device; such an interface often exists, as there must be a way to program the initial firmware during the manufacturing process. However, additional tools or connections may be needed, such as low-level programming devices. Hardware hard brick recoveries are also considered difficult and require electrical knowledge to find and fix hardware issues. For example, an overloaded capacitor in a circuit may explode, thus stopping the flow of electricity and bricking the device. More complex examples involve permanent damage to integrated circuits and processors. Fixing such hardware bricks involve replacing these components entirely or fixing them by either bypassing if the circuit allows or other methods.
Most devices can be hard bricked in a variety of ways. Resolution generally follows a process of analyzing the boot process, determining the sub-type of hard brick, and making changes with the help of external (non-bricked) devices.[3]
A "soft bricked" device may show signs of life, but fails to boot or may display an error screen. Soft bricked devices can usually be fixed relatively easily; for example, a soft bricked iOS device may display a screen instructing the user to plug it into a computer to perform an operating system recovery using iTunes computer software.[4] In some cases, soft bricked devices are unable to be repaired without physical repairs being carried out; an example of this would be an iOS device locked with iCloud Activation Lock, of which the only solution is to contact the owner of the iCloud account the device is locked to, or to replace the entire logicboard with a non-locked board.[citation needed]
Some devices that become "bricked" because the contents of their nonvolatile memory are incorrect can be "un-bricked" using separate hardware (a debug board) that accesses this memory directly.[5][better source needed] This is similar to the procedure for loading firmware into a new device when the memory is still empty. This kind of "bricking" and "un-bricking" occasionally happens during firmware testing and development. In other cases software and hardware procedures, often complex, have been developed that have a good chance of un-bricking the device. There is no general method; each device is different. There are also user-created modifier programs to use on bricked or partially bricked devices to make them functional. Examples include the Wiibrew program BootMii used to fix semi-bricked Wiis, the Odin program used to flash firmware on Samsung Android devices,[6] or the fastboot Android protocol which is capable of re-flashing a device with no software installed.[6]
In principle any device with rewritable firmware, or certain crucial settings stored into flash or EEPROM memory, can be bricked. Many, but not all, devices with user-updatable firmware have protection against bricking; devices intended to be updated only by official service personnel generally do not.
Amongst devices known to have bricking issues are: older PCs (more recent models often have dual BIOSes or some other form of protection), many mobile phones, handheld game consoles like the PlayStation Portable and Nintendo DS, video game consoles like the Wii, Xbox 360, PlayStation 4, and Xbox One, many SCSI devices and some lines of hard disk drives and routers.[citation needed]
dafc88bca6