NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[guruvince]

In regards to bricking ones device, the late Maurice.Green stated "I have basically been trying to brick my device. I would like for a brave soul to verify my findings. If the device seems to bricked or stuck in a loop. Deplete the battery. Remove the battery and the usb power source. Put a RHODIMG.NBH image on the sdcard. Put the SD card in the card slot. Put the dead battery back into the phone. Plug the usb power cord back in to the phone. The charging led will come on. Let it sit for 10 mins the first time and it will try to load. Don't mess with the phone. It will recycle and try to boot again in about 5 min. When it try's to reboot hold down the volume down button, the power button and push the reset. This will bring you to the boot loader. Very quickly flash the NBH on the sdcard to the phone. The phone will cycle about 5 times before coming up completely. Let the battery fully charge and you are back in business."
Whether this works or not, who knows?

[[ACL]]

Originally Posted by guruvince

In regards to bricking ones device, the late Maurice.Green stated "I have basically been trying to brick my device. I would like for a brave soul to verify my findings. If the device seems to bricked or stuck in a loop. Deplete the battery. Remove the battery and the usb power source. Put a RHODIMG.NBH image on the sdcard. Put the SD card in the card slot. Put the dead battery back into the phone. Plug the usb power cord back in to the phone. The charging led will come on. Let it sit for 10 mins the first time and it will try to load. Don't mess with the phone. It will recycle and try to boot again in about 5 min. When it try's to reboot hold down the volume down button, the power button and push the reset. This will bring you to the boot loader. Very quickly flash the NBH on the sdcard to the phone. The phone will cycle about 5 times before coming up completely. Let the battery fully charge and you are back in business."
Whether this works or not, who knows?

lol.. well after witnessing wozzer's bricking i dont wanna take chances. But i will try to write the roofs onto nand first. I'm trying to make sure i write to a safe spot. I dumped nand yesterday even with those errors but the image itself appears to be good. Not really sure at this point.

But if anyone wants to beging making test images, i guess we can start bricking :-p

[natemcnutty]

Originally Posted by [ACL]

lol.. well after witnessing wozzer's bricking i dont wanna take chances. But i will try to write the roofs onto nand first. I'm trying to make sure i write to a safe spot. I dumped nand yesterday even with those errors but the image itself appears to be good. Not really sure at this point.

But if anyone wants to beging making test images, i guess we can start bricking :-p

ACL, I broke apart every single stock ROM for US carriers as well as a bunch of custom ROMs. The zip file I uploaded only contains some of those, but you will notice that the partition tables varied slightly on the 2nd - 4th partitions. I think something like this would be safe compared to all of the custom WinMo ROM's:

0x01C0 - Usually contains ULDR (boot)
Start Address: 0x00000002
End Address: 0x0000063F

0x01D0 - Usually contains XIP (initrd)
Start Address: 0x00000640
End Address: 0x00000FBF

0x01E0 - Usually contains imgfs (rootfs/ext2)
Start Address: 0x00000FC0
End Address: 0x0001BCFF

0x01F0 - Usually contains FAT (data/recovery)
Start Address: 0x0001BD00
End Address: 0x00039FFF

[natemcnutty]

Originally Posted by natemcnutty

Well, maurice.green had something going here: http://forum.ppcgeeks.com/tp2-androi...ml#post2020361

Also, I have attached my dumps of several ROM's as far as partitions go. Finally, I know others reference mtd through cmdline like this:
mtdparts=msm_nand:0x00300000@0x1600000(boot),0x000 40000@0x01900000(root),0x066C0000@0x01940000(syste m),0x08000000@0x08000000(userdata)

Also, I just found a good reason why they use the cmdline for this:

Custom partition layouts, ZERO brick risk! - xda-developers

[[ACL]]

Originally Posted by natemcnutty

Also, I just found a good reason why they use the cmdline for this:

Custom partition layouts, ZERO brick risk! - xda-developers

ahh yea. i saw that too.

Talking with woz and cotulla they both recommeneded i use another driver. They have no faith that our driver is working. So i'll try to port over the hd2 nand driver and see if i can dump nand again with no errors.

Now how do i make a yaffs style image for rootfs ? anyone?

[natemcnutty]

Originally Posted by [ACL]

ahh yea. i saw that too.

Talking with woz and cotulla they both recommeneded i use another driver. They have no faith that our driver is working. So i'll try to port over the hd2 nand driver and see if i can dump nand again with no errors.

Now how do i make a yaffs style image for rootfs ? anyone?

mkyaffs2image-128M is what you want. I have attached it to the post.

Edit: Details here: http://www.friendlyarm.net/forum/topic/663

[[ACL]]

Originally Posted by natemcnutty

mkyaffs2image-128M is what you want. I have attached it to the post.

Edit: Details here: creation of yaffs2 file system as rootfs - FriendlyARM

have i told you lately that you are the muthaf*ckin man ? thank bro..

[natemcnutty]

Originally Posted by [ACL]

have i told you lately that you are the muthaf*ckin man ? thank bro..

Glad I could help

I also found details on the MTD Utilities from TI here: MTD Utilities - Texas Instruments Embedded Processors Wiki

Was gonna try cloning the git here in a little bit and see if those utilities were useful.

[[ACL]]

Moving to the hd2 nand driver seems to make the errors go away. but i still cant write onto the partitions.

So far this is what i've done

# cat /dev/mtd/mtd0 > /sdcard/mtd0.img
# cat /dev/mtd/mtd1 > /sdcard/mtd1.img
# cat /dev/mtd/mtd2 > /sdcard/mtd2.img
# cat /dev/mtd/mtd3 > /sdcard/mtd3.img

mtd0 is the only one that has data. The rest are just empty. I'm assuming its because i wiped the whole phone ? i should have left winmo partially in there to check.

After trying to flash_image one of the partitions i tried to mount it and i get the following.

[ 518.155426] msm_nand_read_oob: unsupported ops->len, 512
[ 518.155517] end_request: I/O error, dev mtdblock3, sector 0

This doesnt look good. i know the 512 error is common but not sure why it's happening. So this is where im at..

[pts69666]

Originally Posted by [ACL]

This doesnt look good. i know the 512 error is common but not sure why it's happening. So this is where im at..

Thanks for all the hard work ACL, it is always great to get an update! =D