yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] yackaro:
it continues even after unplgging. so the USB isn't what's causing it to loop it. I try to shut it down and that basically restarts the loop early rather than shutting it down. i have to wait for the battery to finally die for it to shut off. if i just plug it up it shows the normal charging icon.
[Android Q&A, Help & Troubleshooting] toxinburn:
Yackaroo I think I can help you please lemme teamviewer you thru Linux I have had same prob I'll check inbox later I'll give you my number if y'all want thru privmsg
[Android Q&A, Help & Troubleshooting] yackaro:
ok i don't do privmsg but i do do skype and oovoo

i can't do it right now i have some stupid appointments i need to attend to.

I should be available at maybeeeee 7 pm? maybe a little later.
[Android Q&A, Help & Troubleshooting] toxinburn:
Yea that's good my Skype is toxinburn I'm working right now but send me request I'll help u out later
[Android Q&A, Help & Troubleshooting] tunglethanh90:
use KDZ flash tool Flash stock rom
[Android Q&A, Help & Troubleshooting] thc2013:
May you give details on how to flash it?
[Android Q&A, Help & Troubleshooting] yackaro:
wow how did i get bricked like that without going into bulk mode? LOL strange, we tried though at least,going to take it back for replacement when i can get my hands on the box (which i left at my father's house) how long did we spend over teamviewer trying to get ubuntu to read the blessed thing? 1 hour? 2? idk LOL. i just know no hope for this phone.
[Android Q&A, Help & Troubleshooting] XDA_BUST:
Recovery SD Update Signature Verification Failure

I’m trying to create my own SD update package for the L34C, but I can’t get it to work.

I’m using the signapk.jar to sign the file and a test key file that came with the signing tool.

This is the command I used to sign my zip package:

signapk –w publickey.x509[.pem]privatekey.pk8 input.zip output.zip

I’m able to sign the package but then when I try to actually flash the phone in recovery mode it fails

I attached a picture of the error displayed on the device. Here is the text:

Verifying update package...

E: footer is wrong

E: signature verification failed

Installation aborted.​

I can’t get past the signature verification. I am able to apply an SD update for the L40 on this phone without a problem and it looks like they are signed with the same test key. So, I can’t figure out why it’s not working? I think my error is when I signed it. I also used “auto-sign” which uses the signapk.jar utility.

Any ideas?
[Android Q&A, Help & Troubleshooting] FlyingPoo:
I know this sounds like a shot in the dark, but make sure you have built the .zip with the "store" option and no compression. I spent like a week once trying to figure out the issue, turned out to be something as simple as that.

More on the actual error, if its the footer, that is typically where hash tables and signatures are stored, so It could be some weird hiccup with the signing of the hash table.

I say rebuild the .zip from scratch and try again. Maybe delete the contents of the L40 update package that works and replace it with what you want to flash, resign the updated L40 update.zip and try again. Or don't resign it and see what happens.

Also may be that our recovery doesn't like the test key? Im digging around files to find a cert file specific to this device L34C, I'll post back with finding laster, if no one beats me to it.
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5185336]XDA_BUST[/MENTION]

I have same result flashing from /cache. Modified the root zip from this thread:

http://xdaforums.com/showthread.php?t=2732311

Since I already have everything in the zip, I deleted content of directories directly from zip (empty flash). I've done it this way numerous times in the past. My file manager automatically rezipps, and it works. I think that the stock recovery verifies only the correct signature, as [MENTION=3646165]FlyingPoo[/MENTION] says.
[Android Q&A, Help & Troubleshooting] ibub:
Ok I was wrong. I flashed the unaltered zip, and it flashed just fine. This was my first ever successful flash using a stock recovery. [emoji1] I've been looking at the error messages contained in aboot, recovery, boot (kernel). This phone has so many safeguards, that we'll have to be very careful about what we choose to flash.
[Android Q&A, Help & Troubleshooting] TECHADDICT5610:
Help Please-Can't get full system boot, or Recovery

Ok, Folks, This is a request for some help with this little phone:

Before I copied Build.prop file back to the system directory, I had Root with the TowelRoot method. No problems with the phone until copying the Build.prop file from SD card back to the system directory. Now the phone will only show the Home button pulsing with different colored lighting.

I can get connected with ADB, and ADB Shell is responsive, but I am not familiar enough with the shell to get my backup of Build.prop file back into the system directory. Also have tried the method above to get into recovery, but get bootloader verify error...so I am stuck for now. Surely it is a simple fix for someone that has a lot more experience with ADB, and the shell. I just need the verbatim strings to paste into the shell to get past the read only problem, and the exact syntax for copying from the sd card to the root system directory. This phone has so many checks built into the system, but I am determined to keep researching, and testing things. Thanks.
[Android Q&A, Help & Troubleshooting] ibub:
Possibly, you didn't set permissions by using chmod. I am by no means proficient with adb, but I'll give this a shot. Might double check my syntax. Permissions of my build.prop are 644.

But first need to mount /system as read/ write.

Syntax:

mount -o rw, remount /system

or

mount -o remount rw /system

Copy

cp C:\pathtobuildprop /system/build.prop

Change permissions

chmod 644 /system/build.prop

Then mount system as read only.

mount -o ro, remount /system

A good reference for adb is here:

http://xdaforums.com/showthread.php?t=1364089
[Android Q&A, Help & Troubleshooting] TECHADDICT5610:
Build.prop problem
[Android Q&A, Help & Troubleshooting] ibub:
I found a very good reference that explains a lot concerning the title of this thread:

http://source.android.com/devices/tech/security/dm-verity.html

Tells OEMs how to verify during boot. Might be useful. ?
[Android Q&A, Help & Troubleshooting] TECHADDICT5610:
Build.prop problem-solved

ibub!

I have unbricked my little Fuel!

Once again, much thanks for your help. As promised, I wish to share some helpful info here. If anyone has mucked up your build,prop file, and has a backup of the file,....here is what I pasted into ADB to fix my messed up, and rm'ed build prop file:

adb push c:\build.prop /sdcard/

adb shell

su

mount -o remount,rw /system

cp /sdcard/build.prop /system/

chmod 644 /system/build.prop

mount -o remount,ro /system

This is assuming you have a backup of the file, and it is in the root of your C:\ drive.
[Android Q&A, Help & Troubleshooting] ibub:
Yeah, I have a feeling that we'll be helping each other...a lot. [emoji4]
[Android Q&A, Help & Troubleshooting] thc2013:
I'm waiting on custom recovery come to life:)
[Android Q&A, Help & Troubleshooting] wmt9905:
Unbrick Optimus Fuel

how did you get the su authority? with my device i was able to push the build.prop to the sdcard, but then it's a catch 22 from there. i can't get the file to copy to the /system partition without remounting, but can't remount without su and obviously can't chmod either. however, i can't get the device to go from the shell to su. when i bricked, it made me lose the root privileges i had towelrooted prior to it.
[Android Q&A, Help & Troubleshooting] ibub:
I think you need to have previously allowed access. Mine prompted for me to allow 123abcxyz computer. But strangely, it didn't look like Supersu prompt. Should have looked closer.
[Android Q&A, Help & Troubleshooting] TECHADDICT5610:
I think I was lucky with it because I suspect my device was only Soft Bricked. I had it rooted with towelroot, and had the SuperSu installed before I fouled up my build.prop file. I was able to get the # prompt in ADB Shell before I made the mess for myself. Thankfully I had enough sense to back up a lot of the system files. If you need any copies of files, let me know...I will upload whatever I can to help you. Also, take a look at the link below. It may be relevant to communication problems in ADB. I followed the recommendation when I first got my L34C, and it helped me get connected in ADB.

http://xdaforums.com/showthread.php?t=2180619
[Android Q&A, Help & Troubleshooting] rootappdel8r:
Feel dumb

I have 3 of these nice little fuels. I towelrooted all 3. Got root on all 3. Started using root app for disabling bloatware. Dont use these phone as phones just using them as android devices so I was trying to remove all the stuff related on there that might be slowing it down. Well.. I definitely disabled something I shouldnt have cause now 2 of the 3 boot loop. Everynow and then they will show actually logged in and booted but reset into looping right away. I use linux and am slightly familiar with using adb. Any suggestions on what I should do here to get these 2 I most likely soft-bricked? Any help would be great. Is there a way I can maybe pull off the working phone and push to the ones i messed? Thanks in advance.

for a little more detailed info I am getting past the LG screent to the blue trackphone wireless screen. it is the blue trackphone wireless screen that is looping. I am trying to see if I can get the device detected and usable thru adb while it is looping thru but i could probly use a little help with this part. Id imagine if I can get adb to push n pull I should be able to use files from other phone to this one?
[Android Q&A, Help & Troubleshooting] thc2013:
the problem with mine is Google services and Google play store not working and neither is package installer
[Android Q&A, Help & Troubleshooting] yackaro:
That's A Unique Problem I've Never Heard Of Happening Before.
[Android Q&A, Help & Troubleshooting] thc2013:
your telling me I'm waiting on custom recovery to fix it with another one [emoji1] it doesn't mess with txting,picture mms or calling so it's not a bother but if I can fix it I will [emoji1]
[Android Q&A, Help & Troubleshooting] SuddenlyJelly:
I'm having a similar issue...

Mine is stuck just sitting at the blue tracfone screen. I can talk to it with adb but I can't reboot recovery. What files would you push that could reset any damage done to the phone? I might get another one and try to fix this one...
[Android Q&A, Help & Troubleshooting] thc2013:
mine don't reboot in recovery either through settings don't even work
[Android Q&A, Help & Troubleshooting] ibub:
Did you take out GMSCore.apk from /system/priv-app? This is needed by Google Play services, Google Play Store, etc.
[Android Q&A, Help & Troubleshooting] thc2013:
how do I put them back on it without getting errors?
[Android Q&A, Help & Troubleshooting] ibub:
After copying an apk to /system/app or to /system/priv-app, set permissions to rw-,r--,r-- , or 644 depending upon how it is displayed in your file manager. Or you could use terminal command:

chmod 644 /path/to/appname.apk

For example,

chmod 644 /system/priv-app/ gmscore.apk
[Android Q&A, Help & Troubleshooting] thc2013:
So this get package installer to work again and Google apps again?
[Android Q&A, Help & Troubleshooting] ibub:
Make no promises, because I don't know all of what you've taken out. But it's a good step towards making things right. If it works, there will be a delay, as Google Play Services will automatically update. You won't even see the update because it happens in the background. But eventually you will find it under settings >apps >downloaded apps.
[Android Q&A, Help & Troubleshooting] thc2013:
I put every back on that I seen was missing and now I get different error Unfortunately, the process com.Google process.gapps has stopped. getting closer to fixing it ?
[Android Q&A, Help & Troubleshooting] MasterKairi0:
windows fix

I need a fix to undo lg bootloop brick from dying to use a program to modify the graphics calld opengl ...can you help? Has to be forwind9ws os
[Android Q&A, Help & Troubleshooting] thc2013:
what did you do to get it to boot loop
[Android Q&A, Help & Troubleshooting] thc2013:
my package installer is last that's messed up I got progress though google play store,accounting syncing,YouTube is working,can install off Google play but not third party after I fix it should be good as new [emoji1]
[Android Q&A, Help & Troubleshooting] wmt9905:
Unbrick Optimus Fuel

thanks guys, but i did previously have su authority through towelroot and then supersu.apk. i am able to get to the shell, just not the su command line. i did backup my device system prior to the brick also, but when i bricked, i lost most of my connection ability through any other app/utility other than adb. however, when trying to install/push new .apk's, i get an error that the package installer can not be accessed to complete the process.
[Android Q&A, Help & Troubleshooting] wmt9905:
Unbrick Optimus Fuel

Additionally, does anyone have a working .kdz file for this device? that may be my only shot at this point, as my laptop won't let me dual boot it with linux.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
windows fix for lgl 34c softbrick

what i did IBUB is i installed an alternative to gl tools for android 2.3 backwards but because i had 4.4 it soft bricked when i installe dthe beta egl driver i forgot what the name of the app was
[Android Q&A, Help & Troubleshooting] ibub:
Don't know anything about graphics drivers. Build.prop shows opengles version =196608 or 0x30000 for version 3. But I wouldn't know what files get altered without doing some research. App name would possibility help. [MENTION=5345928]toxinburn[/MENTION]?

Ok Trinity, plug me in...lol
[Android Q&A, Help & Troubleshooting] MasterKairi0:
chainfire 3d semibrick

found it its called chainfire 3d thats what bricked my lgl34c optimus fuel :/
[Android Q&A, Help & Troubleshooting] ibub:
Found this:

http://xdaforums.com/showthread.php?t=2362873

May need to alter the method according to what mode is available. ;)
[Android Q&A, Help & Troubleshooting] MasterKairi0:
cant access device in adb it doesnt connect to adb

so i cant install the device driver either :/ this is an optimus fuel cant access recovery or anything just gets stuck at LG logo (first one )
[Android Q&A, Help & Troubleshooting] ibub:
Can you access phone via adb, while stuck at LG logo?
[Android Q&A, Help & Troubleshooting] thc2013:
hey ibub any way to the package installer to work again on phone I got Google problem resolved just need get package installer to work any ideas?
[Android Q&A, Help & Troubleshooting] ibub:
Don't really know. Might try going to settings >security, and toggle install apps from unknown sources, reboot. Really don't have much of an answer. Let me search around a while.
[Android Q&A, Help & Troubleshooting] thc2013:
I get error going into settings
[Android Q&A, Help & Troubleshooting] MasterKairi0:
cant access adb

i cannot access the device in adb but perhaps you can find a way to manually lock it in ive tried nearly everything i can find to lock it in but none of those processes works as of now :/ really need this phone working
[Android Q&A, Help & Troubleshooting] ibub:
No ADB...no access. Windows or Linux? I have not had any luck with ADB in Linux. But working in Windows power shell. Drivers installed? Worked with my old LG drivers, or Windows automatically updated them. Never looked.

Edit: Just tried adb on my old LG p500 in Linux, and it works just fine. Updated to latest SDK. Still doesn't work on the fuel. Guess I need to edit build.prop or default.prop. Although it may be time to buy that test phone. Need this one working.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
okay :)

and i use windows 8.1 and everything is right drivers and everything the phone doesnt get far enough to access adb i guess lol
[Android Q&A, Help & Troubleshooting] thc2013:
I use Windows 7 I don't like windows 8 or 8.1 ?
[Android Q&A, Help & Troubleshooting] nakperry:
Try holding the volume down button while system is going through loop. My LGL34C will go to Safe Mode, show error messages and then reboot. I got it to stop the loop one time and it was frozen at the Tracphone screen which I was able to connect the LG Support Tool. I eventually was able to boot the system up in Safe Mode and I did a factory reset, the system is still boots in a loop with the reset. I giving up and now that my data is wiped I am going to try to send back to LG for service.
[Android Q&A, Help & Troubleshooting] ibub:
Able to access via adb while stuck at tracfone screen?
[Android Q&A, Help & Troubleshooting] nakperry:
I did not even try adb, because I would not know what to do there. I just opened the LG mobile System Tool and it connected and I tried the Upgrade Recovery option with no luck, eventually it booted completely into the Safe Mode and I just Reset the system.

The error messages are:

Unfortunately, Wi-Fi aggregation has stopped.

Unfortunately, com.android.keyguard has stopped.

---------- Post added at 09:11 PM ---------- Previous post was at 08:45 PM ----------

I was able to get my system up and running just now, like was able to do a few other times.

The problem if I reboot I am certain that it will go back into a boot loop.

I removed battery and pressed power button for a 5 seconds and then battery back and held power and volume down until it buzzes and I release the power button while still holding volume down and I release the volume down once the Safe Mode screen comes up and it rebooted next time in a working system.

Any info why I get the error messages, Unfortunately, Wi-Fi aggregation has stopped. ,Unfortunately, com.android.keyguard has stopped.

Could it be a hardware problem??
[Android Q&A, Help & Troubleshooting] toxinburn:
man if i was you i would overwrite all your partitions with stock partitions again, i had a bricked fuel and somehow miraculously i had it laying with the battery out for two weeks and a guy with similar prob mentioned he shorted the two middle battery terminals after booting phone he removed battery then shorted wires and device manager would see a new device, so i did this and then after awhile i noticed it was seeing another device so i tried to adb shell to it and somehow it started working again, shell only at the time so i used adb push to get my stock partitions pushed back to the internal sdcard then used dd commands to overwrite the boot, aboot, and system partitions then did adb reboot and somehow it works again....and just two weeks ago i would try to shell and would get device offline, i would get lg logo then black screen and led lights flashing....everything was the same this time except shell worked finally.
[Android Q&A, Help & Troubleshooting] jplee3:
Oh man, this isn't good. I got a Optimus Fuel from Walmart back in late mid-late July for my wife and got it working fine on Page Plus until tonight. She said it was acting weird all day and finally within the past hour or so I saw it sitting just charging and stuck on the LG boot screen. :( I don't *think* I even rooted the thing either! I'm trying to recall whether or not I did but I don't think I did. All I recall doing out of the box was activating it onto Page Plus right away and just getting it setup and customized for her to use. Now all of the sudden the stupid thing dies on her!

