Android Already In Flash But Still Bootloop

Monday, 21 August 2017

well here amatnewbe will shed some light why youve flashed hp but maih just so / pain. masri we look at the cause.

The first cause of the file ang used.
In the process of flashing files are used very influential matter why? because the file becomes the main ingredient in the process of flashing. if the file being used is damaged then it will not succeed.
The second cause faulty IC EMMC
IC hp EMMC damaged but can still light up just stuck dilogo / bootlop then flashed some kalipun hp it will never recover.

I know that EMMC damaged hp namely by going into recovery mode.

to mode recovery sign in your android and check the following

� if the first entry into an existing cwm failed to mount sdcard writing it has been ascertained but is not too badly damaged

� when flashed the street but once in the midst of tiba2 failed

� tida can update through recovery

Possible Causes IC EMMC Damaged:

# SDS (Sudden Death Syndrome)

# In Charger for too long (more than 3 hours)

# In the Custom Oprek that does not match the original partition

# When Hank / Stuck in the forcibly pull the battery

# And lain2

Possible beginning ic EMMC want broken:

# Occurrence Sorry android acore The process has stopped unexpectedly

# Appears Unfortunately, Force Closes has stoped

# Often Unmount SD / internal unreadable

# Often Hank / Stuck although not many applications and OS Official

# And lain2

SOLUTION only if ic EMMC damaged namely by taking into service to replace the IC EMMCnya.

nah so I can share information. thank you ...

Source: kaskus.com

download file now