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

[Lmiller1708]

Originally Posted by [ACL]

just one last one..

wine tools/ImgfsToNb.exe tools/imgfs.bin os.nb.payload os-new.nb.payload
ImgfsToNb 2.1rc2
Using bigstorage mode

Sector size is 0x800 bytes
Writing imgfs to offset byte 0x320000, sector 0x640
Input file tools/imgfs.bin cannot be read. Exiting.

Not sure whats up with the imgfs.bin but it just poops out.. anyways i gotta head out but ill be back later..

Here is my tinboot folder. Hope it helps!

[[ACL]]

Originally Posted by Lmiller1708

Here is my tinboot folder. Hope it helps!

nuffin bro.. same thing.

Nate: ? have you tried it ?

[Lmiller1708]

Originally Posted by [ACL]

nuffin bro.. same thing.

Nate: ? have you tried it ?

Humm... What does your Log look like? I'm available to chat at IRC...

[[ACL]]

Originally Posted by Lmiller1708

Humm... What does your Log look like? I'm available to chat at IRC...

thanks for helping earlier. After alot of comparing i see why now this is failing.

When attacking the imgbin, it gets placed at a position where it cuts off the xip. Now sure how this is happening. It looks like your xip is slightly smaller so it clears away just fine. When i attach it however it get cut off so i dont boot.

did you adjust the offset ? or did we always use 320000 ?

[Lmiller1708]

Originally Posted by [ACL]

thanks for helping earlier. After alot of comparing i see why now this is failing.

When attacking the imgbin, it gets placed at a position where it cuts off the xip. Now sure how this is happening. It looks like your xip is slightly smaller so it clears away just fine. When i attach it however it get cut off so i dont boot.

did you adjust the offset ? or did we always use 320000 ?

Nope i didn't change that. Would be nice to know though.... I wondering if smaller would be better? Pass me your initrd.gz and I will give it a try... tomorrow!


Edit: Fixed post... Shouldn't be drinking while posting...

[[ACL]]

Finaly got everything in order (few randome reboots here and there but better than before) . I made the necessary chagnes to tinboot so we are all on the same page. I still need to clean it up a bit. I'm going to remove all the rhod variants and just have 1 line for everyone.

Few things will change with the kernel as well.
1) overclocking will no longer be done via cmd line. What's the most common android app to overclock? whatever it is it would be nice if we just comply with that.
2) I'm going to finish up the variant detection so keyboard will be detected ..
3) cdma detection will be done by the variant as well.

i pushed changes to initrd.. its stripped down now for size. Also i removed sdcard support since we are on nand. No need to go back to sdcard images now. .. now time for bed ..

[arrrghhh]

Originally Posted by [ACL]

Finaly got everything in order (few randome reboots here and there but better than before) . I made the necessary chagnes to tinboot so we are all on the same page. I still need to clean it up a bit. I'm going to remove all the rhod variants and just have 1 line for everyone.

Few things will change with the kernel as well.
1) overclocking will no longer be done via cmd line. What's the most common android app to overclock? whatever it is it would be nice if we just comply with that.
2) I'm going to finish up the variant detection so keyboard will be detected ..
3) cdma detection will be done by the variant as well.

i pushed changes to initrd.. its stripped down now for size. Also i removed sdcard support since we are on nand. No need to go back to sdcard images now. .. now time for bed ..

Couple of apps exist to overclock - "Overclocker" and "SetCPU". Not sure which we should prefer tho, I don't own a native Android device .

Great work tho, can't wait to try it!

[Lmiller1708]

Originally Posted by [ACL]

Finaly got everything in order (few randome reboots here and there but better than before) . I made the necessary chagnes to tinboot so we are all on the same page. I still need to clean it up a bit. I'm going to remove all the rhod variants and just have 1 line for everyone.

Few things will change with the kernel as well.
1) overclocking will no longer be done via cmd line. What's the most common android app to overclock? whatever it is it would be nice if we just comply with that.
2) I'm going to finish up the variant detection so keyboard will be detected ..
3) cdma detection will be done by the variant as well.

