I tried all the solution you mentioned, i stell have the same erorr???
To start: Yes, I have searched the forums for similar items. There are no helpful responses. Hopefully this extra info helps.
Phone: HTC Evo 4G
OS: Cyanogenmod 7.1.0 Supersonic
Kernel Info: 2.6.37.6-cyanogenmod-01509-g8913be8
Background: I need to speak with serial devices via the USB port. The specific device I want to send data is an FTDI device. I am successfully communicating with the device via my Linux-based desktop. The challenge is porting my code to Android.
Here we go.
I started here: http://android.serverbox.ch/?p=285
To get the development environment and kernel for my phone I followed this:
http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source
When compiling my kernel I ran into a problem with the environment variables defined in the tutorial. I replaced CCOMPILE with CROSS_COMPILE and pointed it to my Code Sourcery install:
export CROSS_COMPILE=/home/LINUX_USER/Hardware/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-
I updated my kernel configuration (according to the FTDI tutorial) and tried to build the kernel and FTDI kernel module. My first attempt to "make" the kernel didn't work. I found this:
http://forum.xda-developers.com/archive/index.php/t-932190.html
Which provided me with a flag to get make to run:
# make EXTRA_AFLAGS=-mfpu=neon
The FTDI kernel module built successfully and I pushed the module to the SD card and tried to install module:
# /home/LINUX_USER/Hardware/android/android-sdk-linux/platform-tools/adb push drivers/usb/serial/ftdi_sio.ko /sdcard/
# insmod /sdcard/ftdi_sio.ko
insmod: init_module '/sdcard/ftdi_sio.ko' failed (Exec format error)
Since it didn't work I checked dmesg
# dmesg shows this:
[snip]
<3>[20821.873504] ftdi_sio: version magic '2.6.37.6-cyanogenmod-g996b70e preempt mod_unload ARMv7 ' should be '2.6.37.6-cyanogenmod-01509-g8913be8 preempt mod_unload ARMv7 '
I validated the kernel version on my phone and looked for a fix:
# uname -a
Linux localhost 2.6.37.6-cyanogenmod-01509-g8913be8 #1 PREEMPT Wed Jul 27 21:34:30 EDT 2011 armv7l GNU/Linux
The following tutorial provided me with instructions on how to address this issue:
http://glandium.org/blog/?p=2214
I changed the subversion number for the kernel by updating .scmversion to contain the following data:
-01509-g8913be8
After recompiling I tried to load the FTDI module again and got the following messages:
# insmod ftdi_sio.ko
insmod: init_module 'ftdi_sio.ko' failed (No such file or directory)
# dmesg | tail -15
<6>[58392.044647] batt: batt power_supply_changed: battery at 58389757684756 (2011-11-16 17:35:59.423392893 UTC)
<4>[58392.053100] at 58389762414981 (2011-11-16 17:35:59.413322092 UTC)
<4>[58413.600006] ftdi_sio: Unknown symbol usb_register_driver (err 0)
<4>[58413.602172] ftdi_sio: Unknown symbol usb_serial_handle_sysrq_char (err 0)
<4>[58413.604858] ftdi_sio: Unknown symbol usb_serial_disconnect (err 0)
<4>[58413.607910] ftdi_sio: Unknown symbol usb_serial_generic_open (err 0)
<4>[58413.610290] ftdi_sio: Unknown symbol usb_serial_generic_close (err 0)
<4>[58413.612609] ftdi_sio: Unknown symbol usb_control_msg (err 0)
<4>[58413.615142] ftdi_sio: Unknown symbol usb_deregister (err 0)
<4>[58413.617340] ftdi_sio: Unknown symbol usb_serial_generic_unthrottle (err 0)
<4>[58413.619262] ftdi_sio: Unknown symbol usb_serial_handle_break (err 0)
<4>[58413.622161] ftdi_sio: Unknown symbol usb_serial_generic_throttle (err 0)
<4>[58413.622955] ftdi_sio: Unknown symbol usb_serial_probe (err 0)
<4>[58413.624511] ftdi_sio: Unknown symbol usb_serial_register (err 0)
<4>[58413.630371] ftdi_sio: Unknown symbol usb_serial_deregister (err 0)
Since this failed I tried other compilers as well with the same results.
export CROSS_COMPILE=/home/LINUX_USER/Hardware/android/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
export CROSS_COMPILE=/home/LINUX_USER/Hardware/android/cyanogenmod/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
I need help understanding what I should try next.
Thank you,
cutaway
If you still haven't gotten it running I posted a kernel on the cyanogenmod site with these modules in /system/lib/modules.
Load usbcore.ko, usbserial.ko, then ftdi_sio.ko
Unfortunately I don't have any devices to test, so let me know if it works.
sbradymobile said:
If you still haven't gotten it running I posted a kernel on the cyanogenmod site with these modules in /system/lib/modules.
Load usbcore.ko, usbserial.ko, then ftdi_sio.ko
Unfortunately I don't have any devices to test, so let me know if it works.
Click to expand...
Click to collapse
Link please. I have looked but I cannot locate it.
Thank you,
cutaway
http://db.tt/JQVbCGQS
sbradymobile said:
Load usbcore.ko, usbserial.ko, then ftdi_sio.ko
Unfortunately I don't have any devices to test, so let me know if it works.
Click to expand...
Click to collapse
Okay, I tried but it failed for the reason I thought it would. The .scmversion extensions don't match the kernel I have. I am not going to load the whole kernel as I don't want to trouble shoot the whole system or worry about other issues.
I appreciate your effort.
I need somebody to help me understand why I can successfully build a kernel module with my kernel's .config but it does not have the proper symbols to run the module. I would have thought it would fail to compile. /me sighs
You need host mode for this to work, so the main issue is you have to strip out msm_hsusb and gadget code that is built in to the kernel. This means you need a new kernel image for this to work as there is no module to unload.
The kernel I posted earlier will not work because msm_hsusb is still registered on boot, preventing the ehci-hcd module from loading.
You can try this one if you like http://db.tt/0s7xRlYW; I was able to get ehci-hcd to load, but the dmesg output shows an irq problem.
It is the most recent CM7 kernel.
sbradymobile said:
You need host mode for this to work, so the main issue is you have to strip out msm_hsusb and gadget code that is built in to the kernel. This means you need a new kernel image for this to work as there is no module to unload.
The kernel I posted earlier will not work because msm_hsusb is still registered on boot, preventing the ehci-hcd module from loading.
You can try this one if you like link was here; I was able to get ehci-hcd to load, but the dmesg output shows an irq problem.
It is the most recent CM7 kernel.
Click to expand...
Click to collapse
Was you succeded to bring FTDI up and running?
Current Status: Brick
Hi,
I tried flashing stock SBF CEE 3.4.2-179-2 (retail central Europe) from here http://sbf.droid-developers.org/umts_jordan/list.php
I get IO and checksum errors resulting in FAIL. Now the phone does not boot.
Boot Loader
Code:
Bootloader
09.10
[B]Code Corrupt[/B]
Battery OK
OK to Program
Connect USB Data Cable
With RSD Lite 5.7 on Windows XP and MotoHelper drivers MotoHelper_2.0.40_Driver_4.9.0.exe
RSD Lite log::
2012/12/20 02:05:45 | -- | ERROR: AP Die ID: 1b10000791b963010000dcff0200
2012/12/20 02:05:45 | -- | ERROR: BP Die ID: 0000000000000000000000000000
2012/12/20 02:05:45 | -- | ERROR: AP Public ID: 35bc21063d231f528e8ce8e9b9942dcd161967c5
2012/12/20 02:05:45 | -- | ERROR: BP Public ID: 0000000000000000000000000000000000000000
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 ->(1557)FlashOp
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:13:03 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS ->(1511)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 65 checksums. File: 0x2409, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Flash failed. ->(1195)PST_FP_FlashThread
2012/12/20 02:26:03 | 0 | ERROR: Flash failure: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31 ->(625)FlashHdlr
Click to expand...
Click to collapse
Based on advice from skeevy420, I tried flashing with sbf_flash on linux.
sbf_flash:
Code:
Index[1]: Unexpected chip 32
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed
It looks like writing (or reading) fails, resulting in checksum errors.
More Info:
Verified MD5 of all my downloads
Tried a couple of other SBF from the same version (3.4.2)
Phone is from T-Mobile USA
Can I do something to change brick status?
Do I need a different SBF version?
Does read/write error really means hardware problem, cannot be fixed by software?
Do those IO errors mean driver version problem?
New sbf not compatible with old (old was stock T-Mobile Froyo)?
Accept the fact that the phone is hopeless?
Any help appreciated!
Here's a basic tutorial to flash sbf's with Linux -- RSDLite quit recognizing my Bravo and the Linux sbf_flash tool was the only way to fix it. You may have to install the Linux adb drivers, not sure, but those instructions are on Kayant's Compile CM10 thread (first post).
After flashing, you might have to go to factory recovery and wipe data and cache in order for the phone to boot -- maybe even have to flash a 2nd or 3rd time. I once had to flash the sbf AND wipe data\cache 5 times in a row in order to get my Bravo to boot up after accidentally flashing a Defy boot.img (usually only 1 flash is needed, I do stupid things with my phones)
Thanks, I will give this a try.
Do you install linux on the drive (like dual boot) or boot from a CD? If you boot from a CD, how do you install motorola drivers?
Just did MD5 checksum of all my downloaded files and they are all good.
Tried it with linux, getting similar errors:
Code:
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed
Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium
Just a silly idea: is your USB cable/PC USB port OK? Try it on another PC and with another cable. Use a cable as short as possible and make sure that the phone is the only device connected to the PC via USB including the mouse.
Sent from my MB526 using xda app-developers app
thekguy said:
Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, I think you are right.
I tried the omap option, did not help. Any other tweaks I can do to RSD light?
As far as USB, its the stock motorola cable. I disconnected everything from the computer, basically a laptop with nothing around it. I dont think its the problem, I tried over 10 sbfs and they all consistently show the same errors.
I am gonna hijack this thread...
So I believe I bricked the Defy I was supposed to be fixing.
It was acting up, the battery was sometimes showing a ? mark, and the rom it was flashed with was super buggy.
I decided to flash it with this sbf
Code:
T-Mobile_MB525_6.19.0_1FF
from here (Because I had read that it was the stock 2.1 Eclair from T-Mobile, the one the one was running originally.)
Now it won't boot.
Edit: The battery was dead. The cable was faulty so it cause a problem while flashing. Managed to get back at bootloader. Re-trying again but with:
Code:
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf
EDIT 2: The keyboard is not working so I can't logging into motoblur ._." Frustration... Going to keep flashing to see if its the screen of my phone or the actual program.
Edit 3: It appears it was the screen sensors being dirty. All solved.
-Defy MB525 GREEN LENS-
Any solution for this??
ChavitoArg said:
Any solution for this??
Click to expand...
Click to collapse
Try This
http://forum.xda-developers.com/showthread.php?t=1486731
I am having same problems flashing my defy. Tried different kinds of sbf using rsd lite but keep getting error verifying group code checksums from code 33 onwards...then flashing fails.
Any solutions??
Hi,
My Acer Iconia A500 is in serious trouble.
I use TWRP v2.1.3 and Bootloader Skrilax_CZ's V8.
My problem started with a loop at startup of Android, not passing the cyanogenmod load screen.
I had no backup to restore.
Used an external memory card to install android rom again.
But I can not mount / data.
In the TWRP screen:
- Install / sdcard/cm-100201211140-UNOFFICIAL-a500.zip ...
Fiding update package ...
Opening update package ...
Installing update ...
* Verifying filesystem ....
* Verifying partition sizes ...
E: Ubable to mount / data
E: Failed to mount / data (Invalid argument)
E: Failed to mount / data (Invalid argument)
The option to mount also can not check the option: mount data.
Could anyone help me?