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.

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

below

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

This is just an observation

Certain apps wont install from market, or direct via apk.

didn't mean to single out angry birds !

If you guys are gona want us to report findings, you cant get back in here and knock on how petty
our findings are!

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

LOL I'm all for feedback, but who really cares about Angry Birds? We're working on things like root, keyboard layout, etc. Getting code updated, trying to bring us up to the level that haret is at.

Apps will come. Need to get the base system solid and finished before we can worry about apps ;).

I've never been able to install angry birds... for now that is fine with me

Sent from my MSM using Tapatalk

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

Have you played Angry Birds?!?! Never before have I lost myself on the shitter for longer periods of time than I do while playing Angry Birds. Hours, man, hours...

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

Quote of the year.:toothy10:

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

Who cares about games, let the developers fix the real issues(needs) before getting into the (wants).

Wow... in this thread, really?

Sent from my FRX05-ized TP2

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

Nate/lmiller

Ok, so i may have a test recovery for you guys later tonight. Installing it is somewhat painful but can be done via adb. Unless you cowboys want to roll your own install scripts.

This is the process and i hope yall like it. We will check for a recovery partition when people hold the volume down or the ts screen, if no recovery partition is found we move on to the replimenu. If one is found, then it will load instead of the replimenu.

Now this means a fresh install will always be done by install script or replimenu. The only way around this is to add the recovery inside the initrd which is possible if I slim it down.

Not all features are implemented yet, but what we have is enough to start.

Install, update, mount mass storage, wipe data and adb fully work right now. Backup and restore are in the works.

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

wow dude ur amazing and being that my fone is not in service i dont mind taking the brick risk to test this but i may switch do boost this week will keep u guys updated (btw does anyone know if there is a way to flash it to work on pageplus?)

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

haha, sorry, just sent your pm askin bout this

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

Sounds good. I did figure out how to do ADB over wifi, and it was quite simple. The problem is that you need full root access to start the adb service (since it doesn't recognize USB to start the daemon), and my wifi modules seem to be very flaky. I'm gonna have to make custom builds to get this going pre-Android. Here's the key for anyone interested:

setprop service.adb.tcp.port 5555
stop adbd
start adbd

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

adb is on when android boots, but since you are doing the set prop i geuss you need to restart it.

You should change the default prop on your so adb always uses your set prop.

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

didnt read this posted anywhere but just to make sure i have to be HSPL unlocked to flashed this,....correct?

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

yeah, any 3rd party flashing (custom rom) requires a HardSPL
(kinda the cool thing about using haret.exe, no 'voiding' warranty!!)

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

NICE!!!

Ok sounds great! I will be able to test this tomorrow!

Thought we were going to get rid of replimenu?
Can they not choose the any options?

There should be zero brick risk! Unless you somehow screw up the flash. :)

Good to know how to do this! Thanks for the tip! Are your modules loading correctly, my wifi has been working great... Did you make the changes to the install-seq-sh script to fix the keyboard and leave out the recovery part?


About the root thing...
What apps have you guys not been able to get working because you didn't have root? Have you tried using the Superuser app from the market?
I'm still thinking its a permissions issue. Correct me if I'm wrong but we should be fully rooted...
Currently the su is in the system/bin and system/xbin folders. Do we need them somewhere else? Also is there a newer su file that we should be using? If so Please attach!!!!

And please do not post on here just to post. :)
We do not care about games!!!!
This stuff is our GAME!

Thanks!

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

Oh there are a few games out there... I played Frozen Bubble for quite some time, got stuck in a few tables, like 65, 70, 89, 99 and 100! LOL

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

Is that what we agreed on? i thought you were in love with it. But if you guys wanna get rid of it specially after playing with the recovery, then i can try to shrink it down to see if it can fit in the initrd.

If not then we will rely on the init script for base installs and have it install all 3 (android, update and recovery). I guess it all depends on how yall feel about the recovery

Yes agreed..

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

I have installed SU binary via ADB to /system/xbin. Installed SuperUser App

I can't update BusyBox via Titanium Backup or the BusyBox installer.

Busybox installer app complains about not being able to remount rw for /system even if it is rw via adb.

Titanium just fails never calls up Superuser app, Same with Busybox.

I have a feeling it is looking for the /etc/fstab for mount and unmount as well as some back end permission issues with busybox.

Mainly the "Must be suid on order to work properly" message.

I am thinking whatever user android is running as needs to belong to the correct root group.

Whoami under phone shows unknown id 10049. I am tracking down to see how to set it correctly.


Also looks as if /system/xbin has everything as user root and userid as 2000 except busybox which is root

http://android-dls.com/wiki/index.ph...uids_and_guids

This shows userid is adb/shell user id. Copying su over sets permissions for root root.

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

notin to do with fstab.. actually you are way off.

Issue is on our end. Our initrd includes /bin/su which doesnt give anyone any rights. So we will need to remove the link on our next build. Or remove /bin from the PATH variable.

So if you want to test this out. Mount / as rw and remove /bin/su. Then when you type su, the other version in /system/bin will run.

also make sure su has permissions 4755

Wirelessly posted (Opera/9.80 (Android; Opera Mini/5.1.22460/23.411; U; en) Presto/2.5.25 Version/10.54)

Should we remove it from initrd entirely or replace the link with the real su from rootfs?

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

it should be there at all. But im not sure why its being used. We need to double check the path in the init.rc .. the paths must match xdandroid.

/bin is reallly only for initrd not android.

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

Yeah we can live without it on the init.rc. We have a full busybox on system/bin so we shouldnt lose any functionality. We need tests now.

just remove "/bin" from the path in sysinit.rc and you should be golden. rootfs has a hack to run su from outside busybox.

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

Ok. I was able to get Titanium backup working correctly with the superuser app.
Steps:
1. Go Here and get the newest Zip for Froyo.
2. Extract to you sdcard.
2.1. Install the included supersuer apk.
3. Mount system as rw: mount -o remount,rw /system
4. Remove the su in system/bin and system/xbin.
5. Copy the su included in the zip above to your system/bin folder.
6. chmod 4755 /system/bin/su
7. ln -s /system/bin/su /system/xbin/su
8. run TitaniumBackup and click on "Problem?" button to install BusyBox from App (Thanks m4f1050)

Run Titanium Backup and you should be prompted by the Superuser app to allow access for Titanium backup. You will also have to update the busybox.

This will work for now until we get full root access.

Don't forget when you remove the /bin/su app it will be back there once you reboot your device. ;)

Also I think we should still leave the /bin path in the sysinit.rc, because that's what the xdandroid uses and we do not want to go too far from them...

I'm still looking at not having to use superuser app... But I know the Vogue still uses it... I have not been able to find a su that works without it. :( I have tried the ones included in the rootfs and system/xbin with no luck.

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

Well that makes sense. I will try that. I didn't realize the initrd had it's own /bin setup.
;)

Titanium backup is still not asking for root in the manner SuperUser app notices. I'll try later tonight. I can get Clocksync and MarketAccess apps to work fine before. I pretty much did all those steps above except the sysinit.rc change. After the sysinit.rc change I didn't notice any difference.

I'll restart and try if not well, I know I'm no expert.

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

yeah.. it really shouldnt be there. rootfs on haret uses it to setup all this stuff for android, but since its in the initrd you cant make it go away so might as well use it. Other builds like sense and cyanogen dont use it so im thinking we should just remove it from the path for now and test.

Nate/lmiller: new recovery hopefully tonight. Backup and restore now work, only thing left is the advanced menu for fix permissions (fix userland perms), fix perms (for sys perms that lmiller wrote the script for). Not sure what else we would need but that's a good start right now. I guess if you need more you better learn how to use adb. I might just stub out the advanced features so we dont need to recompile when the scripts are done.

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

Sounds good! I will wait to test the new recovery.
Before you commit the permissions stuff I have a updated one for you...

About replimenu if we can just do everything in the recovery that is good enough. No need for two menu systems that do virtually the same thing. ;)

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

i vote don't care if we "have"/get to use superuser app, so let's just stick with using the app then. Werd to recovery, no use for replimenu fer sure, RIP replimenu....

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

lolol:toothy10:

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

Lmiller your instructions worked, but you need to do 2 things, 1 before the instructions (which is mount / as rw and remove /bin/su) and one after the instructions (do the BusyBox update from TitaniumBackup.)

Here is what I did:

1. adb shell
2. mount -o remount,rw /
3. rm /bin/su
4. (your instructions)
5. run TitaniumBackup and click on "Problem?" button to install BusyBox from App

Thanks!