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

**arrrghhh** · #**2111** (**permalink**) 03-25-2011, 09:14 AM

Quote:

Originally Posted by chunnel

I have run the port via haret from the Project Android thread. That appears dead at this point. However, without Bluetooth capability this is not practical for me. Neither thread seems to have that working. So, do you see that as a possibility? Or has everyone given up on that working?

Please, don't fill this thread with drivel.

Use search, there's a thread dedicated to BT. Kernel fixes are there, but buggy and userland fixes need to still be employed to route audio correctly.

Really do hate when people say the project is dead when it is far from it...

**[ACL]** · #**2112** (**permalink**) 03-25-2011, 09:35 AM

Quote:

Originally Posted by arrrghhh

Please, don't fill this thread with drivel.

Use search, there's a thread dedicated to BT. Kernel fixes are there, but buggy and userland fixes need to still be employed to route audio correctly.

Really do hate when people say the project is dead when it is far from it...

thanks bro ..

**natemcnutty** · #**2113** (**permalink**) 03-25-2011, 01:31 PM

ACL, I've been trying to find a way to get recovery loaded from our NBH. There are only two things I can think of.

First, cat an image of recovery out to the sdcard and then cat it onto the end of the payload. I'd have to figure out padding to get it to write to the correct offset, and I'm not sure if it would mess anything else up since we'd be writing blank or padded values to that protected area of NAND.

The other alternative is that we include recovery.tgz in initrd and have init check /recovery to see if recovery is there yet. If not, extract it from the initrd and launch into it. This way we can still update recovery, but it gets deployed if it doesn't exist.

What do you think?

**[ACL]** · #**2114** (**permalink**) 03-25-2011, 02:22 PM

Quote:

Originally Posted by natemcnutty

ACL, I've been trying to find a way to get recovery loaded from our NBH. There are only two things I can think of.

First, cat an image of recovery out to the sdcard and then cat it onto the end of the payload. I'd have to figure out padding to get it to write to the correct offset, and I'm not sure if it would mess anything else up since we'd be writing blank or padded values to that protected area of NAND.

The other alternative is that we include /recovery in initrd and have init check /dev/block/mtdblock1 to see if recovery is there yet. If not, deploy it from the initrd and launch into it. This way we can still update recovery, but it gets deployed if it doesn't exist.

What do you think?

I dont know about this padding stuff. From what wozzer told me it looks like this thing can end up in different locations so its impossible to predict where. So right now only testing will answer our questions.

I tried in the past to embed the recovery in the initrd, but its simply too big. This is a potential solution if we use LK, but we are too far from that right now.

Another temporary option is to build a small recovery kernel( make a new defconfig) and just disable all the unneeded options. If we can bring the kernel down to 1 meg, then recovery can fit fine in intrd. We just need a kernel to help us hop into the real kernel.. im open to ideas, this is new grown for all of us.

**natemcnutty** · #**2115** (**permalink**) 03-25-2011, 02:29 PM

Quote:

Originally Posted by [ACL]

I dont know about this padding stuff. From what wozzer told me it looks like this thing can end up in different locations so its impossible to predict where. So right now only testing will answer our questions.

I tried in the past to embed the recovery in the initrd, but its simply too big. This is a potential solution if we use LK, but we are too far from that right now.

Another temporary option is to build a small recovery kernel( make a new defconfig) and just disable all the unneeded options. If we can bring the kernel down to 1 meg, then recovery can fit fine in intrd. We just need a kernel to help us hop into the real kernel.. im open to ideas, this is new grown for all of us.

Cool, I'll mess around with trying to pack recovery into initrd and let you know how it goes. I have a few ideas of some things we can do to shrink our space.

Also, I just built the latest kernel/modules and installed. I am unable to get data working, but I have not tried the new RIL in the GSM folder. Wasn't sure if that was for GSM only or if that was required with the new kernel also.

Yesterday, I wasn't able to get service with the kernel I compiled, so at least I have that this time. I'll be testing out neopeek's idea for moving -d /dev/smd0 arg to build.prop next.

**[ACL]** · #**2116** (**permalink**) 03-25-2011, 04:24 PM

Quote:

Originally Posted by natemcnutty

