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

[[ACL]]

Originally Posted by natemcnutty

Yeah, before you needed androidinstall.tgz, androidupdate.tgz, and recoveryinstall.tgz in your andboot folder, then flash the NBH, then hold the screen to boot into recovery (which installed when not found and then loaded up), then install system from in there, and then reboot.

I just pushed the change to include recovery.tgz in initrd and have it extract it if /recovery/init.recovery is not found. I don't think it will initiate an auto-build, but from here on out, I think ACL's autobuild files will include the new method which allows us to get rid of recoveryinstall.tgz from the sdcard.

Yeah this isnt gonna work out. just synced and saw the binaries pop up. I'll remove it but have autobuild generate this exactly like you have it. When i sync bootevn i can have the latest recovery copied over this method is kept intact without ballooning up git. For all the developers, well this should be no big deal.. the noobs can suffer. But not sure if you agreed or not, but are we stripping the busybox or not?

which reminds me, we need a new thread. Or another place to have dev discussions .. lol. some of the posts are getting to be ridiculous so ill leave it up to one of the young guns to man one of these threads ..

Ok so im back home.. tired but im not sure if ill get to work on LK tonight like i hoped.. but i'll definitely run some more test for the gsm folks. Also i started using mountable modules like cyanogen. My only prob is its hard to script which modules to load.

For example this is how my modules are being generated now

2.6.27.46-01267-g6900b6e-dirty.sqsh

We cant leave it entirely up to android to mount since i dont think its able to determine the uname to know which modules to load. So unfortunately either the initrd will have to do the dirty work or the sysinit. Sysinit might load too late so this may not work out.

Also i was thinking about what you mentioned before, and copying this one file to system/lib/modules may not be a bad idea. this way our data restore will work flawlessly. we will have to make a way to do kernel upgrades but thats down the road.

[natemcnutty]

Originally Posted by [ACL]

Yeah this isnt gonna work out. just synced and saw the binaries pop up. I'll remove it but have autobuild generate this exactly like you have it. When i sync bootevn i can have the latest recovery copied over this method is kept intact without ballooning up git. For all the developers, well this should be no big deal.. the noobs can suffer. But not sure if you agreed or not, but are we stripping the busybox or not?

which reminds me, we need a new thread. Or another place to have dev discussions .. lol. some of the posts are getting to be ridiculous so ill leave it up to one of the young guns to man one of these threads ..

Ok so im back home.. tired but im not sure if ill get to work on LK tonight like i hoped.. but i'll definitely run some more test for the gsm folks. Also i started using mountable modules like cyanogen. My only prob is its hard to script which modules to load.

For example this is how my modules are being generated now

2.6.27.46-01267-g6900b6e-dirty.sqsh

We cant leave it entirely up to android to mount since i dont think its able to determine the uname to know which modules to load. So unfortunately either the initrd will have to do the dirty work or the sysinit. Sysinit might load too late so this may not work out.

Also i was thinking about what you mentioned before, and copying this one file to system/lib/modules may not be a bad idea. this way our data restore will work flawlessly. we will have to make a way to do kernel upgrades but thats down the road.

Yeah, sorry about the binary, I wasn't sure what was needed for autobuild and didn't want it to kick off a bad image or something. Should have asked first, and thanks for removing it.

It looks like recovery doesn't need busybox in /recovery/bin. The recovery.tgz I put in the initrd does not have busybox, and it functions just fine. Initially, I had been including it in the recovery.tgz, so it looks like we still have more headroom available in the initrd if we need it for anything else you'd like to include!

I agree about the forming of a new thread for ROM related issues. I'd like to see LMiller write up a post for FRX05 on NAND since I think he did the majority of the work. I'm having a difficult time getting FRX06 working properly, and I don't know what all you guys did to fix it up.

I really would love to see us move modules into system. I wonder if there is a way to reduce the overall size of our modules. They seem so much larger than the modules for other phones.

[[ACL]]

Originally Posted by natemcnutty

Yeah, sorry about the binary, I wasn't sure what was needed for autobuild and didn't want it to kick off a bad image or something. Should have asked first, and thanks for removing it.

It looks like recovery doesn't need busybox in /recovery/bin. The recovery.tgz I put in the initrd does not have busybox, and it functions just fine. Initially, I had been including it in the recovery.tgz, so it looks like we still have more headroom available in the initrd if we need it for anything else you'd like to include!

I agree about the forming of a new thread for ROM related issues. I'd like to see LMiller write up a post for FRX05 on NAND since I think he did the majority of the work. I'm having a difficult time getting FRX06 working properly, and I don't know what all you guys did to fix it up.