i pushed changes to initrd.. its stripped down now for size. Also i removed sdcard support since we are on nand. No need to go back to sdcard images now. .. now time for bed ..

Great ACL! Your mtdparts cmdline is off a bit though...
It should be something more like this:

mtdparts=msm_nand:0x20000000@0x0(nand),0x01500000@0x04000000(root),0x07BA0000@0x05500000(system),-0x06f600000x0D0A0000(userdata)

If you do a cat mtd3 what is the size of your image? With the above mine is 368 MB. We should be able to adjust these a bit more to give us more system space. What do you think a good value for that would be?

Also I didn't see a update on git for the initrd...

For overclocking can we just leave the cmdline in there? And set it for 500? Then we can hex the cmdline if they want to over clock it... This is what they did for the Vogue. They actually have a tool for that, and some other things. Atools. Maybe we could use it in the future...

[[ACL]]

Originally Posted by Lmiller1708

Great ACL! Your mtdparts cmdline is off a bit though...
It should be something more like this:

mtdparts=msm_nand:0x20000000@0x0(nand),0x01500000@0x04000000(root),0x07BA0000@0x05500000(system),-0x06f600000x0D0A0000(userdata)

If you do a cat mtd3 what is the size of your image? With the above mine is 368 MB. We should be able to adjust these a bit more to give us more system space. What do you think a good value for that would be?

Also I didn't see a update on git for the initrd...

For overclocking can we just leave the cmdline in there? And set it for 500? Then we can hex the cmdline if they want to over clock it... This is what they did for the Vogue. They actually have a tool for that, and some other things. Atools. Maybe we could use it in the future...

ahh sorry .. my machine made a mess of git but it should be updated now.

cmd line changes are just too ugly. THe support will remain there if anyone wishes to add it, but adding a /sys entry is easier since it will also allow us to play well with other builds. Cyanogen :-p ?. So yes, the support for cmd line over clock will remain. No need to set it to 500, it can be added if someone wishes.

i trust you guys with the mtd line. You and nate know more about this way more than me. The only thing i didnt really like about the line above is that the name of the partition dissapears. And calls the last partition partition3 or something. This sucks since android relies on the partition naming for mounting. Once you see the initrd, its dumb simple. There is absolutely no mount binds or modifications like the old rootfs. Just because android handles it all via its init script.

You should actually take a look at the sysinit.rc in the last android install i pushed up. look at all the mounts and mkdirs. a lot of it was already there but we can create more as needed. Vendors and custom roms seem to do it this way so might as well study it.

i put up my andinstall, andupdate and install script online as well. This was all i needed to install and run.

Index of /files/xdandroid/

I'm still ironing out some immediate issues. Screen calibration and what not.

[Lmiller1708]

Originally Posted by [ACL]

ahh sorry .. my machine made a mess of git but it should be updated now.

cmd line changes are just too ugly. THe support will remain there if anyone wishes to add it, but adding a /sys entry is easier since it will also allow us to play well with other builds. Cyanogen :-p ?. So yes, the support for cmd line over clock will remain. No need to set it to 500, it can be added if someone wishes.

i trust you guys with the mtd line. You and nate know more about this way more than me. The only thing i didnt really like about the line above is that the name of the partition dissapears. And calls the last partition partition3 or something. This sucks since android relies on the partition naming for mounting. Once you see the initrd, its dumb simple. There is absolutely no mount binds or modifications like the old rootfs. Just because android handles it all via its init script.

You should actually take a look at the sysinit.rc in the last android install i pushed up. look at all the mounts and mkdirs. a lot of it was already there but we can create more as needed. Vendors and custom roms seem to do it this way so might as well study it.

i put up my andinstall, andupdate and install script online as well. This was all i needed to install and run.

Index of /files/xdandroid/

I'm still ironing out some immediate issues. Screen calibration and what not.

I kept getting boot loops until I switched to my sysinit.rc... I think it is a couple of folders not being made... Maybe the sql folder?

Your int file is missing a fi in the automount data part... I'm sure you found that already though.

Still no data though.. This time I don't see the 3G icon at all. We are getting there though...