Database Info

[DEV] [MTK65xx] ROM DEVELOPMENT cm10

Hi all,
i am opening this thread to push the development on the mtk65xx phones. The taget is to boot CM10 on those devices and maybe we could achive this goal with bundled effort, here is how far i get on this:
1. the source code for this devices is now accessible through different sources. as i own an alcatel one touch 998 the code is accessible ( and for many other phones ) on http://sourceforge.net/projects/alcatel/files/.
2 Building the source:
2.1 Pass the Target device through the environment variable during build e.g. TARGET_PRODUCT=jrdsh77_cu_ics2 for my phone
2.1 Add the needed Header to the Product through mkimage -> ./mkimage zImage KERNEL > kernel (mkimage is inside mediatek/build/tools/)
this will add the needed header to boot the image to the compiled zImage.
3. Repack the Image with repack-MT65xx.pl ( my honor and rewards to Bruno Martins )
4. Boot Phone to Recovery and flash the kernel through dd if=<PathToBoot.img>/boot.img of=/dev/bootimg && sync
5. Reboot Phone.
Ok this is about it how i do it, i don not mention to flash the System-Partiton here as this is a obvious task and can easily done by the cm-<...>.zip generated by the normal build procedure, by commenting out the kernel flash lines inside the updater-script.
Problem for me is now that i get into a bootloop: My phone only shows the vendor Logo stays there for some seconds an reboots again, on my x86_64 Machine inside dmesg i get:
Code:
[ 6717.986372] usb 2-4: new high-speed USB device number 17 using ehci_hcd
[ 6718.120618] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6718.120629] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6718.120637] usb 2-4: Product: MT65xx Preloader
[ 6718.120642] usb 2-4: Manufacturer: MediaTek
[ 6718.182193] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6719.142274] usb 2-4: USB disconnect, device number 17
[ 6734.134696] usb 2-4: new high-speed USB device number 18 using ehci_hcd
[ 6734.268987] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6734.268998] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6734.269005] usb 2-4: Product: MT65xx Preloader
[ 6734.269011] usb 2-4: Manufacturer: MediaTek
[ 6734.331210] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6735.294111] usb 2-4: USB disconnect, device number 18
[ 6750.067450] usb 2-4: new high-speed USB device number 19 using ehci_hcd
[ 6750.201879] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6750.201890] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6750.201897] usb 2-4: Product: MT65xx Preloader
[ 6750.201903] usb 2-4: Manufacturer: MediaTek
[ 6750.263563] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6751.230653] usb 2-4: USB disconnect, device number 19
[ 6766.000293] usb 2-4: new high-speed USB device number 20 using ehci_hcd
[ 6766.134432] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6766.134443] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6766.134451] usb 2-4: Product: MT65xx Preloader
[ 6766.134456] usb 2-4: Manufacturer: MediaTek
[ 6766.196292] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6767.150220] usb 2-4: USB disconnect, device number 20
[ 6781.933093] usb 2-4: new high-speed USB device number 21 using ehci_hcd
[ 6782.067271] usb 2-4: New USB device found, idVendor=0e8d, idProduct=2000
[ 6782.067282] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6782.067289] usb 2-4: Product: MT65xx Preloader
[ 6782.067295] usb 2-4: Manufacturer: MediaTek
[ 6782.129241] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 6783.096138] usb 2-4: USB disconnect, device number 21
So it starts -> boots to preloader -> tries to boot the kernel and fails miserably here, as i dont have any chance to get any debug message to find out what is wrong here im stuck, i have no suggestion, i booted a kernel once succesfully but flashing it now does lead to the same beavior. Maybe reseting it to complete stock and starting again would help but i dont know how to do this, maybe someone can provide me here with some Information, or maybe someone can start with the information here, if any Information is needed or some point needs clearification im free to help. i have several Serial debug cables/chips here but i dont see where i could attach a serial console to the phone to read some debug messages, does anyone know if this is possible?
Sorry for my lousy english :/ i try to get better.
Greetz HUELK

I own an mtk6575 device too,Emmc partition, powervr,hvga screen, 512mb ram running J.b 4.1...
But I am new to ROM porting,wish I culd help

I am not sure how far you can go but, atleast booting to CM is an important steps.
I cant understand the log cat, however if you want to use the stock kernel, have you tried this?
BoardConfig.mk file add
TARGET_PREBUILT_KERNEL := device/manufacturer/devicename/kernel

a few words of encouragement
would be great to have CM10 for MTK65xx phones, maybe solve my crap chinaclone GPS problem.
hope you not abandoned the project.
have u checked the CPUgovernor in the original rom, maybe overclocking and setting voltages too high. set the conservative option as default in the kernel build.

stevet99uk said:
would be great to have CM10 for MTK65xx phones, maybe solve my crap chinaclone GPS problem.
hope you not abandoned the project.
have u checked the CPUgovernor in the original rom, maybe overclocking and setting voltages too high. set the conservative option as default in the kernel build.
Click to expand...
Click to collapse
Hello there. At last someone is doing it too. I'm currently downloading the sources again to re attempt the unknown.
I also have that idea of incompatible/unbootable kernel. Have you tried unpacking the stock boot.img by using the mt-65xx-unpack.pl? That is what I'm thinking to do but have not tried it yet since I'm still building the environment.
We get the working kernel from the original boot.img then use it to build the boot.img to be used for cm.

so theres no hope for android chinese. eh. i am trying to port the cm10 but no luck. since there is no real source given to download.

[Q] Can someone help with ADB please?

ADB flatly refuses to recognise my Xoom MZ601.
I run ADB on my Debian Linux computer and it recognises my LG Optimus 2x (P990) which appears in the list provided by 'adb devices' the same command with my Xoom produces 'List of devices attached' with nothing underneath. The USB Debug setting on the Xoom is ticked and the computer recognises the device. The computer's log shows:
Jun 24 12:10:37 dataman1 kernel: [3605717.696244] usb 1-7.2: new high-speed USB device number 67 using ehci_hcd
Jun 24 12:10:37 dataman1 kernel: [3605717.800363] usb 1-7.2: unable to read config index 0 descriptor/start: -71
Jun 24 12:10:37 dataman1 kernel: [3605717.800368] usb 1-7.2: chopping to 0 config(s)
Jun 24 12:10:37 dataman1 kernel: [3605717.807734] usb 1-7.2: New USB device found, idVendor=22b8, idProduct=70a8
Jun 24 12:10:37 dataman1 kernel: [3605717.807739] usb 1-7.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jun 24 12:10:37 dataman1 kernel: [3605717.807742] usb 1-7.2: Product: MZ600
Jun 24 12:10:37 dataman1 kernel: [3605717.807745] usb 1-7.2: Manufacturer: Motorola
Jun 24 12:10:37 dataman1 kernel: [3605717.807748] usb 1-7.2: SerialNumber: xxxxxxxxxxxxxxxxx
Jun 24 12:10:37 dataman1 kernel: [3605717.807878] usb 1-7.2: no configuration chosen from 0 choices
{The serial number has been changed to protect the innocent }
The udev 51-android.rules shows:
# LG Optimus 2x
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="1004", ATTRS{idProduct}=="618e", SYMLINK+="libmtp-%k", MODE="0666"
# Xoom
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTRS{idProduct}=="70a9", SYMLINK+="libmtp-%k", MODE="0666"
# Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
I have run out of ideas. I am hoping to root the Xoom soon so any suggestions would be greatly appreciated.

BarrySamuels said:
ADB flatly refuses to recognise my Xoom MZ601.
I run ADB on my Debian Linux computer and it recognises my LG Optimus 2x (P990) which appears in the list provided by 'adb devices' the same command with my Xoom produces 'List of devices attached' with nothing underneath. The USB Debug setting on the Xoom is ticked and the computer recognises the device. The computer's log shows:
Jun 24 12:10:37 dataman1 kernel: [3605717.696244] usb 1-7.2: new high-speed USB device number 67 using ehci_hcd
Jun 24 12:10:37 dataman1 kernel: [3605717.800363] usb 1-7.2: unable to read config index 0 descriptor/start: -71
Jun 24 12:10:37 dataman1 kernel: [3605717.800368] usb 1-7.2: chopping to 0 config(s)
Jun 24 12:10:37 dataman1 kernel: [3605717.807734] usb 1-7.2: New USB device found, idVendor=22b8, idProduct=70a8
Jun 24 12:10:37 dataman1 kernel: [3605717.807739] usb 1-7.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jun 24 12:10:37 dataman1 kernel: [3605717.807742] usb 1-7.2: Product: MZ600
Jun 24 12:10:37 dataman1 kernel: [3605717.807745] usb 1-7.2: Manufacturer: Motorola
Jun 24 12:10:37 dataman1 kernel: [3605717.807748] usb 1-7.2: SerialNumber: xxxxxxxxxxxxxxxxx
Jun 24 12:10:37 dataman1 kernel: [3605717.807878] usb 1-7.2: no configuration chosen from 0 choices
{The serial number has been changed to protect the innocent }
The udev 51-android.rules shows:
# LG Optimus 2x
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="1004", ATTRS{idProduct}=="618e", SYMLINK+="libmtp-%k", MODE="0666"
# Xoom
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTRS{idProduct}=="70a9", SYMLINK+="libmtp-%k", MODE="0666"
# Bootloader
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
I have run out of ideas. I am hoping to root the Xoom soon so any suggestions would be greatly appreciated.
Click to expand...
Click to collapse
download http://adbdriver.com/upload/AdbDriverInstaller.exe
and install adb drivers installer on pc,open it
and connect your phone to pc and install the
adb drivers.

Syed.Zeshan said:
download http://adbdriver.com/upload/AdbDriverInstaller.exe
and install adb drivers installer on pc,open it
and connect your phone to pc and install the
adb drivers.
Click to expand...
Click to collapse
It is nice of you to try and help but a Windows executable is not going to run on a Linux machine. There are drivers already on the Linux machine because, as I said in my post, I can use ADB to connect to my LG Optimus 2x.

Wasn't there some udev rule that needs adding?
Sent from my HTC One using xda app-developers app

Maybe use WiFi adb? That's another solution that will probably work. I'm sure you can find an app easily enough. Or does stock android has it by default? Don't really remember...

Chaosgod27 said:
Maybe use WiFi adb? That's another solution that will probably work. I'm sure you can find an app easily enough. Or does stock android has it by default? Don't really remember...
Click to expand...
Click to collapse
I'll give that a try and report back.
spychodelics: I have added udev rules as shown in my first post.
Thanks to you both for trying to help.
Update: I have now solved the problem. With some Linux kernels, mine included, if the ehci_hcd module (needed for USB 2.0) is loaded it prevents the Xoom from being recognised so a modprobe -r ehci_hcd will unload that module and, Voila!, my Xoom is now recognised by ADB. I imagine a fix for that bug will be issued sometime.

Ubuntu 12.04 fastboot no devices ASUS MemoPad

After building a system image to root the ASUS MemoPad FHD 10, I am fed up with having to wait almost 15 minutes for Windoze to boot up and shut down so I can run fastboot to flash the image file. So, I've been on a quest to get adb and fastboot working with Ubuntu so I don't have to deal with stupid Windoze.
Using lnusb, tablet has different vendor:device ids when regular booted and usb debug on (adb mode) and when bootloader/recovery booted with fastboot waiting for command.
Tablet mounts using 'go-mtpfs' so I can work with internal/external SDcards.
Tablet displays with 'adb devices' (normal boot) as Medfield9A65CCEC (also shows this with Windoze fastboot devices)
Tablet doesn't display with 'fastboot devices' (bootloader/recovery boot)
51-android.rules file to recognize both vendor ids:
Code:
# ASUS MemoPad FHD 10 32Mb
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666", GROUP="plugdev", OWNER="Me" # MTP mode with USB debug on
SUBSYSTEM=="usb", ATTR(idVendor}=="8087", MODE="0666", GROUP="plugdev", OWNER="Me" # fastboot mode
Tried downloading a different fastboot binary, same results.
At this point I am stumped why adb works but fastboot does not. fastboot works fine in Windoze.

More Info
After some more research, I found this:
http://packages.ubuntu.com/raring/i386/android-tools-fastboot/filelist
which shows a rules file in /lib/udev/rules.d/70-android-tools-fastboot.rules
so I looked in /lib/udev/rules.d and found the rules file: 51-android-rules.rules with loads of entries
and not /etc/udev/rules.d/51-android-rules.rules as most discussions refer to
so I modified the ASUS section to this:
Code:
# Asus MemoPad FHD 10 (Intel)
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", ATTR{idProduct}=="521f", SYMLINK+="android_adb"
SUBSYSTEM=="usb", ATTR{idVendor}=="8087", ATTR{idProduct}=="09ef", SYMLINK+="android_fastboot"
#SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0660", GROUP="adbusers"
#SUBSYSTEM=="usb", ATTR{idVendor}=="8087", MODE="0660", GROUP="adbusers"
If I comment out the first two lines and use #3&4 syslog shows an error - udevd[3982]: specified group 'adbusers' unknown
If I use the first two lines and comment out #3&4 (as shown above) syslog shows:
Code:
Dec 20 14:45:48 kernel: [25297.608132] usb 2-1: new high-speed USB device number 11 using ehci-pci
Dec 20 14:45:48 kernel: [25297.745240] usb 2-1: New USB device found, idVendor=8087, idProduct=09ef
Dec 20 14:45:48 kernel: [25297.745252] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Dec 20 14:45:48 kernel: [25297.745260] usb 2-1: Product: Android-Phone
Dec 20 14:45:48 kernel: [25297.745268] usb 2-1: Manufacturer: Android
Dec 20 14:45:48 kernel: [25297.745275] usb 2-1: SerialNumber: Medfield9A65CCEC
Dec 20 14:45:48 mtp-probe: checking bus 2, device 11: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1"
Dec 20 14:45:48 mtp-probe: bus: 2, device: 11 was not an MTP device
There are no errors, so the rules file in /lib/udev/rules.d and not /etc/udev/rules.d is being used
Also interesting is that lsusb shows:
Bus 002 Device 011: ID 8087:09ef Intel Corp.
...which is a different Vendor ID
However, even with the correct rules file set and no syslog errors on USB connect, fastboot still refuses to recognize the device when connected in fastboot mode.
I have also tried fastboot i 0x8087 reboot and fastboot -sMedfield9A65CCEC reboot and it just waits for device.
It may be possible that fastboot doesn't like the Intel and is looking for ARM, not sure - although Windoze version of fastboot works fine.

On Archlinux I have the same problem
sudo adb devices works, fastboot fails with <Waiting for device>
but in fastboot mode nothing works at all

Same problem in Ubuntu 14.04 for Kindle Fire
I know this thread has been dormant for a while, but it's pretty much the only hit that comes up when searching on how to setup the /lib/udev/rules.d/70-android-tools-fastboot.rules to get device to mount in fastboot properly.
I had followed some other guides like the OP that said to put rules in the /etc/udev/rules.d/51-android-devices.rules which didn't work at all. I do not have a file /lib/udev/rules.d/51-android-devices..rules
I am having issues similar to the OP with a Kindle Fire Gen2. Device shows up when in Adb mode, but not in fastboot (using factory "fastboot" cable).
Was there ever a resolution to this issue?
Anybody have a source of documentation on how these config files need to be set up when in fastboot mode to gain access and/or get a trusted connection in MTP?

Strange behaviour of 51-android.rules file

I've been scratching head all evening trying to solve this, with no luck.
I've added the following lines to the /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="paul"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="paul"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", MODE="0600", OWNER="paul"​When I run adb devices, it looks OK
List of devices attached
07c082820f1e64c0 device​And lsusb | grep Google finds the device (although it is identified as a Nexus 4 for some reason)
Bus 001 Device 105: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)​Finally, ls -Rl /dev/bus/usb/001/105 indicates
crw-rw----+ 1 paul audio 189, 104 Nov 11 00:13 /dev/bus/usb/001/105​
But, when I set the phone to bootloader mode by running adb reboot bootloader, and run fastboot devices, I get an empty line.
When I run fastboot flashall -w, I get
< waiting for device >​When I run lsusb, the Google line is no longer displayed.
Also, I see in the /var/log/syslog that the Google device is added when I boot the phone, and is removed when I change to fastboot mode.
On reboot:
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950990] usb 1-2: Product: AOSP on HammerHead
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950992] usb 1-2: Manufacturer: LGE
Nov 11 00:13:03 LENOVO-W541 kernel: [ 2807.950993] usb 1-2: SerialNumber: 07c082820f1e64c0
Nov 11 00:13:03 LENOVO-W541 colord: Device added: sysfs-LGE-AOSP_on_HammerHead​In fastboot:
Nov 11 00:21:08 LENOVO-W541 kernel: [ 3293.100855] usb 1-2: USB disconnect, device number 105
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-(null)
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-(null)
Nov 11 00:21:08 LENOVO-W541 colord: device removed: sysfs-LGE-AOSP_on_HammerHead​
Can anyone help? I can't even do something as basic as flashing a new image to the phone.
Paul

Try
Code:
sudo fastboot devices

Found the problem (I think). Seems to be a stupid USB cable problem.
At work, with phone in fastboot/bootloader mode:
$ lsusb | grep Google
Bus 001 Device 098: ID 18d1:4ee0 Google Inc.​There seems to be a bug, because in normal mode, the same command gives:
Bus 001 Device 100: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)​At home, in fastboot mode this command gives nothing, just an empty line.
Similarly, at work, in fastboot mode:
$ fastboot devices
07c082820f1e64c0 fastboot​The same command at home gives:
<waiting for device>​
All with the same phone and laptop, just different cables.

After creating rules, did you reload them? either by rebooting or using udevadm?
What distro are you on?

beekay201 said:
After creating rules, did you reload them? either by rebooting or using udevadm?
What distro are you on?
Click to expand...
Click to collapse
beekay,
Yes, I had reloaded the rules, using sudo /etc/init.d/udev restart
Ubuntu 14.04. problem solved, as I indicated above.

"fastboot devices" shows no devices

Hi,
For some reason, "fastboot devices" shows no devices when I connect my LG G Stylo MS631 in the download mode (a.k.a. the firmware update mode) to the PC. Not sure why that is and what could be done about it.
Any ideas? Thanks

More info: when the phone in the dowload mode connected to the PC, in the log I see the following:
Feb 06 10.06:22 tst kernel: [969014.956096] usb 1-2: new high-speed USB device number 37 using ehci_hcd
Feb 06 10.06:22 tst kernel: [969015.172125] hub 1-0:1.0: unable to enumerate USB device on port 2
Feb 06 10.06:29 tst kernel: [969021.740096] usb 1-2: new high-speed USB device number 38 using ehci_hcd
Feb 06 10.06:29 tst kernel: [969021.874612] usb 1-2: New USB device found, idVendor=1004, idProduct=633e
Feb 06 10.06:29 tst kernel: [969021.874624] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 06 10.06:29 tst kernel: [969021.874633] usb 1-2: Product: LGE Android Phone
Feb 06 10.06:29 tst kernel: [969021.874640] usb 1-2: Manufacturer: LG Electronics Inc.
Feb 06 10.06:29 tst kernel: [969021.874647] usb 1-2: SerialNumber: LGxxxxxxxxxxxxx
"fastboot devices" still shows no devices though. Any ideas? Thanks