Develop Bugs

Nasty Bootloop after Flash on Sprint G2

Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!

Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app

I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!

I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob

I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?

If they have parts on hand if not either a swap out or a sendoff

Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?

Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?

to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.

Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.

no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)

Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.

Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.

so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410

pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!

Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone

After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk

Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!

Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything

sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?

[Q] Nexus 7 Bricked due to 4.4.3 Update?

I'm hoping someone might be able to help me recover my Nexus 7 which appears to be bricked currently. It is the 2013 version, and it was never rooted initially and was running stock firmware. (By the way, I'm not the most proficient with messing with my Android devices or even with the terminology, so I apologize in advance if I might require clarification on some of the responses).
A few days ago, I woke up to discover that somehow my home screen had reverted back to the way it was upon initially getting the device. This wasn't a big deal since I didn't lose any data or apps, but I figured something might be wrong and even posted about it on Google's product forums. Then, last night, I attempted to update to 4.4.3 because it had been prompting me to do so for a week or two. It downloaded and attempted the update, but it failed. It then eventually restarted, but upon loading up Android I got an error message that stated:
System UID's Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
with a button to click that says "I'm Feeling Lucky" - I clicked the button figuring I could at least get back in to back up my data, but after about 30 seconds the device just rebooted again (all I managed to do was accidentally click the Chrome icon) and now it is just stuck at the initial boot-up screen displaying the Google text logo.
I have tried to hold down the volume button and hit power, and I get to a screen with 4 options I can cycle through: Recovery mode (which will just put me back the Google text logo), Power off (which turns off the device), Start (which puts me back to the Google text logo), and Restart bootloader (which brings me right back to this menu options page). I'm attaching a screenshot of this page.
I spent about an hour on the phone with Google support, but they were basically useless. I then did some research and downloaded Skipsoft Unified Android Toolkit and was able to get the device to be recognized when it was in that 4-option mode by the Skipsoft Toolkit. However, all fastboot options I tried didn't seem to succeed because the Bootloader was locked. I figured I would try to unlock it, and it told me that in doing so it would wipe my device (so be it I figured since I had already pretty much kissed my data on there goodbye at this point). However, it seems to try and wipe it (even giving me a prompt on the actual Nexus 7), but then just sits and does nothing that I can see (see attached screenshots).
Anyone have any ideas/suggestions? Thanks so much!

To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.

xbi0s said:
To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.
Click to expand...
Click to collapse
Thanks for the reply - I attempted your suggestion, but it didn't work because the Bootloader is still locked; and attempting to unlock the Bootloader seems to stall on erasing userdata.
Any other thoughts? Thanks!

Anyone else have any suggestions/ideas? Thanks!

mbressman said:
Anyone else have any suggestions/ideas? Thanks!
Click to expand...
Click to collapse
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.

Aerowinder said:
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.
Click to expand...
Click to collapse
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!

mbressman said:
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!
Click to expand...
Click to collapse
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.

Aerowinder said:
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.
Click to expand...
Click to collapse
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!

mbressman said:
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!
Click to expand...
Click to collapse
You can try different drivers. Uninstall current ones, and install the ones from my signature.

Aerowinder said:
You can try different drivers. Uninstall current ones, and install the ones from my signature.
Click to expand...
Click to collapse
Ok, so I removed the Clockworkmod ADB drivers from add/remove programs (or uninstall programs - whatever it is called now on Win7), then I went into device manager and deleted the driver for Google Nexus BootLoader Interface, and then I rebooted. After the reboot, plugging the Nexus 7 in showed no driver detected, so I downloaded your Koush Universal ADB drivers, extracted them, and used them to install the Google Nexus Bootloader Interface drivers again (that's what it detected for my Android when I pointed the device listed in device manager to the extracted folder).
I then ran "fastboot oem unlock" but it's still getting stuck at the same place: (bootloader) erasing userdata...
Anything else I can try?
Thanks!

Hi,
I have the same issue since yesterday. When I pulled my nexus from my backpack (charged 12 hours earlier) its battery was drained. After charging it nexus stucked on google screen during normal or recovery boot. Oem unlock also hangs on erasing userdata. I'm looking forward for any solution to this.
Maybe some ****ty update? I've got the LTE version.

Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.

mbressman said:
Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.
Click to expand...
Click to collapse
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.

Gawson said:
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.
Click to expand...
Click to collapse
Gawson - when you got it back did it still have your data on it, or was it wiped?

mbressman said:
Gawson - when you got it back did it still have your data on it, or was it wiped?
Click to expand...
Click to collapse
When I got it was wiped. Flash is on the mainboard so there was no way they could save my data. They do not migrate your personal stuff.
Now its working like new. In fact it has all new guts except battery and screen.
Only problem is that now auto brightness sensor is giving crap instead of useful data. I don't know if its hardware related or just 4.4.3 issue.

[Q] Need help fixing my Gnex

Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike

Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.

AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.

So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.

AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong

Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide

nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.

beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.

mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.

Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.

G4 Completely Bricked, help needed

Hi all,
After installing some OTA on a stock G4, the phone has itself stuck in a bootloop, where i get a screen: "Security Error, authentication fail #9". I can get to the recovery, where the only option is erase all, but even selecting that goes straight back to the error.
I was hoping i could use fastboot to reset it, but no PC i plug it into (windows and linux) is picking up the device. As in, my windows device manager doesn't even see something new plugged in, and linux lsusb doesn't see a device either, so of course fastboot isn't working. Any ideas? I've done much googling, but couldn't find anyone with the complete set of circumstances i have. I'd prefer to not have to send it back
Cheers,
David

did you root it?
if not, I highly suggest you to send it back than fixing it yourself, as the development of G4 is not yet matured and this *could* be a hardware problem, IMHO.

dgoemans said:
Hi all,
After installing some OTA on a stock G4, the phone has itself stuck in a bootloop, where i get a screen: "Security Error, authentication fail #9". I can get to the recovery, where the only option is erase all, but even selecting that goes straight back to the error.
I was hoping i could use fastboot to reset it, but no PC i plug it into (windows and linux) is picking up the device. As in, my windows device manager doesn't even see something new plugged in, and linux lsusb doesn't see a device either, so of course fastboot isn't working. Any ideas? I've done much googling, but couldn't find anyone with the complete set of circumstances i have. I'd prefer to not have to send it back
Cheers,
David
Click to expand...
Click to collapse
You don't say which model you have, whether you are rooted with a custom recovery, etc. If you WERE rooted with a custom recovery and you took an OTA (intentional or not) you could be screwed until/unless someone finds a way to address it.
...my$.02

you said Stock G4, have you had another countries rom on it and tried to return back to stock, what model is it ie H815....

dgoemans said:
Hi all,
After installing some OTA on a stock G4, the phone has itself stuck in a bootloop, where i get a screen: "Security Error, authentication fail #9". I can get to the recovery, where the only option is erase all, but even selecting that goes straight back to the error.
I was hoping i could use fastboot to reset it, but no PC i plug it into (windows and linux) is picking up the device. As in, my windows device manager doesn't even see something new plugged in, and linux lsusb doesn't see a device either, so of course fastboot isn't working. Any ideas? I've done much googling, but couldn't find anyone with the complete set of circumstances i have. I'd prefer to not have to send it back
Cheers,
David
Click to expand...
Click to collapse
Send the 815 model back
BAD ASS NOTE 4

If you didn't do a full nandroid backup before trying to update, then it's kind of on you

Strange somebody seeking urgent help, and vanished after writing incomplete details. People, pls forget about this thread.

r4Rok said:
Strange somebody seeking urgent help, and vanished after writing incomplete details. People, pls forget about this thread.
Click to expand...
Click to collapse
Yeah I have never understood why some people post mini-rants about needing help so bad but ALWAYS leave the details as murky as possible, logically speaking it just never adds up.

I think you can probably restore via KDZ. Check the appropriate thread and try.
At least you aren't stuck in Qualcomm 9008 like I am, where you have to wait for some kind of LG-only tool to be leaked to restore it.

duraaraa said:
I think you can probably restore via KDZ. Check the appropriate thread and try.
At least you aren't stuck in Qualcomm 9008 like I am, where you have to wait for some kind of LG-only tool to be leaked to restore it.
Click to expand...
Click to collapse
May I ask how you managed to do this and what were you attempting to do when this happened??

Bricked my GF's bootlooping G4 after trying to freeze it - please help

Well, my GF's G4 started bootlooping a few days ago, the local store she bought it from doesn't honor the warrenty and says it may be something we did. I didn't like hearing that and decided to take legal action.
In the meanwhile, she asked if the data can be restored, I started playing with it and reading online. The phone bootlooped anytime I took the battery out and reinserted it, then go off. I decided to put it in the freezer after reading about many successful attempts to boot the device. The first time I put it in a plastic bag for 5-10 minutes (when I took it out it had humidity on it which I wiped), it turned on! and went into Android app optimization and we were thrilled, It went off after 2 minutes so I decided to put it in again for 30-40 minutes in a sealed plastic bag (as many recommended), when I took it out it didn't turn on at all no matter how many tries I tried switching batteries, connecting to the charger etc. (it had humidity on it again when taken out of the freezer).
From then on, the phone won't turn on at all, I put it in a bag of rice in get rid of humidity/water but that didn't help and the device won't bootloop at all.
Now, I have no case as it doesn't bootloop and the store can claim there's damage not governed by warrenty, I can't claim it bootloops as it is a brick.
I'm worried the water caused corrosion which totally cancels her warrenty.
Hope someone can help me fix this out, cant believe I hope it will bootloop again.
Thanks.

What version of G4 have you ? H815 ? or other ?
you can try to flash official firmware with LG UP with .kdz file or if you have another G4 with .tot file
You must have computer with drivers installed and LG UP installed
Watch tutorial

It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.

YSAndroid said:
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
Click to expand...
Click to collapse
1. volume up and connect to pc
2. flash the "core disable" kdz/tot (whatever it is)
3. it should boot but it won´t be as fast as i has been

YSAndroid said:
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
Click to expand...
Click to collapse
To be honest with you pal i very much doubt you'll get it back working as the serial is a 505 which means it's included in the bad batch of faulty motherboards on the phone and its that which is causing the bootlooping , you need to tell the place where you got it that the hardware has failed out of your control if they don't help try contacting LG directly you could be lucky....

YSAndroid said:
Now, I have no case as it doesn't bootl
Thanks.
Click to expand...
Click to collapse
When I did the following steps, I was able to get back into the phone with all my apps and internal data right where it was. It only fixed the corrupt system files. It seemed to work like startup recovery on Windows. But as a warning, I've only done this once so cannot guarantee you the same.
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGM..._4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product...reinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
I was lucky and this didn't remove any of my data.
If you have problems with LG Bridge detecting your device:
i) Make sure you have the drivers installed and are using a reliable cable and USB port.
ii) Open up device manager and look for your phone. It should be named [...... COM#].
iii) Right click and go to the ports tab and click advanced. Select COM41. This seemed to work for me.