Hovatek Forum MOBILE Android HELP! Bricked Lenovo P780
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


HELP! Bricked Lenovo P780

HELP! Bricked Lenovo P780

Pages (3): 1 2 3 Next
dan
dan
dan
Junior Member
21
03-07-2015, 11:52 PM
#1



I have a bricked Lenovo P780 phone that was still in boot loop till few days ago until 

I flashed the wrong prelaoder and fed up the phone - it won't turn on anymore but
is still detected on PC

I have 100% the correct ROM as I was able to format and flash the preloader but none of the other files in that ROM (I am always getting BROM ERROR 5069 NO SPACE)

So I ran a memory test and here's the results:

============ Memory Detection Report ===========
 
Internal RAM:
 
 
External RAM:
 
Type = DRAM
 
Size = 0x40000000 (1024MB/8192Mb)
 
NAND Flash:
 
ERROR: NAND Flash was not detected!
 
EMMC:
 
EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000200000(2MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e7000000(3696MB)
 
============ RAM Test ============
 
Data Bus Test:
 
[D0]
[D1]
[D2]
[D3]
[D4]
[D5]
[D6]
[D7]
[D8]
[D9]
[D10]
[D11]
[D12]
[D13]
[D14]
[D15]
[D16]
[D17]
[D18]
[D19]
[D20]
[D21]
[D22]
[D23]
[D24]
[D25]
[D26]
[D27]
[D28]
[D29]
[D30]
[D31]
OK!!
 
Address Bus Test:
 
[A1]
[A2]
[A3]
[A4]
[A5]
[A6]
[A7]
[A8]
[A9]
[A10]
[A11]
[A12]
[A13]
[A14]
[A15]
[A16]
[A17]
[A18]
[A19]
[A20]
[A21]
[A22]
[A23]
[A24]
[A25]
[A26]
[A27]
[A28]
[A29]
OK!!
 
RAM Pattern Test :
Writing ...
0x44332211,
0xA5A5A5A5,
0xA5A5A500,
0xA500A500,
0xA5000000,
0x00000000,
0xFFFF0000,
0xFFFFFFFF,
OK!!
 
Increment/Decrement Test:
Writing...
OK!!
 
============ EMMC Test ============
 
EMMC Pattern Test(0x5A5A):
 
The memory is full despite that I wiped all data and cache and went through the factory reset back when the phone was still in boot loop so the data should have been wiped already not sure why it is still full

So I realize I was always getting the 5069 NO SPACE error because SPFT couldn't write the ROM files to the phone as there was insufficient space on the device

The second problem I encounter is that the ERROR: NAND Flash was not detected! not sure what it means

I tried flashing with these SP versions 3.1304  3.1316  5.1348  5.1516 and all gave me the same error 5069 no space

So I now know for sure the problem is about the memory that is still full

How do I wipe the data from the phone? (I have no access to recovery mode since the phone won't turn on - it's BRICKED)
hovatek
hovatek
hovatek
Administrator
49,570
04-07-2015, 01:23 PM
#2
(03-07-2015, 11:52 PM)dan How do I wipe the data from the phone? (I have no access to recovery mode since the phone won't turn on - it's BRICKED)

your own case of the error 5069 is likely due a partition overlap. might be a fried eMMC chip though
1. do you still have the wrong scatter file and preloader.bin you flashed?
2. have you tried formatting the phone using the new ROM?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
dan
dan
dan
Junior Member
21
04-07-2015, 01:51 PM
#3
Yes that is exactly what a friend of mine told me, that it has something to do with the partitions and that the "nand flash" thing is fried, and I highly doubted it so I had to ask here
Then now it is likely indeed that the chip is fried and/or the partitions are gone/inaccessible

1. I flashed a few ROMs but I clearly remember where I downloaded the first one then yes I can get those 2 files
2. yes I have formatted the phone using the new ROM but the only things I can do with that ROM is "flash whole format" and flash the preloader that came with it - I'm unable to flash any of the other files because it will always give me that 5069 no space error

One question:
EMMC_PART_USER Size = 0x00000000e7000000(3696MB)
Does this mean the memory capacity of the phone? Or is it the amount of memory currently in use? (I'm not sure if the memory is full or empty)
This post was last modified: 04-07-2015, 03:29 PM by dan.
hovatek
hovatek
hovatek
Administrator
49,570
04-07-2015, 05:42 PM
#4
(04-07-2015, 01:51 PM)dan One question:
EMMC_PART_USER Size = 0x00000000e7000000(3696MB)
Does this mean the memory capacity of the phone? Or is it the amount of memory currently in use? (I'm not sure if the memory is full or empty)
thats not what it means
its just a partition block and your output seems fine. here's part of an emmc test result from a perfectly working phone
its a 512MB RAM 4GB ROM phone
I'll highlight some parts in blue so you compare to yours

============ Memory Detection Report ===========

Internal RAM:

Size = 0x00020000 (128KB)

External RAM:

Type = DRAM

Size = 0x20000000 (512MB/4096Mb)

NAND Flash:

ERROR: NAND Flash was not detected!

EMMC:

EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000020000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000000e2c00000(3628MB)

============ RAM Test ============

Data Bus Test:

[D0]
[D1]
[D2]
[D3]
[D4]
[D5]
[D6]
[D7]
[D8]
[D9]
[D10]
[D11]
[D12]
[D13]
[D14]
[D15]
[D16]
[D17]
[D18]
[D19]
[D20]
[D21]
[D22]
[D23]
[D24]
[D25]
[D26]
[D27]
[D28]
[D29]
[D30]
[D31]
OK!!

Address Bus Test:

[A1]
[A2]
[A3]
[A4]
[A5]
[A6]
[A7]
[A8]
[A9]
[A10]
[A11]
[A12]
[A13]
[A14]
[A15]
[A16]
[A17]
[A18]
[A19]
[A20]
[A21]
[A22]
[A23]
[A24]
[A25]
[A26]
[A27]
[A28]
OK!!

RAM Pattern Test :
Writing ...
OK!!

Increment/Decrement Test:
Writing...
OK!!

============ NAND Test ============

SKIP! NAND Flash was not detected!
This post was last modified: 04-07-2015, 05:49 PM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
hovatek
hovatek
hovatek
Administrator
49,570
04-07-2015, 05:46 PM
#5



Yours uses eMMC, not Nand so you cant expect to have a Nand detection
the error 5069 points at a crashed eMMC or an overlap.
we're currently looking at the possibility of a preloader.bin + scatter file Mod fixing the error 5069

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
dan
dan
dan
Junior Member
21
04-07-2015, 08:02 PM
#6
(04-07-2015, 05:46 PM)hovatek Yours uses eMMC, not Nand so you cant expect to have a Nand detection
the error 5069 points at a crashed eMMC or an overlap.
we're currently looking at the possibility of a preloader.bin + scatter file Mod fixing the error 5069

I always thought I had a fried Nand and now it turns out my phone doesn't use Nand but eMMC so yes that makes a lot of sense that the test was perfectly normal except for possibly crashed eMMC (how do I know for sure whether it is fried or just a partition overlap?)
I wonder if you have an estimate when there would be a preloader.bin + scatter file Mod to fix the 5069 problem?
Can I keep on trying different ROMs in the meantime or do I already have the correct ROM? (given I was able to flash the preloader from it)
This post was last modified: 04-07-2015, 08:16 PM by dan.
dan
dan
dan
Junior Member
21
04-07-2015, 10:29 PM
#7
(04-07-2015, 05:46 PM)hovatek Yours uses eMMC, not Nand so you cant expect to have a Nand detection
the error 5069 points at a crashed eMMC or an overlap.
we're currently looking at the possibility of a preloader.bin + scatter file Mod fixing the error 5069

One more question, I read on other threads that you replied the possible causes of the 5069 error could be:

1. not installing the correct drivers  -  given I Was able to flash the preloader from a few roms (but not the other files) then is it still a possibility that I have the wrong drivers? Or do I already have the correct drivers?
2. using an incompatible ROM - if I was able to flash the preloader from a few roms, then those roms are compatible? 
3. emmc / nand crash  - if the answer to the above two questions is yes (have the correct drivers and rom) then the only reason I am getting 5069 is a fried emmc chip?
hovatek
hovatek
hovatek
Administrator
49,570
05-07-2015, 12:19 PM
#8
(04-07-2015, 08:02 PM)dan I always thought I had a fried Nand and now it turns out my phone doesn't use Nand but eMMC so yes that makes a lot of sense that the test was perfectly normal except for possibly crashed eMMC (how do I know for sure whether it is fried or just a partition overlap?)
I wonder if you have an estimate when there would be a preloader.bin + scatter file Mod to fix the 5069 problem?
Can I keep on trying different ROMs in the meantime or do I already have the correct ROM? (given I was able to flash the preloader from it)

keep trying different methods mean for your exact model, not for other models.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
hovatek
hovatek
hovatek
Administrator
49,570
05-07-2015, 12:28 PM
#9
(04-07-2015, 10:29 PM)dan One more question, I read on other threads that you replied the possible causes of the 5069 error could be:

1. not installing the correct drivers  -  given I Was able to flash the preloader from a few roms (but not the other files) then is it still a possibility that I have the wrong drivers? Or do I already have the correct drivers?
2. using an incompatible ROM - if I was able to flash the preloader from a few roms, then those roms are compatible? 
3. emmc / nand crash  - if the answer to the above two questions is yes (have the correct drivers and rom) then the only reason I am getting 5069 is a fried emmc chip?

the error 5069 is a region size mismatch

1 and 2 are the same thing, just in two forms
case 1: if you install an incompatible driver then the information SP flash tool will get from the installed driver will be different from what it gets from the phone/ROM. Mismatch!
case 2: If you use an incomatible ROM then the scatter file / preloader info will be different from the phone's info. Mismatch!

if the driver , ROM and phone info match but the place to flash the files to on the phone's storage is crashed (eMMC in your case) . Mismatch due to No space!

we're still researching it ATM as I earlier mentioned.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
dan
dan
dan
Junior Member
21
08-07-2015, 12:28 AM
#10



(05-07-2015, 12:28 PM)hovatek
(04-07-2015, 10:29 PM)dan One more question, I read on other threads that you replied the possible causes of the 5069 error could be:

1. not installing the correct drivers  -  given I Was able to flash the preloader from a few roms (but not the other files) then is it still a possibility that I have the wrong drivers? Or do I already have the correct drivers?
2. using an incompatible ROM - if I was able to flash the preloader from a few roms, then those roms are compatible? 
3. emmc / nand crash  - if the answer to the above two questions is yes (have the correct drivers and rom) then the only reason I am getting 5069 is a fried emmc chip?

the error 5069 is a region size mismatch

1 and 2 are the same thing, just in two forms
case 1: if you install an incompatible driver then the information SP flash tool will get from the installed driver will be different from what it gets from the phone/ROM. Mismatch!
case 2: If you use an incomatible ROM then the scatter file / preloader info will be different from the phone's info. Mismatch!

if the driver , ROM and phone info match but the place to flash the files to on the phone's  storage is crashed (eMMC in your case) . Mismatch due to No space!

we're still researching it ATM as I earlier mentioned.

Thank you very much for the info and the apologies for the dealy in response, I have some followup:
I took my cousin's idential, working P780 (his and mine are the exact same, bought from same place, both have the exact same rom and everything) and backed up the rom from his device, tried to flash it in spft to my dead device and again the same 5069 error

I also tried to flash from my brother's xp system where I installed 100% the correct drivers, his pc recognizes my dead phone and i was able to flash the preloader from there too, but still 5069 for the other files

with this new information, I'm now certain that:
- it isnt the spft version, i tried many versions and all breed the exact same error
- it isnt the rom since i now have the exact same factory stock rom i had on my phone when i first got it
- it could only be a fried chip or partition overlap?

one more update, I ran the memory test, now just for the emmc, and here's the results:

Internal RAM: Size = 0x00020000 (128KB)
 
External RAM: Type = DRAM
 
     Size = 0x40000000 (1024MB/8192Mb)
 
NAND Flash:   ERROR: NAND Flash was not detected!
 
EMMC :     EMMC_PART_BOOT1   Size = 0x0000000000200000(2MB)
      EMMC_PART_BOOT2   Size = 0x0000000000200000(2MB)
      EMMC_PART_RPMB    Size = 0x0000000000200000(2MB)
      EMMC_PART_GP1     Size = 0x0000000000000000(0MB)
      EMMC_PART_GP2     Size = 0x0000000000000000(0MB)
      EMMC_PART_GP3     Size = 0x0000000000000000(0MB)
      EMMC_PART_GP4     Size = 0x0000000000000000(0MB)
      EMMC_PART_USER    Size = 0x00000000E7000000(3696MB)
 
============       EMMC Test         ============
 
EMMC Pattern Test(0x5A5A):
 
FAILED!!
 
 does this mean my emmc is dead, or not necessarily?

is there any chance i can still manage to flash by modding some files in the rom? if yes what file do i need to edit and what to edit in there? or there's any way to fix the partition overlap? (if there is one)

unsure if it helps but I added a few screenshots
1 - shows the error 3149 i get when i run memory test for emmc
2 - shows the files i am trying to flash (the rom backup from my cousin's working p780)
3 - shows "download ok" when i flashed preloader
4 - shows "format ok" when i "format whole flash except bootloader"
5 - shows the 5069 error when i flash other files
6 - when i place the mouse cursor at the bottom of flash tool it shows this data including the emmc details - this means it recognizes the emmc? then the emmc isnt fried? (or is it fried but the spft still detects it?)

in case the emmc isnt fried, then the only option left is partitions overlap i guess - any way we can possibly fix it?
This post was last modified: 08-07-2015, 01:13 AM by dan.
Attached Files
.jpg
1.jpg
Size: 312.58 KB / Downloads: 7
.jpg
2.jpg
Size: 191.31 KB / Downloads: 6
.jpg
3.jpg
Size: 422.59 KB / Downloads: 10
.jpg
4.jpg
Size: 415.38 KB / Downloads: 8
.jpg
5.jpg
Size: 369.16 KB / Downloads: 9
.png
6.png
Size: 160.63 KB / Downloads: 40
Pages (3): 1 2 3 Next
Users browsing this thread:
 2 Guest(s)
Users browsing this thread:
 2 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram