yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] ibub:
I didn't mean black screen in recovery. I meant for you to try dd command from where you are bootlooping. Don't reboot recovery until you have used dd command to write the twrp recovery to recovery partition.
[Android Q&A, Help & Troubleshooting] vwnut13:
Ah, I understand now. I just tried and no dice, "cannot open for read: Permission denied"

It seems that I can finally say there is no hope for this thing. My issue is that I didn't allow permission to Shell in SuperSU, simple as that.

There is nothing that I can do because I can't access root permission to shell without being able to boot up. I can't uninstall SuperSU because it is a system app (and because it seems this phone is pretty borked, trying to install an app flashes errors in ADB).

Oh well, at least I have some replacement parts. Thanks everybody for all the help.
[Android Q&A, Help & Troubleshooting] Area51Rebuilt:
Not sure if it really matters. But I have gotten past the bootloop I had the lgl34reboot". loop. Rooted it through towel root. Then accidentally deleted chrome and all of a sudden the background disappeared and none of the button worked as far as back arrow. Home and windows button. So I decided to turn it off then back on. Went through and did the same thing so I pulled down notifications tab. And wiped the phone. Turned it on and bam LG bootloop. So instead I held down the volume down and power button for about 4 bootloops. Let go and let it sit at the tracfone screen for about 30 minutes. I started pressing the buttons. Mainly the middle home button. And the phone came to the LG setup wizard.

This is where I became stuck. I would click continue through everything. However at the end it says " LG setup wizard has suddenly stopped". No matter what I do I cannot get past this screen. I have however figured out a way to get usb debugging on while in this menu.

How to do this : 1 continue through all screens of the setup wizard.

2. When it says " LG setup wizard has stopped working" pull down notification bar.

3. Click and hold locations. ( you can find this by scrolling to the right)

4 now just press the back arrown on top left. And go down to the about phone software. Kernel and tap 7 times. It will unlock dev options click it and allow usb debugging.

So through all of this. Now I'm stuck. Can I just download adb and run "adb shell reboot" or will that not work i can send screenshots if needed or could I use a factory flashed version
[Android Q&A, Help & Troubleshooting] ibub:
adb reboot will do nothing but reboot device, which is the same thing that you have managed to do without adb. And a factory reset does not restore system apps that people reclessly delete. It only erases downloaded apps and settings from /data and /cache. And unless you converted SuperSU to a system app prior to factory reset, then you MAY have POSSIBLY lost root access. IF you are able to access device via adb (type and enter adb devices to see), then it MIGHT be possible to reinstall SuperSU.apk and regain root (adb install /storage/external_SD/supersu.apk). IF this is successful, then you MIGHT be able to recieve rsa security prompt on your device and select allow this computer access. But then you would need to write twrp to recovery partition, and use it to restore the system image that daishi4u provided on page 29. I would suggest using LG flash tool, but since we don't seem to have access to download mode I'm not sure that would work.
[Android Q&A, Help & Troubleshooting] mateo121212:
hey i got a username and password for that site. the links that are hidden are broken anyways they dont work.

send me a PM to get the links because i cant post them

even with password there is another link for each file that i need 2 content points to read. once i figure out how to get those i will see what hidden links are available
[Android Q&A, Help & Troubleshooting] Eli hutchison:
I accidentally deleted my play store and my settings crash every time I open it, and "unknown resouces" is unchecked so I'm pretty much screwed on this phone
[Android Q&A, Help & Troubleshooting] Night AoX:
Upload it to https://mega.co.nz/ 4shared is just too messy.. Thanks for the link though.

---------- Post added at 03:52 PM ---------- Previous post was at 03:31 PM ----------

Is this part still working right? :

1 Turn the phone off.

2 Press and hold the Power/Lock Key + Volume Down Key .

3 Hold down the Volume Down Key and release the Power/Lock Key when the LG logo is displayed.

4 Press the Power/Lock Key again within 3 seconds while the Volume Down Key holding down.

5 When the Factory data reset screen appear, release all keys.

6 Use the Volume Keys to highlight Yes and press the Power/Lock Key to confirm.

7 Use the Volume Keys to highlight Yes and press the Power/Lock Key to confirm one more time.

8 Your phone will perform a factory reset.

Can't seem to get it to work properly..
[Android Q&A, Help & Troubleshooting] ibub:
No, that method does not work for these devices. If you want to factory reset, go to settings > backup + reset, and choose your options for backup before performing the reset. But if you want to access recovery, there are other options posted later in this thread.
[Android Q&A, Help & Troubleshooting] Night AoX:
The phone won't boot at all.

So no in-phone options. According to http://www.howardforums.com/showthread.php/1854851-Recovery-mode-in-Optimus-Fuel-L34C-**SOLVED** it looks like Tracfone didn't include some necessary packages for a proper hardware button reset. The phone wasn't rooted. If the method you're speaking of doesn't require the phone having been rooted, please link the post. Thank you for providing some extra insight.
[Android Q&A, Help & Troubleshooting] ibub:
No, the only way we have access to recovery by key press is via daishi4u modified kernel, which requires root to install.
[Android Q&A, Help & Troubleshooting] Night AoX:
Cruel, cruel fate. Thank you for the confirmation.
[Android Q&A, Help & Troubleshooting] Night AoX:
I got this LG-L34C from a friend. She says she does believe it was in fact rooted before this bootloop started.

I'm going to try and fix it but, there are a few caveats.

1) I haven't needed to use ADB in a long time because I never worked with a phone this cumbersome.

2) I do have the USB driver installed for my LG Optimus F7. It's my understanding that the LGMobileDriver_WHQL_Ver_4.0.4.exe driver is essentially a universal USB driver for LG phones. When I plugged the phone in via USB, the phone boot looped this screen:

and Device Manager didn't recognize any devices and the PC didn't make the "a device has been connected" sound. There is no driver download option for the LG-L34C on the LG website. Will the driver I currently have work? After about 50 boot loop runs, while I was looking up ADB tools, the boot loops finally stopped and then the PC made the "a device has been connected" sound. I checked Device Manager, scanned for hardware changes and I now see this:

3) Since I haven't needed to use an ADB tool in 5 years, I don't even remember much about them. Which tools do you recommend? I understand the syntax but, I'm just having an issue with getting the USB driver installed for the PC to fully recognize the device.

4) She has more of these devices that may too be rooted that are also having this infamous boot loop. If I can get the one I have here back up and running, I should be able to guide her through the process but, I need to know if there is a way to get the PC to recognize a device has been connected without having to sit through an infinite amount of boot loops. I mean, did I just get lucky that the PC even recognize the device at all? Is there anything I can do to get the PC to recognize the device faster?

5) Also, I'm running Windows 10 64-bit. I don't know if that has anything to do with why it took so long for the PC to recognize the device but, something tells me that it does so, there's that bit of information.

Any help will be greatly appreciated.
[Android Q&A, Help & Troubleshooting] Logiel:
Have you ever flashed a ROM or other thing ? Maybe you have a problem with the phone's NAND.

Sorry for my bad english : I'm french...
[Android Q&A, Help & Troubleshooting] Night AoX:
Haha. I'm guessing you're talking to me. The phone has never had another ROM. Just stock rooted; that's if her memory is correct and she did in fact root the phone..
[Android Q&A, Help & Troubleshooting] ibub:
Can't see either of the images you posted, but I'm guessing that you are looping on the LG logo. Any text? Anyway, if it's reloading the kernel over and over, then it probably disconnects each time. So in order to send a command via adb would need to be timed just right (difficult, if not impossible). I'm not sure that a factory reset would work or not. If SuperSU was not converted from a user app to a system app, then a factory reset will erase the app and you will likely lose root access. You could try to install daishi4u's kernel (boot.img) and twrp recovery.img in adb shell via the dd command. The kernel would give you access to recovery via key press. The recovery MIGHT allow you to reboot the system (I had to do that a couple of days ago, after switching to a spare battery ). But I'm really not sure that any of this will work. These devices are very finicky.
[Android Q&A, Help & Troubleshooting] Night AoX:
Do you have Ghostery or a script blocker? A similar extension probably blocked the images.. I'll upload them though so you can see exactly what they say. Also, how do I ADB into the phone? I haven't used these tools in 5 years.. Vaguely remember using an ADB tool..
[Android Q&A, Help & Troubleshooting] ibub:
Well now I have the exact opposite problem. I noticed that the device was running slow. So I looked at internal storage and RAM usage, and both were pretty used up. So I uninstalled some apps, moved some downloads to external SD, cleared app caches, etc. But it didn't seem like I had gained very much, so I tried a reboot. Now the system won't boot, but I can still access twrp. Tried restoring backup of system and boot.img. No go. Finally sacrificed my data by factory reset. Still won't boot system. I am now using my spare Fuel.
[Android Q&A, Help & Troubleshooting] Night AoX:
Yeah, light weight = potato. It's okay though. If some sort of miracle occurs, awesome.
[Android Q&A, Help & Troubleshooting] Night AoX:
Okay androidarea51 is literally a broken piece of crap so, I'm hoping you can help me.

Okay so, I just made a backup. I'm now trying to restore on another LG Fuel but, TWRP didn't make a .zip. It just made a .L34CV10c file? So, when attempting to flash the backup, there's no .zip to use? I'm completely lost here. I tried to enabled compression figuring compression would = .zip but, nope. I don't understand what I'm doing wrong..
[Android Q&A, Help & Troubleshooting] ibub:
Twrp backup is not the same as a flashable zip. To RESTORE a backup, you must use the RESTORE function. If you are attempting to restore a backup from another phone, then you first need to make a small backup with the phone that you wish to add the backup to. This will create the proper folder name within the twrp backup folder. So it will look like: TWRP/BACKUPS/ lgl34cabc123xyz, or something similar. The last folder name has a different code on the end for each individual phone, so this is necessary. Then place your backup inside of that folder, reboot to recovery, choose restore, select your backup, and restore it.
[Android Q&A, Help & Troubleshooting] Night AoX:
Yeah, I found that out from http://androidforums.com/threads/verizon-solved-twrp-cannot-find-backup.654751/ but, I forgot to post it here..

It would be nice if TWRP didn't work like that or at least gave the option to disable it. Would've saved me a lot of time..
[Android Q&A, Help & Troubleshooting] toxinburn:
Samsung Galaxy Ace Style SM-S765C Firmware &amp;amp; CSC for odin

Hey bub just thought i would share, I have the firmware and csc which is ready for flash through odin I think maybe it could help alot of folks that have bricks on this thing and hopefully spark a bit of interest in continuing to get the bootloader unlocked on these now that they can actually save their device. I am currently uploading to my drop box so it may take a little bit but they will be available from the following links.

https://www.dropbox.com/s/dpnqot9fm...3_REV00_user_low_ship_MULTI_CERT.tar.md5?dl=0

https://www.dropbox.com/s/fkgy0lrea...3_REV00_user_low_ship_MULTI_CERT.tar.md5?dl=0
[Android Q&A, Help & Troubleshooting] ibub:
Cool, thanks brother. :) I didn't know that you could use Odin on an LG device. And I've never had a Samsung, so I've never used it. But if you say that it works, then that's good enough for me. Wish I had this 3 weeks ago when my daily died. Although after a while I couldn't even use it as a charger, so I think the hardware might have been cooked. So now my test device is my daily, and I trashed the other. Might look into acquiring another (if I can find a cheap one).
[Android Q&A, Help & Troubleshooting] toxinburn:
Oh dang i forgot Odin won't work on a lg lmao...but that is the firmware for Samsung galaxy ace style so it works for that.

---------- Post added at 08:56 PM ---------- Previous post was at 08:50 PM ----------

I guess their is some confusion but if you need firmware for a specific device lemme know I can get some for LG too
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

Well I guess that this thread is not necessarily specific to ANY device, even though it's history is pretty much all about the Fuel.

:)
[Android Q&A, Help & Troubleshooting] rb2tfm:
Well hello strangers!!!!

I figured Id'e bust out the old fuel again because i just knew ya'all was missing me like crazy in this thread. =) NOT!!!

Anyway, nothing has changed here, still in a bootloop, can't ADB, can't get it to boot to anything but bootloop with any key combination..... Am I really still tinkering with this thing ?.... really ??? =)

Good to see everyone...... Missed yun's!... kinda =)
[Android Q&A, Help & Troubleshooting] toxinburn:
Well i am getting octoplus box tomorrow if you reallllly need something fixed I can maybe help if you want to send it in for me to revive
[Android Q&A, Help & Troubleshooting] rb2tfm:
Hey appreciate the offer! Thank You.

I'm going to shoot ya a pm. =)
[Android Q&A, Help & Troubleshooting] stere0123:
I've had my Fuel for about a year and it randomly died 3 weeks ago. It shows the LG logo for a few seconds, but instead of continuing to the blue tracfone screen, the backlight dims and then the screen goes black, whilst the LED cycles colors. It continues to have a black screen (no backlight) and LED color cycling indefinitely. I've tried numerous reboots, USB/battery combinations, and button combinations but haven't gotten anything different. This started after a reboot (which I've read can be problematic for these devices).

Any ideas? It is recognized via USB as an LG device but isn't shown in adb devices (I never enabled USB debugging..).
[Android Q&A, Help & Troubleshooting] crogomon:
HELP PLZ!!! I rooted the lgl34c then with supersu uninstalled random stuff. Then i cant do anything except dismiss a message saying

com.android.keyguard has stopped

What do i do all i can to is dismiss the message. And im not a tech wizard so i cant put in codes and such
[Android Q&A, Help & Troubleshooting] Crashoverride1993:
Is there anyway to root this phone?
[Android Q&A, Help & Troubleshooting] ibub:
Towelroot. Geohot actually provides the codes to use for the LG Fuel.

I had to switch to my current phone because I was working in an area where service was unavailable. Now 14 months later, I have a job closer to home. So I thought I'd switch back to the Fuel. So I fired it up and got an update to system ui. To finish the update, it asked for reboot. When I rebooted I got LG logo and constant reboot back to the logo. Restored several backups of system, data, and kernel. But still it only boots when it wants to. I guess that the boot image is not being completely read or loaded into ram. So if I can't trust it to boot up, I guess I can't use it daily. So sad.
[Android Q&A, Help & Troubleshooting] toxinburn:
Their are or were custom roms I think for the fuel even it took awhile but afaik it was bypassed etc....I think possibly just signing the images would work now but I do know for sure their were methods to get into recovery in this thread.
[Android Q&A, Help & Troubleshooting] RealWelder:
I have copies of bumped boot, twrp, and cwm for the fuel. If anyone needs them.
[Android Q&A, Help & Troubleshooting] ibub:
Hey brother, it's been a long time. ;)

I am able to access recovery via boot_bumped.img, but the system doesn't always boot. I'm thinking about reflashing aboot.img, but that would only be so that I could eliminate that as a possibility. Will have to dd if=/storage/external_SD/aboot.img of=/dev/block/mmcblk0p6 because twrp doesn't have the option to flash an image to that partition. Would have tried sooner, but I could only boot up the zone2 as a reference, and I wasn't sure the partition was at the same address. But I'm honestly thinking that the hardware is not reading it right.
[Android Q&A, Help & Troubleshooting] awadh730:
how can i enter to download mode?
[Android Q&A, Help & Troubleshooting] ibub:
As far as we know, download mode has been disabled on these phones. Might try LG update software on your computer, but I don't really know if it will be able to access it or not.
[Android Q&A, Help & Troubleshooting] LDBAKE:
Is there anyplace to download stock firmware for these lgl34c phones? if so, can I just dd it to the phone to return it to stock?
[Android Q&A, Help & Troubleshooting] toxinburn:
Man I will have to check later when i get off work but I think it's around somewhere links maybe expired now but I usually save firmware seems like I had uploaded that one before...sorry if I forget I am super busy but I still get email when someone responds to this thread.
[Android Q&A, Help & Troubleshooting] LDBAKE:
Thanks toxinburn. I just use this thing for storing/playing my music files. Recently is started having trouble booting up. It just sort of bootloops with message "Source booting error" "Cause: boot certification verify"......if I leave it alone for a while it will (or at least it has been) eventually boot up. Just thought I'd try sending it a reload of firmware to see it that helps. I don't know if it will, but nothing ventured nothing gained. Thank you again for replying. I know this thread is basically dead. I'm sure most (if not all) people have moved on from this little phone. If I can't find a firmware somewhere, I'll just toss it.
[Android Q&A, Help & Troubleshooting] toxinburn:
It has been quite awhile but I did not have that firmware so far that I can find anyhow but I made a post about unbricking these and I recall I had the exact same error when mine was messed up and it was recoverable with Linux so I am hoping you have a virtual machine or Linux box to try this on. https://xdaforums.com/showpost.php?p=54285893&postcount=52 read over this post but you will need the exact partitions you messed with I am assuming the aboot or boot was replaced or even recovery which could of caused your issue I no longer have this phone or I would upload my partitions for you to use but using the method I lay out in that post you can actually push clean partitions back to the device and pass the checks again which would get it back running. Short of that I am not sure how else to fix it because the site that used to have the custom rom for it etc I think is also down now. I am still searching my drive accounts and other file upload sites to make sure I don't have any backups will post them if I find any.
[Android Q&A, Help & Troubleshooting] Mac23:
Unfortunately this link is dead. I googled a lot and found nothing. As far as I know daishi4u´s boot image is the only way to boot straight into recovery without the need for any software (flashify, twrp manager and so on). Where can I find daishi4u`s boot image? Or is there another solution available by now?
[Android Q&A, Help & Troubleshooting] daishi4u:
Here you go. Surprised that I still had this in my Google Drive

https://drive.google.com/file/d/0ByNiE7lUnRZsVnp3RDhPMmlHeUU/view?usp=drivesdk
[Android Q&A, Help & Troubleshooting] Mac23:
Thank you. Found it also in this thread: https://xdaforums.com/showpost.php?p=73009859&postcount=18

Everything works:

phone was already rooted by "Towel root"

flashed official twrp 2.8.7.0 using official TWRP app [but still waiting for some answer about TWRP 3]

flashed your custom boot image [MD5: fa4ea415df441100dba0c8536dcb576c]

recovery can be started by powering on and the repeatedly pressing vol+ for some seconds. After that, the LG logo appears a second time and twrp starts.
[Android Q&A, Help & Troubleshooting] SadioXao:
No Recovery from Boot Loop?

I do not understand most of this thread. I have 3x LGl34c. 2 of them have gotten stuck in Boot Loop. There is no recovery or safe mode option. None of the buttons that have been posted here work. I do not know anything about rooting or any of the bootloaders or extra files you guys are writing yourself.

I just want to get my damn phones to Boot up. It is just the eternal cycle of Black screen, buzz, LG logo, black screen. I have accepted that Ill have to factory reset the ***** and lose everything on the phone, but I can't even get the thing to start.

The most recent boot loop started when the battery died and my daughter tried to plug it in to charge and power it on. Now it is stuck in hell. We have never rooted anything or even know how. The phone worked fine, she left it in her bag or a few days and let the battery die, then tried to power on and before the battery had time to charge.
[Android Q&A, Help & Troubleshooting] ibub:
The only way I can think of to help you without root access and without a custom kernel or a custom recovery is to post a link to LG support.

http://www.lg.com/us/support/software-firmware-drivers

Type in L34c and choose it from the drop down menu. Download the drivers for Windows and run the installation. Next download the mobile support tool for Windows and install. Start the support tool take the battery out of your phone and plug charging cord into computer and phone. Wait for the phone to be recognized. Type in your serial number and/or imei and choose recovery phone. The tool should be able to put your phone into download mode and reflash your firmware. You will lose all of your data. However Google may be able to resync that data later. Not sure. Good luck.

Edit: the individual driver windows will stack in front of each other during installation so spread them out to be able to access them all. Do Not close any of these windows until you have installed them all.
[Android Q&A, Help & Troubleshooting] LeoPap:
I have a kind of same problem.

My phone is stuck on this screen and nothing works, I've tried almost everything i found on net... Nothing! A friend told me to boot from sd a custom rom (cyanogenmod / lineageos) but my Lenovo S60a is not in their list... Any ideas?
[Android Q&A, Help & Troubleshooting] ibub:
In order to boot from sd your boot image would need to support it. A skilled developer might modify fstab and init.rc in your existing image and then bump the image to pass verification. But since you already have one image that doesn't verify you might actually be adding to the problem. Have you modified the phone?
[Android Q&A, Help & Troubleshooting] LeoPap:
My full story is here : https://xdaforums.com/android/help/help-phone-boot-t3726797

Yes, it was a big mistake, because the patch modified the phone for sure ...
[Android Q&A, Help & Troubleshooting] ibub:
From that warning screen it may be possible to enter fastboot mode and possibly unlock the bootloader. Then you could flash a custom recovery image, boot to that recovery and flash a stock or custom ROM.

https://xdaforums.com/showthread.php?t=2277112