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

**natemcnutty** · #**1961** (**permalink**) 03-21-2011, 05:37 PM

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.

**[ACL]** · #**1962** (**permalink**) 03-21-2011, 06:01 PM

Quote:

Originally Posted by natemcnutty

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.

yeah .. but imagine if we can have the NBH put the recovery straight into the recovery partition ? now that would be sweet. I asked wozzer to look into that and lets hope he gets somewhere. He said in the past he was able to put more stuff in so it may be possible now that we know the key to success with nand.. just cross your fingers.

Anyways: so is there an sdcard issue? i still think there is because of that line inside the initrd

**natemcnutty** · #**1963** (**permalink**) 03-21-2011, 06:10 PM

Quote:

Originally Posted by [ACL]

yeah .. but imagine if we can have the NBH put the recovery straight into the recovery partition ? now that would be sweet. I asked wozzer to look into that and lets hope he gets somewhere. He said in the past he was able to put more stuff in so it may be possible now that we know the key to success with nand.. just cross your fingers.

You know, it's all about combining it into the payload at the right offset. I guarantee Wozzer is better at that than I am, but I'll gladly take a look at it

For the old install script, I think we can remove it entirely. I think it would be good to maintain it on git though since you are using it in recovery. Maybe the other scripts from recovery can go in the bootenv/scripts folder too?

Finally, those mtdparts I listed are working perfectly for me using the method we are currently doing. I can't get LMiller's to work even changing to the cat method. I'm not sure what magic he is using to get that partition layout working, but I'd love to commit what I posted for now. If we can squeak out a little more space, we can update that later

**Lmiller1708** · #**1964** (**permalink**) 03-21-2011, 06:18 PM

Quote:

Originally Posted by natemcnutty

You know, it's all about combining it into the payload at the right offset. I guarantee Wozzer is better at that than I am, but I'll gladly take a look at it

For the old install script, I think we can remove it entirely. I think it would be good to maintain it on git though since you are using it in recovery. Maybe the other scripts from recovery can go in the bootenv/scripts folder too?

Finally, those mtdparts I listed are working perfectly for me using the method we are currently doing. I can't get LMiller's to work even changing to the cat method. I'm not sure what magic he is using to get that partition layout working, but I'd love to commit what I posted for now. If we can squeak out a little more space, we can update that later

Magic... Nahh.. I screwed up again, I had them working at 4 not 3. Not sure what I was thinking...

Anyway is your WIFI working with the latest MTDParts?

**[ACL]** · #**1965** (**permalink**) 03-21-2011, 06:20 PM

Quote:

Originally Posted by natemcnutty

You know, it's all about combining it into the payload at the right offset. I guarantee Wozzer is better at that than I am, but I'll gladly take a look at it

For the old install script, I think we can remove it entirely. I think it would be good to maintain it on git though since you are using it in recovery. Maybe the other scripts from recovery can go in the bootenv/scripts folder too?

Finally, those mtdparts I listed are working perfectly for me using the method we are currently doing. I can't get LMiller's to work even changing to the cat method. I'm not sure what magic he is using to get that partition layout working, but I'd love to commit what I posted for now. If we can squeak out a little more space, we can update that later

he is having vm issues so knock urself out. if u can do that then ill work on the multiple kernel thing we have for the /data/modules part. plus some more kernle upagrades hopefully

**natemcnutty** · #**1966** (**permalink**) 03-21-2011, 06:23 PM

Quote:

Originally Posted by [ACL]

he is having vm issues so knock urself out. if u can do that then ill work on the multiple kernel thing we have for the /data/modules part. plus some more kernle upagrades hopefully

Sounds great. Just curious on this, why don't we just cp the modules into system instead of symlinking from data? I think the issues we were having before probably had to do with mounting system as ro before android started.

**natemcnutty** · #**1967** (**permalink**) 03-21-2011, 06:37 PM

Quote:

Originally Posted by Lmiller1708

Magic... Nahh.. I screwed up again, I had them working at 4 not 3. Not sure what I was thinking...

Anyway is your WIFI working with the latest MTDParts?

Yeah, wifi works just fine. I don't think mtdparts will affect modules unless you data partition is being overlapped by system or something. Then you would have more issues than just wifi not working though :P

**Lmiller1708** · #**1968** (**permalink**) 03-21-2011, 06:53 PM

Quote:

Originally Posted by natemcnutty

Yeah, wifi works just fine. I don't think mtdparts will affect modules unless you data partition is being overlapped by system or something. Then you would have more issues than just wifi not working though :P

Well that's great News!

We thought it was related to the MTDParts because every time I would try these parts they would break WIFI... But now since ACL made the change in the kernel WIFI works!!

Have you tried 4000000 instead of 4800000? Like I said above I was able to get it to work that way... I won't have anytime to test these tonight...

**natemcnutty** · #**1969** (**permalink**) 03-21-2011, 07:15 PM

Quote:

Originally Posted by Lmiller1708

Well that's great News!

We thought it was related to the MTDParts because every time I would try these parts they would break WIFI... But now since ACL made the change in the kernel WIFI works!!

Have you tried 4000000 instead of 4800000? Like I said above I was able to get it to work that way... I won't have anytime to test these tonight...

Yup, fails on 4000000 but works on 4800000.

MassStash · #**1970** (**permalink**) 03-21-2011, 07:51 PM

so with the sdcard BS, we're at what exactly? Testing those ideas?

Acl, fn no worky in boot code, so wuah wuah to that one.... annnnnd, what's good with terminal in recovery? Eh eh? Dat'd be pretty shweet, specially with green font, idk...

Also, I'll reiterate = !@#$%^&*()+=-_£€\/'";

>. My keyboard fn shiznit is workin business stylee.... nothin tweaked in install-seq either, straight from bootenv

Sent from my sdcard hanicapped MassStashed kustomkookedkernel of nandroid (woot mute button endcall)