FORUMS
Remove All Ads from XDA

Discussion thread for /data EMMC lockup/corruption bug

5,342 posts
Thanks Meter: 7,242
 
By sfhub, Senior Member on 9th May 2012, 01:08 PM
Post Reply Email Thread
9th March 2015, 04:14 PM |#981  
UPdownLoAD's Avatar
Senior Member
Thanks Meter: 235
 
More
Have you tried another cable? I swear I've had that error before back in the days of my Epic and it was cured by using a different cable.
 
 
9th March 2015, 05:33 PM |#982  
garwynn's Avatar
Retired Forum Moderator / Inactive Recognized Developer / XDA Portal Team
Flag NE Ohio
Thanks Meter: 8,731
 
Donate to Me
More
Quote:
Originally Posted by vov120

It fails during boot.bin flashing.
I tried also with Heimdall, but with near the same result.
Heimdall is able to read PIT but at the end reports:
Ending session...
ERROR: Failed to receive session end confirmation!

Looks as if at the end of session SBL tries to write something into NAND and fails.

I've read somewhere that as result of "superbrick" bug, just some blocks of flash get corrupted/unavailable.
I count on that JTAG dump will contain most of 16GB data valid.
It's the main reason why I asked if it's possible to use JTAG to read flash dump of "superbrick"-ed phone.
Does it sound reasonable?

Absolutely sounds reasonable, but let's make sure that's the problem you're facing first.
If it were indeed the brick bug, the phone would just freeze and require a battery pull... Both on boot error and download.
If you're not seeing that in both cases - that's not it.

Can you send me the Odin flash log next time you try? And definitely consider a different cable as suggested.
We can also try flashing individual images to see if we can get recovery, system or userdata to take.
9th March 2015, 07:16 PM |#983  
Lanchon's Avatar
Senior Member
Thanks Meter: 4,424
 
Donate to Me
More
Quote:
Originally Posted by vov120

It fails during boot.bin flashing.
I tried also with Heimdall, but with near the same result.
Heimdall is able to read PIT but at the end reports:
Ending session...
ERROR: Failed to receive session end confirmation!

Looks as if at the end of session SBL tries to write something into NAND and fails.

I've read somewhere that as result of "superbrick" bug, just some blocks of flash get corrupted/unavailable.
I count on that JTAG dump will contain most of 16GB data valid.
It's the main reason why I asked if it's possible to use JTAG to read flash dump of "superbrick"-ed phone.
Does it sound reasonable?

it can require some extra work. as i already said, the emmc could stop responding while reading some areas, JTAG or not. if that happens, it would require the operator to power cycle the phone, skip a guessed number of sectors, and continue dumping. you could also read backwards from the end, or just some partitions.

the point is that it may misbehave, and the operator has to want to do something about it and not just call it quits.

i9100 emmcs are known to fail from time to time. this has nothing to do with brickbug. brickbug is a bug in the implementations of the secure erase and secure trim emmc commands, and your OS never issued those. this is just a random failure.

i have talked to people with similar malfunctions out of the blue.

i have (remotely) tried two things:

1) i made custom PIT files that relocated the boot (kernel+recovery) partition to the area in the HIDDEN (ie: preload) partition (new end of storage) and also another near the beginning. the idea was to flash the PIT, then flash a kernel, then boot into recovery and dump the data. or repartition to skip the damaged area. or attempt a full emmc reset.

it didnt work. the emmc was locked in read only mode (the emmc firmware seemingly detected an unrecoverable problem and boot into that mode to let you at least read out the contents... say via JTAG). but i encourage you to google that xda thread and try the approach, it might work for you.

2) in another case, the emmc was read only too, but he was able to enter recovery. we attempted a full emmc reset (resize of the special bootloader partitions). this would have cured the emmc of damage caused by brickbug but is very dangerous because the bootloader is also wiped. if something goes wrong before you rewrite the BL, you need JTAG to recover.

it didnt work. the reset was totally ignored by the read-only emmc. curiously enough, the PIT flashing itself worked. and im willing to bet that flashes to the BL areas could have worked too. these areas of the emmc are treated in a more robust fashion and dont get handled by the same 'general' FTL in the emmc (which is what gets corrupted in these failed emmcs, i presume). you can google this thread if your are curious but you can't attempt this.

so there are your options. JTAG might fully work. if the emmc hangs, it would be better if you did the JTAGging yourself to avoid the problematic areas.
9th March 2015, 07:19 PM |#984  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by garwynn

Can you send me the Odin flash log next time you try

<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!

In the past I tried it with different cables, usb ports, Odin versions (1.83 - 3.09) and even another PC.
I don't want to try to repartition the flash (at least meantime) as my main purpose is to retrieve the user data.
9th March 2015, 09:43 PM |#985  
Junior Member
Thanks Meter: 0
 
More
Regarding the second case:
Quote:
Originally Posted by Lanchon

the reset was totally ignored by the read-only emmc. curiously enough, the PIT flashing itself worked

when new PIT was flashed, didn't you try to flash kernel etc. in the new partitions?
After I finish with data recovery, if my emmc is writable, I probably will play with custom PIT's to get kernel working and when run bad block scanner.
10th March 2015, 02:29 AM |#986  
Lanchon's Avatar
Senior Member
Thanks Meter: 4,424
 
Donate to Me
More
Quote:
Originally Posted by vov120

Regarding the second case:

when new PIT was flashed, didn't you try to flash kernel etc. in the new partitions?
After I finish with data recovery, if my emmc is writable, I probably will play with custom PIT's to get kernel working and when run bad block scanner.

fair. good luck with that. take care
1st December 2016, 01:09 PM |#987  
@anonymous94's Avatar
Senior Member
Thanks Meter: 26
 
More
How to fix hanging issue even in stock after wiping everything, phone keeps freezing and force close.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes