It sounds as if the permissions problem and default properties problem just require some minor tweaks to the ramdisk portion of boot.img. However, the rilproxy conflict sounds more involved. How did you actually go about fixing that?
On Tuesday, October 15, 2013 1:09:03 PM UTC-4, Eduardo González wrote: > Check my post of blog > http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html. Sorry > my poor english > > > > On Tuesday, October 15, 2013 11:06:15 AM UTC-4:30, V wrote: > > > On Sunday, October 13, 2013 11:41:31 PM UTC+2, Eduardo González wrote: > > > > > > > Hi, i have modified the original boot image and adapted it for zte open > > > commercial devices and custom builds via B2G repository. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Donwload > > > https://mega.co.nz/#!uJ52xZJa!M_YwAEXRwifN21QmQbHgNCcEc5Ml2CKw57IBGxnvdm4 > > > > > > > > > > > > > > > > > > > > > > > > > > > > change filename to boot.img and copy into > > > <B2G_root>/out/target/product/inari/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > then run ./flash.sh > > > > > > > > > > > > > > > > > > > > > > > > > > > > Edu > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > Thank you very much! Care to explain what modifications you did? > > > > > > > > > > > > V _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
