[General Questions and Answers] Jakodo:
[Q] How to use ADB on really soft-Bricked LG

Hello Everyone.

Let me begin by first asking 2 questions before I share my problem.

1.Is it truly possible to use ADB on a phone without enabling USB debugging?

2.Can I use this method to help the Situation described below?

I have a really tricky device (by my experience) on hand. An LG MS 345 (aka leon). Based on my reasearch I am still not sure that I can accomplish what I need to do (how to fix this phone).

I think my solution lies in ADB. But I cannot connect with ADB for reasons I am hoping someone here can point out, I know this is THE forum.

I am uncertain if ADB can actually do the Job, because for starters I cannot enable USB debugging on a device that fails to boot. There seems some evidence that people out there have used ADB to connect without enabling the option on their device.

Here is my case

MS 345 (leon)

Status/operability:

Boot = loop / Fail. (optimizing app 1/31)

Download/Firmware Mode = accessible

Factory Reset = accessible, but avails nothing.

Android MTP device driver installation (Fails.)

LGE Mobile USB composite Device (Installs)

--------------------------------------------------------------------------------------------

Background/info:

(I want to: either go stock firmware on this phone, or get the system to forget about "optimizing apps" and so actually BOOT.)

Roadblocks

LG suite cannot communicate with Device.

LG Flash tool will complete an operation succesfully – but I cannot changeto factory.kdz version! (why??)

Also Phone uses a Brand/Custom “Factory Reset” menu. Its colorful and has only 2 options. YES AND NO, whereas the usual other android ones are text based and offer several options. I may not be very experienced with androids, but I feel strongly this is quite a tricky nut. I do not even have options like "clear update cache" ect, from this boot menu.

Using a PC, I get Windows Device manager Entries for this device to show, when phone is in android 'firmware upgrade' mode.

--EDIT -- Progress: Drver installed, but says could not start.

History(continued):

( When it had original firmware

>>Brother Does his handiwork (Problem) phone hangs during MetroPCS logo Animation. Factory reset at this point avails nothing.

>>Flashed to later Revision of firmware from LG / Metro Rev b. to d.

>> Optimizing app 1/31 – goes to around 22, reboots before finishing. Endless.

---------------------------------------------------------------------------------------------

Well My suspicion is that the phone doesn't have enough free space to do what it needs to re:moving operations Mind you, I'm a novice when it comes to the android realm, but i could not clear the cache due to the strange recovery menu / bootup rom LG uses.

At this point I reckon my options are :

1. Access the partitions directly using ADB / a partition tool and wipe the partition so I could flash it with the original OS.

Is this a viable option? (apparently NOT, because I cannot enable USB debugging)

I have downloaded and installed Android Studio, and even tried the stand alone SDK windows package.

Here are my CURRENT obstacles in trying to fix this Android.

ADB cannot see phone. command:adb Devices)

Again, People recommend putting phone into USB debug mode in Android>Settings. But that's not an option with a 'bricked' phone. I tried to manually install several drivers (for MTP) but none of them work, only the composite ones. But I didnt know whether MTP drive would be mandatory to access the partitions.

Ive done quite a bit of reading. What am I missing. Is this phone locked away forever in a software-brick dome?

Strangely even though I can use the flash program and operate on the phone, I still cannot use ADB to access the phone so I can wipe the partitions.

If anyone knows how else I could REALLY wipe this Android, or think I am on the wrong Path. Please, please help.

EDIT

I have recently succesfully edited the ADB driver and installed it. The system did say the device cannot start, but ignoring this, What Next?

The driver installed just now. But adb bridge cannot see the android (set to firmware upload).

The command |adb devices| still shows no devices connected.

Thanks for any suggestions in advance.