yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] deepak2111:
--I have downloaded 12 rom and can download others from zopo,jiayu,zte, and others with similar specs.

--we need to find out which kernel works...

--as I said I have little knowledge linux,HPUX 64,solaris but new to Android structure...

--and again want to participate in this work though not much time..

--it would be great help if you mention steps in short..

--i can extract,pack images,jar--- i am not a programmer

thanks
[Miscellaneous Android Development] debasish497:
Although there are so many tutorials in ROM porting, particularly this one from RishabRaj is helpful.

http://xdaforums.com/showthread.php?t=1908008

Since I was only concerned with whether the device was booting or not, I ignored other functionalities.

our aim is to find the best suitable 4.2* ROM as close as possible for our Phone. if its booting then we are done somewhat.

Yuwengs Tutorial is helpful too. It has some tools in this.

http://xdaforums.com/showthread.php?t=2123239

Setup ADB and Logcat

http://xdaforums.com/showthread.php?p=43363723#post43363723

you dont need to download the entire android sdk, adb is also available without that, the link to it available in the hyperlink link above.

Regarding Logcat, if you fail just after the boot.

http://xdaforums.com/showthread.php?t=2176660

Unpack-Pack Kernel image. Boot.img in windows, although Linux recommended.

http://www.freeyourandroid.com/guide/extract-edit-repack-boot-img-windows

Alternate tutorial: from bgcngm(Thanks)

http://xdaforums.com/showthread.php?t=1587411

Take the base ROM as the one from Somberi, and the port Rom the one downloaded.

Once you have ported the created ROM, by changing the boot.img from the port rom in the base rom, create the cwm flashable rom and setup logcat and get that. Check whether you are getting past the bootanimation. If you are through, get the logcat. Dont waste time if any ROM is not getting past the booting, check in the logcat, whether it stuck somewhere or keeping in writing different I/O related stuff.(but remember to wipe the dalvik cache after flashing the zip).
[Miscellaneous Android Development] RickyGoldsmith:
I hear this multiple times. I don't think it is easy to brick the MTK device family. I never had a brick. They are as standard as the samsung devices, with the exception that they do not release the sources.
[Miscellaneous Android Development] RickyGoldsmith:
Thanks [MENTION=5277821]debasish497[/MENTION] for the comprehensive post. I'll just add to the part about booting. It is, at times, hard to define past where. Your best bet is to get the logcat. Sometimes your boot is stuck because of an incompatible hw library. In that case, it is just the matter of fixing the library. This was the common case for me when porting the version 2 of the MIUI ROM you see in this thread.

The worst case, where you should look out, is when you start the boot and the kernel immediately panics and reboot. In android world, they call it early boot loop. This is the situation where the kernel is completely incompatible.

Hope this helps.
[Miscellaneous Android Development] debasish497:
Hope we can get more help from this point from those who wants to collaborate.
[Miscellaneous Android Development] deepak2111:
Sure...

At list we have to find out which kernel works...

Tomorrow i'll check all the kernel downloaded.......:(
[Miscellaneous Android Development] debasish497:
dont worry mate, you're not alone,..

we are with you
[Miscellaneous Android Development] deepak2111:
thanks

Not able to check kernels...but...

TWRP-2.4.4.0 works on our "DREAM" D1...

please find ...dont want to open new thread so uploaded.........Here
[Miscellaneous Android Development] debasish497:
TWRP reduces the woes, can you give emphasis on the giyayu G4 ROM and the A820 ROM from lenovo.
[Miscellaneous Android Development] deepak2111:
Interface is cool and useful if you need less key press...

-Is 4.2 job require compatible apps?

-have to change BOOTCLASSPATH?

-framework?
[Miscellaneous Android Development] debasish497:
Yes, might require
[Miscellaneous Android Development] deepak2111:
Twrp recovery Bug removed i'll upload after some testing.
[Miscellaneous Android Development] deepak2111:
Bugs removed redownload and flash.:good:
[Miscellaneous Android Development] RickyGoldsmith:
Thank you for TWRP. I just flashed it now and it is wonderful. You have done a great job. THANK YOU. :good::good::good::good:
[Miscellaneous Android Development] RickyGoldsmith:
Kernel source

