![]() |
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
Also, I would assume it's still effected by the time drift - although I haven't specifically tested for it, I don't see why it would just disappear :p. Clocksync is still the best remedy for that, until we figure out the root cause (which we may never, seems we don't have a hardware clock to speak of...) |
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
|
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
|
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
Quote:
I tried the newest as of last night, and wifi was broken and IIRC so was the keymaps... I'll try it again when I get home (hopefully). |
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
|
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
I've been testing new placements for mtdparts, and I think I have regained a ton of space for us :) Can someone please try these for the mtdparts? Code:
mtdparts=msm_nand:0x4800000@0x0(protected),0x800000@0x4800000(recovery),0x0A000000@0x5000000(system),0xF000000@0xF000000(userdata),0x2000000@0x1E000000(cache)I just tested grabbing the latest files from autobuild, and I'm having all sorts of issues. Edit: I forgot /sdcard causes issues, so that problem is my own fault. One thing I noticed is since recovery is first in the init, I can't install using install-seq.sh unless recoveryinstall.tgz is not on the sd card which then means I can't install it through the install-seq.sh. So at this point, I think we might want to swap the order of install-seq.sh script and recovery, and then maybe someone else with a rhod500 can test recovery and let me know if it is working for them. |
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
what issue are you having with the recovery ? |
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
|
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
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) |
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
Quote:
or leave the mkdir /sdcard as is, and remove it right before exec init.android is called. both need to be tested i suppose. |
| All times are GMT -4. The time now is 06:38 PM. |
Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com