Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

su: must be suid to work properly

(that's the message I get when I try to run SU from phone, maybe there is a clue to what it's needed... the user needs to be in the suid group?)

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

search next time. i answered this for someone else a couple pages back. We are not yet fully rooted, as in no root access for you. This means you are not a superuser, thus you do not have permission. Getting root access is in the works, you will be able to do w/e you want soon enough lol :toothy10:

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

like my mama always said . whiners are wieners . :-p

But just keep track of the errors. if you can replicate the issue on demand, then even better. Reporting a bug or issue means you are able to replicate it and have some logs to help the devs fix. Otherwise we wont be able to narrow down the root cause of the issue.

Ok for those of you who want root. Read a few posts back since its already there how to do it. its so easy i don't even want to type it again.

For those of you who say the thing crashed. Try this. Try to plug the phone to usb and adb into it. If you can adb, get logs (dmegs, logcat) and we can take it from there. If not, then we need to see if there was anything specific that would have cause it.

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

U got me... I never searched, I just got back in the TP2 scene and didn't start reading from where I left off. Good thing someone else caught it also.

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

Yea I sat down this morning, tried again. Adding su wasn't hard. :D

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

Angry birds wont install via market or apk..

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

guys im having some problems gettin this goin. do i still need the system.ext2 and all those files in my andboot folder? B/c when i create a direction on my sd card called /andboot, and put the 3 required files (named correctly), and then flash the nbh n try to get ti goin, i get an error that says modules are not installed, please put androidupdate.tgz and put it in your andboot folder

also, do i need to do the "hold volume button up" thing, cuz when i did that, i says welcome to the android installer, but i cant click ok b/c theres no enter key on our phones?

any ideas?

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

I think there's bigger problems for NAND to worry about before we should ever be concerned about angy freakin birds...

Sounds like you don't have the right modules.

Make sure your androidupdate is the newest, and matching. You don't need anything but the nbh to flash, and androidupdate.tar/tgz, install-seq.sh, and androidinstall.tar/tgz. The install has the system image, update has the kernel, modules, etc. The .sh file takes care of the install, no need to ever enter the tinboot menu really.

This isn't really ready for general consumption, FYI. It's more for testing - lots of things to fix.

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

yeah im not new to the nand scene, i did it with my vogue for a while, thats why I was curious about the volume thing, thats how we did on the vogue. I'll be happy to post logs and stuff once i get it running if ya need me to. Just wanted to try it out on my rhod =).
anyway, my android update is the newest, i literally just downloaded all the files from the first post. i noticed u put .tar/.tgz is there a difference? I named mine .tgz, i know they're both 7zip files. I'm not sure what's up really. I reflashed the NBH a few times too, jus to make sure.

also, the files already have the .tgz extension so do I need to add it again? Then i think it thinks its androidupdate.tgz.tgz

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

You shouldn't rename them, I used the slash to show they could be either - although like I said, you should not be renaming them.

We don't use tinboot's menu, we just have an install script that runs :p. I'm thinking Android's recovery will be the final thing we use, not positive tho.