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

[MassStash]

haha, sorry, just sent your pm askin bout this

[natemcnutty]

Originally Posted by [ACL]

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.

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

[[ACL]]

Originally Posted by natemcnutty

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

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.

[vzihome]

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

[AkumaX]

Originally Posted by vzihome

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

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

[Lmiller1708]

Originally Posted by 86shelby

Quote of the year.

NICE!!!

Originally Posted by [ACL]

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.

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?

Originally Posted by vistazifta

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?)

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

Originally Posted by natemcnutty

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

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!

[m4f1050]

Originally Posted by zizou90

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

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

[[ACL]]

Originally Posted by Lmiller1708

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?

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

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

Thanks!

Yes agreed..

[coolsilver]

Originally Posted by Lmiller1708

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!

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.

[[ACL]]

Originally Posted by coolsilver

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

Android UIDs and GIDs - Android Wiki

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

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