Quote:
Originally Posted by Lmiller1708
Kill the script. No real need for it.
Nate,
Not sure what your problems are... But when I was trying to make the MTDParts like you are now you have to format the partitions in the correct order. MTD1 - MTDn...
I'm guessing that you have all sorts of rw errors once you tired to go back to the original... This can be corrected by changing the order of erasing like i just posted above.
Our initial install script should be put together this way also.
EDIT: ALSO Nate if you want to test these MTDparts out we might need to look at how the NBH is being created again.
Might have to go back to what the Vogue is using...
Just a hunch I have  , but I have not had enough time to look at it. 
This was my latest MTDParts:
Code:
mtdparts=msm_nand:0x3000000@0x0(boot),0x800000@0x3000000(recovery),0x8C00000@0x3800000(system),0x10800000@0xC400000(userdata),0x2000000@0x1CC00000(cache)
They work... but WIFI does not! ACL said it's because we could be writing over the place where that stuff is stored... |
LMiller, remember, when you use the recovery, it only mounts mtd1 initially and formats it, so it doesn't matter about the order. I tried with your mtdparts, and it gives me this:
msm_nand_erase: cannot erase block in protected area, addr=0x2000003000000
flash_eraseall: /dev/mtd/mtd1: MEMERASE: Invalid argument
Failed
Failed to format Recovery
If you are doing the cat method to get the size smaller, I'm concerned that will cause more issues since cat doesn't adjust the partition tables like the nbtools do.
As for the script, I want to get rid of it too, but only after recovery is working properly. For now, recovery is not working for me, and I'm going to assume it isn't working for others in its current state on the autobuild. Maybe I'm missing something?
Edit: OK, now it is working for me. There comes a time in a man's life when he must format the sd card... That time was now, lol. That being said, to hell with install-seq.sh and long live ACL's recovery because that beast is sexy as hell.