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

[Lmiller1708]

Originally Posted by [ACL]

Yeah i was using wozzers line but thats different than what you posted. Where did u get that ?

mtdparts=msm_nand:0x10000000@0x0(nand),0x01500000@ 0x04000000(root),0x066C0000@0x05540000(system),0x0 6f60000@0x0Bc00000(userdata)

However one thing no one knows is if ous msm_nand.c is actually working. We cna pass all these params down to the kernel but if they arent showing up on linux, then something might be wrong with the driver.

Cotulla recommended we try to flash to the last portion of the partition. This way we dont kill anything important. Makes sense but i dont know enough about the partitioning to do that.

Can just compile the msm_nand.c and add it to the NAND manually without the flash?
Not too sure we have to mess around with the mtdparts until we get the drivers working correctly.

[[ACL]]

Originally Posted by Lmiller1708

Can just compile the msm_nand.c and add it to the NAND manually without the flash?
Not too sure we have to mess around with the mtdparts until we get the drivers working correctly.

how will we know if its working right without passing mtd parts? we have to pass it right or else we wont be able to tell if its actually visible.

thoughts ?

[Lmiller1708]

Originally Posted by [ACL]

how will we know if its working right without passing mtd parts? we have to pass it right or else we wont be able to tell if its actually visible.

thoughts ?

Let me restate... We still need the mtdparts in the cmd line, But I'm not sure the values will matter that much (currently). They can always be changed later. Just my thoughts.

[[ACL]]

Originally Posted by Lmiller1708

Let me restate... We still need the mtdparts in the cmd line, But I'm not sure the values will matter that much (currently). They can always be changed later. Just my thoughts.

The mtdparts is important since we can overwrite and brick .. i dont want to brick myself :-p .. I double checked with wozzer about his values

Those values I used for mtd parts were far enough in that it couldn't overwrite the radio and hspl.

As a backup, you will probably want to do a hard reset, flash the os.nb (android) then take a full MTD backup of nand.

There you have it folks.. more reading to do

[[ACL]]

ok so i finally see the /dev/mtd . Damn rootfs didnt call my modprobe like expected.

Now i was trying to dump stuff but lot of weird errors on dmesg

[ 351.681854] msm_nand_read_oob 31a1000 1000 0 failed -74, corrected 0
[ 351.683624] msm_nand_read_oob 31a2000 1000 0 failed -74, corrected 0
[ 351.685424] msm_nand_read_oob 31a3000 1000 0 failed -74, corrected 0
[ 351.687225] msm_nand_read_oob 31a4000 1000 0 failed -74, corrected 0
[ 351.689331] msm_nand_read_oob 31a5000 1000 0 failed -74, corrected 0

i dont have the balls to attempt a write yet. but if read fails i doubt write will be any better.

[guruvince]

Do it!

[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?