Hovatek Forum MOBILE Android [Downloads] x556 bricked
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


[Downloads] x556 bricked

[Downloads] x556 bricked

nijazxp
nijazxp
nijazxp
Techie Member
55
08-03-2018, 10:46 PM
#24
First backup these files as said in bottom of text, below 4 methods, do not make mistake in copying text! Then try these methods one by one, also best to go to your current scatter file and turn off cache and data flashing either by removing them (these group of texts) or changing word true to false. Like this: "is_download: true" to "is_download: false", under groups of text userdata and cache! They don't affect bootloop/broken phone, and will waste your time trying to flash, even system partition takes already much time, but system is important.
WHEN USING ANY METHOD, USE FORMAT ALL + FLASH OPTION.

Also just to verify your version of spflashtool won't be responsible for errors, do this. Download hashmyfiles from nirsoft.net. Then in your version of spflashtool flash only boot.img (unselect all others) and then after that do readback with this data:
start address: 0x1D80000
length: 0x1000000
region: EMMC_USER
file: boot2

Now compare it with hashmyfiles, just open that file and your normal boot.img you flashed. If you see same hashes, or much more simply same number in "identical" tab when you scroll to the right, then everything is ok. Otherwise you can't use your version of spflashtool.

METHOD 1:
That error is because of text "MT6737M" as "platform:" in scatter file. I noticed your and mine phone has almost same data here. So..
Maybe try changing that text to MT6582. It simply means that version is incompatible with your phone, although our phones have similar scatter.
If more errors appear after that, give up, it's not worth it.
Flash using spflashtool 5.1532.
Tell us results.

METHOD2:
Change this data in your scatter file: partition_size: 0x400000 to partition_size: 0x40000 under group of text for preloader.
Meaning just remove one zero. This was only difference in scatter file for your build and two you flashed before, so maybe mistake is here.
Flash using your spflashtool you used before.
Tell us results.

METHOD3:
Same as method 2. Just this time use file method3.txt as your scatter file, put it in same folder where your normal (one you edited in method2) scatter file and flash files are, i uploaded.

METHOD4:
Maybe your power on key is dead/broken inside. That happens to me randomly. It works always when i push paper between that key and plastic from display side, meaning parallel to length. You can try from opossite of display side too. Then you can pull paper when you no longer need to test this. Push it as hard as possible to be sure it will work. This is obviously last desparate step. If none of methods work then nobody can help you. Then it means whoever uploaded that firmware gave dead files.

Best before you try that, using your normal spflashtool, backup (readback) these partitions (enter these data in these feilds, 1st group below is just template):

start address
length
region
file

0x0
0x80000
EMMC_USER
pgpt

0x80000
0x300000
EMMC_USER
proinfo

0x380000
0x500000
EMMC_USER
nvram

0x880000
0xA00000
EMMC_USER
protect1

0x1280000
0xA00000
EMMC_USER
protect2

0x1D00000
0x80000
EMMC_USER
para

0x4580000
0xA00000
EMMC_USER
expdb

0x4F80000
0x80000
EMMC_USER
seccfg

0x5000000
0x200000
EMMC_USER
oemkeystore

0x5800000
0x800000
EMMC_USER
keystore

0x6A00000
0x100000
EMMC_USER
frp

0x6B00000
0x2000000
EMMC_USER
nvdata

0x8B00000
0x2500000
EMMC_USER
metadata

0xFFFF0084
0x1000000
EMMC_USER
flashinfo

0xFFFF0004
0x80000
EMMC_USER
sgpt

Then save all these files in some zip or rar file and keep your backup like that. Add this scatter file (full scatter.txt) to that backup files which will allow you to restore backup if ever needed:
This post was last modified: 08-03-2018, 11:24 PM by nijazxp.

Messages In This Thread
x556 bricked - by Nengbani - 07-03-2018, 08:46 AM
RE: x556 bricked - by hovatek - 07-03-2018, 12:58 PM
RE: x556 bricked - by Nengbani - 07-03-2018, 02:15 PM
RE: x556 bricked - by X3non - 07-03-2018, 05:36 PM
RE: x556 bricked - by Nengbani - 07-03-2018, 10:25 PM
RE: x556 bricked - by nijazxp - 07-03-2018, 06:06 PM
RE: x556 bricked - by nijazxp - 08-03-2018, 12:00 AM
RE: x556 bricked - by Nengbani - 08-03-2018, 01:15 AM
RE: x556 bricked - by nijazxp - 08-03-2018, 01:33 AM
RE: x556 bricked - by Nengbani - 08-03-2018, 01:52 AM
RE: x556 bricked - by nijazxp - 08-03-2018, 02:19 AM
RE: x556 bricked - by Nengbani - 08-03-2018, 03:01 AM
RE: x556 bricked - by hovatek - 08-03-2018, 10:16 AM
RE: x556 bricked - by Nengbani - 08-03-2018, 12:26 PM
RE: x556 bricked - by nijazxp - 08-03-2018, 01:05 PM
RE: x556 bricked - by Nengbani - 08-03-2018, 02:16 PM
RE: x556 bricked - by nijazxp - 08-03-2018, 03:07 PM
RE: x556 bricked - by Nengbani - 08-03-2018, 05:17 PM
RE: x556 bricked - by nijazxp - 08-03-2018, 05:47 PM
RE: x556 bricked - by Nengbani - 08-03-2018, 06:16 PM
RE: x556 bricked - by nijazxp - 08-03-2018, 06:29 PM
RE: x556 bricked - by Nengbani - 08-03-2018, 07:37 PM
RE: x556 bricked - by X3non - 08-03-2018, 04:48 PM
RE: x556 bricked - by nijazxp - 08-03-2018, 10:46 PM
RE: x556 bricked - by Nengbani - 09-03-2018, 03:11 PM
RE: x556 bricked - by hovatek - 10-03-2018, 10:57 AM
RE: x556 bricked - by Nengbani - 10-03-2018, 06:51 PM
RE: x556 bricked - by X3non - 10-03-2018, 08:31 PM
RE: x556 bricked - by nijazxp - 08-03-2018, 11:28 PM
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram