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
Related
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
Yup. I have similar experiences on my linux box.
Try adb shell and see if you get a shell into the device.
ketchupotamus said:
I've been trying in vain to get adb recognize my vogue running android. Specs:
Phone:
- HTC Vogue CDMA
- Antenna version 3.42.50
- myn warm donut 320x480 (16-03-2010)
- NAND installation of dzo's voguimg-320x480 (26-03-10)
- USB debugging enabled.
Dev Environment:
- Android SDK 2.1 + Eclipse ADT + Ubuntu 9.10
Contents of /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",MODE="0666"
The server is being started/killed as root:
# ./adb kill-server
# ./adb start-server
lsusb output:
<snip>
Bus 006 Device 002: ID 0bb4:0c02 High Tech Computer Corp.
<snip>
When I scan for devices using # ./adb devices, I get this output:
???????????? device
Anyone else??
Click to expand...
Click to collapse
the one time I had that problem, killing and starting adb fixed it, but it looks like you're already doing that.
Try launching Eclipse?
When I had the same setup as you (ubuntu 9.10 + Eclipse + all relevant parts), adb "just worked".
Running under Vista32bit though, adb only works when I have Eclipse running. Don't know why. Don't care why. Felt like banging my head into a wall when I realized that. (More specifically: under Vista32bit, my Vogue shows up with only one question mark, not a whole slew like you have.)
Anyway, try making sure Eclipse is running when you try to connect via adb. Who knows. Maybe it's a cross-platform issue.
Thanks for the reply. Everything works fine in Windows Vista 32bit, although the device serial number shows up as a question mark. I read somewhere that adb is broken for the 2.6.27+ kernels. There is a proposed fix:
review.source.android.com/#patch,sidebyside,10633,1,adb/usb_linux.c
I've compiled the source, tried the new adb and still not working... maybe the next official release will be better.
I shell access and can browse filesystem with adb shell, but ddms in Eclipse doesn't show much useful information.
Excellent work by the way! And thank you.
Found a compiled version of adb with the fix highlighted on code.google.com:
h t t p ://floe.butterbrot.org/external/adb.gz
Don't forget to make it executable.
That worked for me
This was hard to find. Thanks.
I just installed Android on my Sprint touch vogue. No luck using adb to get a shell on my phone.
My environments are Debian sid 2.6.32 and/or OS X Snow Leopard. I installed the r06 SDK and adb doesn't work under either OS. ./adb devices shows nothing, ./adb shell shows device not found. Under debian, I downloaded the recompiled version of adb linked above, no change
dmesg shows:
Code:
usb 1-3.2: USB disconnect, address 28
usb 1-3.2: new full speed USB device using ehci_hcd and address 31
usb 1-3.2: New USB device found, idVendor=0bb4, idProduct=0c02
usb 1-3.2: New USB device strings: Mfr=3, Product=2, SerialNumber=0
usb 1-3.2: Product: Android Phone
usb 1-3.2: Manufacturer: HTC
usb 1-3.2: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 31
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
sd 9:0:0:0: Attached scsi generic sg2 type 0
sd 9:0:0:0: [sdb] Attached SCSI removable disk
Thanks for any help.
Might have figured something out that can help. uninstall the mass storage driver. I just did this and it connected right up.
HOWTO: Compile USB Host Enabled Kernel for the G1/Dream
Hi everyone,
I've got my new HTC Dream and I love it. It's my first Android based device. Now I'm running CyanogenMod 6 Rom.
So this is what I have:
Model number: HTC Dream
Andreoid ver: 2.2
Kermel ver: 2.6.34.5-cynogenmod
Mod version: CyanodenMod-6.0.0-DS
Build number: FRF91
I followed these guides to compile usb host enabled kernel. Please thank Andrew de Quincey, Sven Killig , Michael Mitchell and Frank Sposaro for their awesome work.
Preparing Android Build Environment
mkdir ~/cm-kernel-usbhost/
cd ~/cm-kernel-usbhost/
git clone git://github.com/CyanogenMod/cm-kernel.git
cd cm-kernel
git branch -r
git checkout --track -b cm-2.6.34 origin/android-msm-2.6.34
Patch the kernel source tree
wget http://sven.killig.de/android/N1/2.2/usb_host/android-kernel_msm-bca5320_Nexus-One_usb-host.patch
patch -p1 < android-kernel_msm-bca5320_Nexus-One_usb-host.patch
open ~/cm-kernel-usbhost/ cm-kernel /drivers/usb/host/ehci-msm7201.c and delete line 313
Export a variable for the ARM cross compiler
export CCOMPILER=~/android-ndk-r4b/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi-
Download kernel .config here and move to .config
Edit!: Use attached config file!
mv g1-cm-kern-2.6.34-usbhost.config .config
Then start the build:
make ARCH=arm CROSS_COMPILE=$CCOMPILER
At this point you should have a kernel stored in ~/cm-kernel-usbhost/cm-kernel/arch/arm/boot/zImage
Now, get the kernel on the phone:
I use fastboot to boot from RAM (not persistent)
~/android-sdk-linux_86/tools/fastboot boot arch/arm/boot/zImage
Look above at the output from the kernel build. The last thing completed is the module building (total = modpost). Notice the hierarchal structure of the compiled modules within the filesystem. Ex: /system/drivers/usb/core/usbcore.ko
Copy modules to sdcard
Now we need to load the modules into the running kernel.
Open a terminal emulator on the phone (connectbot also works, connect to local)
get root:
su
then load the usb core and ehci modules:
insmod /sdcard/usbcore.ko
insmod /sdcard/ehci-hcd.ko
You can download compiled kernel and modules here.
Hope that this guide will be helpful to newbies like me.
Regards,
Andy
NB!
This kernel currently disables USB mount and adb over USB.
usb-storage.ko module is loaded fine but when a usb flash drive is pluged-in the phone reboots itself.
You need a powered hub or Y-cable and USB A Female / A Female Adaptor to connect your usb devices.
Now wifi is working!
UPDATE: 11.12.2010
How to make an OTA package and switch between usb host and otg.
wget ww2.cs.fsu.edu/~mitchell/android/ZipBuilder.tar
tar -xvf ZipBuilder.tar
cd ZipBuilder
./builder.sh
rename update_signed.zip usbhost_signed.zip and copy it to sd card.
make a Nandorid backup and split boot.img using split_bootimg.pl
rename boot.img-kernel to zImage and copy it to ~/cm-kernel-usbhost/cm-kernel/arch/arm/boot/
than run ./builder.sh again
rename update_signed.zip to otg_signed.zip and copy it to sd card.
Now you can flash these zip from recovery.
Any luck with Sven's img?
Yes, I tried to boot Sven's zImage but without success.
So now I'm trying to compile android-msm-2.6.34 kernel pathced with Sven's patch file.
The patch was successfully applied but when I started compilling this error occured:
In file included from drivers/usb/host/ehci-hcd.c:1153:
drivers/usb/host/ehci-msm7201.c: In function 'usb_hcd_msm7201_probe':
drivers/usb/host/ehci-msm7201.c:313: error: 'struct msm_hsusb_platform_data' has no member named 'phy_shutdown'
I don't know how and where to add this member.
I'd appreciate some help.
Regards Andy
kodovoimeji said:
In file included from drivers/usb/host/ehci-hcd.c:1153:
drivers/usb/host/ehci-msm7201.c: In function 'usb_hcd_msm7201_probe':
drivers/usb/host/ehci-msm7201.c:313: error: 'struct msm_hsusb_platform_data' has no member named 'phy_shutdown'
Click to expand...
Click to collapse
This seems to be defined only in the Hero Kernel. Delete line 313.
Thank you very much for quick reply!!!
Now everything is OK!
I used fastboot to boot from RAM and then load the usb core and ehci modules.
And...yeeeeeeee now my G1 is usb host device!
I'm using Y-cable from my external HDD.
I must compile some modules like usb-storage and start testing.
My usb mouse works great with usbhid.ko.
Thank you again!
P.S. I'll update the first post soon!
That's Great~! I've found this for several months! Could you post your detailed tutorial for us? I think most G1 owner should want it. Maybe, you could make a special patch for the roms of CM 6, and everyone could update kernel more effortlessly.
Cheers!
Fox
I updated the first post and now you can download compiled kernel-2.6.34 and modules.
I tried usb-storage.ko but when I pluged my usb flash drive the phone reboot itself.
kodovoimeji said:
I tried usb-storage.ko but when I pluged my usb flash drive the phone reboot itself.
Click to expand...
Click to collapse
Is there something in /data/dontpanic directly after the reboot?
sonic74 said:
Is there something in /data/dontpanic directly after the reboot?
Click to expand...
Click to collapse
No, it's empty.
I load these modules: usbcore.ko, ehci-hcd.ko, usb-libusual.ko, usb-storage.ko.
Usb-storage.ko depends on usb-libusual.ko
I'm curious if it's possible to run my ACR122 contactless smartcard reader.
I installed Debian Leny and ACR drivers on sdcard as I do on my PC.
This is the output when I run dmesg:
[ 196.719024] msm_hsusb msm_hsusb: GetStatus port 1 status 80001803 POWER sig=j CSC CONNECT
[ 196.719573] hub 1-0:1.0: port 1: status 0101 change 0001
[ 196.819427] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[ 196.820007] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[ 196.939056] usb 1-1: new full speed USB device using msm_hsusb and address 2
[ 197.089111] usb 1-1: ep0 maxpacket = 8
[ 197.093750] usb 1-1: skipped 1 descriptor after interface
[ 197.095733] usb 1-1: default language 0x0409
[ 197.098724] usb 1-1: udev 2, busnum 1, minor = 1
[ 197.099426] usb 1-1: New USB device found, idVendor=072f, idProduct=90cc
[ 197.100280] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 197.100769] usb 1-1: Product: CCID USB Reader
[ 197.101593] usb 1-1: Manufacturer:
[ 197.106353] usb 1-1: usb_probe_device
[ 197.106872] usb 1-1: configuration #1 chosen from 1 choice
[ 197.108795] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 197.116180] drivers/usb/core/inode.c: creating file '002'
[ 197.117492] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
Click to expand...
Click to collapse
But I can't see it when I run lsusb.
This is the output of pcscdaemon:
00000000 pcscdaemon.c:280:main() pcscd set to foreground with debug send to stderr
00000336 debuglog.c:239: DebugLogSetLevel() debug level=debug
00018596 pcscdaemon.c:498:main() pcsc-lite 1.4.102 deamon ready
01416524 hotplug_libhal.c:460:HPRegisterForHotplugEvents() error: dbus_bus_get: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused
00000244 pcscdaemon.c:517:main() SVCServiceRunLoop returned
00000091 pcscdaemon.c523:at_exit() cleaning /var/run/pcscd
Click to expand...
Click to collapse
kodovoimeji said:
Usb-storage.ko depends on usb-libusual.ko
Click to expand...
Click to collapse
Strange, I haven't seen this module yet.
kodovoimeji said:
But I can't see it when I run lsusb.
Click to expand...
Click to collapse
You have to do
Code:
mount -t usbfs none /proc/bus/usb
Hi again,
thanks for your help. It seems that usb-storage.ko depends on usb-libusual.ko only when this modul is selected. I compiled kernel with build-in usb-storage but no matter i do my phone reboots after I pluged-in a usb flash storage. /data/dontpanic is empty.
Code:
mount -t usbfs none /proc/bus/usb
Now I can use lsusb.
I looked at .config but didn't find something about smartcard reader so if I manage to sort out drivers in Debian will it start working?
Kind regards
Andy
Please reupload link to kernel and modul.
http://ifile.it/ekountp/G1-usbhost-kern-and-modul-2.6.34.rar
Hi, newbie here. I was wondering whether once you have this setup, you can read read raw data directly from the usb port like you could in linux via /dev/hidraw2 or something similar?
Hello again,
why doesn't the wifi module work with this kernel?
is there any body going well of this?
my G1 detected the keyboard and my external HDD, I input the command 'lsusb' and 'dmesg', it seems working well; but a few moment later, it gives the message like this "can't enumerate usb devices in port 1"...what's more, I'm a noob with kernel and driver, anybody who can tell me how could I access the HDD and make the keyboard working, thans
Hi again,
at first I used Michael Mitchell's config file but than I decided to make my own config file:
1.Retrieve a working kernel config from your phone:
adb pull /proc/config.gz
gunzip config.gz
mv config .config
2.Customize the kernel:
make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
And now with my config file wifi is working.
There are CONFIG_USB_HIDDEV and CONFIG_HIDRAW options. I have basic skills in Linux so I can't help you.
I tried to compile USB Gadget Support as a module but receive this error:
Code:
CC [M] drivers/usb/gadget/msm72k_udc.o
drivers/usb/gadget/msm72k_udc.c: In function 'usb_phy_reset':
drivers/usb/gadget/msm72k_udc.c:1017: warning: unused variable 'retries'
drivers/usb/gadget/msm72k_udc.c:1016: warning: unused variable 'ret'
drivers/usb/gadget/msm72k_udc.c:1015: warning: unused variable 'val'
drivers/usb/gadget/msm72k_udc.c: At top level:
drivers/usb/gadget/msm72k_udc.c:1299: error: redefinition of 'msm_hsusb_set_vbus_state'
arch/arm/mach-msm/include/mach/board.h:121: note: previous definition of 'msm_hsusb_set_vbus_state' was here
make[2]: *** [drivers/usb/gadget/msm72k_udc.o] Error 1
make[1]: *** [drivers/usb/gadget] Error 2
make: *** [drivers] Error 2
hello ;D
Could i get a 2708 (15mb hack kernel mod) kernel with usb host support,please?;>
thanks for work,and congratulations for great idea!
Yeah I want too 2708 kernel with USB Host
Hi guys, I'm trying to get this working on the latest version of CyanogenMod 6 but am having troubles... has anyone else done this who fancies helping me out?
thanks!
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
New universal method of rooted for the Optimus 2x
After much programming and experimenting with another great part, already I can deliver my latest work.
So far have only made for Linux and Mac. (there are methods to not be as done in CMD)
Apparently it seems very simple, but it cheats, it is quite complex, since I've programmed detection of errors and possible solutions to the problems of communication.
The program is smart, detects the operating system that we are using, Linux or iOS, and detects the version of ROM installed to determine installation done.
Also installs the CWM Recovery, and also knows which install depending on the GB ROM or ICS, all automatic, without having to think that option used.
Before you root it will ask you if the CWM Recovery is installed and if it is not you can do it at that time.
The method used is not new, I already used it in earlier versions of GB, the difference with the other methods is that you don't have to copy anything to the SD and things of these, simple and clean installation.
Well I hope that you have Linux or a Mac can root without having to boot the "tedious" Windows.
CHANGELOG
V-0.5
-Implemented detecting permissions
-Implemented detection system 32/64b
-Fixed bug, was not working in Ubuntu 11.04 and higher
V-0.4
-Detection of new possible connection failures.
-Detection of errors in routines Android
-Optimized routines
V-0.3
-Fixed bug of execution, did not work on some current versions of Ubuntu and derivatives
-New start menu.
-New header
V-0.2
-Re-raise with correction error in English language, it only pulled in Spanish
-Includes English language
-Changing the graphic appearance
V-0.1
-Only in Spanish
Click to expand...
Click to collapse
DOWNLOAD
Toolkit_ICS-Root_Stock-v-0.5_LINUX-MAC_by_Homero.rar - 13.40 MB
Thank's Man...and have a nice year 2013!!!...
Nice, it should became sticked.
Also... your program must be also noob-proof
Great work, homero! Thank you.
Sent from my LG-P990 using xda app-developers app
Homero again back with a bang...you're hulk of lg optimus forum..you rock bro
Finally some Linux love.... :thumbup:
Sent from my LG-P990 using xda app-developers app
Thanks homero
Enviado desde mi O2X
I have committed an error, and the English version, and does not run.
You can download the new corrected version or edit and modify.
Edit the root file and look for this line:
Code:
if [ "$ANSWER" = 1 ]; then
tools/es.sh
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
elif [ "$ANSWER" = "x" ] || [ "$ANSWER" = "X" ]; then
Changing this:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
why another:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/en.sh
Save and ready, already operates the English version
Homero2 said:
I have committed an error, and the English version, and does not run.
You can download the new corrected version or edit and modify.
Edit the root file and look for this line:
Code:
if [ "$ANSWER" = 1 ]; then
tools/es.sh
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
elif [ "$ANSWER" = "x" ] || [ "$ANSWER" = "X" ]; then
Changing this:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
why another:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/en.sh
Save and ready, already operates the English version
Click to expand...
Click to collapse
Beware of #!/bin/sh ... read -n command is bash command, and it does not work well in /bin/sh ...
Confirmed on NetRunner (kubuntu 12.10 ).
You should use #!/bin/bash. That applies to all *.sh scripts.
asmerito said:
Beware of #!/bin/sh ... read -n command is bash command, and it does not work well in /bin/sh ...
Confirmed on NetRunner (kubuntu 12.10 ).
You should use #!/bin/bash. That applies to all *.sh scripts.
Click to expand...
Click to collapse
OK, that is the answer that was waiting, since neither worked in Ubuntu 12.04
EDIT:
Re-raise corrected v-0.3
Though your tool says that flashing the recovery worked successful, I can't boot into recovery. When pushing vol- and power I'm just stuck at the pink LG logo (it's in a boot loop while holding vol- and power). Since the system is not rooted, yet, I also cannot boot into recovery with the CWM app.
thorstenhirsch said:
Though your tool says that flashing the recovery worked successful, I can't boot into recovery. When pushing vol- and power I'm just stuck at the pink LG logo (it's in a boot loop while holding vol- and power). Since the system is not rooted, yet, I also cannot boot into recovery with the CWM app.
Click to expand...
Click to collapse
Don't worry in excess, can be retrieved very easily, but before answer to these questions.
Android version?
did CWM previously installed?.
Terminal type? (P990, P990, etc.)
on slackware 14.0, expanded in /opt:
two patches applied;
files are executables with right permissions;
dir 'tools' is accessible;
lg2x is connected via USB (on, off, MTP, PC Suite, without battery and vol -, ...?)
but same result
Terminal: P990 (EU)
ROM: ICS stock
Previous ver: CM 7.2 stable
Previous CWM: 5.0.2
Homero2 said:
Android version?
did CWM previously installed?.
Terminal type? (P990, P990, etc.)
Click to expand...
Click to collapse
Android 4.0.4 (official V30A)
CWM - well, under GB layout I could install it (I was on CWM5 first and later switched to CWM6), but this was my first try on ICS layout
Terminal type - you mean the shell? I'm using Ubuntu 12.10, so /bin/sh did not work and I replaced all /bin/sh with /bin/bash, that means I was running bash when I "bricked" my phone.
kanzy said:
on slackware 14.0, expanded in /opt:
two patches applied;
files are executables with right permissions;
dir 'tools' is accessible;
lg2x is connected via USB (on, off, MTP, PC Suite, without battery and vol -, ...?)
but same result
Terminal: P990 (EU)
ROM: ICS stock
Previous ver: CM 7.2 stable
Previous CWM: 5.0.2
Click to expand...
Click to collapse
Is about understands that this method of single rooted is for Stock ROM versions.
Clarified the issue, I see errors jump to run ADB.
Try with the latest version that I uploaded, the V-0.4
thorstenhirsch said:
Android 4.0.4 (official V30A)
CWM - well, under GB layout I could install it (I was on CWM5 first and later switched to CWM6), but this was my first try on ICS layout
Terminal type - you mean the shell? I'm using Ubuntu 12.10, so /bin/sh did not work and I replaced all /bin/sh with /bin/bash, that means I was running bash when I "bricked" my phone.
Click to expand...
Click to collapse
Not be what could happen...
Doing tests I found that if you are in Recovery, and the SYSTEM partition is not mounted, the program cannot determine partition type should be used.
That error is already fixed in the V-0.4.
It can reflash the Recovery with one of the many versions that we have in the Forum, one in Flash only recovery or All in one.
I say this because it is the only thing that could have happened, since the rooted is not harmful, only copy two files in the system.
Using V-0.4, and it does not work...
Homero2 said:
Is about understands that this method of single rooted is for Stock ROM versions.
Clarified the issue, I see errors jump to run ADB.
Try with the latest version that I uploaded, the V-0.4
Not be what could happen...
Doing tests I found that if you are in Recovery, and the SYSTEM partition is not mounted, the program cannot determine partition type should be used.
That error is already fixed in the V-0.4.
It can reflash the Recovery with one of the many versions that we have in the Forum, one in Flash only recovery or All in one.
I say this because it is the only thing that could have happened, since the rooted is not harmful, only copy two files in the system.
Click to expand...
Click to collapse
Same problem as on slackware, got booloop after flashing recovery. Cannot enter recovery
After this step:
INSTRUCTIONS
CWM will be installed for version ICS V-4.0.4 of Android
Nvflash started
rcm version 0X20001_____________________________________________________________
System Information:
chip name: unknownh Recovery CWM
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x045070c04120b4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: tools/fastboot.bin
/ 1027184/1027184 bytes sent
tools/fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: tools/recovery_cwm-6_ics_opti.img
\ 7145472/7145472 bytes sent
tools/recovery_cwm-6_ics_opti.img sent successfully
everything went wrong, and my stock ICS got bootloop.
Using Kubuntu 12.10, stock ICS and V-0.4 of your tool.
Thank you mate! Gonna share it like a bee
asmerito said:
Same problem as on slackware, got booloop after flashing recovery. Cannot enter recovery
...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=921169
Fixed bug, now works in Ubuntu 11.04, 11.10, 12.04 and 12.10
An error has been detected by Jonki, Thank you!!
Homero2 said:
Fixed bug, now works in Ubuntu 11.04, 11.10, 12.04 and 12.10
An error has been detected by Jonki, Thank you!!
Click to expand...
Click to collapse
What was the problem?
This is the first phone I've ever plugged in to my Linux Mint PC that ADB does not recognize.
I see the device in lsusb, and I can browse the files in Caja, but ADB does not see it.
Does anyone know how to get this to work?
Blu R1 HD Amazon Prime
Linux Mint 17.3 x64 MATE
Code:
[email protected] ~ $ [B]lsusb[/B]
Bus 002 Device 003: ID 0e8d:201d MediaTek Inc.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0461:4e35 Primax Electronics, Ltd
Bus 001 Device 003: ID 060b:0540 Solid Year
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected] ~ $ [B]adb devices[/B]
List of devices attached
[email protected] ~ $
Linux doesn't need ADB drivers. Make sure you have USB debugging turned on and you approved the computer on your phone when it pops up.
triggerlord said:
Linux doesn't need ADB drivers. Make sure you have USB debugging turned on and you approved the computer on your phone when it pops up.
Click to expand...
Click to collapse
USB debugging is enabled.
When I connect phone to computer, no authorization popup shows up on phone. I have tried several USB cables that work with other phones and have tried on my desktop and laptop, both of which are Linux Mint 17.3 x64 MATE.
ericpeacock79 said:
USB debugging is enabled.
When I connect phone to computer, no authorization popup shows up on phone. I have tried several USB cables that work with other phones and have tried on my desktop and laptop, both of which are Linux Mint 17.3 x64 MATE.
Click to expand...
Click to collapse
It should work with Mint 17.3 but I'm on Mint 18.
Have you done
sudo apt-get install android-tools-adb android-tools-fastboot
I'm assuming your on Ubuntu or at least a debian based build
Of course. LoL
I have used these two pc's to flash many Android devices.
I have every adb/fastboot/android package from synaptic installed, as well as android and Java sdks and other things from 3rd party ppa's.
I'm backing up files now, and will install Linux Mint 18 from scratch after the file copy (203GB including virtual machines) is complete.
detects fine in Linux Mint 18.
rooted, twrp'd, debloated, BL unlocked now.
ericpeacock79 said:
This is the first phone I've ever plugged in to my Linux Mint PC that ADB does not recognize.
I see the device in lsusb, and I can browse the files in Caja, but ADB does not see it.
Does anyone know how to get this to work?
Blu R1 HD Amazon Prime
Linux Mint 17.3 x64 MATE
Code:
[email protected] ~ $ [B]lsusb[/B]
Bus 002 Device 003: ID 0e8d:201d MediaTek Inc.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0461:4e35 Primax Electronics, Ltd
Bus 001 Device 003: ID 060b:0540 Solid Year
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected] ~ $ [B]adb devices[/B]
List of devices attached
[email protected] ~ $
Click to expand...
Click to collapse
I know it sounds crazy, but you may need to add udev rules. Atleast its worth trying. Or update to a newer version of ubuntu/mint. Also, I would not recommend using adb/fastboot from the ubuntu repos because they never kept up to date. you need to use the latest versions from the actual SDK.
bynarie said:
I know it sounds crazy, but you may need to add udev rules. Atleast its worth trying. Or update to a newer version of ubuntu/mint. Also, I would not recommend using adb/fastboot from the ubuntu repos because they never kept up to date. you need to use the latest versions from the actual SDK.
Click to expand...
Click to collapse
I wiped my laptop and installed Linux Mint 18 fresh. I installed the advice and fastboot packages from synaptic and it works great.
I was running 4.2 kernel on Mint 17, but Mint 18 is 4.4 kernel. I have no idea if that made any difference though.
ericpeacock79 said:
I wiped my laptop and installed Linux Mint 18 fresh. I installed the advice and fastboot packages from synaptic and it works great.
I was running 4.2 kernel on Mint 17, but Mint 18 is 4.4 kernel. I have no idea if that made any difference though.
Click to expand...
Click to collapse
Awesome, though I would still recommend installing from SDK, but thats up to you. Good luck
sorry for the rez. same issue, found this topic and it helped. running debian jessie, adb installed and fastboot.
i enabled debian unstable repo and upgraded from the stable version of adb and fastboot, had to add an ssl lib but that was all.
phone detected on 5.1.1.r29-2
android-tools-adb
android-tools-fastboot
i am surprised there are no intermediary versions in jessie-backports though.
stable was 4.2.2+git20130529-5.1