Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,808,312 Members 39,118 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Why the smartphones hard bricks?

Tip us?
 
aacsanchez
Old
#1  
Junior Member - OP
Thanks Meter 1
Posts: 6
Join Date: Dec 2010
Location: Sao Paulo
Default [Q] Why the smartphones hard bricks?

Im getting old (30 years old) and Im trying to understand how the Android boot works.

For me, the concept about inicialize a system, in a few words, is:
1. The BIOS inicialize the mains components (like a RAM, Video, etc);
2. After that, call a bootsector of HD;
3. On bootsector are present a bootmanager (MBR, Grub, etc), who is responsable to "identify" and start the OS (like a Windows ou Linux).
4. The OS start and the magic happens.

Some things are very simple to assume:
1. You don't need modify (unlock) or replace the BIOs, because it just inicialize the computer.
2. After BIOS you have a bootmanager and you can modify or replace it as many times as you want.
3. Change the OS doesn't brick my PC.

I readed a lot of articles about inicialization and partitions, but I can't understand why the smartphones bricks?
Now, the questions:

1. So, WHY the smartphones bricks?
2. Do Hard brick happens in bootloader process or before?
3. Why do I need unlock the bootloader?
4. Does the custom ROMs change the bootloader? If, yes and assume the bootloader hard brick the devices, why the Custom ROMs doesn't create a bootmanager after the bootloader official (as Grub call MBR)?
5. Can I replace the smartphone "BIOS"?


I spend a lot of money in a Atrix 2, and I really want understand how this things works to customize it.
 
aacsanchez
Old
#2  
Junior Member - OP
Thanks Meter 1
Posts: 6
Join Date: Dec 2010
Location: Sao Paulo
Nobody? I have the same questions.

Enviado de meu MB865 usando Tapatalk
 
androidrocks23
Old
#3  
androidrocks23's Avatar
Senior Member
Thanks Meter 109
Posts: 187
Join Date: Oct 2013
Location: Bangalore

 
DONATE TO ME
A hard brick is where
you're device won't boot at all. You have to either
repair it yourself, using a JTAG or send it into a
JTAG service to have it fixed. These are usually
caused by people flashing ROMs or kernels not
meant for their device. Flashing a ROM not meant
for your device, can throw your system through a
loop, because it also flashes the kernel.
The kernel is what allows your phones software to
interact with the hardware. It contains all the
necessary info for boot, and also your phones drivers.
There's a line in the kernel called "bootclasspath",
and if this isn't what it should be for your device,
you will get a hard brick

Sent from my GT-S5360 Using tapatalk 2

PreSS ThanKs If i HelPeD YoU ?!?
Device using: Galaxy y(GT-S5360)
Rom:Hyperion 8
Ram:512 MB
Processor:1 GHZ maxed out(OVERCLOCKED)
Gpu:Broadcomm(chainfire 3d)
Android Version:2.3.6(GINGERBREAD)
Rooted:Yes

Device using:Galaxy S4(GT-I9500)
Rom:Stock(Touchwiz)
Ram:2 GB
Processor:2 GHZ
Gpu:PowerVR SGX 544MP3
Android Version:4.4(KITKAT)
Rooted:Yes


The Following User Says Thank You to androidrocks23 For This Useful Post: [ Click to Expand ]
 
laith al shishani
Old
#4  
laith al shishani's Avatar
Junior Member
Thanks Meter 14
Posts: 21
Join Date: Feb 2013
Location: Jeddeh
If You Have flashed a wrong rom without a kernel it will not brick but no boot after device photo or something but if you flashed a rom with a kernel its will brick
I tryed it
Sent from my GT-S7500 using xda app-developers app
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes