I ran into the same issue. Try adding the custom boot.img from here to
your build folder.
http://sl.edujose.org/2013/10/adapted-boot-image-for-use-with-b2g.html
On Sat, Dec 28, 2013 at 10:25 AM, wrote:
> On Monday, October 14, 2013 2:41:31 AM UTC+5, Eduardo González wrote:
>> Hi, i have modifie
On Monday, October 14, 2013 2:41:31 AM UTC+5, 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_YwAEXRwifN21QmQbHgNCcEc5Ml2CKw57IBGxnv
On Sunday, 20 October 2013 21:43:47 UTC+1, Eduardo González wrote:
> Hello James. I have not got the kernel, boot.img i offered via external file
> locker was created exploding stock boot.img, changing few lines of startup
> scripts and default.prop file and repacking to new boot.img, then kerne
Hello James. I have not got the kernel, boot.img i offered via external file
locker was created exploding stock boot.img, changing few lines of startup
scripts and default.prop file and repacking to new boot.img, then kernel wasn't
modified.
However, i have tried compilation of kernel specially
On Friday, October 18, 2013 5:06:31 PM UTC-4, Eduardo González wrote:
> Exactly, rilproxy is built-in in the stock kernel (i understood it because
> kernel messages shows integrated rilproxy is emabled) then solution is
> deactivate rilproxy built by b2g and pushed into phone. Is there other chan
On Friday, October 18, 2013 5:06:31 PM UTC-4, Eduardo González wrote:
> Exactly, rilproxy is built-in in the stock kernel (i understood it because
> kernel messages shows integrated rilproxy is emabled) then solution is
> deactivate rilproxy built by b2g and pushed into phone. Is there other chan
On Sunday, October 13, 2013 5:41:31 PM UTC-4, 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_YwAEXRwifN21QmQbHgNCcEc5Ml2CKw57IBGxnv
Exactly, rilproxy is built-in in the stock kernel (i understood it because
kernel messages shows integrated rilproxy is emabled) then solution is
deactivate rilproxy built by b2g and pushed into phone. Is there other change
over default property file enabling root access to adb service
_
He commented out its registration as a service in init.b2g.rc :)
___
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
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
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 im
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_YwAEXRwifN21QmQbHgNCcEc5Ml2CKw57IBGxn
On Sunday, October 13, 2013 2:41:31 PM UTC-7, 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_YwAEXRwifN21QmQbHgNCcEc5Ml2CKw57IBGxnv
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 /out/target/product/inari/
then run ./
I am trying to flash a 1.2 build onto my ZTE Open (US eBay version) according
to the instructions on the Mozilla wiki, and it goes smoothly until the end
when it fails with this error:
Attempting to set the time on the device
time 1381424366 -> 1381424366.0
settimeofday failed Bad file number
I
15 matches
Mail list logo