Hovatek Forum MOBILE Android [Downloads] x556 bricked
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


[Downloads] x556 bricked

[Downloads] x556 bricked

Pages (3): Previous 1 2 3
Nengbani
Nengbani
Nengbani
Junior Member
21
08-03-2018, 06:16 PM
#21



(08-03-2018, 05:47 PM)nijazxp Your first screenshot should be of inside that file (when you double click on that file to the right), you showed only outside.
Finally show screenshot of how spflashtool looks like when you load that (for your build) scatter, before flashing anything. Maximize window fullscreen.
Your V70 and V133 scatters are same, but different from your build scatter, i checked now.

ok. just upload new screenshot now.
Attached Files
.jpg
spflashtooscrsht.jpg
Size: 339.3 KB / Downloads: 5
.jpg
newscrshtforext2expl.jpg
Size: 117.7 KB / Downloads: 2
nijazxp
nijazxp
nijazxp
Techie Member
55
08-03-2018, 06:29 PM
#22
I think problem is in your spflashtool version. Scatter file and flash files are OK. Download version 5.1532 and flash using it.
You'll notice this is newest version that doesn't have "authentication file" box above.
https://spflashtools.com/windows/sp-flash-tool-v5-1532
This post was last modified: 08-03-2018, 06:33 PM by nijazxp.
Nengbani
Nengbani
Nengbani
Junior Member
21
08-03-2018, 07:37 PM
#23
(08-03-2018, 06:29 PM)nijazxp I think problem is in your spflashtool version. Scatter file and flash files are OK. Download version 5.1532 and flash using it.
You'll notice this is newest version that doesn't have "authentication file" box above.
https://spflashtools.com/windows/sp-flash-tool-v5-1532

i receive an error will loading the scatter file in the version of sp-flashtool i just downloaded. i upload the screenshot.
Attached Files
.jpg
spflashtoolerrorscrsht.jpg
Size: 143.84 KB / Downloads: 4
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.
nijazxp
nijazxp
nijazxp
Techie Member
55
08-03-2018, 11:28 PM
#25



And maybe as last desparate measure, let's call it METHOD5, try repeating METHOD3, but when that two files from extra folder are inside main folder instead those already present. Tell us results. Hope some method will work.

And as METHOD6, try same as METHOD5 but with original (one you downloaded yesterday) scatter file, meaning one without removed zero.
This post was last modified: 08-03-2018, 11:31 PM by nijazxp.
Nengbani
Nengbani
Nengbani
Junior Member
21
09-03-2018, 03:11 PM
#26
(08-03-2018, 10:46 PM)nijazxp 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:

once again i must appreciate you for your effort and dedication, thanks a lot.
Method 1: i did'nt receive that error again, the file upload successfully in the sp_flash tool version 5.1532 but,  the phone will not flash an error popup saying "the scatter file is invalid"

Method 2 and 3: the phone will flash but, will not charge neither will it power (same).
method 4: did not work.
 what i'm suggesting is that, if i can get a backup rom of a similar phone i think and i hope it will work.
thanks. waiting in anticipation.
hovatek
hovatek
hovatek
Administrator
49,570
10-03-2018, 10:57 AM
#27
(09-03-2018, 03:11 PM)Nengbani once again i must appreciate you for your effort and dedication, thanks a lot.
Method 1: i did'nt receive that error again, the file upload successfully in the sp_flash tool version 5.1532 but,  the phone will not flash an error popup saying "the scatter file is invalid"

Method 2 and 3: the phone will flash but, will not charge neither will it power (same).
method 4: did not work.
 what i'm suggesting is that, if i can get a backup rom of a similar phone i think and i hope it will work.
thanks. waiting in anticipation.

You could keep searching for someone with a working phone of this Build number.
Three things we need to consider
1. Emmc issue
2. Power issue
3. X556-H371A1-M-170119V136 is not the original build number

Lets run a few tests.
1. How exactly did the phone get bricked in the first place?
2. For Power issue, have you tried taking out and reconnecting the battery?
3. Follow the guide at https://www.hovatek.com/forum/thread-21970.html and do a full dump of the phone' firmware. Lets see a screenshot of the processed rom folder (list view so we can see details)

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Nengbani
Nengbani
Nengbani
Junior Member
21
10-03-2018, 06:51 PM
#28
(10-03-2018, 10:57 AM)hovatek
(09-03-2018, 03:11 PM)Nengbani once again i must appreciate you for your effort and dedication, thanks a lot.
Method 1: i did'nt receive that error again, the file upload successfully in the sp_flash tool version 5.1532 but,  the phone will not flash an error popup saying "the scatter file is invalid"

Method 2 and 3: the phone will flash but, will not charge neither will it power (same).
method 4: did not work.
 what i'm suggesting is that, if i can get a backup rom of a similar phone i think and i hope it will work.
thanks. waiting in anticipation.

You could keep searching for someone with a working phone of this Build number.
Three things we need to consider
1. Emmc issue
2. Power issue
3. X556-H371A1-M-170119V136 is not the original build number

Lets run a few tests.
1. How exactly did the phone get bricked in the first place?
2. For Power issue, have you tried taking out and reconnecting the battery?
3. Follow the guide at https://www.hovatek.com/forum/thread-21970.html  and do a full dump of the phone' firmware. Lets see a screenshot of the processed rom folder (list view so we can see details)

1. the phone just hang in booting. if power on, the phone will show XOS and will not boot. after flashing the phone, the phone get bricked. the phone was flash with rom downloaded from  romkingz and that is how it goes.
2. yes. i have unplug and plug the battery.
3. no phone to use for rom backup
X3non
X3non
X3non
Recognized Contributor
22,062
10-03-2018, 08:31 PM
#29
(10-03-2018, 06:51 PM)Nengbani 1. the phone just hang in booting. if power on, the phone will show XOS and will not boot. after flashing the phone, the phone get bricked. the phone was flash with rom downloaded from  romkingz and that is how it goes.
2. yes. i have unplug and plug the battery.
3. no phone to use for rom backup

after flashing the rom from romkingz, did the phone go totally dead or just stuck at bootlogo?
if it was stuck at bootlogo, then try reflashing it and lets know if the phone goes from been totally dead back to been stuck at bootlogo
Pages (3): Previous 1 2 3
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram