[fastboot] l9 p760 p765 p768 p769

[yurais]

I take no responsibility for any damages incurred to your phone
Please use this script only when necessary


Here is a little script I put together to fastboot L9s with ability to flash/restore ics xloader and uboot (p760, p765, p768, p769) jb (p760)

*I've only tested it on Win 7, but it should work on Vista , not sure about XP and 8

Very useful post about installing the drivers

*Some phones may need a different timing, 4 seconds won't work, worth to try between 0 to 4s and see what works best

Original thread about fastboot
http://forum.xda-developers.com/showthread.php?t=2119090

It's based on wpark - [DEV][Bootloader] u-boot / omap4boot for P920/P720/P940 and its variant


update: file updated, mylk Thanks for catching the mistake!
update2: added p769 20f

Hello

am trying to unbrick an L9
phone has no download mode, or fastboot, it just have the omap mode.

I tried the script and I can go to fastboot mode, however, I cant do anything more, I cant write anything.

When I tried to write bootloaders, fastboot get as response: Partition not found

as if ohone has no partitions or need repartitioning.

When I got this phone, it was stuck at LG logo, I could easily enter Download mode, by inserting usb cable while holding Vol +

I treied to flash phone with Octoplus Box LG tool, it started writing then stopped with error: Cant erase u-boot

any idea how to unbrick this?

 

[yurais]

Someone posted in this thread about repairng partitions with octopus.

I do have Octopus and I cant flash phone using this tool, it gives errors erasing u-boot

 

[rethus]

Does there an 51-android.rules need in /etc/udevs/rules.d/ ?
I didn't have any.
I see the device with

fastbood devices -l

, but If I try to flash the recovery, I got:

fastboot flash recovery ./recovery.img --unbuffere
target didn't report max-download-size
sending 'recovery' (10558 KB)...
FAILED (command write failed (Success))
finished. total time: 0.001s

Hope somebody can give me a hint.

 

[rethus]

Ok, found some usefull pages - even if not a solution.
Here a page how to figure out the udev for the device:
http://weininger.net/how-to-write-udev-rules-for-usb-devices.html

For me:

$ lsusb  # and loog for:   Bus 001 Device 043: ID 18d1:d00d Google Inc.

#so bus 001 and Device 043 ... go on got info about the device:
$ udevadm info -a -p $(udevadm info -q path -n /dev/bus/usb/001/043)
# watch out, Device change on each replugin!!!

Result in

udevadm info -a -p $(udevadm info -q path -n /dev/bus/usb/001/043)

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2':
    KERNEL=="1-1.2"
    SUBSYSTEM=="usb"
    DRIVER=="usb"
    ATTR{authorized}=="1"
    ATTR{avoid_reset_quirk}=="0"
    ATTR{bConfigurationValue}=="1"
    ATTR{bDeviceClass}=="00"
    ATTR{bDeviceProtocol}=="00"
    ATTR{bDeviceSubClass}=="00"
    ATTR{bMaxPacketSize0}=="64"
    ATTR{bMaxPower}=="100mA"
    ATTR{bNumConfigurations}=="1"
    ATTR{bNumInterfaces}==" 1"
    ATTR{bcdDevice}=="0100"
    ATTR{bmAttributes}=="c0"
    ATTR{busnum}=="1"
    ATTR{configuration}=="DUMMY LGE Config"
    ATTR{devnum}=="43"
    ATTR{devpath}=="1.2"
    ATTR{idProduct}=="d00d"
    ATTR{idVendor}=="18d1"
    ATTR{ltm_capable}=="no"
    ATTR{manufacturer}=="Google"
    ATTR{maxchild}=="0"
    ATTR{product}=="Android"
    ATTR{quirks}=="0x0"
    ATTR{removable}=="unknown"
    ATTR{serial}=="1234567"
    ATTR{speed}=="480"
    ATTR{urbnum}=="12"
    ATTR{version}==" 2.00"

Here you see the Name "google" and the ATTR{serial} ... its identical with result of

$ sudo fastboot devices -l 
#returns:
1234567                fastboot usb:1-1.2

So this seems to be the right device.
Now create the udev-rule:

$ nano /etc/udev/rules.d/51-android.rules
# add this line:
SUBSYSTEMS=="usb", ATTRS{product}=="Android", ATTRS{idVendor}=="18d1", GROUP="users", MODE="0666"
# on nter Arch-Linux udev reloaden:
udevadm control --reload-rules
# on debian oder ubuntu "service restart udev"

Even found this Page here where the udev macht product_id an vendor_id: https://github.com/M0Rf30/android-udev-rules. So try my own way and this git-udev, but both still return:

FAILED (command write failed (Success))

Don't know why ??!!
PS: Some fastboot commands as overview: https://www.lineage-os-forum.de/Thread-TUTORIAL-Anleitung-wie-ADB-bzw-Fastboot-zu-benutzen-ist

Video with many Links in description: https://www.youtube.com/watch?v=VSO-zVNDqdw