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

[arrrghhh]

Originally Posted by odz

Hey guys are you running "cat /dev/zero > /dev/mtd/mtd2" before running flash_image? seems that's what alot of people recommend doing when flashing a boot image..


Take a look at this

My Linux Blog - Download and build the Google Android

Looked at install-seq.sh and it seems we don't?

A quick bit of googling shows that this seems to be standard practice for alot of people
"cat /dev/zero > /dev/mtd/mtd2" - Google

Wouldn't this only matter after the flash? You're assuming the flash functions correctly and we're getting to the point where the install-seq.sh gets kicked off. We're never making it to that point...

I'm by no means an expert, but if you think the issue is in the install-seq.sh, I think you're wrong . Keep the ideas flowing tho, don't want to diminish that!

[[ACL]]

I lost track and im trying to figure out what people tried and didnt try.

So last i heard the original NBHs work fine but obviously wipe nand. I'm assuming this is because our payload had some weird padding in there where the bad stuff may have been skipped? i never quite understood the internals of the payload.

We may need to work backwards here in this case and begin with the old payload and work backwards. Not sure what else to recommend at this point

[arrrghhh]

Originally Posted by [ACL]

I lost track and im trying to figure out what people tried and didnt try.

So last i heard the original NBHs work fine but obviously wipe nand. I'm assuming this is because our payload had some weird padding in there where the bad stuff may have been skipped? i never quite understood the internals of the payload.

We may need to work backwards here in this case and begin with the old payload and work backwards. Not sure what else to recommend at this point

This is how I understand where we are as well.... the old payload missed the bad blocks before, and are not now.

[[ACL]]

Originally Posted by arrrghhh

This is how I understand where we are as well.... the old payload missed the bad blocks before, and are not now.

How good is your hex edits?

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS) [ONLINE] - xda-developers

You can always take the original payload and begin the butchering ..

Edit: Also i notice that we are still using a different compression that the vogue (XPR vs lzx).. Did anyone ever try out the other one? (i included a bin if anyone wants to try it.)

[Lmiller1708]

Originally Posted by [ACL]

How good is your hex edits?

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS) [ONLINE] - xda-developers

You can always take the original payload and begin the butchering ..

Edit: Also i notice that we are still using a different compression that the vogue (XPR vs lzx).. Did anyone ever try out the other one? (i included a bin if anyone wants to try it.)

ACL good idea about the compression.
I have been able to get it to now boot with adding the imgfs.bin by tinboot. @ @ Tinboot V 1.0 @ Very simple bootloader for H - Tinboot
My partition table is very close to what the partition table of the booting ones are. NBInfo 2.1rc2 '00_OS.nb.payload' has valid boot - Rhod_Payload

I made a couple of changes this morning adding in the imgfs.bin instead of the emptyimgfs. (lzx instead of xpr)

Stinebd also pointed out that night that a couple parts of our scripts are wrong. Both Nate's and what is on GIT.

For Nate's FullBuild.sh Line's 54, 70 and 76 need to have a - behind the $TOOLCHAIN_PATH... Like this $TOOLCHAIN_PATH-

This is also the same for the GIT. And line 27 has the wrong config.
It should be: make ARCH=arm htc_msm_nand_defconfig

As DZO stated the bad blocks should be handled by the SPL... So maybe this is not working like it should with some devices. So I would like someone with bad blocks (like arrrghhh or Nate ) to flash back to stock, and try it again.

I'm cooking up a ROM like now that I would like you guys to test and get back to me. I will attach the modules if successful. It also looks like ACL pushed the camera?

Happy Flashing!

EDIT: My Androidupdate.tar

[arrrghhh]

Downloading now, thanks L_miller... I'll let you know how it goes!

Status quo... no double vibe :/

ACL, I'll read and re-read that page... hopefully start to mess with this stuff. First reading leaves me in a fairly glazed state to be honest... .

[[ACL]]

Originally Posted by Lmiller1708

ACL good idea about the compression.
I have been able to get it to now boot with adding the imgfs.bin by tinboot. @ @ Tinboot V 1.0 @ Very simple bootloader for H - Tinboot
My partition table is very close to what the partition table of the booting ones are. NBInfo 2.1rc2 '00_OS.nb.payload' has valid boot - Rhod_Payload

I made a couple of changes this morning adding in the imgfs.bin instead of the emptyimgfs. (lzx instead of xpr)

Stinebd also pointed out that night that a couple parts of our scripts are wrong. Both Nate's and what is on GIT.

For Nate's FullBuild.sh Line's 54, 70 and 76 need to have a - behind the $TOOLCHAIN_PATH... Like this $TOOLCHAIN_PATH-

This is also the same for the GIT. And line 27 has the wrong config.
It should be: make ARCH=arm htc_msm_nand_defconfig

As DZO stated the bad blocks should be handled by the SPL... So maybe this is not working like it should with some devices. So I would like someone with bad blocks (like arrrghhh or Nate ) to flash back to stock, and try it again.

I'm cooking up a ROM like now that I would like you guys to test and get back to me. I will attach the modules if successful. It also looks like ACL pushed the camera?

Happy Flashing!

EDIT: My Androidupdate.tar

I didnt even know people use that build script .. I think everyone is mature enough to know how to compile a kernel right?

[[ACL]]

Originally Posted by arrrghhh

Downloading now, thanks L_miller... I'll let you know how it goes!

Status quo... no double vibe :/

ACL, I'll read and re-read that page... hopefully start to mess with this stuff. First reading leaves me in a fairly glazed state to be honest... .

Ok, so i want to shift gears a bit and just concentrate on at least getting the double vibe. Means the kernel is actually up. Lets not worry about the initrd for now.

Soooo.. can you build without the full initrd? or make a really small one. I say this because the original nhb missed the bad parts.. so the kernel is in a safe spot and most likely the initrd is broken. So we can either shrink it to a few K or move it far back. I say shrink it since Lmiller is able to append it on tinboot now. all we need is a initrd small enough to miss all the bad poop

[Lmiller1708]

Originally Posted by arrrghhh

Downloading now, thanks L_miller... I'll let you know how it goes!

Status quo... no double vibe :/

ACL, I'll read and re-read that page... hopefully start to mess with this stuff. First reading leaves me in a fairly glazed state to be honest... .

Did you flash back stock first? If so maybe we need to try relocking???


Can any ROM cooker help out?

[arrrghhh]

Originally Posted by Lmiller1708

Did you flash back stock first? If so maybe we need to try relocking???


Can any ROM cooker help out?

Hrm, I can try relocking... I did flash back to stock tho.