Dunno what to do - I've tried hard resetting per the manual and per various methods posted here but no go. Seems this thing is just dead. When I connect it to my Macbook Air I see the little Android guy pop-up but it's not recognized by adb or fastboot at all. This is super-frustrating... I ordered a couple Boost Moto Gs and plan on unlocking/rooting/flashing them over to PP so hopefully I don't have as horrible an experience I am with this little Fuel.

I'm already outside the return policy for Walmart but maybe I'll call just to see if they'll be nice and take it back. Otherwise, I'm SOL and stuck with working with LG to try to resolve this. Arghhhh
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

Glad that you are back brother. I had previously tried to boot with battery out and plugged in. Got no battery error. Never occurred to me to boot first and then pull the battery. Wonder if kernel enables adb under the shorted condition. Default.prop says ro.debuggable =0

and

persist.sys.usb.config =boot

But on my p500 it says

persist.sys.usb.config =adb

Haven't tried it yet, but I think that a reboot will only restore the previous values. Or If I recompile it into the kernel, the verification will fail, and I'll have a brick, lol. Possibly a script to run at startup (late) could enable adb for me in Linux (works in Windows).
[Android Q&A, Help & Troubleshooting] vwnut13:
Well, it appears that I've finally ruined my Fuel.

Accidentally restarted it when TiBu was converting an app to a user app.

I'm stuck at the LG logo and adb will not recognize.
[Android Q&A, Help & Troubleshooting] ibub:
Maybe try to boot into safe mode, by volume down and power. If able to boot, could connect computer, pull battery, and short middle two battery connectors to get recognized, as [MENTION=5345928]toxinburn[/MENTION] has posted.
[Android Q&A, Help & Troubleshooting] yackaro:
I tried this, is it supposed to be able to completely boot into the OS?
[Android Q&A, Help & Troubleshooting] ibub:
See posted by [MENTION=5987461]nakperry[/MENTION] above.
[Android Q&A, Help & Troubleshooting] yackaro:
so it needs to be able to fully boot? well that shine of hope just vanished for me.
[Android Q&A, Help & Troubleshooting] MasterKairi0:
driver for usb tool ?

which lg driver did you use for the lg mobile download tool ? i cant find the lgl34c
[Android Q&A, Help & Troubleshooting] vwnut13:
Can't get into Safe Mode. I know it's possible, I accidentally did it a time or two when trying to get into recovery. ;)

I think I'm going to buy a new one and chalk this one up as a (non-total) loss. It seems that I could easily swap the motherboard from a new phone into this one. Then I would have an extra casing, extra screen/digitizer, and extra battery for $30. Saving hours of work (frustration) and getting some spare parts for $30 doesn't seem like a bad deal at all.

My family uses these phones with Straightalk, and this 'revelation' will save a ton of hassle in the future. You cracked your screen? Just buy a new one and swap the screen from the new one. You've instantly got your old phone back, no need to install any apps or anything, it's all there. Oh, and best of all, no need to activate/deactivate with Straightalk.

Now, a question I have, and it's related to what caused all this. Has anyone else got the stock android gallery to work on this phone? I hate the LG version!

I was unsuccessful when trying to direct install the Stock Gallery from 4.4. So I took the Stock Gallery APK (1.1.30682) from my Kyocera Event (4.0.4) and installed that onto the LG L34C successfully. I once again tried to install the 4.4 version, but again was unsuccessful. So I downloaded the 4.3 version of Gallery, and that installed! Even better, it installed the 4.3 Camera (part of the gallery app) as a nice bonus.

I froze the stock Gallery app and rebooted. Oddly enough, when I rebooted, the LG version showed up again, so I uninstalled it. Then I noticed that the Edit feature of the new 4.3 Gallery caused the app to crash after I rebooted. It was working fine before. I was going to convert it back into a user app (don't know why really), uninstall, then reinstall it. When converting it back into a user app TiBu seemed to be "stuck", so I stupidly restarted, and... bootloop.
[Android Q&A, Help & Troubleshooting] ibub:
[MENTION=5345928]toxinburn[/MENTION]

I only found the first 7 characters of the string:

20 00 eb 00 00 50 e3

at address 32461.

Possibly they used different bootloader, or have edit and compile to their own use. Just speculating.

Edit:

Don't know if we can flash new unlocked aboot. Possibly sha256 verification, but don't know. Also would different bootloader properly load kernel(s)?