First of all, yes I have gone through droves of posts on XDA and frankly it’s a mess, but I can tell you that after following a few threads that just refer to themselves in loops, there’s no actual solution.
I have an LG US730 which was rooted and everything was great. I must have toggled something in SuperSU - I think maybe the option to be rooted during boot.
Anyway, now all I get is Security Error and it shuts off. None of the recovery power on switches will work. The only thing I could do is VOL+&- power while the usb is plugged in and it goes to a download in progress screen. Of course nothings happening and I need to remove battery in order to get this powered off at this point.
Anyway, I’d love if anyone has a tool to repair this. LG’s utilities all do nothing at all I think they’ve purged the back-end of older stuff so the programs that should download something and proceed simply wait forever.
Figured out what you meant. No, fastboot devices does nothing. And I did search xda I can’t find anything that makes sense.
Just to confirm, when your phone is connected to your computer with a USB cable and in the download in progress screen, running
fastboot deviceson the computer shows a message to the tune ofno device connected?If that’s the case and the other startup combo actions do nothing, the phone is dead.
Yeah neither adb nor fastboot see it.
This really sucks. It would seem it’s bricked, but then I have read lots of articles that swear that it is not hopeless.
The problem is LG has purged all files related to this device. Any download links or menus etc. you can find lead to dead links. I spent many hours and checked easily like 20 websites. There’s absolutely nowhere to be found an original rom image. Nada, nischt, zilch, bupkis, squat. Even the few XDA mentions are dead links :-(
I’d love to get it running again, but for now at least, I have stuff to do so this goes on the back burner. I have it in my box should I ever want to take another crack at it.
Say… you feel up to a minor challenge? I have like a dozen devices and I wish to document what are the possibilities for each of them, vis-à-vis alternate rom such as havoc, resurrection remix, etc., or aosp / gsi, or just rooting if that’s all that can be done. This way I can know what to prioritize trying.
I gotta tell you I find the XDA forums to be absolute chaos and incoherent. I’ve tried very sincerely to make sense of it, but sometimes I go to the forum for a device and it’s post after post with titles that don’t even contain a single actual word, it’s just acronyms and version numbers. And I’m sure that makes sense to the pros, but I can’t even figure out where to look for a starting point. So that’s why I’d like at least to catalog my options and then I can proceed knowing I’ve got starting points to look for.
If you’re up to it let me know I’ll post a pic of all the devices labeled. No worries if you’re not interested, I know it’s a pain in the ass what I’m looking for. Anyway thanks for trying to help with the LG. I’m not giving up hope yet, I love that little phone it’s sweet.
Have you tried internet archive? I don’t think it’ll help with your specific problem because only LG tools can fix this and I suspect they want to use original URLs even if you can find the file.
Sure, I can’t guarantee I’ll succeed but I can take a look.
I just wanted to let you know I have not forgotten; I’m working on compiling an album of all the devices I’d want to consider. It’s a fair bunch, but honestly whatever insights you could offer will be so appreciated, and if you have no ideas I will still appreciate the effort. I should have it posted by later today.
Ok my friend, here is my bunch of devices that I have available for customization. My idea situation would be anything that lets me get the best out of the device. If that means Lineage, or Havoc, or any of the other dozen or so ROMs, or even just GSI or AOSP. Barring any of those as an option, root access at least so I can manually debloat it a little.
My devices
galaxy a12: lineage this tutorial: https://xdaforums.com/t/guide-gsi-installing-lineageos-or-gsi-roms-for-a127f-binary-u7.4513051/
galaxy grand prime: i’m not teaching you to bypass FRP. this is a stolen phone.if you ever get it unlocked, and can find a functionnal aromainstaller download: https://xdaforums.com/t/rom-aroma-pre-rooted-stock-rom-g531h-pre-rooted-deodexed-debloated-stock-rom.3551178/
galaxy j7: flash lineage by following this https://xdaforums.com/t/rom-sl-lineageos-19-1-for-j7-2017-pro-alpha.4604345/
desire 530: technically lineage is available but no tutorial and probably unstable: https://xdaforums.com/t/rom-6-0-lineageos-13-0-for-htc-desire-530.4682192/
j3: lineage with tutorial: https://xdaforums.com/t/rom-lineageos-14-1-for-samsung-galaxy-j3-2016-sm-j320fn-f-g-m-unofficial.3667015/
galaxy s5: lineage from this link (no tutorial): https://xdaforums.com/t/unofficial-lineageos-19-1-android-12l.4427639/
moto e4: lineage with vague tutorial from: https://xdaforums.com/t/rom-unofficial-woods-darklineage-14-1-20200913-mod-of-lineageos.4162339/
galaxy s III: locked to verizon so probably not possible, this might work, it might not https://xdaforums.com/t/rom-unofficial-14-i9300-lineageos-21-0-alpha.4648114/
lg us110: couldn’t find anything
lg d415: https://xdaforums.com/t/rom-official-cyanogenmod-11-for-lg-l90.2831541/ maybe
l38-c: couldn’t find anything
us-730: is already bricked as you know
moto x: lineage (no tutorial) https://xdaforums.com/t/official-lineageos-18-1-for-the-moto-x-2014.4255337/
i won’t even try the last 2 what the fuck is this
I’ll look through these thank you!
Ooh sorry about the galaxy S3 I actually already rooted it that’s all I expected to ever be able to do like you said Verizon locks the boot loader.
FRP does not mean stolen phone. More often than not it’s one of many many other reasons. But that’s fine you don’t do something you’re not comfortable doing. Totally respect that. It’s just a very quick thing to conclude when more often that’s not the reason.
Also, I know many ways to do it and have succeeded on many, but sometimes something in the phone is glitched. As is the case here.