Related
Hi all,
Hopefully you can help me, i have just installed the latest radio and Modaco ROM (this isn't the first time i've did this).
After installation i got what looked like an image of a drive and an arrow, i assume this meant it couldnt find the boot image. I then tried a couple of times to reboot holding the home key but now i cant even switch it back on... even on charge the light isn't coming on
Any help would be gratefully appreciated
Thanks
GF
When the arrow and drive comes up, you're meant to leave your phone well alone, it means it's flashing something (usually something important!)
If your phone doesn't turn on, sounds like you've made a full hard brick, nothing you can do but see if you can get it repaired.
Gutted, cheers
Can you pull the battery and get into fastboot?
Breakthecycle2 said:
Can you pull the battery and get into fastboot?
Click to expand...
Click to collapse
Not sure what that is? I've tried the various power+key sequences
Thanks
GaelForce said:
Not sure what that is? I've tried the various power+key sequences
Thanks
Click to expand...
Click to collapse
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.
docsamsom said:
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.
Click to expand...
Click to collapse
Worked a treat, got a doorstep exchange today
Thanks
Ok guys, Long time lurker, First time poster here.
Been hanging out around the forums for a while now, but this is the first problem I've ever had that I just couldn't figure out on my own.
Screen dead. Have to return to TMO. What to do about existing rom???
Last Saturday night I was playing around with my phone before bed. Everything was fine. Woke up in the morning and the screen was dead.
The backlight comes on but no display what so ever. No HTC screen, no bootflash, no nothing. Everything else still works.
I can feel events happening on the screen when I touch so the digitizer is clearly up to snuff.
Also I have been able to get the phone into fastboot from memeory, so its a start.
I contacted Tmo about a replacement and it arrived today. I'm running GingerVillian 1.4. So the big question is what do I do about the ROM on my phone. Also, what happens if they get the phone back and discover it has been rooted. Will I get a bill for the full price of the unit? Anybody know??
The way I see it I have three options, but if I'm missing something please let me know.
1. Attempt to flash stock ROM via recovery using up down vol and track pad. And just not worry about S-off. If it looks the look, will they check Hboot for s-off???
2. Attempt a side by side deroot using the new G2 and the broken one next to each other.
3. Physically damage the memory somehow preventing the phone from booting.
#2 seems like the worst option simply because I will have no way of verifying that any step in the process is successful... (Scary prospect) of course this applies to option 1 as well but I figure I could go through the flash process two or three times just to be sure. Option three doesnt exactly sound like a winner either, just putting it out there.
Comments please, a little help would be greatly appreciated.
I would go for the blind flash of pcimg10 from sd root. Then plead ignorance. Confused tho ...did u say u can see the bootloader txt or no?
Sent from my HTC Vision using XDA App
No, screen displays jack squat, nada.
Also wasnt there a huge writeup about how I'm not supposed to flash pcimg10...?
Bluetygator said:
No, screen displays jack squat, nada.
Also wasnt there a huge writeup about how I'm not supposed to flash pcimg10...?
Click to expand...
Click to collapse
Depends on how you're rooted. I'm gfree'd and every now and then I'll copy that out to sd root and reflash it. It flashes fine, unroots the phone, but still leaves s-off. I've been thinking about this - again- after reading your post because I've thought this would be the worse-case scenario. That is a screen in some state where you just can't see what's going on.
If it were me, I'd at least want the factory load on it and hope that should they run some diags, put on a new LCD then boot it up, it could all be done without really noticing the s-off in bootloader.
For me though, I just would have a hard time physically damaging it - that would get me a 130$ refurb on my handset protection or if I tried to just kill some internal IC like the ram, I'd be even more worried they'd eventually find that for what it was.
edit: obviously your number 1 is the easiest since it's just answering volume up after giving it a few minutes on boot to parse the pcimg10 file.
edit2: okay, how about, hook jumper cables to it, blast it, then send it back and just claim you were hit by lightning
I'm perm rooted using visonary r12.
Yeah not going to damage it. I just wouldn't have it in me.
What worries me is if I flash pc10.img and something goes wrong I would have no way of even knowing it. Was thinking about just regular old CM6.1.
You people worry too much. Just send it in. As long as they receive an intact G2 with no physical damage to the screen (this bit is crucial if you got a swap out for anything screen-related) then you'll be just fine.
I have read on more than one occasion that if you cant turn on or see screen, as long as ur void stickers are still intact, and there is no water damage (moisture detectors all ok) they do not care.
Though not confirmed.
EDIT..... But if I were in your position then I would do as ZKID suggested with the pc10img thingy.
if there is nothing on the screen, it sounds to me that maybe the copper ribbon on the phone that attached the bottom of the phone with the keyboard to the screen portion could be damaged or loose... this happend with a buddies g2 and he was rooted and everything like you... he just sent it in as is and they never mentioned anything to him or gave him any problems because if it. he thinks they just saw the screen wasnt working and that was it.
Hi, I'm having problems with my DINC.
I was running SkyRaider Athena 1.2 with the stock Kernel, HBOOT 0.92, Radio 2.15.00.09.01 and S-OFF. It was getting a little slow and bogged down so I decided to start afresh and flash a new rom. I upgraded my Custom Recovery from 2.5 to 3.5 (it had been a while since I had flashed a rom) and flashed SkyRaider Sense 3.5.
Here is where the problems start. Whenever I turn off the phone and try to turn it back on I get the "HTC Incredible" screen, which then goes to black and I get 5 vibrations and a green flashing LED. I can get to the bootloader but when I try to get to the Custom Recovery, the same thing happens. One thing that I have noticed is that S-Off is now S-ON.
The only way that I can get the phone to turn on is to press the power button, and plug the phone into a usb for power. At that point it will start up normally, however the phone will not read the SDcard or internal phone storage at all, even in when I do the same thing to get to the custom recovery, which means that I can't flash roms, or use any apps that require some sort of memory.
I don't know if this is a problem with the rom so I posted this in the general discussion.
I've also found some posts on other websites where people have had similar issues but no solution:
http://www.incredibleforum.com/foru...f-vibrates-5-times-green-light-flashes-3.html
http://www.droidforums.net/forum/dr...9959-need-help-5-vibrates-blinking-green.html
Yes. I'm QuickSilver98 on those sites too
Any help would be greatly appreciated.
Sorry to say but I have yet to see a solution other then a insurance claim. I hope someone smater then I can help.
Just do a battery pull when that happens.
It has happened to me before a couple times, but after a battery pull everything works fine.
thanks for the suggestion, I've tried tons of battery pulls, but there's no change.
I've never heard of this problem but, then again, I've only been in the Android community since September and am far from an authority. I do have one thought though which I'm guessing is not a cure all for your problem but, could possibly be a part of the problem. Is it possible that maybe your SD card has crapped out on you? Have you tried putting it in a card reader to see if it is still readable? Just a thought, as I said. Good luck with your problem, in any case.
Sent from my ADR6300 using XDA App
I had this problem, I took the phone back to Verizon and they gave me a refurb. But this may help you
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
c_live_lee said:
I've never heard of this problem but, then again, I've only been in the Android community since September and am far from an authority. I do have one thought though which I'm guessing is not a cure all for your problem but, could possibly be a part of the problem. Is it possible that maybe your SD card has crapped out on you? Have you tried putting it in a card reader to see if it is still readable? Just a thought, as I said. Good luck with your problem, in any case.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I thought of that, the memory card does work in other phones and other memory cards can't be read by the incredible. So it's definitely the phone.
Yeah, I figured it was something more. Just wanted to put it out there because of the possibility of more than one issue going on simultaneously. I know it's rare to have multiple problems at once but it does happen on occasion. Any luck zeroing in on your problem?
Sent from my ADR6300 using XDA App
Hey there, You linked to my post. I ended up having to get a refurb from verizon. my situation was the same and I was able to get the phone to "s-off" before I called them up and went through verizons troubleshooting routine.
they overnighted a refurb for free.
Best of luck with your phone.
Ixa said:
Hey there, You linked to my post. I ended up having to get a refurb from verizon. my situation was the same and I was able to get the phone to "s-off" before I called them up and went through verizons troubleshooting routine.
they overnighted a refurb for free.
Best of luck with your phone.
Click to expand...
Click to collapse
I'm thinking of going that route as well. I haven't been able to find any solutions anywhere and that seems like the best option.
My brand new Inc did this out of the box. I could get it to boot if it was plugged into USB, but even then things weren't quite right (Bluetooth didn't work, WiFi was wonky, internal storage was not recognised, etc). Apparently this is a Qualcomm hardware error code, and a warranty replacement is your only real option. Good luck!
fix
ok this happens all the time and all i have to do is pull out the battery and wait 20 seconds then i just either boot the phone up or boot it into hboot and then boot into recovery and reboot the phone.
Forum Noob here, I was using my Galaxy S3 (Wind) and all of a sudden the screen went black and it turned off. Something similar had happened a couple hours before and the phone wouldn't turn on through the power button so I simply took out the battery and put it back in and it worked. Then when it happened for a second time I tried the same thing but to no avail the phone stayed dead.
So far I've tried:
Using another GS3 Stock Battery
Tried getting into download and recovery mode
Tried charging it (I do know that the battery is charging since I checked it on another phone. The red light is not on but it turns on when I take out the battery and then plug it in. After 20-30 seconds of battery insertion the red light goes away and is completely unresponsive all that time)
Tried Keeping the battery out of the phone for a couple of hours (Suggested by a friend)
Also Tried connecting it to a pc, and it only connects when I keep the battery out. When it finally connects it tries to install drivers for "QHSUSB_DLOAD" but fails.
I have no idea what's happening to my phone and I would like to get it fixed as soon as possible. After some searches I've narrowed down to either a Hard Brick or a Sudden Death Syndrome but it doesn't completely match with all the characteristics of either problem. I greatly appreciate any help and I would like to know what exactly the problem is and what my best viable option.
Thank you.
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
TheSoldierDude said:
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
Click to expand...
Click to collapse
Only reason I suspect the power button is you mentioned you couldn't get it to turn on using the button, but removing/replacing the battery worked. And it can work perfectly and then fail out of nowhere. So goes when you have plastic parts! But lots of people have had issues with this button recently.
Wasn't trying to convince you that was the problem, just letting you know it's a potential culprit.
But if you think it's ok, then try to use KAsp3rd's debrick thread and see if that gets you going again.
Sent from my SGH-T999 using Tapatalk
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
ssingh0247 said:
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Click to expand...
Click to collapse
Since they are seeing the QHUSB_DLOAD (which is technically a hard brick) a simple USB jig wouldn't work, however they can attempt to use my recovery method. It's at no cost and just takes some time and reading.
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Remove and reinsert battery. If it turns on by itself, you are probably right about the button.
Sent from my SGH-T999N using Tapatalk
You're Right I believe
tomy1986.nt said:
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
Click to expand...
Click to collapse
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Nope
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Nothing happens at all.. its completely dead, simply a paper weight.. a very bad one of sorts
TheSoldierDude said:
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Click to expand...
Click to collapse
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Thank you
Perseus71 said:
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Click to expand...
Click to collapse
Nope.. xD 3 months off warranty, and yes I got it repaired from Samsung.. Motherboard was replaced, $300.. :|
Thanks to everyone helping out though
I can't believe I didn't know about these forums before :good:
Samsung Galaxy S3 died-black screen
my s3 gone black,its not getting turned on.there was red light(indicator) for some time before i tried to restart but when i tried to switch on. it's completly died,i am not getting any display.i have purchased in UK, unlocked using it now in India.some guys told me it would because of motherboard issue (if i replace motherboard it in India will it work normal,is there any possibility?)how to fix it?please give me some solutions.
screen not working
Hi all. In my s3 the red light is flashing fast. Also the screen is black but it works. Also the phone works and I can receive phone calls. Every few minutes the screen turns on for a sec and goes off again. I can feel the vibration when I touch the screen. Pkease help me.
Thanks
hard bricked
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
syben7 said:
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
Click to expand...
Click to collapse
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
yea, sry about that, was actually trying to get 10 posts in so that i could go post in the dev thread concerning this, gonna check out the method you sent, thanks a ton man!
STUCK
Well my s3 (us cellular r530u), has no boot but has a red led without the battery. Is there a debricking procedure? And if so..where can i find a debrick file.
There is for us. But you need to be in Sprints forums. Theres nothing for your device here, and I dont know what they have over there. Good luck though!
Sent from my SGH-T999 using Tapatalk
Hey Guys, long time reader never posted. I think i may have hard bricked my brand new 5X. I am not new to flashing ROMs I have had great sucess with my old Nexus5 for year (now I have to revert to that phone for now)
I was running Cyanogenmod then decided to try Catalysm. All was wokring fine and then i decide to just reflash to stock. I downloaded the correct factory image went into terminal like usual (linux) executed sudo ./flash-all in the correct folder and it went through the process in about a second then the phone turned off and my terminal screen said waiting for device. After waiting a while i tried turning the phone on got nothing. unplugged the phone tried volume down and power all the regular stuff to make the phone turn on. Plugging it into the charger shows nothing and I cant get into the bootloader.
I have never had an issue like this before I cant figure out flashing stock image would brick my phone? Am i totally screwed with warannty?
Thanks for any help gusy.
Maybe a to simple question.
How long was it ago? Maybe it's stick stuck in the loop with the screen off and maybe you have to wait it out.
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
brick
bobby janow said:
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
Click to expand...
Click to collapse
This just happened about an hour or so ago. Well i was thinking the same thing with the phone looping and no screen but it doesnt feel warm like its on. Also adb devices doesnt list it as on although i would imagine boot looping it would not see the device. Ive tried letting it charge for about a half hour with no luck. should I try letting it sit over night on the charger or off the charger in case its looping and i need it to die eventually?
I just reflashed the stock firmware on my old nexus 5 with no issues, its working fine i did that to make sure it wasnt an error i made.
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?( not sure if it displays on linux
republicano said:
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?,
Click to expand...
Click to collapse
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
If you can't get the phone to turn on you're out of luck.
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
thanks for the help
Czepek said:
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
Click to expand...
Click to collapse
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
kmsgli said:
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
Click to expand...
Click to collapse
Also, holding the power button for a few minutes to see if it eventually boots
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
lsusb
republicano said:
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Click to expand...
Click to collapse
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
kmsgli said:
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
Click to expand...
Click to collapse
Sounds about right, that thread is for lg g2 and was just for display purpose, I not 100% sure if you can go through lg process on lg nexus,
Since the phone is also new I have not found any information on emmc fix.
You will have to go here and see if you can get help, but I think it will be some time till its released/leaked, you may have to pay to get it serviced.sorry about your Christmas present
forum.gsmhosting.com/vbb/f606/
Call Google and get it replaced. They are very good about that stuff.
kmsgli said:
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
Click to expand...
Click to collapse
Let Google know what happened, they're usually pretty good with that stuff and will probably let you RMA it. Google generally expects people to root their device, even though damaging the device while doing so is not technically covered under warranty they will probably help you out.
If 1 rep says no, call back and try another one. You can find countless examples online of people in your situation who Google helped out. Good luck!
Thanks guys
Thanks for all the help guys, I really apprecaite it, this site is really a great site full of people who want to help. ( im used to car forums where people call you an idiot any chance they get).
Ill post back if google did in fact help me out I will just wait for monday as I want to make sure if the phone is on for some reason with a weird screenless boot loop it has time to die and I can make sure I cant get it to boot myself.
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
kmsgli said:
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
Click to expand...
Click to collapse
So I guess that means it was so damaged even LG's equipment couldn't read any software/firmware details from the phone. Lucky for you. Just curious, what excuse did you give LG to make them think it wasn't caused by a software modification?
That's just it I was 100% honest and told them I accidentally flashed the nexus 5 image rather then the 5x image and bootloader was first on the flashall script. The girl who took the initial call didn't understand what I was saying so she typed exactly what I told her in the notes. I have to assume LG has a facotry cable that can flash the correct bootloader in seconds and the phone is back to new again.
really happy with LG service!!!!!