Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

......
Just go to "Index of / files / xdandroid" look.
Download there has been.
I was thinking. I need to download to test it?

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

While GSM does not work, but I can test the functionality.
I re-entered the android.
Discovery. A lot of software can not be installed.
Prompt "Install Failed ".
Other things did not go further to test.
Because they can not install the software, I do not do many things

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Nate/lmiller

Put up new nbh, modules and updated recovery(corrected key).

removed the gsm ril directory since i put the ril itself in the installtgz.

I actually have to go in to work today so i wont get to work on much else until tonight.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

and now we have end on "in call" screen, settled. and everything's smaller like GB, shweet

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

My battery drained on my Sprint Touch Pro 2 and now it is stuck in a boot loop. I removed the battery and put it back then i plugged it in. It charges for 5 minutes then auto boots. The power button doesn't seem to be working. Do you have any ideas?

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

I had the same problem once. Once the phone turns on after booting, unplug the phone and pull the battery out. Then put the battery back in and hold volume down while you turn the phone on. From there you can re-connect the phone to your computer, make sure to re-run the custom RUU.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Ahh, now I get what you mean :) And yes, I think that sounds perfect. Keep full recovery but remove busybox since it is already in initrd. I will also keep looking into a better way to include it outside of initrd but still be in the NBH so we don't have to push that binary to the git. Only way around this is if we only push huge updates for recovery and leave the minor ones to be fixed with androidupdate.tgz.

Yes. The NBH and androidupdate.tgz are a pair and must go together. The one on Index of / files / xdandroid is compiled by the server. The GSMTEST is one that I made for testing.

Awesome. I'll compile the new recovery into initrd and test it. Got feedback from 3 people so far that the new method works great. Also, about 3 more people over at XDA used the files to successfully install (though GSM still doesn't boot right).

If LMiller is around, maybe we can work on getting FRX06 up and running before you get off work tonight :)

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

So late still work?
I will publish the progress of NAND forum in China.
Hope to get more feedback.
Also,I mentioned above, there are many software in the NAND can not be installed.
This is a problem with the kernel?
Or the system?
Continue to work hard, I hope the work of GSM as soon as possible.
TO Oil.
I will continue to monitor the progress of the project.
Good night.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

OK, so I'm working on fixing up FRX06 for NAND. Instead of compiling all of this into androidinstall, I'm going to basically compile a patch for the official FRX06 that will be applied through androidupdate.tgz to fix it up for NAND. Here is what I have so far for reference if anyone else is working on this:

androidupdate.tgz
1. cp -ar /rootfs/init.etc/* /androidupdate/system/etc/
2. cp -a /rootfs/lib/froyo/hw /androidupdate/system/lib/hw
3. cp latest libhtcgeneric-ril.so /androidupdate/system/lib/
4. mv /androidupdate/system/etc/ppp /androidupdate/data/ppp
5. cp latest sysinit.rc /androidupdate/system/
6. cp latest sysinit.sh /androidupdate/system/bin
7. cp latest first-time.sh /androidupdate/system/
8. cp official build.prop to /androidupdate/system
9. edit build.prop: rild.libpath=/system/lib/htcgeneric-ril.so

androidinstall.tgz
1. mv /system/etc/ppp/* /androidupdate/data/ppp
2. rm -rf /system/etc/ppp

These two we either have to do through a script, or we have to modify the official release.

If you guys see anything I'm missing (especially LMiller), please let me know. I really want to get a good procedure down for actually creating a patch for official releases so it makes it really fast and easy to get the imminent builds of GB that I'm sure will start flowing here pretty soon :)

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Well, using the androidupdate.tgz method to create a patch simply didn't work for me. I'm still messing with that method, but to get it pushed out for some testing, I ended up downloading our NAND FRX05 and copying the missing files over to FRX06. This is a quick and dirty method, but here's the files that were missing between the two:

/first-time.sh
/sysinit.rc

/system/bin/netcfg
/system/bin/run-as
/system/bin/su
/system/sysinit.sh

/system/etc/dbus.conf
/system/etc/init.goldfish.sh
/system/etc/bluetooth/audio.conf
/system/etc/bluetooth/input.conf
/system/etc/bluetooth/main.conf
/system/etc/dhcpcd/dhcpcd-run-hooks

/system/lib/invoke_mock_media_player.so
/system/lib/libterm.so

Edit: Well crap, there must be something I'm missing since data won't work... Got it booting in, wifi works, but no data :(

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Hey guys. Don't know if you've run into any errors with the new way of installing, but I'm getting the same "Modules are not installed. Download the matching androidupdate.tgz and boot into recovery mode to install". I made sure I had the right files, along with the correct .nbh. Still nothing. So I used the old method to re-flash. Just letting you guys know.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

As per the first post:
Follow the directions, and you won't get that error ;)

Also, it will be changing very soon. I'm going to update init so it forcefully installs recovery and boots into it the first time after you flash. That should make this even more user friendly.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Well, that's what I was saying. I was trying to use the NEW system you guys were testing (removing recovery.tgz, and letting the boot screen run without touching it after updating with the new .nbh, which if I read correctly, has recovery packaged in with it). That's when I get that error. After trying a few different thing to see if it would work (to no avail, obviously) I went back to the original system and all was right with the world. I just didn't know if any of you had run into the same issue that I had.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Ahh, sorry, I misunderstood. The files on the autobuild do not have the auto-recovery install method yet. Only the ones that I have been building have that. I will be pushing those changes to the git later today after I get a chance to make a couple more minor adjustments and test them.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

That explains a lot then. What exactly is the install method for the .tgz and .nbh that I was using? Was I supposed to leave recovery on my SD card?

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

I think it has something to do with the battery. My friend has the same phone so he let me try his battery and the power button worked fine then and it booted no problem. I couldn't try your solution because the power button wont turn on the phone it only turns on after it has been plugged in for about 5 minutes. Then it tries to boot but only gets half way through and turns off. Any thoughts?

Edit: I got it to boot into the menu when i hold down the volume down button but it wont charge. I am going to keep trying.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

If your friend has the same phone, charge your battery then do what I said before. Chances are your power button isn't the problem, but the fact that your battery doesn't have enough of a charge to start up.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Please tell me you updated this since my post last night, and I am not an idiot - who missed it even after reading several times!!!

Now I see how to install it! Thanks

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

@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

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

repost! i'm a noob

Re: NAND Boot Testing - 03-08: Full NAND FRX05 Testing (Data not working for some)
 

i know it was mentioned some pages ago, but i'm not able to move any apps to the SD card. any solutions to this? even using App 2 SD to indicate which apps can be moved, i'm getting "Failed to move application" notifications at every attempt. i'm using a 4gb microSD card and a sprint cdma tp2

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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.

Re: NAND Boot Testing - 03-08: Full NAND FRX05 Testing (Data not working for some)
 

I believe this is still due to us not having a real root. It looks like when we took /bin out of the PATH, we no longer had access to /bin/busybox. In our initrd, we have /system/bin/sh pointing to /bin/busybox. I'm testing pushing the latest su to /system/bin/su, copy /bin/busybox to /system/bin/busybox during install, and then ln -s /system/bin/sh /system/bin/busybox. We'll see how that works out.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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

Wirelessly posted (TP2: Mozilla/5.0 (Linux; U; Android 2.2.2; en-us; MSM Build/FRX05) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

@Nate/ACL,

I have been really busy around the house with spring cleaning! Still have snow in my back yard though... and going to trim my apple trees today! ;)

Ok back on topic! I will try to look at FRXO6 this morning and see if I can getv it working. Nate can you post what you have so far? Save me some time or atleast post what issues you are having.

Thanks for all of your hard work guys! And maybe we can move this over the ACL'S thread and help here with testing and Noobs... Thoughts?

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Its prob best you do it from scratch and try to automate it. I dont think stine will start making us tgz anytime soon, so if we can take the existing imgs and just automate the process, it will make it easier to do updates :-).

i dunno about the threads. i say start a new one just for chatter..

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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?

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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 :oops: 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.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Well... We can't call a thread Testing if we don't want anyone to post the test results here... ;)

About the system... There is not much to change at all.. I'm uploading a install now, but I have not tested it..: Here are the steps I took.
This system just has the regular version of libhtcgeneric-ril.so, so it will need to be added to the andriodupdate.tgz file.

This whole process could be automated. I'm thinking that we could just mount the system.etx2 to the sdcard and have at it! :toothy7: When I have more time I will look into that.

As for now test out the system FRX06! androidinstall.tgz

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Yeah i know.. we will have to think of something.

mount to the SD ? haha sounds like a killer idea. Just copy off that beotch.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

And change the above files. ;) Should not be too hard to do.

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

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

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

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

Nate. must have broken something. Cant seem to boot off the autobuild version of the initrd.

Missing commits to tinboot? I got the recovery even smaller but hangs on main logo. no double vib so im assuming it may be the same issue as before. Right now the nbh is about 3.4mb

Re: NAND Boot Testing - 03-24: FRX05 on NAND (Testing new RIL)
 

I am having problems in recovery mode. The power button isn't bringing up the recovery menu. I completely reformatted my sd-card and re-flashed the .nbh. I need some help, please.