Official firmware release for s82 series

[lewy20041]

As to win xp users that get java not instaled issue just go to control panel-system-adwanced-add system varibles (cant remember exact name) and add in higher text box add PATH and in the lower c:/pathtojavajdk/bin and click ok. After that the tool should work.

[Lokie]

Phew.. kernel compiled - now to start testing tomorrow.

[no_spam_for_me]

Phew.. kernel compiled - now to start testing tomorrow.

Good luck!

[Finless]

Getting the tool to work with the JDK

Windows 7, to get the tool to see you have installed the JDK.

Right click on "My Computer" and select properties.
Click advanced system settings
Click the environment variables button

Edit the CLASSPATH line and add this to the end of the existing line:
classpath=C:\Program Files (x86)\Java\jdk1.7.0_40\lib;

Now edit Path and add this line to the existing line
C:\Program Files (x86)\Java\jdk1.7.0_40\bin;C:\adb

Save close and reboot.

Now you can unpack everything and repack.

Bob

[Finless]

OK well after playing with the tool.... It does have it's limitations. I will use it for simple stuff but I still must do some thing by hand in Linux. So while it will make pulling apart a IMG easier, and some other things, I do more tweaking than this tool allows.

Prime example it you cant see all of init.rc with it. So.... back to Linux we go

Bob

[Finless]

Oman - question?

I notice the 6330 ROM works on the 6210 device as well. I see in /etc/wifi both drivers are there.

I can flash both ROMs and they work fine on my S89 Elite.

So why do we need a different ROM or kernel?
This has actually had me confused since day one since I compared both ROMs and kernels (decompiled ARM) and the only difference I could see was wifi? Something I am missing?

Thanks Oman,
Bob

[oman]

回复: Official firmware release for s82 series

I notice the 6330 ROM works on the 6210 device as well. I see in /etc/wifi both drivers are there.

I can flash both ROMs and they work fine on my S89 Elite.

So why do we need a different ROM or kernel?
This has actually had me confused since day one since I compared both ROMs and kernels (decompiled ARM) and the only difference I could see was wifi? Something I am missing?

Thanks Oman,
Bob

..BT is also different...

来自我的 GT-I9300 上的 Tapatalk

[Finless]

..BT is also different...

来自我的 GT-I9300 上的 Tapatalk

OK I did not do a full compare of 102K but on 100 and 101K, there was no difference in the BT files in the ROM. Is this then in kernel?

Bob

[Finless]

OK never mind! I see BT is not working on 6210 when flashed with 6330 ROM. It use to work but 102K is different. No problem I will figure that out.

What I want to do is make ONE large ROM download and a patcher ZIP to convert to 6210 from 6330 ROM. That is what I have been doing since 101K4. It worked so far but I see it's not working now

Never mind, I will figure that out.

But question. Is the kernel different in any way? As that is important.

Thanks Oman,
Bob

[Finless]

OK Sorry Oman, I already figured it out.

libhardware_legacy.so

That is the difference for Bluetooth. I got it working using the 6330 ROM on my 6210 box. Only file needed that I see is libhardware_legacy.so

Again though on the kernel. Is there really any difference? I have not analyzed your 6330 and 6210 kernels of 102K yet. But it would be good to know if I just include boot.img in the patcher.zip between the 2 ROMs?


Bob

[Finless]

OK between the 2 ROMs, I see kernel is still #1 but build date is different.

I am gong to assume for now that kernel is not the same although I do not understand why it really is.

Thus for my ptacher ZIP from 6330 to 6210 I will just make sure boot.img with kernel is applied.

Oman.... Can I just say THANK YOU from all of us for what you have provided today!

Because of you, we will have a lot of FUN with this platform I think

Bob

[oman]

U are welcome,Bob..

For ap6210&ap6330,I'll clarify something,wait for a moment.

Today is Saturday,and now is morning...

[oman]

OK between the 2 ROMs, I see kernel is still #1 but build date is different.

I am gong to assume for now that kernel is not the same although I do not understand why it really is.

Thus for my ptacher ZIP from 6330 to 6210 I will just make sure boot.img with kernel is applied.

Oman.... Can I just say THANK YOU from all of us for what you have provided today!

Because of you, we will have a lot of FUN with this platform I think

Bob

First,the apxxx are all use broadcom IC:
AP6210->BCM40181(wifi)&20710(bt)
AP6330->BCM4330x

And in 102k4,WIFI is already compatible for both two,but BT is not...we change the wifi driver,and copy both wifi's config files into system/etc/wifi,such as fw_bcm*.bin and nvram*.txt...

BTW,wifi driver is not in the kernel tree,it's in the sdk/hardware..

And for BT,yep,we didn't find a way how to,but now...
BOB,pls try to push BCM20702.hcd and BCM4330.hcd to system/etc/bluetooth..I wish to some miracles?

[oman]

OK I did not do a full compare of 102K but on 100 and 101K, there was no difference in the BT files in the ROM. Is this then in kernel?

Bob

I am confused,did u compare system/etc/bluetooth?

[oman]

OK Sorry Oman, I already figured it out.

libhardware_legacy.so

That is the difference for Bluetooth. I got it working using the 6330 ROM on my 6210 box. Only file needed that I see is libhardware_legacy.so

Again though on the kernel. Is there really any difference? I have not analyzed your 6330 and 6210 kernels of 102K yet. But it would be good to know if I just include boot.img in the patcher.zip between the 2 ROMs?


Bob

Really?

Kernel is the same now..
And u said libhardware_legacy.so,I didn't modify anything...ok,Let me check