Database Info

[Q] Did I brick my Nexus 5?

Hello...
I have a horrible question. Did I ruin my Nexus 5? The short story, or just the problem I am having is that the phone is "Boot Looping", it launches as far as the 4-color animation, restarts, and repeats.
I downloaded WugFresh's toolkit and attempted to flash to stock. At this point the phone was on and operating, but the radio didn't seem to be working properly after I attempted to return to stock using a guide on youtube. When using this guide I got as far as the final command, fastboot -w update image-hammerhead-krt16m.zip. Every time I attempted to run this command a dialog box would inform me that fastboot had stopped working. So I attempted to use the toolkit Provided by WugFresh. I selected the option for a phone that was on and functioning and clicked "Flash Stock + Unroot. Everything went as I expected until it seemed to stop working, and the command window said: "erasing userdata". It would I left it like this over night and the phone was NOT booting.
I now am attempting to "Force Flash" with Wug's kit. But it's hanging on "writing system".
Can anyone advise me on what I should do next? Is my device completely bricked? What are my options? :crying:

I am going to try this: http://forum.xda-developers.com/showthread.php?t=2513937 I am going to assume that WugFresh's toolkit will NEVER finish "writing system".
I still seek council.

I would try this http://forum.xda-developers.com/showthread.php?p=47156064
I don't like tool kits and one click methods
When it's writing system how long do you give it? It can take like 5 minutes

BrightLancer said:
I downloaded WugFresh's toolkit and attempted to flash to stock.
Click to expand...
Click to collapse
That's why you should NEVER ever use a toolkit, I've seen too many instances just like this.
Use this guide to flash factory images, it's stickied in the general section :http://forum.xda-developers.com/showthread.php?t=2513701
Edit: As long as your phone can boot to the Google logo/fastboot, its all recoverable, so don't stress. And in many cases it can be recovered even if you can't get to the Google logo
Sent from my Nexus 5 using Tapatalk

jd1639 said:
I would try this http://forum.xda-developers.com/showthread.php?p=47156064
I don't like tool kits and one click methods
When it's writing system how long do you give it? It can take like 5 minutes
Click to expand...
Click to collapse
I gave it more than 2 hours. :/
I will try your link. I have had no success with method in the link I posted.

I just tried the method you suggested (above poster) and once again it seems to be unable to get past 'erasing "userdata""...

I just tried erasing "userdata" with the "fastboot -w" and it appeared to be working... until fastboot stopped working and launched a windows dialog box as previously described. I read in a different thread, regarding a nexus 7 with a similar issue, that using a different computer with fresh drivers, solved the issue... Anyone have any ideas what is preventing userdata from being erased? Or maybe that is not my issue... Rawr!
Let's solve this!!! Come on guys! Guys?
Humor aside, I appreciate the suggestions so far.
Any one else have any ideas?
Edit: Thank you for the reassurance!

Can you boot into your coustom recovery/ normal recovery (Volume down and power, keep holding them till you see a menu) if you can do that you're fine
Sent from my Nexus 5 using xda app-developers app

I fixed it... I used a different computer, an idea I got from this thread: http://forum.xda-developers.com/showthread.php?t=2424390
I appreciate all the help and I hope that someone wiser than I can isolate exactly what the problem is... Dome kind of driver issue if I know anything...
I really appreciate the quick and sincere replies to my questions and I look forward to being a part of the community.
-Kevin

[GUIDE] How to recover from OnePlus soft bricked?

I decided to write a guide on how to recover from a bricked OnePlus One. This is my first guide.
About me: I am a newbie on Android.However, the XDA community has taught me a lot about my Android phone for the first month of using it. That's right! I have only been using Android for less than one month so take this guide with a grain of salt. But if you happen to soft brick your One, this is the guide to turn to. I have created two mind-bending/heartbreaking/frightening scenarios that I have experienced. Though, resolved thanks to this community.
Note: This will wipe your phone!
Scenario 1:
Soft bricked, (CM gear keeps spinning but won't boot to lock screen)
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
How to find out if you have unlocked bootloader:
1. Locate the folder where you installed the OPO Toolbox.
2. Hold Shift and right click on ANY white area within the folder.
3. Left click 'Open command window here'
4. Type:
fastboot oem device-info
If it returns True on tampered. Then you have unlocked your bootloader.
I hope this guide helps solve your soft-bricked problem. Good luck!

I suggest that a mod moves this to the General section

pandasa123 said:
I suggest that a mod moves this to the General section
Click to expand...
Click to collapse
Report the thread if you think its necessary.

Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:

Digital Arm said:
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Click to expand...
Click to collapse
You don't have an unlocked bootloader.
Transmitted via Bacon

timmaaa said:
You don't have an unlocked bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx got it:cyclops:

Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
Hi i am stuck in scenario 2...I did all a u said but i cant flash CM XNPH22R ...where do i find this file...i cant find it on my phone either ..pls help ??

Thank god for this thread omg, saved my life

Locked Bootloader
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??

RiccoSuave said:
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
Click to expand...
Click to collapse
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.

Champi12301 said:
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Click to expand...
Click to collapse
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.

RiccoSuave said:
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
Click to expand...
Click to collapse
Then first you need to unlock the bootloader via fastboot,but that action erases all data. I assume,if you modified the boot via fastboot, USB DEBUGGING is working,so after try to do the softbrick tutorial of the thread.
Tecleado desde mi 1+1.

how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!

deanwinchester370 said:
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
Click to expand...
Click to collapse
Did you find a solution ?
I'm facing the exact same issue on my OPO.
>> bootloader locked
>> no recovery
>> impossible to unlock the bootloader
>> OPO stuck at 1+ logo and keep rebooting agin and again and again...
....i think my OPO is dead T_T
Is it a way to force the bootloader unlock ?
Please HELP !!!

Didn't work for me
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.

All done
davmeva said:
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
Click to expand...
Click to collapse
No one replied to this but never mind, took me two days but I now have a working phone. So you can call in the dogs, cheers

hi davmeva
did you fixed your oneplus one till now or not because i have also same situation here and no success till now .
i did by mistake all this stuff and now nothing work still same condition
if you got any solution please share it

[Q] Tried installing Drivers for Shield Tablet, is it bricked?

All I want to do is root this thing, and after spending the better part of a day updating firmware, it seems I screwed the pooch doing that first.
I tried my best to follow the outdated tutorials, first step of each sent me onto another tutorial, etc. So I had device manager up, I sent it to look for the Universal Naked Driver, it said I was up to date, plugged along. Mini ADB and fastboot went up, my shield was in dev debug mode. ADB reboot command fails, and now my tablet won't power up with the hard key, and the computer wont recognize it.
Are there any solutions to this problem?

If the tablet doesn't power up maybe u have to send it to nvidia. [emoji20]
I just followed this
http://forum.xda-developers.com/showthread.php?p=57478001
And everything worked fine.

BareGrizzly said:
All I want to do is root this thing, and after spending the better part of a day updating firmware, it seems I screwed the pooch doing that first.
I tried my best to follow the outdated tutorials, first step of each sent me onto another tutorial, etc. So I had device manager up, I sent it to look for the Universal Naked Driver, it said I was up to date, plugged along. Mini ADB and fastboot went up, my shield was in dev debug mode. ADB reboot command fails, and now my tablet won't power up with the hard key, and the computer wont recognize it.
Are there any solutions to this problem?
Click to expand...
Click to collapse
Seems quite strange that it would get bricked since you seem to have not done any operations to the tablet at all. Did you try to flash anything while in adb or fastboot? Are you holding down the power button long enough to power on? You need to hold that mushy button for what might seem like forever. There are tools like Win Droid that do what you're trying to do.
But yes, seems like you might need to send it in if the tablet is actually bricked.

Fustigador said:
If the tablet doesn't power up maybe u have to send it to nvidia. [emoji20]
I just followed this
http://forum.xda-developers.com/showthread.php?p=57478001
And everything worked fine.
Click to expand...
Click to collapse
That was the one I started with, but I had to follow the breadcrumbs through the separate tool threads.
I factory reset the device before beginning this process, I hadn't entrenched myself in the tablet since I've only had it since last Thursday. Doubt that has bearing.
I'd noticed software issues, freezing in and out of the lock screen. This was high among the reasons I decided to root it. Its possible I got a lemon, and if I didn't muck up the bootloader its still under factory warranty, correct? Should I contact Amazon who I bought it from before contacting Nvidia?

If it doesn't turn on maybe it as nothing to do with unlocking the bootloader.
Just activate the waranty.

I charged it overnight, and turned it on via recovery (down volume and power). It seems to be running fine now. Thanks for the advice, and I'll continue the process in the appropriate threads.
:good:

[Q] Hard Bricked LG G3.

The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.

voxoph said:
The issue with my phone.
I can't get into Download mode, computer won't pick it up and non of the buttons work. So I can't just flash a new rom.
It happened when I was trying to install This(I was being stupid and didn't look at the device.) So is there a way to fix it?
Things I tried and have
I have tried ADB, and fast boot they all get stuck waiting for the device (on every port).
I have the laf file. BUT here is the main issue my computer won't pick it up rendering the laf file useless.
I have looked on the forums and all methods purposed. Were for 32 bit computers or didn't work.
Signs of Life (Update One)
It just showed signs of life. It was dead so I charged it and the LED was flashing red and it charged now it is back to black screen and now sign of life though. I tried ADB on my tablet (didn't work) so I know the ADB issue might be my computer. That is good news because it means there is a chance of fixing it.
I am going to try to use ADB on my other computer to see if that works. If it does then there may be a chance of fixing it.
Click to expand...
Click to collapse
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?

cmulk said:
I looked into the zip that you tried to flash, and it looks like it flashed the mmcblk0p5 partition, which on the G3 is aboot (and I believe is why even download mode is broken). You can get a clean aboot.img from the thread here (http://forum.xda-developers.com/att-lg-g3/development/rom-lg-d850-20f-lollipop-5-0-1-extras-t3052041) , but you will have to have some way to flash it. Are you able to get into anything at all on the phone itself, recovery even?
@southern87 : maybe you can provide some insight. I remember in the Lounge a while back you had a broken aboot. Where you ever able to get back to download mode or some other way to repair aboot?
Click to expand...
Click to collapse
Thanks for responding. I am going to try ADB again but I can't get into recovery mode at the time being.

A similar thing just happened to me, except I got right out of it. Device was completely unresponsive, no download mode, adb nothing, indicative of a hard brick. Scared the **** out of me as I've had it less than 6 hours... Started holding buttons, and it came to life after ~1 minute of power button + volume down. Related? Well maybe not, thought I'd post it here. (TWRP 2.8.5 + Rooted CM12)

True Hard Brick, No OS!
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.

TSF14 said:
Well I really did it this time. F*cked up big time. Wiped everything on phone, all I have is TWRP which is useless. Nothing. No bootloader, no sideloader, NO files! Guess I'll try to get into download mode.
Anyone have any ideas? Would be greatfull for any help.
Click to expand...
Click to collapse
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089

hyelton said:
Follow the TOT method.
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.

TSF14 said:
Thanks hyelton, I don't even have download mode. Nothing, zero, (no).zip, zilch, nada. Guess I'll run it up to the AT&T Corporate store & see how much $s they'll charge to put it back to stock.
Click to expand...
Click to collapse
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 plug using the OEM LG cable while holding volup and then plugging in the USB cable?

hyelton said:
They don't put it bAck to stock.. They either will tell you no as you voided warranty or it will be sent off for warranty. They don't flash in store.
You have to have download mode to flash.
So your plugging your phone inTo a non USB 3.0 CCCC?
Click to expand...
Click to collapse
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.

TSF14 said:
Yes, AT&T said they would replace it for $199.00. Screw that. they gave me the phone # for LG, I will call them & see how much they charge to reinstall the OS. Yes, plugging into 2.0 usb while holding vol up with phone off. No sign of life.
Click to expand...
Click to collapse
Are you sure your battery is not dead??

hyelton said:
Are you sure your battery is not dead??
Click to expand...
Click to collapse
Yes, if only it was that easy.

There are a few things you can try :
1.) Press the Powerbutton for a longer time
If you have a responce like the LG Logo or something like that, you might want to try and plug it to the computer and use the managing software
with which you can emergency reinstall the firmware.
2.) Press Power + Volume Down
If it restarts into the recovery menu, try to find a way to load a flashable stock rom of your handy onto the memory of your phone in order to "reflash" it.
(I don't know how you can do that )
3.) Go to the shop where you bought it and explain your problem, since rooting a LG device is not really easy to detect the chances that your warranty will cover for it are pretty high.
Sent from my LG-D955 using XDA Free mobile app

http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965

Read this.
http://forum.xda-developers.com/att-lg-g3/help/bricked-d850-help-t3064874

[Q] Nexus 5 stuck on boot loop

Hello everyone:
This is the first time I ask for help on the Nexus 5. I read the couple of post about boot loop, but they could not help me. What happened was that I was checking some link on the browser and all of the sudden the phone restarted, I saw the google logo then the four color dots and it stayed there for ever. I check for info on how to deal with the problem and tried the power button plus the volume down (-) to get into the loader. After I was on the loader I tried unsuccessfully all the different menus that come with it, i.e., Start, Reboot, Restore, Power off. The only one that produces any result is the power off with which I can just turn the device off. I have had the phone since November 2013 and it is untouched, original google phone. It updated to os 5 a few months ago and there was no problem with it. I wanted to restore it to factory settings but as mentioned before the phone will not let me in. Is there any other way I could try to access it to restore? Thanks for your help.

Do a search for nexus factory images. You'll have to unlock your boot loader and then follow the instructions on that page.
Sent from my Nexus 5 using Tapatalk

Thanks but...
ldubs said:
Do a search for nexus factory images. You'll have to unlock your boot loader and then follow the instructions on that page.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you Idubs for the help, I am still reading and got stuck on the following:
I got an HP Envy 17 with windows 8.1 and I am trying to follow this instructions to get the Universal Naked Drivers install put can get this to appear:
To Install on Windows 8, you must additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
All that is on bold can't be access. The closest I get is to Restart and the laptop restarts, which makes me loose everything and no driver can get installed.
Any suggestions?

Using Win 7 computer
After hours of no go with Win 8.1, I finally tried my old Win 7 pc. I got android sdk installed per instructions on this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I can get to the point where I type fastboot oem unlock, and the phone shows it's unlocked, then I am supposed to type fastboot reboot. The phone reboots and stays on the permanent boot loop. I waited 30 minutes and nothing. Is it something I am doing wrong or the phone is toasted? I will like to know before I send it to Google for repairs as it is not in warranty any more and they will probably charge me what the phone was worth in the begining. Any ideas?

Put it back in fastboot mode and flash the factory images using the instructions from the page where you downloaded them.
Sent from my Nexus 5 using Tapatalk

@abyss1957 what happens when you flash a kitkat rom?

Frustrated
Hi:
I did a flash-all per instructions and the phone will not accept it. I unlock the phone, at least it says so on the display, when I give it the command the first thing it does is it reboots the loader and gets locked again. From there on the whole operation fails because it says it can not write to a lock device. I am using the adb program with the windows 7 command line. I think I will let google play with it if is not to costly, anyway I have to call them tomorrow to find out what happened with the shipping labels and instructions they were going to send.

abyss1957 said:
Hi:
I did a flash-all per instructions and the phone will not accept it. I unlock the phone, at least it says so on the display, when I give it the command the first thing it does is it reboots the loader and gets locked again. From there on the whole operation fails because it says it can not write to a lock device. I am using the adb program with the windows 7 command line. I think I will let google play with it if is not to costly, anyway I have to call them tomorrow to find out what happened with the shipping labels and instructions they were going to send.
Click to expand...
Click to collapse
If the bootloader is re-locking itself it's a classic sign of an emmc failure. Sorry man you've done all you can. See if Google will still warranty it. Keep asking to talk to a higher level of costumer service if they say no. Sometimes they can be really generous about out of warranty phones.

Thanks all
I tried today to revive the phone again by doing it per bitdomo thread:
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
After it got to about 6% is failed and the message was: userdata erase failed, and from there nothing happened. I guess it is really toasted. Thanks anyway for all the help all I can say is that I know today more than I did yesterday thanks to the great site. You all have a nice day. :laugh:

abyss1957 said:
I tried today to revive the phone again by doing it per bitdomo thread:
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
After it got to about 6% is failed and the message was: userdata erase failed, and from there nothing happened. I guess it is really toasted. Thanks anyway for all the help all I can say is that I know today more than I did yesterday thanks to the great site. You all have a nice day. :laugh:
Click to expand...
Click to collapse
Don't give up yet..... Look at my post http://forum.xda-developers.com/goo...p-lollipop-t3098632/post60491129#post60491129
I was in a similar situation and managed to fix my phone. Give it a try :good:

Thanks a lot eross
Thanks for the post, unfortunately I tried to flash it a couple of times after I posted my last and nothing happened. Always stuck at 6%, so I finally send it to LG for repairs. It should be back next week. Mine never allowed me to write anything to it, maybe a component bad. They send me an email with the charges for the repair but never said what was really bad with it, except that it was on a start up loop (like I didn't knew that). Anyways thanks to all for the help it was a real learning experience. :good:

Don't give up yet read a post above
LG is a waste of money