View Single Post
  #1892 (permalink)  
Old 03-19-2011, 04:43 PM
[ACL]'s Avatar
[ACL]
VIP Member
Offline
Location: NY
 
Join Date: Feb 2010
Posts: 1,534
Reputation: 6350
[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:
Originally Posted by natemcnutty View Post
Great news. I'm just heading out to the zoo with the wife for a couple of hours, but when I get back, I'll make the replimenu commits. I have a couple of changes that I'd like to make to it because the way it is being done right now, we still need a sd card to get into recovery.

I'm wondering if we should do the OTA method where they flag a file for recovery intent, then have init check for that file to determine if it should go into recovery. Then as part of the leaving recovery it can remove that file.
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.
__________________
Reply With Quote