Cool, I'll mess around with trying to pack recovery into initrd and let you know how it goes. I have a few ideas of some things we can do to shrink our space.

Also, I just built the latest kernel/modules and installed. I am unable to get data working, but I have not tried the new RIL in the GSM folder. Wasn't sure if that was for GSM only or if that was required with the new kernel also.

Yesterday, I wasn't able to get service with the kernel I compiled, so at least I have that this time. I'll be testing out neopeek's idea for moving -d /dev/smd0 arg to build.prop next.

yeah the gsm dev ril might be use for all devices soon. Havent finished the part bout forcing yourself into a network that your device dont belong on yet.. lot of work. but i might do that last.

**natemcnutty** · #**2117** (**permalink**) 03-25-2011, 05:09 PM

Quote:

Originally Posted by [ACL]

yeah the gsm dev ril might be use for all devices soon. Havent finished the part bout forcing yourself into a network that your device dont belong on yet.. lot of work. but i might do that last.

Cool. Any idea how I can force the data to work for now?

Also, I just stuck the recovery.tgz in the root of initrd.gz, had init check for /recovery/init.recovery, if not found, extract recovery from /recovery.tgz, and boot into recovery.

So, with that done, now we don't need recoveryinstall.tgz on the sdcard, and you don't even need a sdcard to get into recovery... The NBH ends up being 5 MB if you leave recovery in the tgz, and from what I can tell, Android is booting up and working just fine with the increase in size.

**[ACL]** · #**2118** (**permalink**) 03-25-2011, 05:26 PM

Quote:

Originally Posted by natemcnutty

Cool. Any idea how I can force the data to work for now?

Also, I just stuck the recovery.tgz in the root of initrd.gz, had init check for /recovery/init.recovery, if not found, extract recovery from /recovery.tgz, and boot into recovery.

So, with that done, now we don't need recoveryinstall.tgz on the sdcard, and you don't even need a sdcard to get into recovery... The NBH ends up being 5 MB if you leave recovery in the tgz, and from what I can tell, Android is booting up and working just fine with the increase in size.

wtf .. didnt we try this before like 100 times and we couldnt get past 3.25mb ? or am i on crack? that must be it.. crack..

anyways this is huge bro. I have what i call "oem_recovery" its a stripped down recovery for just installs and some basics. I planned to deploy this with the intrd in the past but i couldnt get it to work sounds like you did so ill get

Anyways if this is working, then i say we have a success on or hands..

if you are using the new ril then you will be forced cdma by default. You can check on a logcat -b radio to make sure cdma is being used and not gsm.

**natemcnutty** · #**2119** (**permalink**) 03-25-2011, 05:32 PM

Quote:

Originally Posted by [ACL]

wtf .. didnt we try this before like 100 times and we couldnt get past 3.25mb ? or am i on crack? that must be it.. crack..

anyways this is huge bro. I have what i call "oem_recovery" its a stripped down recovery for just installs and some basics. I planned to deploy this with the intrd in the past but i couldnt get it to work sounds like you did so ill get

Anyways if this is working, then i say we have a success on or hands..

if you are using the new ril then you will be forced cdma by default. You can check on a logcat -b radio to make sure cdma is being used and not gsm.

Awesome. So here's what I'm going to do. I'm going to compile a new NBH with the androidupdate.tgz to include the new RIL. I'll post that here and have as many people test it out as possible. If I get enough feedback, I'll push it to git.

Note, we still need to change the button mappings in recovery. Right now, I just changed the one value in the gpiokeys to be home instead of power, and I commented out the navipad.

**natemcnutty** · #**2120** (**permalink**) 03-25-2011, 05:46 PM

OK, here is the new test NBH with the androidupdate.tgz. To make sure there is no funny business, please do the following:

Make sure recoveryinstall.tgz is removed from /sdcard/andboot
Put androidinstall.tgz and androidupdate.tgz in /sdcard/andboot
Flash the NBH
Do NOT touch the phone and watch to make sure it boots straight into recovery
Once in recovery, install like you normally would

This method is absolutely sexy! If recovery is ever corrupted for some reason, you can restore the original recovery by simply deleting init.recovery from the root

http://dl.dropbox.com/u/11790134/recoverytest.zip

Edit: Data does not work on first boot, but appears to work fine after a reboot!