Quote:
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 |
Just a couple of things I wanted to add.
First, I have tried a combination of everything from the Vogue including flashing their partition table and their emptyimgfs with our initrd and zImage.
Second, my post with those scripts is insanely outdated. I've had the nand defconfig for quite a long time. The scripts on GIT have never worked for me, so I've always used my own script.
Third, it isn't bad blocks that are preventing people from booting. I have a couple of theories, but I'm pretty sure it has nothing to do with bad blocks. If you look at the reports of bad blocks, they have been assigned numbers outside of the possible number block. We would have to flash at least 10,000 times in order to wear out the flash, and the blocks just don't go bad that easily.
The frist theory I had was that some of us have a slightly different SPL. I know all of ours say SPL-1.00.OliNex, but they did update the SPL and then stated that if you already HSPL'd that you didn't have to do it again. I can't test this theory because I can't USB. If I relock, I'll be stuck on stock forever. Reference:
http://forum.ppcgeeks.com/cdma-tp2-d...w-hardspl.html