View Single Post
  #1893 (permalink)  
Old 03-19-2011, 09:20 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
ok.. yall got it under control. Well OTA is usually done by userland. So lets say android somehow knows there is an update. Then it will write a command to /cache/recovery/command. Then the recovery will parse that command and automatically update. In our case we can check for that command when we boot, if something juicy is found, then load recovery with the command. If not, then back to android.
That sounds great to me. I'd also like to set it up so we can install recovery, updates, or even system from NAND. LMiller hinted that you might have data working in recovery, and we could totally do an updater that always grabs the latest files right off the site. So exciting

I made the commit to remove replimenu. I did a tiny bit of cleanup while I was at it. I have a couple of other ideas to clean it up further, but I need to test them out first.
__________________
Reply With Quote