Hi, Guest! Login / Register




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

lenovo s820 hard bricked :(

#1

hi ive got an issue,
my lenovo s820 got bootloop when ota update, so i firmware upgrade it with sp flashtool but get an error BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069).
i decide to try another stock rom for lenovo s820 but still getting that error (have been try 3 different rom).
i frustated, i try to format whole flash without bootloder and my phone cannot power on, cannot charge,but still detected by computer as mediatek usb preload vcom.
when i firmware upgrade appear error "Firmware Upgrade could not be executed without PMT. Please "Download" ONLY first to create PMT on the target!"
when i choose download instead firmware upgrade, appear an error BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069).
so guys how can i revive this phone?
thanks.

Sent from my ASUS_T00N using Hovatek mobile


Reply
#2
(03-11-2015, 12:40 PM)ferson Wrote: hi ive got an issue,
my lenovo s820 got bootloop when ota update, so i firmware upgrade it with sp flashtool but get an error BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069).
i decide to try another  stock rom for lenovo s820 but still getting that error (have been try 3 different rom).
i frustated, i try to format whole flash without bootloder and my phone cannot power on, cannot charge,but still detected by computer as mediatek usb preload vcom.
when i firmware upgrade appear error "Firmware Upgrade could not be executed without PMT. Please "Download" ONLY first to create PMT on the target!"
when i choose download instead firmware upgrade, appear an error BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069).
so guys how can i revive this phone?
thanks.

Sent from my ASUS_T00N using Hovatek mobile

error 5069 is an overlap error. the stock backup from a brand new phone of the same model usually fixes this. lets focus on these 3 ROMs you downloaded. check their sizes to be sure they're not all the same thing from 3 different sources. are they all unique?
Reply
#3
(03-11-2015, 02:34 PM)hovatek Wrote:
(03-11-2015, 12:40 PM)ferson Wrote: hi ive got an issue,
my lenovo s820 got bootloop when ota update, so i firmware upgrade it with sp flashtool but get an error BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069).
i decide to try another  stock rom for lenovo s820 but still getting that error (have been try 3 different rom).
i frustated, i try to format whole flash without bootloder and my phone cannot power on, cannot charge,but still detected by computer as mediatek usb preload vcom.
when i firmware upgrade appear error "Firmware Upgrade could not be executed without PMT. Please "Download" ONLY first to create PMT on the target!"
when i choose download instead firmware upgrade, appear an error BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069).
so guys how can i revive this phone?
thanks.

Sent from my ASUS_T00N using Hovatek mobile

error 5069 is an overlap error. the stock backup from a brand new phone of the same model usually fixes this. lets focus on these 3 ROMs you downloaded. check their sizes to be sure they're not all the same thing from 3 different sources. are they all unique?

where can i find the stock backup for this phone?
the 3 roms ive try to install is official all of it.
first rom is s820_row_s223_150119, which is kitkat and have around 1,7gb size.
the second one i tried is s820_s139_130723 which is jellybean version with around 700mb.
the third one is S820_ROW_S124_140404 jellybean to, with around 600-700mb size.
fyi, even i tried to install just the kernel only its say BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069) to.

Sent from my ASUS_T00N using Hovatek mobile
Reply
#4
(This post was last modified: 03-12-2015, 10:55 AM by hovatek. )
(03-12-2015, 04:25 AM)ferson Wrote: where can i find the stock backup for this phone?
the 3 roms ive try to install is official all of it.
first rom is s820_row_s223_150119, which is kitkat and have around 1,7gb size.
the second one i tried is s820_s139_130723 which is jellybean version with around 700mb.
the third one is S820_ROW_S124_140404 jellybean to, with around 600-700mb size.
fyi, even i tried to install just the kernel only its say BROM ERROR : S_DL_PMT_ERR_NO_SPACE (5069) to.

Sent from my ASUS_T00N using Hovatek mobile

1. what version of Sp flash tool are you using? have you tried at least 5 different versions?
2. Have you uninstalled vcom drivers and re-intalled using this guide @ https://forum.hovatek.com/thread-440.html ?
Reply
#5
[/quote]

1. what version of Sp flash tool are you using? have you tried at least 5 different versions?
2. Have you uninstalled vcom drivers and re-intalled using this guide @ https://forum.hovatek.com/thread-440.html ?
[/quote]

1.i have already try 4 different sp flash tool, each rom that i downloaded include their own version of flashtool, the last sp flash tool that i tried is the latest one.
2. already using that guide,but the error still showing.
Reply
#6
lets stick to the ROM with the least size. Are you able to flash any single file at all using sp flash tool
Reply
#7
(03-12-2015, 03:55 PM)hovatek Wrote: lets stick to the ROM with the least size. Are you able to flash any single file at all using sp flash tool

as i said before, with the least size rom i even cant flash preloader and kernel only,
its keep saying error 5069
Reply
#8
(03-12-2015, 06:03 PM)ferson Wrote: as i said before, with the least size rom i even cant flash preloader and kernel only,
its keep saying error 5069

if im not mistaken, you mean you cant even flash a single file on any of the ROMs?
Reply
#9
[/quote]
if im not mistaken, you mean you cant even flash a single file on any of the ROMs?
[/quote]

yes, cant flash any single file of the rom, except preloader only.
but its not make change anything to my phone, its still cant boot up.


Sent from my ASUS_T00N using Hovatek mobile
Reply
#10
(This post was last modified: 10-14-2016, 10:56 AM by hovatek. )
As hard as this might sound, you would want to try another ROM for your exact model. error 5069 is one of the most stubborn SP flash tool errors i've encountered and in the cases where it got fixed, it was one particular ROM (after trying many for the same model) that fixed it. In some cases, it was the stock backup of a brand new phone of the same model.
The emmc chip might be damaged
Reply










Users browsing this thread:
1 Guest(s)