View Single Post
  #1742 (permalink)  
Old 03-14-2011, 12:30 PM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:
Originally Posted by [ACL] View Post
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
Reply With Quote