Writing it here instead of the closed FB Gionee group.

I was thinking about the kernel problem.

I am going to try build Varun's repo and see if that kernel works. Because if it does, we atleast have one base available.

[MENTION=5287167]DEEPAK211[/MENTION] [MENTION=1779668]debashish[/MENTION]497

Have you guys checked out the code? Check it out so that you have a copy of it.

On the android front, I couldn't find the kernel config in the ROM. Do you guys know where the kernel build config could be on android. On typical linux, we enabled it and make in available in /proc/config and /boot/ also.
[Miscellaneous Android Development] debasish497:
I will check out the Varun's repo from github.

no mate, /proc/config is the location

can you tell the typical contents of that file,..so that I can do some research?

I have found two repos for mt6589 sources.

Liufeias's

https://github.com/liufeias/MT6589_kernel_source

Varun's

https://github.com/varunchitre15/MT6589_kernel_source

I was going through the BoardConfig.mk for A820,

https://github.com/liufeias/android_device_lenovo_a820/blob/master/BoardConfig.mk

and THL w8

https://github.com/liufeias/android_device_thl_w8/blob/cwm/BoardConfig.mk

how to change this for our device,..
[Miscellaneous Android Development] deepak2111:
[MENTION=3094817]RickyGoldsmith[/MENTION] you are right. I also not a FB guy...

Jiayu g4..g3N not works.. dive into deep..
[Miscellaneous Android Development] RickyGoldsmith:
I too tried the same jiyau g3 latest MIUI build. I think the kernel boot loop has to do with more than just the kernel framework. I used the same gionee kernel bitty still boot looped. Hence my understanding about boot loops is not complete. I wanted to share this information with you guys.

I will continue to investigate
[Miscellaneous Android Development] RickyGoldsmith:
I have now gotten past the kernel boot loop. The Jiyau G3 ROM is a very recent MIUI 3.7.5 ROM. So if we port it, it'll be awesome. I am able to get Zygote, adb to start. The pvr is failing to initialize, which I think I know the cause. The rest of the stuff is crashing. It will take a lot of reverse library lookup.

I am not reverting back to MIUI v2 ROM. If anyone wants to play with it, ask now. I can put it up somewhere online tomorrow. I might work on it over the weekend if time permits.
[Miscellaneous Android Development] debasish497:
Let's call it v3 ROM, just to reduce confusion.
[Miscellaneous Android Development] deepak2111:
great... i am ready to work...

just tell me what to do...

i can spare some time in a day..most time spent in learning..understanding..searching:fingers-crossed:

thanks
[Miscellaneous Android Development] RickyGoldsmith:
Great. I will try to upload the half baked rom today. I did take its backup.
[Miscellaneous Android Development] RickyGoldsmith:
The config is the build setting for the kernel or what features are to be built... It has all the details on how the kernel has been built.

Here's an example of what a kernel config is like on a regular linux distribution

A great place to start learning on how the kernel is built, could be Semaphore kernel He's been doing it for long and his kernel Just Works. I've used it for long on my GT-I9000 device.

The BoardConfig looks more of a per device build config for android.
[Miscellaneous Android Development] RickyGoldsmith:
MIUIv5 for Dream D1 - Version 3

I just added it to the main page. It inherits the same problems that were there in v2. I haven't noticed any regression otherwise. I hope we can improve it further. This one is still 4.1.2.
[Miscellaneous Android Development] debasish497:
it was my assumption that since MIUI v2 is based on the mobile lenovo A820, so the front camera + torch doesnt work since it missing the hardware. I may be wrong!! :(

http://www.gsmarena.com/lenovo_a820-5462.php

I am hating the bootanimation of this V3 ROM, finding ways to change it...

the attached screenshot from the ROM shows it contains the A820 baseband,... [MENTION=3094817]RickyGoldsmith[/MENTION] is this ROM based on jiayu g3? the bootanimation too is same as the previous v2.
[Miscellaneous Android Development] RickyGoldsmith:
Yes. And even v3 is based on Lenovo A820....

Oh!! Okay!! I wasn't aware that the A820 didn't have the torch.

the attached screenshot from the ROM shows it contains the A820 baseband,... [MENTION=3094817]RickyGoldsmith[/MENTION] is this ROM based on jiayu g3? the bootanimation too is same as the previous v2.[/QUOTE]
[Miscellaneous Android Development] debasish497:
I am using v3 in my mobile since you uploaded :) there has been zero force closes. Very stable. But the PITA is it is inheriting the odds from v2.

Regarding the kernel.config: its not available in any of the available mt6589 phones. I have checked my friends MMX a116 and zoo 900.

Is is available as some other name? Even googling yielded no result.

What is the default usb vendor Id for Gionee? While setting USB rules in linux

We are never successful with ROMs other than A820, can we try with the 4.2.1 ROM available in needrom
[Miscellaneous Android Development] RickyGoldsmith:
Kernel.config: Hmmm!!! I have checked out the sources. I will see if I can get some time this weekend to explore the kernel build.

USB ID: Bus 003 Device 041: ID 0bb4:0c03 HTC (High Tech Computer Corp.)

lsusb is your friend. More details

Bus 003 Device 041: ID 0bb4:0c03 HTC (High Tech Computer Corp.)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0bb4 HTC (High Tech Computer Corp.)
idProduct 0x0c03
bcdDevice 2.55
iManufacturer 2
iProduct 3 WALTON Primo-X1 Primo-X1
iSerial 4 PZSODYTGS8Q845YD
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 55
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 1 Mass Storage
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

Other ROMS: It is not that I haven't been trying. That is why I asked you guys to see if you can get a bootable kernel from the 4.2.x ROMs. At least, if we have that, I can be much quicker to port a 4.2 ROM. :rolleyes::rolleyes::rolleyes:
[Miscellaneous Android Development] debasish497:
GreAt!!!

link to change the boot logo from Ankadnikov

http://xdaforums.com/showthread.php?t=1953726
[Miscellaneous Android Development] debasish497:
For mt6589 I think its a bit different. I might be wrong but, when I was looking into mt65xx kernel compilation, they are different than the snapdragon ones.

http://xdaforums.com/showthread.php?p=43532297
[Miscellaneous Android Development] RickyGoldsmith:
Kernel build

I think [MENTION=3750240]stratosk[/MENTION]'s build howto should be a good start to learn how to build a custom kernel. It will NOT be identical for our device, but should give an overview. You can access the howto here.

And this is what we need to hunt in terms of a kernel config.

Varun's kernel source repo is incomplete. It doesn't include the mediatek kernel build config. Take a look at others. They have

Without the build config even the mediatek build script will fail.
[Miscellaneous Android Development] debasish497:
Can we try with the MT6577 one? There are few tutorials in china.iPhone.RU, but translating is PITA
[Miscellaneous Android Development] RickyGoldsmith:
Didn't get any time today. Try it out yourself
[Miscellaneous Android Development] RickyGoldsmith:
Torch and front can should work now. Front cam may still fail in photo shoot.
[Miscellaneous Android Development] debasish497:
I have tried and there's something missing it says. Cannot simultaneously use Linux and internet, will paste the errlog soon. There must be something missing.
[Miscellaneous Android Development] debasish497:
Front Cam force closes, looks like library issue.

[MENTION=3094817]RickyGoldsmith[/MENTION]

there are these many camera libs,..

libcam.camadapter.so

libcam.campipe.so

libcam.camshot.so

libcam.client.so

libcam.paramsmgr.so

libcam.utils.so

libcamalgo.so

libcamdrv.so

libcameracustom.so

libcameraservice.so

libcamera_client.so

libcam_camera_exif.so

You have only replaced these-

libcameracustom.so

libcam.client.so

libcam.paramsmgr.so

libcamera_client.so

can you please share why you have chosen only 4 of these? have you got anything in the init.rc?
[Miscellaneous Android Development] RickyGoldsmith:
Font cam will only work for video recording. It crashes as soon as it starts using the auto-focus modes.

Why I chose those libraries: Because of their symbol lists, and then a little bit of guess work.
[Miscellaneous Android Development] debasish497:
It takes lots of effort than it looks buddy, kudos. Of course I admit the power of Linux in this debugging.

Lots a time ago I used to check symbol table/list using the following command(got it from my company mail, shared with a colleague once). I don't know what command you use, nm or readelf.

readelf -Ws /system/lib/mylib.so | grep '^\([[:space:]]\+[^[:space:]]\+\)\{6\}[[:space:]]\+[[:digit:]]\+'

readelf -Ws /system/lib/mylib.so | awk '{print $8}';
[Miscellaneous Android Development] RickyGoldsmith:
Yes. If you filter out the other junk (which you are doing with awk / grep, then you get similar stuff. Otherwise, the default elf output, that's too much to look at. ELF is the standard binary format for Linux. If you look at the default readelf output, it is way too much. And may not be relevant to this requirement. You need ELF support (like libdw etc) when you have a dependency on the ELF data. For example, have a look at the debugging and instrumentation tools. systemtap relies on elf data from each binary to determine their dwarf objects. IIRC similar is the case for sysprof.

If you look at the android so's, you'll see this:

mtk-ril.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, stripped

They are type ELF, claim dynamically linked and stripped. But if you run nm on them, there's no return.

And I don't know why it claims to not be a dynamic executable when it reported earlier.

rrs@zan:/media/DATA/Gionee Hacks/GiONEE_signed_051113_154234/system/lib$ ldd mtk-ril.so

not a dynamic executable

What I simply do is to extract the strings from the library (use the strings command), shared or static. :)

It definitely throws a lot of junk, but then that's how you deal with it. Your friend's readelf will also give similar results. The real meat is in taking the output, and relating it to the problem you have at hand. :laugh::laugh::laugh::laugh:
[Miscellaneous Android Development] RickyGoldsmith:
[MENTION=2078222]deepak2111[/MENTION] [MENTION=5277821]debasish497[/MENTION]

Is any of you looking at the GPS problem? I haven't had much time to spend there, and whatever time I've spent, it hasn't worked, yet.
[Miscellaneous Android Development] debasish497:
Yes, that was the reason I was asking how you look at the libs. Although I know this might be a case much bigger than only lib issue.

For those who want to look and be part of this,GPS by greatanjum
[Miscellaneous Android Development] RickyGoldsmith:
Updated Modem

The updated modem is added. But still, from my limited tests, the location service ain't working.

If any one of you have the time, please follow the same method in the update, and flash the GiONEE shipped modem firmware. And see if that helps. Thanks.
[Miscellaneous Android Development] deepak2111:
I am out of town this week... So don't spare time to look in... Sorry..
[Miscellaneous Android Development] debasish497:
no its not working.

tried with both stock bin and the attached. max when i used the stock i saw 2 satellites using the gps test app.
[Miscellaneous Android Development] wasi006:
My screen is stuck at ydss.cn. how to solve that?
[Miscellaneous Android Development] debasish497:
[MENTION=4277919]wasi006[/MENTION] Have you flashed on a D1?

The reason I ask is all the MIUI roms shared here are been flashed multiple time in many Devices

(d1) and nobody except you have complained.

Can you try it again and see? By the way what are you using TWRP or CWM?

However it can happen that the new D1s are having updated(read downgraded) boards, it is not uncommon that these Chinese companies update the pc board just too often, to maintain the cost effectiveness (see the news how q800 aka gn708w was downgraded with mt6589m).

If anything like this has happened, we are very sorry. As both mine, [MENTION=3094817]RickyGoldsmith[/MENTION], others who are using gn878 since April/May are having common hardware. Well the above is just a speculation, but we are eager to hear from you.
[Miscellaneous Android Development] RickyGoldsmith:
I wasn't aware of this. But this is highly possible. Apart from this, you could also check if the zip you downloaded was correct. The checksums are listed on the main page.
[Miscellaneous Android Development] debasish497:
Well that is unlikely. If the Zip was corrupted then the flashing wouldn't be completed and the boot animation wouldn't have changed. Accidentally I tried flashing a corrupt zip which aborted midway.

I cleared the data/cache, formatted the system/cache and reflased with a proper zip, and it was good again.

News that gn708w was downgraded.

q800(gn708w) downgrade

Since both gn878 and gn708w were manufactured and released together, upgraded from mt6577 together, and now when gn708w is downgraded I was suspecting the same for Dream d1. Even the boxes now don't pack the usual 2 plastic shell covers, it now contains a flip cover.

One more interesting fact: exact chipset clone of gn878 is gn818T(Exactly same phone except a Kevlar Back like Motorola). gn818T was released with china unicom like gn708w, so it has greater audience than gn878. ROM hunters, can you check the ROMs for this phone.
[Miscellaneous Android Development] Ganesh Kumar:
[MENTION=5277821]debasish497[/MENTION].....Then in needrom.com roms are available for GIONEE GN708W can able to flash directly to dream d1?
[Miscellaneous Android Development] debasish497:
No, some of our XDA/FB group members and myself tried to Flash them, all of the available failed.

although the gn708w and gn878 were released together, they have some differences in hardware/

the exact clone in gn818T. but it is not available in needrom.

to sum up:

-- I am not sure that the device [MENTION=4277919]wasi006[/MENTION] is using is a re-launched gn878 with a downgraded chipset.

The speculation arised since it is the first time, MIUI ROM failed to boot after flashing.

-- Although gn708w was downgraded recently, it is beyond our scope to testify that gn708w and gn878 have same hardware after downgrade. Remember, gn878 has Amoled display which might require different display adapter/hardware whch again accounts for different software.

-- We can develop software for the available hardware only due to our limited scope. Even if gn878 has been downgraded, its not available to us.

But if really its has been downgraded, the ones who have them are welcome in this thread to help us and themselves to modify the software for their hardware.
[Miscellaneous Android Development] RickyGoldsmith:
kernel build

Any luck with the kernel build? You were planning on trying the scripts from the other source...
[Miscellaneous Android Development] debasish497:
I am getting one error and many warnings while I was trying to compile. I will try again tonight , try to get the Zimage created.

---------- Post added at 07:44 PM ---------- Previous post was at 07:26 PM ----------

How much different do you think the 6577 and 6589 configs be, is there any way to extract it from our boot.IMG?
[Miscellaneous Android Development] deepak2111:
[MENTION=3094817]RickyGoldsmith[/MENTION] [MENTION=1779668]debashish[/MENTION]497

In MIUIV5-Version3 rom check this file /system/data/misc/projectconfig.mk

Just trying to helpful.
[Miscellaneous Android Development] RickyGoldsmith:
I have no idea. It would be similar but there could be some major differences, for one it is a completely different device platform.
[Miscellaneous Android Development] RickyGoldsmith:
That looks more like an android project config file... Just speculating...
[Miscellaneous Android Development] debasish497:
You're right. Its different from the Mtk6577 kernel config
[Miscellaneous Android Development] wasi006:
Nothing to be sorry about. I am downloading the zip file again. I am using TWRP recovery. will let you know when I install it again. Thanks for the prompt reply.

And I am using it on my Walton X1 mobile (one other user installed it successfully, so I am hopeful here)

EDIT: Redownloaded. Still stuck at ydss.cn :(
[Miscellaneous Android Development] deepak2111:
GPS test on MIUIV5 Version3-with new modem

I have tested GPS on new modem uploaded by RickyGoldsmith.

with wifi on and under open sky..

at first try..first fix time was 02:13

second try it was 01.31

with data enabled connected to internet

it was 00:09!!!!!

after reboot it was 00:15

see the sreeenshots..
[Miscellaneous Android Development] RickyGoldsmith:
Then you need to help us debug it. Are you in a position to gather the logs? Use logcat.
[Miscellaneous Android Development] RickyGoldsmith:
That is a delight. So the GPS works. Now we need to nail the Location Services.