Unyaffs for the Blade

[Guest fonix232]

After reading through the Racer topic, I am pretty sure it can be done.

So, first of all, I've modified the source code a bit. Yes, SPARE_SIZE 0 what I made, but it won't extract anything (still, but at least the script ends).

If anyone knows a bit more, please share it here so we can get unyaffs working!

[Guest Arr Too]

OK, I'll bite: what are you on about? unyaffs works for me on those Blade things I've tried it on (ROMs and ClockwordMod backups). Do you have a specific example image in mind that's causing problems?

[Guest fonix232]

OK, I'll bite: what are you on about? unyaffs works for me on those Blade things I've tried it on (ROMs and ClockwordMod backups). Do you have a specific example image in mind that's causing problems?

Actually I have. The Hungarian Blade (only 256MB RAM, TFT screen, the chinese version, not the San Francisco) has an almost 220MB huge system.img, what has no SPARE area. It can not be extracted, usual unyaffs segfaults on it, and when I edit the source to have no spare part, it won't extract anything.

[Guest asturel]

this works fine for me (for system+data)

edit: i have hungarian blade too

Edited November 29, 2010 by asturel

[Guest Arr Too]

Build for Cygwin (Windows)

[Guest fonix232]

this works fine for me (for system+data)

edit: i have hungarian blade too

I am using the ZTE_Blade-_-TM_P729TV1.0.0B02-_-Hungarian_T-Mobile.zip package, it's system image returns the following error:

2 [main] unyaffs 5248 exception::handle: Exception: STATUS_ACCESS_VIOLATION

779 [main] unyaffs 5248 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump

Content of stackdump:

Exception: STATUS_ACCESS_VIOLATION at eip=004010A0

eax=1C312600 ebx=00000000 ecx=00000000 edx=00E718DA esi=0022CD34 edi=00000000

ebp=0022CCD8 esp=0022CCA0 program=M:\ZTE Blade\test\unyaffs.exe, pid 5248, thread main

cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023

Stack trace:

Frame	 Function  Args

0022CCD8  004010A0  (0022CD39, 00000000, 611F0108, 00401323)

0022CD08  0040139F  (00000002, 00E58388, 00E58268, 00000001)

0022CD68  61006E73  (00000000, 0022CDA4, 61006720, 7FFDF000)

End of stack trace

And it won't extract.

May you be please so kind to link a firmware you extracted? I've heard that the dd command also returns invalid YAFFS2 image!

Ja és köszi a segítséget, ahogy nézem elég sok magyar van errefelé :P

[Guest asturel]

I am using the ZTE_Blade-_-TM_P729TV1.0.0B02-_-Hungarian_T-Mobile.zip package, it's system image returns the following error:

i used my own nandroid backup, where did u get this?

here is my system.img, (i dont know what u wanna do with this, so i did not extract)

btw.: i deleted/added few things (e.g. hw accel + modified cpu lib for that)

there is (somewehere :P) an another zip, i think (which system is extracted)

[Guest fonix232]

i used my own nandroid backup, where did u get this?

here is my system.img, (i dont know what u wanna do with this, so i did not extract)

btw.: i deleted/added few things (e.g. hw accel + modified cpu lib for that)

there is (somewehere :P) an another zip, i think (which system is extracted)

Thank you.

What I linked is an official flashable version of the T-Mobile HU firmware, that was what I was trying to extract. I will try your files, thank you!

[Guest Sebastian404]

Thank you.

What I linked is an official flashable version of the T-Mobile HU firmware, that was what I was trying to extract. I will try your files, thank you!

The only link I could find with the name ZTE_Blade-_-TM_P729TV1.0.0B02-_-Hungarian_T-Mobile.zip was an VERY unoffical rom that someone on this forum dumped.. you can tell its unofficial since he used clockwork recovery...

the system.img file is only about 83meg...

Where did you get the one your working on?

[Guest fonix232]

The only link I could find with the name ZTE_Blade-_-TM_P729TV1.0.0B02-_-Hungarian_T-Mobile.zip was an VERY unoffical rom that someone on this forum dumped.. you can tell its unofficial since he used clockwork recovery...

the system.img file is only about 83meg...

Where did you get the one your working on?

It's from a Hungarian forum, original link here:

http://www.mediafire.com/?sw76yad8jalmlow

It's said it's an official TMob firmware...

[Guest Arr Too]

OK, I think I understand this now. The system.img you were trying to "unyaffs" has been dumped with "dd" (or similar) rather than "nanddump". This means it is missing all the batches of 64 spare bytes which follow each 2KB chunk of memory in the NAND storage. The YAFFS filesystem uses this for critical information, hence those system.img files are BROKEN and missing data. You may be able to extract bits and pieces, but you're going to have a tough time putting it all back together, I think. That is, you can't just set SPARE_SIZE to 0 and expect it to work at all.

So, the moral of this is that the YAFFS partitions cannot be dumped quickly as an image by simple means (you need something like "nanddump"). The slightly more tedious mechanism of archiving the individual files (using "tar") will work fine, of course. ClockworkMod is probably the best way for most of us to get a system.img file.

[Guest devzor]

OK, I think I understand this now. The system.img you were trying to "unyaffs" has been dumped with "dd" (or similar) rather than "nanddump". This means it is missing all the batches of 64 spare bytes which follow each 2KB chunk of memory in the NAND storage. The YAFFS filesystem uses this for critical information, hence those system.img files are BROKEN and missing data. You may be able to extract bits and pieces, but you're going to have a tough time putting it all back together, I think. That is, you can't just set SPARE_SIZE to 0 and expect it to work at all.

So, the moral of this is that the YAFFS partitions cannot be dumped quickly as an image by simple means (you need something like "nanddump"). The slightly more tedious mechanism of archiving the individual files (using "tar") will work fine, of course. ClockworkMod is probably the best way for most of us to get a system.img file.

Yes, it was me who dumped it with dd. I did not have this knowledge at that time. I made a tar backup of the system partition as well, you can find it at the hungarian thread (might add there's stuff made by universal androot and adfree in that backup, so you need to clean it).

edit: i never said anywhere it's an official rom provided by t-mobile.

Edited December 17, 2010 by devzor