Hi, Guest! Login / Register




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Tecno P5 hard bricked and not detected by SP Flash Tool

#11

(10-26-2014, 08:05 AM)hovatek Wrote:
(10-26-2014, 07:50 AM)codedtee Wrote: I mistakenly hard-bricked the second working P5 last night. I then successfully flashed the MTK backup I did somee minutes earlier and it worked.. Note that while flashing, it brought out the mobile phone's chip info at the bottom left corner of the SP tool. The tool saw the phone on a DA Com port.

I then tried to flash the dead phone with the same procedure and files but it didn't work. It didn't show the chip's info and still gave the error 4032. It saw the phone on MTK Com Port 17.

Am guessing the two phones might not necessarily be the same type even though they are both P5. This is because the dead P5 once got hard-bricked cos it was once flashed by the guys at Carlcare.

What's the next step please..? Thank you.

format the bricked p5 using sp flash tool. Do Not format Bootloader. just a normal format

Did that also overnight but gave me the same Error 4032


Reply
#12
(10-26-2014, 08:09 AM)codedtee Wrote: Did that also overnight but gave me the same Error 4032

what version of sp flash tool did you use?
Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply
#13
(10-26-2014, 08:12 AM)hovatek Wrote:
(10-26-2014, 08:09 AM)codedtee Wrote: Did that also overnight but gave me the same Error 4032

what version of sp flash tool did you use?

5.1352.01
Reply
#14
The HINT is:

Please check your load matches to your target which is to be downloaded.
Reply
#15
(10-26-2014, 08:14 AM)codedtee Wrote: 5.1352.01

try version 3.13 after format. if it's still the same error then you'll need to get p5 new OS since you said it was flashed at carlcare

Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply
#16
(10-26-2014, 08:20 AM)hovatek Wrote:
(10-26-2014, 08:14 AM)codedtee Wrote: 5.1352.01

try version 3.13 after format. if it's still the same error then you'll need to get p5 new OS since you said it was flashed at carlcare

Am guessing something was changed at carlcare. How can I get the new OS?
Reply
#17
(10-26-2014, 08:21 AM)codedtee Wrote: Am guessing something was changed at carlcare. How can I get the new OS?

You'll need to keep scouting for other P5s. for M3, the difference between old OS and new OS lies in the background color of the app drawer and it's design (see pictures @ http://forum.hovatek.com/thread-311.html ). can't say for P5.

Hint: you can try flashing one file at a time. start with system.img (Android) . This should tell you which file exactly is incompatible.
Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply
#18
(10-26-2014, 08:28 AM)hovatek Wrote:
(10-26-2014, 08:21 AM)codedtee Wrote: Am guessing something was changed at carlcare. How can I get the new OS?

You'll need to keep scouting for other P5s. for M3, the difference between old OS and new OS lies in the background color of the app drawer and it's design (see pictures @ http://forum.hovatek.com/thread-311.html ). can't say for P5.

Hint: you can try flashing one file at a time. start with system.img (Android) . This should tell you which file exactly is incompatible.


OK. thanks. Lemme start that now
Reply
#19
Or is there any chance that the scatter file am using won't work for the new OS?
Reply
#20
(10-26-2014, 08:32 AM)codedtee Wrote: Or is there any chance that the scatter file am using won't work for the new OS?

that's another possibility. they might have slightly different block addresses. try the current scatter file first
Need further assistance? Speak with a Hovatek Representative:
Working Hours: Mondays - Saturdays ; 09:00 - 18:00 (GMT +1:00)
Reply










Users browsing this thread:
1 Guest(s)