I really would love to see us move modules into system. I wonder if there is a way to reduce the overall size of our modules. They seem so much larger than the modules for other phones.

ahh i was confused. Yes i see busybox is gone but the links are still there. Its cool. dont worry bout it still trying to automate all this. Reason recovery had its own busybox is that it also can serve as an initrd incase you want to boot into a recovery kernel. This way you can wipe kernels in the future, but we are far from that stage so lets not even talk about it until we are there.

Yeah im sure lmiller is cooking up frx6. not a bad idea to create an update tho. Test our update code

for the modules the squashed version brings them down to 6mb. So only 6mb get copied to over system. Best i can do for now. I think once we remove the uneeded ones we can see a reduction in size. Means we would need to go over the defconfig and figure out what we need. (not thrilled about that).

Ok, if we do move modules to the system. Then what do we do about pppd and the other junk in android update so we can get rid of all that nonsense. I think the pppd issue is just bad code on the ril. I can fix that and bring it back to system. not really sure what else we have on android update.

[tiger2wander]

@Nate: I've just test your "GSM Test " and still can not get GSM work, even after I tried to kill rild service. Anything else:
- WiFi also not work
- New sexy recovery still work like charm.

Here is my dmesg

[a460162314]

Storage system can not open the file URL?
This：
http://htcdevs.wirelesstcp.net/files/xdandroid/

[jadenq]

Here is an update on my situation. I found several possible solutions. One of which is to just let it continually boot loop for a night and see if the fixes it. I tried this one but it didn't work. My next solution is to leave the battery out for about a day. I am hoping this will work, but I fear that my battery might be fried.
I have noticed that when I plug it in and it tries to auto boot if I remove the battery before it boots and then insert the battery again the charge light comes on. But after 10 seconds the light turns off then back on and even if I unplug it the light stays on.
I don't know if that means anything? I have done a lot of research. Let me know if you have any thoughts?

[[ACL]]

Originally Posted by jadenq

Here is an update on my situation. I found several possible solutions. One of which is to just let it continually boot loop for a night and see if the fixes it. I tried this one but it didn't work. My next solution is to leave the battery out for about a day. I am hoping this will work, but I fear that my battery might be fried.
I have noticed that when I plug it in and it tries to auto boot if I remove the battery before it boots and then insert the battery again the charge light comes on. But after 10 seconds the light turns off then back on and even if I unplug it the light stays on.
I don't know if that means anything? I have done a lot of research. Let me know if you have any thoughts?

this is a known issue bro.. i dunno what kinda research you did but i know we must have at least pasted about 10 pages about this.

So with that said ive yet to find a fix. My last attempt does not seem to charge the batt like i had hoped so this is why you are getting this.

So either get yourself a batt charger or go back to winmo. Hopefully you have enough juice to flash back.

[jadenq]

Originally Posted by tiger2wander

yall need an external charger as I said in few earlier pages to get your batt enough energy before it can continue its job, else u will get a boot loop because of early boot process will not charge your batt and it will simply drain and power off.

Originally Posted by [ACL]

this is a known issue bro.. i dunno what kinda research you did but i know we must have at least pasted about 10 pages about this.

So with that said ive yet to find a fix. My last attempt does not seem to charge the batt like i had hoped so this is why you are getting this.

So either get yourself a batt charger or go back to winmo. Hopefully you have enough juice to flash back.

Thank you. I will probably just buy a new battery. Its only 7 dollars on Amazon. Thank you again.

[Lmiller1708]

Originally Posted by jadenq

Thank you. I will probably just buy a new battery. Its only 7 dollars on Amazon. Thank you again.

You might not have enough battery to flash back to winmo, it might die mid flash and if it does you should be OK it just won't boot past the first or second boot screen but it might have the drivers in there to charge ...
It might be wort a shot, if you don't mind can you give it a try?

Just use a custom ROM, Smaller the better! You can enter bootloader as soon as the device get to the first boot screen.
EDIT: Try one of these ROM's I would start with the 38MB one: http://forum.ppcgeeks.com/android-tp...6-5-6-1-a.html

[jadenq]

Originally Posted by Lmiller1708

You might not have enough battery to flash back to winmo, it might die mid flash and if it does you should be OK it just won't boot past the first or second boot screen but it might have the drivers in there to charge ...
It might be wort a shot, if you don't mind can you give it a try?

Just use a custom ROM, Smaller the better! You can enter bootloader as soon as the device get to the first boot screen.
EDIT: Try one of these ROM's I would start with the 38MB one: http://forum.ppcgeeks.com/android-tp...6-5-6-1-a.html

I will try this. If it works I will be surprised but very happy

Edit: I tried it and it flashed 100%! it seems to be charging! THANK YOU!!!!