Hovatek Forum MOBILE Android sp tools error 5069 !!!
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


sp tools error 5069 !!!

sp tools error 5069 !!!

Pages (2): 1 2 Next
shubhamverma27
shubhamverma27
shubhamverma27
Enthusiastic Member
11
16-01-2015, 07:30 PM
#1



micromax a110q... i am unable to flash it and am getting error 5069 in sp tools ....what should i do...!!!please help!!!
flashing with vol down button or up or power has no effect ...even flashing with/without battery has no effect ...all i get is error 5069 ie no space error...tried full format also!!!
hovatek
hovatek
hovatek
Administrator
49,570
16-01-2015, 09:46 PM
#2
(16-01-2015, 07:30 PM)shubhamverma27 micromax a110q... i am unable to flash it and am getting error 5069 in sp tools ....what should i do...!!!please help!!!
flashing with vol down button or up or power has no effect ...even flashing with/without battery has no effect ...all i get is error 5069 ie no space error...tried full format also!!!

try doing a readback of this very phone using this guide @ https://www.hovatek.com/forum/thread-526.html 

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
shubhamverma27
shubhamverma27
shubhamverma27
Enthusiastic Member
11
17-01-2015, 02:51 PM
#3
(16-01-2015, 09:46 PM)hovatek
(16-01-2015, 07:30 PM)shubhamverma27 micromax a110q... i am unable to flash it and am getting error 5069 in sp tools ....what should i do...!!!please help!!!
flashing with vol down button or up or power has no effect ...even flashing with/without battery has no effect ...all i get is error 5069 ie no space error...tried full format also!!!

try doing a readback of this very phone using this guide @ https://www.hovatek.com/forum/thread-526.html 



my phone is not detected in mtk droid tools...as its not getting switched on!!!

what to do??
hovatek
hovatek
hovatek
Administrator
49,570
17-01-2015, 03:08 PM
#4
(17-01-2015, 02:51 PM)shubhamverma27 my phone is not detected in mtk droid tools...as its not getting switched on!!!

what to do??

the read back uses Sp flash tool not MTK droid tools

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
shubhamverma27
shubhamverma27
shubhamverma27
Enthusiastic Member
11
17-01-2015, 03:48 PM
#5



(17-01-2015, 03:08 PM)hovatek
(17-01-2015, 02:51 PM)shubhamverma27 my phone is not detected in mtk droid tools...as its not getting switched on!!!

what to do??

the read back uses Sp flash tool not MTK droid tools

ok so i did it using sp tools skiping the part of mtk droid tools ...now what to do?
hovatek
hovatek
hovatek
Administrator
49,570
17-01-2015, 06:10 PM
#6
(17-01-2015, 03:48 PM)shubhamverma27 ok so i did it using sp tools skiping the part of mtk droid tools ...now what to do?

was the readback successful? whats the size of the readback file?
This post was last modified: 17-01-2015, 06:16 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
shubhamverma27
shubhamverma27
shubhamverma27
Enthusiastic Member
11
17-01-2015, 08:26 PM
#7
(17-01-2015, 06:10 PM)hovatek
(17-01-2015, 03:48 PM)shubhamverma27 ok so i did it using sp tools skiping the part of mtk droid tools ...now what to do?

was the readback successful? whats the size of the readback file?
the readback was succesful for the boot.img file but for the whole rom the readback stopped at about 48-50% and the phone got automatically disconnected..till this % the size of "rom_1" file is 330mb!!!!
hovatek
hovatek
hovatek
Administrator
49,570
17-01-2015, 08:34 PM
#8
(17-01-2015, 08:26 PM)shubhamverma27 the readback was succesful for the boot.img file but for the whole rom the readback stopped at about 48-50% and the phone got automatically disconnected..till this % the size of "rom_1" file is 330mb!!!!

alright, seems we have a culprit. here's what you'll do. reeadback these one at a time
boot.img
recovery.img
system.img
data.img (userdata)
FAT.img

waiting....

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
shubhamverma27
shubhamverma27
shubhamverma27
Enthusiastic Member
11
17-01-2015, 09:19 PM
#9
(17-01-2015, 08:34 PM)hovatek
(17-01-2015, 08:26 PM)shubhamverma27 the readback was succesful for the boot.img file but for the whole rom the readback stopped at about 48-50% and the phone got automatically disconnected..till this % the size of "rom_1" file is 330mb!!!!

alright, seems we have a culprit. here's what you'll do. reeadback these one at a time
boot.img
recovery.img
system.img
data.img (userdata)
FAT.img

waiting....
ok so how do i do that??
i know the start address but not the length ....also it is too long of a process ...can you help me with it using tamviewer or something???
hovatek
hovatek
hovatek
Administrator
49,570
17-01-2015, 10:17 PM
#10



(17-01-2015, 09:19 PM)shubhamverma27 ok so how do i do that??
i know the start address but not the length ....also it is too long of a process ...can you help me with it using tamviewer or something???

so far you have the blocks map, you'll have the scatter value and size values for each.

the video @ https://www.hovatek.com/forum/thread-526.html explains this clearly

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram