Database Develop

[MODULES][ARC][NEO][FW:4.0.A.2.368] USB-OTG {Storage, Keyboard & Mouse}

GUYS I BRING GREAT NEWS!
WE NOW HAVE FUNCTIONAL USB-OTG SUPPORT!
[ screenshots ]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[ WARNING ]
do not use the connected device for a LONG time period... u may risk burning the device chip/motherboard due to the voltage supply in host mode...
u have been warned!
[ requirements ]
Xperia Arc (Neo?/Play?) on FW: 4.0.A.2.368
preferably rooted + busybox installed
USB-OTG hardware cable
Terminal Emulator app
[OPTIONAL] adb Wireless app
[ tested on ]
Xperia Arc Stock FW: 4.0.A.2.368 with DooMKernel v08
[ how to ] (general instructions for modules) [u can use this app to auto-load module]
download the modules and push the modules to /system/lib/modules/
use adb shell or terminal emulator to enter following code/commands
Code:
su
cd/system/lib/modules/
busybox insmod usbhid.ko
busybox insmod usbmouse.ko
busybox insmod usbkbd.ko
busybox insmod usb-storage.ko
check if all modules are live are not:
Code:
lsmod
done the modules are LIVE!
[IMP] u will have to manually reload the modules on EVERY boot... unless u use start-up scripts which will take care of this!
[ how to ] (instructions for usb-storage) [simpler way]
download app: http://android.gval.biz/download/Q5_USB_Memory_Manager.apk
follow instructions: http://android.gval.biz/Q5_USB_Menory_Manager.php
the usb storage device should now be mounted to /usb_storage/
u will need to use RootExplorer for this to work
[ how to ] (instructions for usb-storage) [manual way]
before u begin/connect device there are few things which need to be done
creating necessary directory structure
Code:
su
cd /sdcard/
mkdir usbStorage
chmod 777 usbStorage
now connect the usb storage device via usb-otg cable to phone
now enter the following command:
Code:
dmesg
at the last part u will see some info of connected device (an if it was rejected due to power issues)
now enter
Code:
ls -l /dev/block/sd*
u will get output similar to the one posted below
note if the last part: /dev/block/sda1
finally mount this device (following is generic command... for NTFS specific command read this post)
Code:
mount /dev/block/sda1 /sdcard/usbStorage
if u get no error then enjoy usb storage is now mounted
to unmount usbstorage (following is generic command)
Code:
umount /dev/block/sda1
if that doesnt work try the following command: (this will try to force unmount)
Code:
umount -f /dev/block/sda1
if that doesnt work try the following commandthis will try to force unmount and remove loop) [use this as LAST resort]
Code:
umount -f -l /dev/block/sda1
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ download links ]
USB-STORAGE
USB-HID
USB-KEYBOARD
USB-MOUSE
[ known issues ]
usb mouse works but there is no cursor... but u can move around and select (left click on stuff)
when using usb-storage mode some devices will not be mountable if:
they require more power (u can check this in dmesg)
they have filesystem not supported by ur current kernel
sometimes the mounted usb-storage files wont appear using some apps... i have tested it to be wrking using RootExplorer... though it will work in adb shell/terminal emulator also...
[ troubleshooting ]
when u post any error/issue please include the full output of dmesg command (adb shell dmesg > dmesg_log.txt) OR (dmesg > /sdcard/dmesg_log.txt)
P.S.: all these features will be included in next version of DooMKernel for all supported Xperia 2011 devices
enjoy!

reserved reserved

Good
can u add more
Example

Thank you very much DooMLoRD

Oh my god, it actually works Tried with my Microsoft Wireless Desktop thing with a wireless receiver. Couldn't get the keyboard to work, but the mouse works perfectly!

<3>[39396.128906] NTFS-fs error (device sda1): parse_options(): Unrecognized mount option shortname.
<3>[39396.128906] NTFS-fs warning (device sda1): parse_options(): Option utf8 is no longer supported, using option nls=utf8. Please use option nls=utf8 in the future and make sure utf8 is compiled either as a module or into the kernel.
<3>[39396.129943] NTFS-fs error (device sda1): parse_options(): NLS character set utf8 not found.
#
cant mount usbstick on neo :-(
Sent from my MT15i using Tapatalk

inteks said:
<3>[39396.128906] NTFS-fs error (device sda1): parse_options(): Unrecognized mount option shortname.
<3>[39396.128906] NTFS-fs warning (device sda1): parse_options(): Option utf8 is no longer supported, using option nls=utf8. Please use option nls=utf8 in the future and make sure utf8 is compiled either as a module or into the kernel.
<3>[39396.129943] NTFS-fs error (device sda1): parse_options(): NLS character set utf8 not found.
#
cant mount usbstick on neo :-(
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
but are the modules getting inserted properly?
wht does lsmod say?
also which kernel are u using?

Im using your latest kernel for neo. Lsmod is ok all modules are loaded. I think it because of missing utf8 in kernel.
Btw im tzping this on an connect usb keyboard , that works so far ;o) (but kezmapping...)
Btw. My usbgamepad does NOT work with FPSE ;-)
Here the dmesg output
<6>[40873.999359] hub 1-0:1.0: USB hub found
<6>[40873.999420] hub 1-0:1.0: 1 port detected
<6>[40874.316741] usb 1-1: new low speed USB device using msm_hsusb_host and address 2
<3>[40874.475799] usb 1-1: device v0583 p2060 is not supported
<6>[40874.475921] usb 1-1: New USB device found, idVendor=0583, idProduct=2060
<6>[40874.476013] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
<6>[40874.476104] usb 1-1: Product: USB,2-axis 8-button gamepad
<6>[40874.488586] usb 1-1: configuration #1 chosen from 1 choice
<6>[40874.501922] input: USB,2-axis 8-button gamepad as /devices/platform/msm_hsusb_host.0/usb1/1-1/1-1:1.0/input/input9
<6>[40874.502075] generic-usb 0003:0583:2060.0001: input: USB HID v1.10 Joystick [USB,2-axis 8-button gamepad ] on usb-msm_hsusb_host.0-1/input0
#
#
Sent from my MT15i using Tapatalk

sahha said:
Good
can u add more
Click to expand...
Click to collapse
i think that device will require a lot of power (to transmit/receive)... so it might not work...
Ambroos said:
Oh my god, it actually works Tried with my Microsoft Wireless Desktop thing with a wireless receiver. Couldn't get the keyboard to work, but the mouse works perfectly!
Click to expand...
Click to collapse
only low-power devices are supported... try using a power USB hub...
inteks said:
Im using your latest kernel for neo. Lsmod is ok all modules are loaded. I think it because of missing utf8 in kernel.
Btw im tzping this on an connect usb keyboard , that works so far ;o) (but kezmapping...)
Btw. My usbgamepad does NOT work with FPSE ;-)
Here the dmesg output
<6>[40873.999359] hub 1-0:1.0: USB hub found
<6>[40873.999420] hub 1-0:1.0: 1 port detected
<6>[40874.316741] usb 1-1: new low speed USB device using msm_hsusb_host and address 2
<3>[40874.475799] usb 1-1: device v0583 p2060 is not supported
<6>[40874.475921] usb 1-1: New USB device found, idVendor=0583, idProduct=2060
<6>[40874.476013] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
<6>[40874.476104] usb 1-1: Product: USB,2-axis 8-button gamepad
<6>[40874.488586] usb 1-1: configuration #1 chosen from 1 choice
<6>[40874.501922] input: USB,2-axis 8-button gamepad as /devices/platform/msm_hsusb_host.0/usb1/1-1/1-1:1.0/input/input9
<6>[40874.502075] generic-usb 0003:0583:2060.0001: input: USB HID v1.10 Joystick [USB,2-axis 8-button gamepad ] on usb-msm_hsusb_host.0-1/input0
#
#
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
have u tried v6?
http://forum.xda-developers.com/showthread.php?p=16651299&highlight=DooMKernel#post16651299
it has NLS-UTF8 support
about gamepads i dont know... will have to look into it... but neither do i have the xperia neo nor the usb gamepad

DooMLoRD said:
i think that device will require a lot of power (to transmit/receive)... so it might not work...
only low-power devices are supported... try using a power USB hub...
have u tried v6?
http://forum.xda-developers.com/showthread.php?p=16651299&highlight=DooMKernel#post16651299
it has NLS-UTF8 support
about gamepads i dont know... will have to look into it... but neither do i have the xperia neo nor the usb gamepad
Click to expand...
Click to collapse
flashed the new kernel (v6) but still cant mount ntfs ubsstick. (i dont have a fat32 stick here to test)

Script
You can use my simple script to load modules after each reboot
install Gscript Lite from market : https://market.android.com/details?id=nl.rogro.GScriptLite&feature=search_result
put ''Load Modules.sh'' to sdcard
in Gscript App select add script and than load file from sd card
you can load modules with one touch
for mount & umount you have to create folder as (0-USB) name manually on root of sdcard or edit scripts file with Gscript app for other folder name

inteks said:
flashed the new kernel (v6) but still cant mount ntfs ubsstick. (i dont have a fat32 stick here to test)
Click to expand...
Click to collapse
can u post the exact dmesg error?

DooMLoRD said:
can u post the exact dmesg error?
Click to expand...
Click to collapse
the same as with v5 kernel...
http://forum.xda-developers.com/showthread.php?p=16793689
Sent from my MT15i using Tapatalk
edit: i tried it just again without q5usb and it works with terminal -->> mount /dev/block/sda1 /sdcard/usbStorage

inteks said:
the same as with v5 kernel...
http://forum.xda-developers.com/showthread.php?p=16793689
Sent from my MT15i using Tapatalk
edit: i tried it just again without q5usb and it works with terminal -->> mount /dev/block/sda1 /sdcard/usbStorage
Click to expand...
Click to collapse
ya i am also having problem with that app...

NTFS
mount command for NTFS usb-storage devices:
Code:
chmod 777 /sdcard/usbStorage
Code:
busybox mount -t ntfs -o rw,umask=0000,uid=1000,gid=1015 /dev/block/sda1 /sdcard/usbStorage
with this command the files should now be visible under any standard file manager (not just RootExplorer)
there is still some issue with writing files to external device (NTFS) but we will figure something out soon

Worked like a charm for my usb stick, thanks. I got a cheap micro usb otg adapter from dealextreme that worked great.

In the latest ROM for Xperia Pro (4.0.A.261) there is an usbotg.apk in /system/app

MoridinBG said:
In the latest ROM for Xperia Pro (4.0.A.261) there is an usbotg.apk in /system/app
Click to expand...
Click to collapse
interesting... can u post it here?

DooMLoRD said:
interesting... can u post it here?
Click to expand...
Click to collapse
It is on the Arc and Neo .368 too. Nothing special, as far as I know it is the thing that says unsupported device connected. It's only 70kb so can't be much.
Sent from my MT15i using XDA App

Does it works on X10 ? Can u pls make it also possible )

[UPDATE][ICS] USB 3G Huawei Dongle Drivers

UPDATE - I have built the required kernel modules ( magic: 3.0.8+ SMP preempt mod_unload ARMv7) for ICS.
Download: archos-ics-gsm.zip
Remember these are only the kernel level drivers and a bit more hacking is required if you want to used these in the android environment.
Happy Hacking!
[ORIGINAL POST]
Hi
Here is the required kernel module (usb_wwan.ko) to enabled the modem functionality at the kernel level for Huawei 3G Dongles on the archos G9.
I don't know if anyone will find it useful but I thought I'd share it anyway
It was built from the archos-g9-gpl and is compatible with kernel version "2.6.35.7+ #1 SMP PREEMPT"
Notes:
Huawei USB 3G Modems actually require 2 modules to function usb_wwan.ko and option.ko. Archos already ship option.ko in /lib/modules on the device so this was the only one missing.
To use:
1. insmod usb_wwan.ko
2. insmod option.ko
3. Use usb_modeswitch to initialize the modem
The modem can be then be found at /dev/ttyUSB*
See this post for a quick guide into making a ppp connection using this driver
Thanks

I'm very interested in this. So I have a Huawei EC168 air card from a little cdma provider named Alltel (who is now partially owned by Verizon), would installing this allow it to function? I mean do you know if this is a universal driver or is it meant for GSM only?
I'm a bit of a noob at this. I've got the first two commands to run and usb_wwan.ko is just in my /mnt/storage
What are the specific switches I need to get the usb_modeswitch command working? -H just results in "No default vendor/product ID given. Aborting."
Btw I'm running everything through Terminal Emulator as I don't have adb or anything like that up and running currently on my computer.
Edit: I can't mess with this until I get hdd mounting working again. That was the whole reason I bought this tablet.
If anyone can help with that my topic is here. http://forum.xda-developers.com/showthread.php?p=22722509

I'm unsure whether this is a CDMA driver but you can give it a go.
From the command line I copied usb_wwan.ko to /lib/modules on the device and then did then following (the command should work equally as well in terminal emulator, with out the adb shell bit obviously )
Code:
adb shell insmod /lib/modules/usb_wwan.ko
adb shell insmod /lib/modules/option.ko
Then I Usb Mode Switched to the modem. I my case a Huawei E1752 [O2 UK Branded]
I discovered the correct target product [0x1436] (which isn't included in the 12d1_1446 config file) after plugging it into linux an listing my USB devices using lsusb in a terminal window.
Code:
adb shell usb_modeswitch -s 6 -v 12d1 -p 1446 -V 12d1 -P 1436 -M 55534243123456780000000000000011062000000100000000000000000000 > /dev/null
Obviously the usb modeswitch parameters are unique to your device and you can of course specify a configuration file using the -c switch instead of using the switches I have here.
After this I had access to the modem on the /dev/tttyUSB*
I gave the modem about 1 minute to initialize and then ran
Code:
adb shell /system/bin/pppd /dev/ttyUSB0 115200 nocrtscts nocdtrcts local usepeerdns defaultroute noipdefault ipcp-accept-local ipcp-accept-remote user cmnet password cmnet debug kdebug 7 connect "/system/xbin/chat -v -t 500 -s -f /data/media/gprs_start"
This brings up a PPP connection on ppp0. Although it didn't register as any sort of connection in android, it does however allow me to use the android web browser on this connection.
Note:
You do need 2 additional files which I have attached - The gprs_start script which I copied to the /data/media directory and is run by pppd and ip-up which you need to place in your /etc/ppp directory. This handles setting the correct dns servers after you have connected
This method is a little rough and I have been experimenting with the android ril interface but I'm having some problems keeping the connection alive for any length of time after starting the ril-daemon and I found the connection was at it's most stable when the ril-daemon is stopped.

Hi
trevd said:
It was built from the archos-g9-gpl and is compatible with kernel version "2.6.35.7+ #1 SMP PREEMPT"
Click to expand...
Click to collapse
Hi. how you install this kernel?
Add link

I didn't manage to get the full kernel to build because there was errors in the makefile last time in downloaded the source
out of more speculation than anything else I copied the makefile from the gen8 gpl source.
This didn't complete the build, it failed on ffmpeg but it did build kernel modules which is all I really needed for this.
I might have another go now that I understand a little more about the build process and makefiles.
Sent from my HTC Sensation XE with Beats Audio using xda premium

trevd said:
I didn't manage to get the full kernel to build because there was errors in the makefile last time in downloaded the source
out of more speculation than anything else I copied the makefile from the gen8 gpl source.
Click to expand...
Click to collapse
Current kernel sources are fine- compilation went without any problems. Included linux.config seems to be the recovery kernel config though (2.5 MB zImage, quite some modules built).
Compiled using crosstool-ng 1.9.3 on xubuntu 10.10 x86 (in VirtualBox)

hi, very interested in this, I have an Archos 80 G9 16GB Turbo and a Huawei USB 3G dongle as well. But I'm coming from windows mobile, just my first android device. Anyone willing to give some more info & instructions on how to get it working all together? Is it required to have a rooted device?
Maybe a little app can be created to automate the installation/usage of non archos USB 3G dongles?
CIAO!
VOODOOS!L

Hi Voodoos!l
Rooted Device is required. Apologies for the light instructions post 3 explains slightly more
It still may not be enough if your coming from a windows only environment!
I Assume at least some basic knowledge of:
Android Debug Bridge (ADB)
Composite Usb Devices (usb_modeswitch)
Android/Linux Kernel Modules (Installing insmod /lsmod etc)
Point to Point Protocol (How to start a connection)
I did write a quick and dirty app to do the mode-switching and then start the connection, I can give you the code if you want, it's nothing special, It just runs the commands from android using Superuser.
I've not had chance to work on this lately and I think a better route to go down is to hack the UsbKeyManager.apk which is what Archos use to turn on there own 3G Dongle. We should be able to modify it to accept any dongle. I had begun testing with HoneyComb but was waiting for ICS to appear before continuing.

i have archos 101 g9 can you have a video to do this?i have pen k3565 vodafone

@ trevd
i am very insteresting by a video or photos
and a todo for Dummys

Hi Guys.
I'll get the drivers compiled for ICS later on and see If I can get smoother solution for you folks to play with.
@jamespvz Is this the one you have http://3g-modem.wetpaint.com/page/Huawei+K3565+%28Vodafone%29? can you confirm that this is the one made by Huawei and not ZTE?
TIP: The Huawei one has the code K3565-H
Thanks
Trev

yes is that pen

Hi all.
I'm following this thread too because I need a 3g adapter but I found that the archos one is 7Mbps, while I'd like to have a 14Mbps one. Trevd, I hope that you will find the solution for me and the other archos fans!
If you suggest me a good adapter, I'll buy it and then help you with tests.
Thanks.
Bye

Hello
this work with ICS 4?
Regards, Robert

file is corrupt archos-ics-gsm.zip 554 byte ... resend please

h47e said:
file is corrupt archos-ics-gsm.zip 554 byte ... resend please
Click to expand...
Click to collapse
The file is not corrupt, i'ts correct 404 error html. But not zip, really.

# usb_modeswitch -s 6 -v 12d1 -p 1446 -V 12d1 -P 1436 -M 55534243123456780000000000000011062000000100000000000000000000
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
No devices in default mode found. Nothing to do. Bye.
# ls -la /dev/tty*
crw-rw-rw- 1 root root 5, 0 Apr 21 18:04 /dev/tty
crw------- 1 root root 249, 0 Apr 21 18:04 /dev/ttyGS0
crw------- 1 root root 249, 1 Apr 21 18:04 /dev/ttyGS1
crw------- 1 root root 249, 2 Apr 21 18:04 /dev/ttyGS2
crw------- 1 root root 249, 3 Apr 21 18:04 /dev/ttyGS3
crw------- 1 root root 252, 0 Apr 21 18:04 /dev/ttyO0
crw------- 1 root root 252, 1 Apr 21 18:04 /dev/ttyO1
crw------- 1 root root 252, 2 Apr 21 18:04 /dev/ttyO2
#dmesg
[ 2338.794708] hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 2338.795043] hub 1-0:1.0: unable to enumerate USB device on port 1
Bus 002 Device 013: ID 12d1:1446 Huawei Technologies Co., Ltd. E1552 (HSPA modem)
3g stick ON

[DEV] [ROMTEST] Debugging ICS KU5900 ROM on Optimus Black P970

This thread doesn't have ROM to download, so don't expect it happen soon!
It's an explanation or procedure to make ICS KU5900 boot on our our device P970.
Remember, just BOOT, not running perfect.
WARNING! This intended as development, so don't try this if you don't know what to do!
First, I'm using V30I. If you want to use V30G or V30H it might be different, I don't know, since I have deleted V30G and V30H so I'm not trying for G/H version.
This method are using Windows OS, and to debugging we need Linux OS.
I wont explain all in detail, I assume that you have your knowledge to do this.
PREPARING THE FILES
I get V30i KU5900 from here..
Code:
http://csmg.lgmobile.com:9002/swdata/RNDTESTSW/LGKU5900/KTF/G8MU86SJS7/V30i_00/V30I_00.kdz
Use this tools to decrypt and extract KDZ to BIN and FLS.
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=24083497&postcount=1"]http://forum.xda-developers.com/showpost.php?p=24083497&postcount=1[/URL]
Then proceed...
Code:
> copy /b KU5900_AP[?].bin+KU5900_AP[1?].bin KU5900_AP.bin
Use this tools to extract partition from BIN
Code:
[URL="http://forum.xda-developers.com/showpost.php?p=31476664&postcount=17"]http://forum.xda-developers.com/showpost.php?p=31476664&postcount=17[/URL]
Extract system.img and system2.img using this tools
Code:
[URL="http://www.diskinternals.com/linux-reader/"]http://www.diskinternals.com/linux-reader/[/URL]
Extract system.img to system and system2.img to system2
Put all files inside system2 to system/vendor
The list of directory supposed to be like this:
Code:
[URL="http://pastebin.com/sD2HKTSM"]http://pastebin.com/sD2HKTSM[/URL]
Download my customized boot.img
Code:
[URL="http://www.mediafire.com/?5klw4df6sf2wd8c"]http://www.mediafire.com/?5klw4df6sf2wd8c[/URL]
Download my updater-script to make flashable zip.
Code:
[URL="http://www.mediafire.com/?f6u97faa1abyrd9"]http://www.mediafire.com/?f6u97faa1abyrd9[/URL]
Cook! I use this...
Code:
[URL="http://forum.xda-developers.com/showthread.php?t=633246"]http://forum.xda-developers.com/showthread.php?t=633246[/URL]
adb push "zip" /sdcard
reboot recovery
Flash! and flashing means bootloop
------------------------------------------------------------------------------------------------------------
DEBUGGING
Because Windows OS not detecting the port, we need Linux OS, I'm using Ubuntu 12.04.
This sample are using my environment, so adapt or adjust yourself...
ATTENTION, If you adb without root permission, then you'll get this
Code:
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
???????????? no permissions
So, run adb with "sudo"
Code:
[email protected]:~$ cd sdk/platform-tools/
[email protected]:~/sdk/platform-tools$ sudo ./adb kill-server
[sudo] password for redy:
[email protected]:~/sdk/platform-tools$ sudo ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~/sdk/platform-tools$
Check connection,
Code:
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 1004:61d7 LG Electronics, Inc.
Perhaps your detected ID would be different.
Code:
[email protected]:~$ adb devices
List of devices attached
62F400029FFC00000000000000000000 device
Great, adb detected.... :victory:
Let's have fun with debugging....

It seems gabwerkz can have adb running in Windows OS. We'll see....

I Download this and try too

Use u-boot of V20. I used V20S
Logcat + dmesg all work Windows/Linux :victory:
I deleted apps... still it's almost full. Need delete more.

Do you guys still have the libsurfaceflinger error? How about trying the versions of 4.0.3 ICS build? I mean redy u already tested the 4.0.4 ones and they didnt work. Or do you think the error is really ramdisk dependent?

N00BY0815 said:
Do you guys still have the libsurfaceflinger error? How about trying the versions of 4.0.3 ICS build? I mean redy u already tested the 4.0.4 ones and they didnt work. Or do you think the error is really ramdisk dependent?
Click to expand...
Click to collapse
Mine still has it. But my firmware is V30G. Though redy uses V30I, I don't know why it errors out. Might be ramdisk.

I'm thinking about bootargs u-boot... at kernel log, see
Code:
Kernel command line: mem=511M init=/init videoout=omap24xxvout omap_vout_mod.video1_numbuffers=6 omap_vout_mod.vid1_static_vrfb_alloc=y vram=5M,0x9FA00000 omapfb.vram=0:5M lpj=2334720 rs=s fuelgauge=q muic_state=0 console=/dev/null
While KU5900 bootargs,
Code:
mem=512M init=/init videoout=omap24xxvout omap_vout.video1_numbuffers=6 omap_vout.vid1_static_vrfb_alloc=y vram=16M omapfb.vram=0:5M lpj=2334720 fuelgauge=g androidboot.hardware=black
and kernel log produce,
Code:
<3>[ 1.054168] omapfb omapfb: failed to allocate framebuffer
<3>[ 1.054290] omapfb omapfb: failed to allocate fbmem
<3>[ 1.054565] omapfb omapfb: failed to setup omapfb
<4>[ 1.054687] omapfb: probe of omapfb failed with error -12
And based on this, error -12 = Out of memory
Code:
[URL="http://www.omappedia.org/wiki/Frequently_Faced_Display_errors"]http://www.omappedia.org/wiki/Frequently_Faced_Display_errors[/URL]
So I think it because VRAM are not enough to load framebuffer.. u-boot V20 vram=5M, u-boot V30 vram=16M.
-CMIIW-

I read somewhere that korean one has only storage, cache and few software (bloatware) extra with our OB.
If camera is same and we have extractor working then is it not possible to just pick the camera HAL?

pkb_always4u said:
I read somewhere that korean one has only storage, cache and few software (bloatware) extra with our OB.
If camera is same and we have extractor working then is it not possible to just pick the camera HAL?
Click to expand...
Click to collapse
The source is needed since theirs is compiled for 3.0 not 2.6.
Sent from my LG Optimus Black

@Redy
Need to update your updater-script. you don't have permissions to vendor folder. Check what missing too, symlinks perhaps.
Code:
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");

I had a look at the u-boot from V20 (P970) and V30 (KU5900). They are in a totally different format and they don't even have the same file identifiers.
The kernel args are easy to find in the img but the u-boot image doesn't match that of anything I managed to find so I am not sure of the offsets. There is four 00 bytes after the bootargs that might be padding but it could also be the next things reserved bytes or something. So I can assume that it is padding and simple change the VRAM to 16 and use 1 of the four padding bytes but If it is not that then I am not sure what will happen.
I don't know where it splits of to SW Update and breaking the u-boot might make your device unrecoverable.It is a very small chance but it is a risk I'm not willing to take. The SW Update might be loaded from the ROM and then we can do pretty much whatever we want besides break it physically and we'll still be able to recover it. If someone knows more on this please tell me.
Have you guy tried using the u-boot from V20 of the KU5900. In the other thread they said they flashed that successfully ( It was part of the steps used to get it working on the KU5900 so they tried it. ).
Good luck.

gabwerkz said:
@Redy
Need to update your updater-script. you don't have permissions to vendor folder. Check what missing too, symlinks perhaps.
Code:
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
Click to expand...
Click to collapse
Actually, it's already setup by
Code:
set_perm_recursive(0, 0, 0755, 0644, "/system");
But I don't know if /system/vendor need owner of uid 2000
xonar_ said:
I had a look at the u-boot from V20 (P970) and V30 (KU5900). They are in a totally different format and they don't even have the same file identifiers.
The kernel args are easy to find in the img but the u-boot image doesn't match that of anything I managed to find so I am not sure of the offsets. There is four 00 bytes after the bootargs that might be padding but it could also be the next things reserved bytes or something. So I can assume that it is padding and simple change the VRAM to 16 and use 1 of the four padding bytes but If it is not that then I am not sure what will happen.
I don't know where it splits of to SW Update and breaking the u-boot might make your device unrecoverable.It is a very small chance but it is a risk I'm not willing to take. The SW Update might be loaded from the ROM and then we can do pretty much whatever we want besides break it physically and we'll still be able to recover it. If someone knows more on this please tell me.
Have you guy tried using the u-boot from V20 of the KU5900. In the other thread they said they flashed that successfully ( It was part of the steps used to get it working on the KU5900 so they tried it. ).
Good luck.
Click to expand...
Click to collapse
Well, I know that u-boot was used by SFT to manage recovery if we got bricked, and hacking via hex editor are considered dangerous if it might break u-boot port that read by SFT. So if we can't hack it, then leave it. I'm also won't take that risk
V20 KU5900 are having the same bootargs as V20 P970, vram=5M, so I assume that it still the same, won't work..
I'm under downloading Code Composer Studio (CCStudio) from TI, to try booting to u-boot environment and we might able to change the bootargs via u-boot console. I learn that actually we can enter u-boot environment, but I don't know how to do it for omap 3630, so it might be we can try using CCStudio to enter it. The concept does actually the same as SFT, it read the u-boot serial port which I think it might can be setup via NFS,
Code:
baudrate=115200 <-- I think it's the serial port
ipaddr=192.168.1.101
serverip=192.168.1.100
netmask=255.255.254.0
But, I don't know, I'm currently downloading the tools, haven't tried it yet...
-CMIIW-

redy2006 said:
Well, I know that u-boot was used by SFT to manage recovery if we got bricked, and hacking via hex editor are considered dangerous if it might break u-boot port that read by SFT. So if we can't hack it, then leave it. I'm also won't take that risk
V20 KU5900 are having the same bootargs as V20 P970, vram=5M, so I assume that it still the same, won't work..
I'm under downloading Code Composer Studio (CCStudio) from TI, to try booting to u-boot environment and we might able to change the bootargs via u-boot console. I learn that actually we can enter u-boot environment, but I don't know how to do it for omap 3630, so it might be we can try using CCStudio to enter it. The concept does actually the same as SFT, it read the u-boot serial port which I think it might can be setup via NFS,
Code:
baudrate=115200 <-- I think it's the serial port
ipaddr=192.168.1.101
serverip=192.168.1.100
netmask=255.255.254.0
But, I don't know, I'm currently downloading the tools, haven't tried it yet...
-CMIIW-
Click to expand...
Click to collapse
If you can get a u-boot connection while in sw update mode then we can read from the device and get a disk dump. That would help a lot. I tried doing it but the I could get no data from the serial connection. Succesfully established but nothing, probably missed a fairly significant detail somewhere. The recovery might be something like nand write that can be configured by the ROM without full u-boot.(Still not a risk I'm willing to take). If it has a IP Address then it needs u-boot set up properly though but SFT asks for a Direct Serial Port so that's why I'm not sure.
The baudrate is the bitrate at which it can communicate. If you can get a u-boot connection and enter u-boot terminal please tell me how .

CCStudio aren't f*cking running in my computer...
xonar_ said:
The baudrate is the bitrate at which it can communicate. If you can get a u-boot connection and enter u-boot terminal please tell me how .
Click to expand...
Click to collapse
Hmm, I'm thinking probably something like this..
Code:
[URL="https://www.ridgerun.com/developer/wiki/index.php/Setting_up_Picocom_-_Ubuntu"]https://www.ridgerun.com/developer/wiki/index.php/Setting_up_Picocom_-_Ubuntu[/URL]
You need to know the name of the serial port. Also, you should have read/write permissions to the serial port. Typical serial port names are /dev/ttyS0 for PCs with a built-in serial port and /dev/ttyUSB0 if you are using a USB to serial dongle.
picocom is wonderful in that you can specify all the serial port setting as parameters on the command line. For 115,200 baud (-b 115200), 8 bits (default setting), no parity (default setting), no flow control (default setting), and with no port reset (-r) and no port locking (-l), use:
Code:
picocom -b 115200 -r -l /dev/ttyUSB0
Click to expand...
Click to collapse
See that baudrate are the same value to ours...
Maybe we can test it, while on mode SFT recovery...
But but "picocom" need Linux environment. I can't test it now, since I'm at the office..

redy2006 said:
CCStudio aren't f*cking running in my computer...
Hmm, I'm thinking probably something like this..
Code:
[URL]https://www.ridgerun.com/developer/wiki/index.php/Setting_up_Picocom_-_Ubuntu[/URL]
See that baudrate are the same value to ours...
Maybe we can test it, while on mode SFT recovery...
But but "picocom" need Linux environment. I can't test it now, since I'm at the office..
Click to expand...
Click to collapse
Picocom doesent work. Just tried on your behalf. I get the same baudrate
Sent from my LG Optimus Black using Tapatalk 2

SoulExertz said:
Picocom doesent work. Just tried on your behalf. I get the same baudrate
Click to expand...
Click to collapse
Okay, test mode...
Code:
[email protected]:~$ [B][COLOR="blue"]lsusb[/COLOR][/B]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[B]Bus 001 Device 002: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000[/B]
[email protected]:~$ [B][COLOR="Blue"]sudo modprobe usbserial vendor=0x1004 product=0x6000[/COLOR][/B]
[email protected]:~$ [COLOR="blue"][B]dmesg[/B][/COLOR]
--wraped--
[ 746.531997] usbcore: registered new interface driver usbserial
[ 746.532075] USB Serial support registered for generic
[ 746.532106] usbserial_generic 1-4:1.0: Generic device with no bulk out, not allowed.
[ 746.532119] usbserial_generic: probe of 1-4:1.0 failed with error -5
[ 746.532133] usbserial_generic 1-4:1.1: generic converter detected
[ 746.532788] usb 1-4: generic converter now attached to [B]ttyUSB0[/B]
[ 746.532811] usbserial_generic 1-4:1.2: generic converter detected
[ 746.533721] usb 1-4: generic converter now attached to ttyUSB1
[ 746.533758] usbcore: registered new interface driver usbserial_generic
[ 746.533762] usbserial: USB Serial Driver core
[email protected]:~$ [B][COLOR="Blue"]sudo picocom -b 115200 -r -l /dev/ttyUSB0[/COLOR][/B]
picocom v1.4
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
noinit is : no
noreset is : yes
nolock is : yes
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv
Terminal ready
Skipping tty reset...
Thanks for using picocom
[email protected]:~$

I am currently trying to use OMAPFlash. Apparently OMAP boards are capable of booting from serial. If we can get that to work we can recover even if we wiped uboot completely. We can also test uboot changes without flashing it onto the device.
I got stuck at now reboot the board...
It's possible LG removed this or changed this. There is a download that is a way to get it working on I9003 that I haven't looked at yet.
There is also a Tool LG Flash that I haven't looked at yet.
Sent from my LG Optimus Black
---------- Post added at 12:46 PM ---------- Previous post was at 12:43 PM ----------
SoulExertz said:
Picocom doesent work. Just tried on your behalf. I get the same baudrate
Sent from my LG Optimus Black using Tapatalk 2
Click to expand...
Click to collapse
Don't select ttyS0 like the link says ,that's the serial connection on the motherboard. Use lsusb to get the USB device and its corresponding serial port.
Sent from my LG Optimus Black

xonar_ said:
I am currently trying to use OMAPFlash. Apparently OMAP boards are capable of booting from serial. If we can get that to work we can recover even if we wiped uboot completely. We can also test uboot changes without flashing it onto the device.
I got stuck at now reboot the board...
Click to expand...
Click to collapse
Which one the tools of OMAPFlash?
xonar_ said:
Don't select ttyS0 like the link says ,that's the serial connection on the motherboard. Use lsusb to get the USB device and its corresponding serial port.
Click to expand...
Click to collapse
I have connected with u-boot, but how we can enter the terminal command?

redy2006 said:
Which one the tools of OMAPFlash?
Click to expand...
Click to collapse
This one : OMAPFlash
I just read it doesn't work well with Win7 so my Consumer Preview Win8 isn't going to fair much better,
redy2006 said:
I have connected with u-boot, but how we can enter the terminal command?
Click to expand...
Click to collapse
Nice. No Idea never used picocom before.

Whats the proposite of bugging that rom on our black? Are u trying to boot that room on our black?
Sorry about the noob question
Enviado desde mi LG-P970 usando Tapatalk 2

GUIDE: connect OP3 with MTP on Linux (ubuntu)

I got my OP3 today and my laptop, running ElementaryOS (ubuntu based) didn't recognize the OP3 as MTP,
Here is a guide how to fix this, I based this guide on this guide for the OP2.
steps:
Do NOT connect your OP3 to your pc
run the command "lsusb" from your terminal
Connect your OP3 to your pc with original cable
run the command "lsusb" again
You will see a new device, my OP3 is called " Bus 001 Device 012: ID 05c6:900e Qualcomm, Inc. "
You see that it has an ID, in my case "05c6:900e".
the first value is the vendor-id, the second the product-id, you need those so write them down!
so in my case it's :
vendor id: 05c6
product id: 900e
Install the MTP drivers: "sudo apt-get install libmtp-dev mtpfs"
edit the following file with the command: "sudo gedit /lib/udev/rules.d/69-libmtp.rules"
if you don't have gedit installed use the command: "sudo nano /lib/udev/rules.d/69-libmtp.rules"
Add the following line to the file:
Code:
ATTR{idVendor}=="[COLOR="Blue"]vendor-id[/COLOR]", ATTR{idProduct}=="[COLOR="blue"]product-id[/COLOR]", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", TAG+="uaccess"
make sure you change the blue values to your own values found in the step above.
safe the file
restart the service: "sudo service udev restart"
If you did it correct you will see a popup on your OP3, select "File Transfers (MTP)", select that and now you can transfer files between your OP3 and linux
I don't know if the vendor-id and/or product-id are always the same, if some people can confirm that then I will edit the post.

Hey, I got the same vendor id and product id as you did.
However, even after following the procedure step-by-step, I am unable to transfer files between my OP3 and my laptop running Ubuntu 12.04 LTS.
The OnePlus drivers folder gets loaded as a CD(though I'm connecting the phone using USB) when I change the "Use USB for" setting to "File Transfer(MTP)," and the file named "adb_config_Linux_OSX.sh" doesn't do anything when run in terminal either.
Could you help me out with this?

I run Ubuntu 16.04 and needed to install any drivers. simply connect op and I was able to access it.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

krankyvampire25 said:
Hey, I got the same vendor id and product id as you did.
However, even after following the procedure step-by-step, I am unable to transfer files between my OP3 and my laptop running Ubuntu 12.04 LTS.
The OnePlus drivers folder gets loaded as a CD(though I'm connecting the phone using USB) when I change the "Use USB for" setting to "File Transfer(MTP)," and the file named "adb_config_Linux_OSX.sh" doesn't do anything when run in terminal either.
Could you help me out with this?
Click to expand...
Click to collapse
update: In "设置" -"其他设置" - "内部设备和USB" - "USB计算机连接", select -- "File Transfers (MTP)", everything is ok.
14.04 can't transfer file. a folder cant write anything(not cd image folder).

hi....... i have a other problem with the same OS (Ubuntu 16.04)
MTP works
fastboot works
ADB DON'T !!!
do you know why ?????
ADB and fastboot are working at the same device with Win 10
OK, thanks, forget it, i found a file named "adb_config_Linux_OSX.sh" on the phone and run it...... now it works

ty, it worked after two reboots and a system update. btw, i have the OP3 soft gold with ID 2a70:f003
cheers!

washichi said:
I got my OP3 today and my laptop, running ElementaryOS (ubuntu based) didn't recognize the OP3 as MTP,
Here is a guide how to fix this, I based this guide on this guide for the OP2.
steps:
Do NOT connect your OP3 to your pc
run the command "lsusb" from your terminal
Connect your OP3 to your pc with original cable
run the command "lsusb" again
You will see a new device, my OP3 is called " Bus 001 Device 012: ID 05c6:900e Qualcomm, Inc. "
You see that it has an ID, in my case "05c6:900e".
the first value is the vendor-id, the second the product-id, you need those so write them down!
so in my case it's :
vendor id: 05c6
product id: 900e
Install the MTP drivers: "sudo apt-get install libmtp-dev mtpfs"
edit the following file with the command: "sudo gedit /lib/udev/rules.d/69-libmtp.rules"
if you don't have gedit installed use the command: "sudo nano /lib/udev/rules.d/69-libmtp.rules"
Add the following line to the file:
Code:
ATTR{idVendor}=="[COLOR="Blue"]vendor-id[/COLOR]", ATTR{idProduct}=="[COLOR="blue"]product-id[/COLOR]", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", TAG+="uaccess"
make sure you change the blue values to your own values found in the step above.
safe the file
restart the service: "sudo service udev restart"
If you did it correct you will see a popup on your OP3, select "File Transfers (MTP)", select that and now you can transfer files between your OP3 and linux
I don't know if the vendor-id and/or product-id are always the same, if some people can confirm that then I will edit the post.
Click to expand...
Click to collapse
I just now happened upon this forum because my OP3 wasn't connecting for file transfers over USB. This worked like a charm for me; the vendor and product IDs were different (as I'm sure others have commented already), thank you for putting this out there, I definitely hit that 'thanks' button!!!!!!!

It's also possible to use this script (Vendor & Product id can differ).
Code:
#!/bin/sh
# adb configuration script
PATH=$PATH:/bin:/sbin:/usr/sbin
ANDROID_HOME=~/.android
ANDROID_CONFIG=~/.android/adb_usb.ini
CUST_VID="0x2a70"
if [ -e $ANDROID_HOME ] ; then
echo "android home is exist!"
else
echo "creat android home!"
mkdir $ANDROID_HOME
fi
grep $CUST_VID $ANDROID_CONFIG 2>/dev/null
if [ $? -eq 0 ] ; then
echo VID $CUST_VID is already configured..
echo "adb should be OK!"
exit 0
else
echo config adb ...
echo $CUST_VID >> $ANDROID_CONFIG
fi
adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "try sudo exec adb.."
sudo adb kill-server
if [ $? -eq 0 ] ; then
echo "OK! You can use adb now!"
exit 0
else
echo "Please do command \"adb kill-server\""
fi
fi
exit 0
Useful link: https://wiki.archlinux.org/index.php/android#Android_Debug_Bridge_.28ADB.29

Thanks a lot washichi It worked liked a charm on my OnePlus3T. Thanks a ton

Try to port Ubuntu Touch for Moto G 2014

Hi , i'm trying to port Ubuntu Touch for Moto G 2014
can any one help me to resolve this error
make: *** No rule to make target '/home/walid/phablet/out/host/linux-x86/framework/signapk.jar', needed by '/home/walid/phablet/out/target/product/titan/obj/APPS/TimeService_intermediates/TimeService.apk'. Stop.
Edit :
I'm in the end step of booting
[ 7.433841,1] initrd: mounting /dev/disk/by-partlabel/boot as /root/android//boot
[ 7.454993,3] initrd: checking mount label recovery
[ 7.457615,0] initrd: mounting /dev/disk/by-partlabel/recovery as /root/android//recovery
[ 7.497315,3] initrd: checking mount label mmc_host*
[ 7.517051,2] initrd: checking mount label usb1
[ 7.554915,0] initrd: checking mount label zram0
[ 7.558913,1] initrd: mounting /dev/zram0 as /root/android/none
[ 7.563701,1] initrd: mounting /root/var/lib/lxc/android/system.img as /root/android/system
[ 7.631982,1] systemd-udevd[181]: Validate module index
At this point the system try to mount system.img
But after that the system crash
[ 7.998344,1] Crash partition in use!
[ 8.998513,1] wcnss crash shutdown 0
[ 8.998592,1] Rebooting in 5 seconds..
[ 13.998672,1] Going down for restart now
[ 13.999581,1] failed to disable wdog debug: -4
[ 13.999672,1] Calling SCM to disable SPMI PMIC arbiter
PREV
Linux version 3.4.42-g832c593-dirty ([email protected]) (gcc version 4.8 (GCC) ) #5 SMP PREEMPT Thu Feb 2 21:02:43 UTC 2017
full log her,
https://drive.google.com/file/d/0B-F-xs4jYP12dWdsWGFXYlpIeEU/view?usp=sharing
Can any one help me please
Edit again:
Ubuntu Touch now work in my phone , yes work , but no RIL, no Camera and no Wifi.
I will start fix this bugs as soon as possible
https://drive.google.com/file/d/0B-F-xs4jYP12ellZQ25FR05SWVk/view?usp=sharing

walidham said:
Hi , i'm trying to port Ubuntu Touch for Moto G 2014
can any one help me to resolve this error
make: *** No rule to make target '/home/walid/phablet/out/host/linux-x86/framework/signapk.jar', needed by '/home/walid/phablet/out/target/product/titan/obj/APPS/TimeService_intermediates/TimeService.apk'. Stop.
Click to expand...
Click to collapse
ask to dev by PM nobody responde here

marianoasis said:
ask to dev by PM nobody responde here
Click to expand...
Click to collapse
thanks, i resolved the error by adding signapk.jar in out/host/linux-x86/framework.
The problem now, in deodexed apk file(TimeService.apk...) , i will try disabled it in build.

walidham said:
thanks, i resolved the error by adding signapk.jar in out/host/linux-x86/framework.
The problem now, in deodexed apk file(TimeService.apk...) , i will try disabled it in build.
Click to expand...
Click to collapse
good luck with that. and happy new year dude!

marianoasis said:
good luck with that. and happy new year dude!
Click to expand...
Click to collapse
Thanks,
I have compiled and generated boot.img, system.img and recovery.img
But after installation, phone can't boot.
Now come the real work, i will fix boot first (i must see ubuntu touch start).
Happy new year

marianoasis said:
good luck with that. and happy new year dude!
Click to expand...
Click to collapse
Hi
I compiled Source code based on ubport ub5.1 using CM12.1 device tree
recovery.img work fine, i can boot in recovery mod (Ubports Recovery)
But boot.img is big i got this error
error: /home/walidham/ub5/out/target/product/titan/boot.img too large (10729472 > [10771200 - 270336])
Can any one help me how i can reduce boot.img size ?

walidham said:
Hi
I compiled Source code based on ubport ub5.1 using CM12.1 device tree
recovery.img work fine, i can boot in recovery mod (Ubports Recovery)
But boot.img is big i got this error
error: /home/walidham/ub5/out/target/product/titan/boot.img too large (10729472 > [10771200 - 270336])
Can any one help me how i can reduce boot.img size ?
Click to expand...
Click to collapse
Did you resolved the error(making boot.IMG smaller).... After compiling what did you get zimage or boot.img directly.....????

radelpha said:
After compiling what did you get zimage or boot.img directly.....????
Click to expand...
Click to collapse
when i change max size in BoardConfig.mk, after compilation i have 3 files : system.img, recovery.img and boot.img and others files like ramdisk_android.img, ramdisk_ubuntu.img, dt.img....
But still can't flash boot.img (failled due to the size is big).
I'm now trying to delete unneeded drivers and files in device tree and hope will work

walidham said:
when i change max size in BoardConfig.mk, after compilation i have 3 files : system.img, recovery.img and boot.img and others files like ramdisk_android.img, ramdisk_ubuntu.img, dt.img....
But still can't flash boot.img (failled due to the size is big).
I'm now trying to delete unneeded drivers and files in device tree and hope will work
Click to expand...
Click to collapse
Hmmm... Give it a try... Try unpacking the boot.IMG(Ubuntu) and unpack stock titans boot.IMG then replace its zimage(stock) with ubuntu's zimage then repack it.... Hope this works.....

radelpha said:
Hmmm... Give it a try... Try unpacking the boot.IMG(Ubuntu) and unpack stock titans boot.IMG then replace its zimage(stock) with ubuntu's zimage then repack it.... Hope this works.....
Click to expand...
Click to collapse
When i just unpack and repack the boot.img generated, the size is reduced (10.8mb to 9.5mb), i don't know why?, i got 5 files :
boot.img-base,
boot.img-cmdline,
boot.img-pagessize,
boot.img-ramdisk.gz and
boot.img-zimage
I will try your idea

walidham said:
When i just unpack and repack the boot.img generated, the size is reduced (10.8mb to 9.5mb), i don't know why?, i got 5 files :
boot.img-base,
boot.img-cmdline,
boot.img-pagessize,
boot.img-ramdisk.gz and
boot.img-zimage
I will try your idea
Click to expand...
Click to collapse
Yes.... Flash this boot.IMG with only fastboot or else it won't work.....

Now i have the three files : recovery.img, boot.img and systme.img based on cm-12.1
recovery work , but after flashing boot and system , phone stop in moto logo,
Her some logs :
<3>[ 2.643604,2] init: failed to open '/sys/class/graphics/fb1/msm_fb_type'
<3>[ 2.643745,2] init: failed to open '/sys/class/graphics/fb2/msm_fb_type'
<3>[ 2.644593,2] init: Unable to open persistent property directory /data/property errno: 2
<6>[ 2.763154,0] cpr_scale: Down: cpr status = 0x000025dd (error_steps=7)
<3>[ 0.947143,0] mdss_mdp_parse_dt_prop_len: Error from prop qcom,mdss-ad-off : spec error in device tree
<4>[ 1.077626,1] mmi_factory: probe of factory_support.71 failed with error -16
Can any one help me

I'm in the end step of booting
[ 7.433841,1] initrd: mounting /dev/disk/by-partlabel/boot as /root/android//boot
[ 7.454993,3] initrd: checking mount label recovery
[ 7.457615,0] initrd: mounting /dev/disk/by-partlabel/recovery as /root/android//recovery
[ 7.497315,3] initrd: checking mount label mmc_host*
[ 7.517051,2] initrd: checking mount label usb1
[ 7.554915,0] initrd: checking mount label zram0
[ 7.558913,1] initrd: mounting /dev/zram0 as /root/android/none
[ 7.563701,1] initrd: mounting /root/var/lib/lxc/android/system.img as /root/android/system
[ 7.631982,1] systemd-udevd[181]: Validate module index
At this point the system try to mount system.img
But after that the system crash
[ 7.998344,1] Crash partition in use!
[ 8.998513,1] wcnss crash shutdown 0
[ 8.998592,1] Rebooting in 5 seconds..
[ 13.998672,1] Going down for restart now
[ 13.999581,1] failed to disable wdog debug: -4
[ 13.999672,1] Calling SCM to disable SPMI PMIC arbiter
PREV
Linux version 3.4.42-g832c593-dirty ([email protected]) (gcc version 4.8 (GCC) ) #5 SMP PREEMPT Thu Feb 2 21:02:43 UTC 2017
full log her,
https://drive.google.com/file/d/0B-F...ew?usp=sharing

Stuck in boot animation
https://drive.google.com/file/d/0B-F-xs4jYP12dWFlSUVqTmV3RDQ/view?usp=sharing

Ubuntu Touch now work in my phone , yes work , but no RIL, no Camera and no Wifi.
I will start fix this bugs as soon as possible

@walidham i try to port using cm 13.1 what you defconfig ? thanks, and good work, waiting for fix ...

horuxan said:
@walidham i try to port using cm 13.1 what you defconfig ? thanks, and good work, waiting for fix ...
Click to expand...
Click to collapse
Sorry, you want port Ubuntu Touch using cm-13.0 ?
If yes, you must change titan_defconfig using this script
https://github.com/janimo/phablet-porting-scripts
But you must disable some flags like CONFIG_DEBUG_RODATA

Congo for your first boot... and please contact @h2o64 as he ported ubuntu touch to moto g 2013.... Hope he will help you

walidham said:
Sorry, you want port Ubuntu Touch using cm-13.0 ?
If yes, you must change titan_defconfig using this script
https://github.com/janimo/phablet-porting-scripts
But you must disable some flags like CONFIG_DEBUG_RODATA
Click to expand...
Click to collapse
thanks @walidham )))) :fingers-crossed:
---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------
walidham said:
Sorry, you want port Ubuntu Touch using cm-13.0 ?
If yes, you must change titan_defconfig using this script
https://github.com/janimo/phablet-porting-scripts
But you must disable some flags like CONFIG_DEBUG_RODATA
Click to expand...
Click to collapse
thanks @walidham )))) :fingers-crossed: