View Single Post
Old 05-30-2014, 05:15 PM   #242
JimMcLaren
Addict
JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.JimMcLaren ought to be getting tired of karma fortunes by now.
 
JimMcLaren's Avatar
 
Posts: 260
Karma: 1014230
Join Date: Jan 2010
Device: Onyx Boox T68, Kobo Aura HD, Pocketbook 302, Pocketbook 912, Nook HD+
Well I figured it out. For those trying to do the same thing, here's what I did.
  • cat /proc/self/mountinfo - This was just to get the list of mountpoints
  • mount -o rw,remount -t yaffs2 /dev/root / - This mounts the drive for read/write
  • chmod 777 build.prop - This allows me to overwrite or edit the build.prop
  • edit the build.prop and save it
  • chmod 750 build.prop - I'm not 100% certain this is the right permissions for build.prop but it should be safe.
  • reboot
The device is certainly more usable now.
JimMcLaren is offline   Reply With Quote