Database Users

[Q] It seems to be a "full brick"

Was updating using Odin when, as my luck always proves out, a circuit breaker tripped and cut power to my PC. The phone seemed to be frozen on the "Download Mode" screen (30+ minutes of zero activity) so I pulled the battery. Upon reinserting the battery I discover that the phone is 100% unresponsive. I've tried every trick google could produce for me with the exception of the "homemade jig" method as it seemed fairly clear that the phone needed some semblance of life for that to be effective.
So, my question is... WTF??? I've soft modded wiis, hard modded xboxes, hacked PSPs flashed hundreds of phones and generally revel in futzing around in this manner of endeavor and have NEVER bricked a device (even after some incredibly stupid mistakes). This just doesn't make sense and I haven't seen sysmptoms such as mine presented in any of my web searches. Any ideas???

I'm not saying your not a modder, but you should know to have a UPS hooked up to your dev box, for me its a laptop, so...
Anyway, try removing the battery for 1m, press power button with batt removed, now start up Odin, plug the phone in (batt removed still) and see if the phone connects. I'm sure someone will pop in here and provide links to several threads that describe different methods to help you fix this, I would but I'm sorta busy...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Sent from MyEF02 using XDAPA...

Keep the battery out for like a half hour and then try again. That has worked for some people.

Or try the mysterious button that may or may not exist. I know I'd be pushing the heck out of it just in case.

Thank you so much for your quick input... I tried precicely that 3-4 times (google search turned it up) and it was a futile endeavor.
And yes, I am fully aware of all the proper precautions to take, unfortunately I am also fully stupid with frightening regularity (well, maybe just lazy and reckless), I seem to have become a tad cocky as I have never really had to face disaster before today.
It won't happen again!

plug phone into computer without battery. Then hold power and 1 to go into download mode (still no battery)
That there is what I've seen as most effective thing to work on bricked phone's.

cool... I just popped out the battery and will let you know the result in about 40 minutes...

this happened to me recently, i found a post with the solution being to pull the battery out of the phone hold down 1 and the power button at the same time before popping the battery back in and it will send you to the proper screen to odin back to what you need, worked perfect for me

oh crap I editted my previous post. i forgot to mention go into download mode...
It's --
Remove battery and plug into computer. then go into download mode WITHOUT Battery still.

If your not getting any sign of life from ur phone, try this:
http://forum.xda-developers.com/showthread.php?t=1042746
It worked for me.

Krojian said:
If your not getting any sign of life from ur phone, try this:
http://forum.xda-developers.com/showthread.php?t=1042746
It worked for me.
Click to expand...
Click to collapse
there is no hole in the back case of my device. I've had my device powered on and bent the **** out of a paper clip trying to push the 'hidden magic button' to no avail.
YMMV (false hope ??)

Cool, didn't know that little button existed!

I bricked mine the same way a few weeks ago and tried every trick in the book over the course of 2 days. It was truly bricked. I don't have insurance; however, my phone was under warranty. Since I couldn't get the phone to boot or anything I figured there was no real way of telling what went wrong. I sent it in for warranty repair and 10 days later, the phone returned in working order. Work order says they replaced the main board. I marked the phone before returning it so I know its the same phone and it works fine now.
And before anyone says anything, I know, I'm an evil bastard. But I figure it's payback for a samsung flatscreen that died 6 months out of warranty.

I've done this, leaving my battery out for 20 mins or so, and leaving it out while going into download mode worked for me. I don't know why but sometimes I can't even get into download mode with my battery in.

keeepinitgansta said:
Cool, didn't know that little button existed!
Click to expand...
Click to collapse
it doesn't..
to prove this (or dis-prove it).. go into clockwork and make a nandroid backup (you know, just in case)...then boot normally and while you're looking at your home screen, jam a paper clip in there as hard as you can. Your device will do nothing.

daddymikey1975 said:
it doesn't..
to prove this (or dis-prove it).. go into clockwork and make a nandroid backup (you know, just in case)...then boot normally and while you're looking at your home screen, jam a paper clip in there as hard as you can. Your device will do nothing.
Click to expand...
Click to collapse
I hope you guys are messing with him...

hardrock121 said:
I hope you guys are messing with him...
Click to expand...
Click to collapse
No, it's just not proven. Some people swear by it, some say it's a myth and some say it depends on when your phone was made.
Sent from Godot's place.

Possibly bricked forever - Stuck at Sumsung logo endless reboot

Stupid thing is that I can do everything to it aside from getting it to boot all the way to work! I tried reflashing OEM roms and I tried custom roms. They all work just fine and it just won't boot all the way. I can turn it on and off, use format option, download mode and magldr. I keep my sim out and memory card. Before this all happened I always used OEM OS. Last thing I did was check my bank account, close the browser and click the power button to turn it into sleep mode. Few weeks ago I did have an issue with it for a day. It kept turning on and off constantly boot to random points. Mostly to the AT&T screen. It would boot all the way rarely and I got it to stay on a couple times for about 10 mins to copy all my stuff from it. Is it possibly something to do with the hardware being a POS and Just crapping out for no reason because cell phones are poorly made expensive bricks?

I've seen this issue across the forum several times. Unfortunately, just one case seemed to "return" to life, without understanding the reasons behind the "lapse".
What I can suggest you can do (and feel free to disagree) is get in touch with Cottula (creator of MAGLDR) and see if you can help you. You can send him the phone, maybe he can analyze it and get something out of it.
GL, mate, and if you find a solution, I'm sure other folks here would be glad to hear it.

Ahhh ok thats what I figured. I browsed a bit, but most of what I saw is people couldn't do anything. I didn't see anyone saying they could do as much as what I can do with it. I'll try your advice and see if maybe he could help. I took apart the phone to see if maybe someone came loose, though I saw nothing. Clean as a whistle. What I think maybe happen is it burnt up finally. I notice at times it would run extremely hot, mostly when I'm talking on it for more then an hour.

Well, for your sake I hope it's not burned out (hardware issue). I hope it has some software component that's screwed and that has a chance of being investigated and maybe fixed.
Also, the getting hot while talking/browsing for periods more than 30 min it's a known issue. It's however supposed to be quite warm, but not actually really hot, if you know what I mean. It it however possible that exposing the phone to higher temperatures to cause hardware issues.
In any case, I wish you good luck. Who knows?

I gave AT&T a call to see what they could do. The software warranty is 6 months past and she wasn't able to override anything that much passed over. Though I was able to get my 2 years wavered and get a early upgrade. So I got myself a Xperia Ion. I'm happy I don't have to put up with a flip phone for another 4 months. lol
I tried working on my focus a bit more playing with zune and other programs I found. Though I don't see it coming back to life trying all the different ROMs. I would think to make it work again is to re-flash the actual phone bios itself. Just like a computer starting it still uses DOS then loads the OS. I don't know how a phone works to much, but I'd assume same process. Something to do with the root-root of the phone telling it to be stupid and not boot properly.
Another note, where is the best place to sell this to get some money out of it? Screen and other pieces of its hardware are 100%. Should I try ebaying it?

I had a similar issue, last thing i did was removing the SD card before re-flashing the MGLDR and custom ROM

[Q] LG repair costs

My phone is bootlooping and I can't access recovery. I can't restore the phone's stock software because I edited build.prop and it's not showing up as a Verizon phone. I decided to bite the bullet and just pay LG to reset it. However, when I contacted them to do this they told me I need to mail the phone in and they will tell me how much it costs after their tech looks at it. I'm worried if I do this that they'll charge me an exorbitant amount to fix it... Does anyone have any idea how much they usually charge to do this?

Sending the phone off to LG should be your last resort. It sounds like you've not tried everything!

Send it in to warranty. As long as there's no physical damage Verizon isn't going to give a rats a$$

06stang said:
Send it in to warranty. As long as there's no physical damage Verizon isn't going to give a rats a$$
Click to expand...
Click to collapse
Well, in another thread a Sprint tech said that LG did not give them a method to flash the stock software if the model check failed. I assumed this was the case for Verizon as well. I'll call them tomorrow and ask, I may have misunderstood what he wrote. I can't seem to find his post now. I'll update this post after work tomorrow if they can recover the phone.
theoneofgod, what is it that you think I haven't tried yet? If you have a suggestion which would save me the trouble of sending this phone in I would be super happy. To recap, here's what I've tried:
1. Using hard keys to factory reset (on TWRP 2.6.3.1 so it actually factory resets instead of booting into recovery)
2. Hitting "adb reboot recovery" over and over as TWRP loads and performs factory reset (this worked for people on 2.6.3.1 on AT&T but doesn't seem to be working on my Verizon phone for some reason. I've tried it dozens of times and even wrote a batch file which spams "adb reboot recovery" many, many times faster than I could type it)
3. Flashing the .tot file through download mode (Model check fails)
4. Flashing the .kdz file through download mode (Hangs at either 4% or 10% and asks me to restart. Never gets past 10%)
5. Entering my IMEI into the LG update tool, letting it download the software for the phone, and letting it try to flash the software (it fails)

What was the reason for bootloop? i also change my model name to make camera app show pics in menu, but it didn't help, and i returned to stock build.prop. So whats your story? Its good to know what i should NOT do with the phone.

Yea a good idea if you share what you've done so readers can be aware of it. Goodluck to your G2 pal and we're sorry for you..

marshygeek said:
Yea a good idea if you share what you've done so readers can be aware of it. Goodluck to your G2 pal and we're sorry for you..
Click to expand...
Click to collapse
Np don't mind sharing, thanks for the sympathy this definitely sucks aha. I usually add in qemu.hw.mainkeys=1 to get rid of the software keys when I put a new ROM on. It worked the first time I did it on this phone, my best guess is that I mistyped something. I'm not 100% sure why this is making my phone not show up as a Verizon model during the model recovery check...someone more knowledgeable than me would have to explain that.
Melodycd, I think you should be fine doing that as long as you're careful. I was pretty careless and made a lot of mistakes to get in my position. As long as you don't do ALL of the following things you should be safe:
1. Not have the latest recovery
2. Not have USB debugging enabled
3. Mess up while editing a build.prop file so you bootloop

It doesn't matter what they can or can't do with the phone. They don't care what you did to it as long as it's not physically damaged or have water damage. Software issues can be fixed. If they couldn't flash new software they wouldn't have CLN devices to send out for warranty.
I've sent in several dozen phones that I left rooted (for legitimate defect concerns) and none were charged back. They don't need to know what happened to the phone when you call all they need to know is its not working and to send you out a device. They'll receive yours, flash it or send it back to LG to flash, then send it out to someone else as a warranty device.

06stang said:
It doesn't matter what they can or can't do with the phone. They don't care what you did to it as long as it's not physically damaged or have water damage. Software issues can be fixed. If they couldn't flash new software they wouldn't have CLN devices to send out for warranty.
I've sent in several dozen phones that I left rooted (for legitimate defect concerns) and none were charged back. They don't need to know what happened to the phone when you call all they need to know is its not working and to send you out a device. They'll receive yours, flash it or send it back to LG to flash, then send it out to someone else as a warranty device.
Click to expand...
Click to collapse
Okay I'll send it in tomorrow. Thanks man, I was just worried that since the phone says "rooted" in download mode they would flip out about it. Appreciate the reassurance.

ccmbr002 said:
Okay I'll send it in tomorrow. Thanks man, I was just worried that since the phone says "rooted" in download mode they would flip out about it. Appreciate the reassurance.
Click to expand...
Click to collapse
I'm just sharing my experience. Over the past 5 years I've been rooting and returning. I can't guarantee anything but i can tell you my experiences and what I've been told by vzw people I know.

I had my g2 repaired when it was rooted. My camera wasn't working atall would just show up black when i opened the app. I sent it in rooted w CWM recovery as i stupidly forgot to remove it. And i had a replacement within 5 days no questions asked.
Not sure if this is because i am in UK or not, but they didn't blink an eye.

Swanseatom said:
I had my g2 repaired when it was rooted. My camera wasn't working atall would just show up black when i opened the app. I sent it in rooted w CWM recovery as i stupidly forgot to remove it. And i had a replacement within 5 days no questions asked.
Not sure if this is because i am in UK or not, but they didn't blink an eye.
Click to expand...
Click to collapse
Yep I was just worried because the Verizon phone explicitly states that it is rooted. Just to follow up for those who are on Verizon and are stuck bootlooping and with no way to flash the stock ROM, what 06stang said held true for me (so far). The Verizon rep on the phone couldn't help me (she said she needed me to put my SIM card in my G2 when I was calling her from my old phone) so I took it to a Verizon store. The dude checked it for physical damage, tried to turn it on, and when he saw it bootloop he put in an order to get me a replacement phone. I'll report back in a week or two after I send in my rooted phone and let people know what happens, it seems like they won't charge me as of right now though.

Nexus 6P bootloop fix

Hello!
My nexus 6P is in bootloop. However, USB debugging is disabled. I can't access recovery mode. What options do I have to fix my device? I am willing to unlock my bootloader even if the internal storage will be wiped. I have come across a thread about a fix but it says that it will affect device performance. Is there any way to fix this without compromising performance?
Thank you!

didnt you ask this question already a few days ago about saving the data? idk what thread you found but when it happened to me, i heated up the phone (in my space behind my knee lol) and it eventually booted long enough to get the debugging enabled.

This has been treated before, Heat it and try again

rogernizzLe said:
didnt you ask this question already a few days ago about saving the data? idk what thread you found but when it happened to me, i heated up the phone (in my space behind my knee lol) and it eventually booted long enough to get the debugging enabled.
Click to expand...
Click to collapse
Yes, I asked this before but I was initially hoping to retrieve my files. But now, I just want to get my device to work again. I tried heating it with a hair dryer but it didn't work.

my advice, dont use hair dryer cause youll never know how hot you need it. plug your phone to charge, turn it on and stick the phone behind your knee (squished between your hamstring and calf). if you aint thick, be patient and let your body heat do the magic. every few minutes check to see if the bootloop stopped and when it does, immediately go to settings > about phone and tap the build number until you get dev options. back out, go to that and enable the oem unlocking and usb debugging

rogernizzLe said:
my advice, dont use hair dryer cause youll never know how hot you need it. plug your phone to charge, turn it on and stick the phone behind your knee (squished between your hamstring and calf). if you aint thick, be patient and let your body heat do the magic. every few minutes check to see if the bootloop stopped and when it does, immediately go to settings > about phone and tap the build number until you get dev options. back out, go to that and enable the oem unlocking and usb debugging
Click to expand...
Click to collapse
Okay thanks! I'll try that method

if it works, let me know so i can laugh about it. never loved my thicc legs until i bootlooped

rogernizzLe said:
if it works, let me know so i can laugh about it. never loved my thicc legs until i bootlooped
Click to expand...
Click to collapse
I tried it for around 20-30 mins but it didn't work

LG randomly overheating and won't stay on - No previous heat issues

Hi, I have a LG K20 Plus. I currently can't turn the phone on, so I don't have much software information to give you. The phone was bought at T-Mobile (Metro by T-Mobile) and I had a SafeLink sim card and a 16 gb micro sd card inserted when the issue started. I have since removed both. It says Qualcomm snapdragon on the screen when it starts. It was also rooted and the bootloader is unlocked.
I broke the screen on my phone and I decided to do the repair myself. I have done about 7 or 8 screen replacements and I actually did this phone a year ago with no issues, so I felt I could manage this one as well. I bought an entire display (from ebay) and switched it out with no problems. Initially it worked great! I used it for a few days before realizing that I had no sound. I opened it back up and noticed the loud speaker had fallen out. I found it, put it back in, reassembled it as I normally do and turned it on.
NOTE: when I was reassembling it the second time, I actually tried to put a screw in a hole that wasn't a screw hole. I used a light to normal amount of pressure but I didn't force it. I think it's the hole where the moisture detector is. Picture #1
I turned it on and right after the logo screen I got a message that said "High temperature detected Powering off for your safety" and it immediately shut off. The phone does appear to charge normally but it won't stay on. I did a factory reset (I'm not sure if it's still rooted but the bootloader is still unlocked). I also switched back to the old (broken) display just to check if that would work. I couldn't see any difference in the shielding but I switched them just to be sure. I bought a new battery and installed it. I took a q-tip and 95% Isopropyl Alcohol and cleaned pretty much the entire motherboard, paying special attention to the battery connections. After each one of these things, I tried to start it with the same error message immediately upon start up.
NOTE: At no point has the phone every physically felt hot or even warm. I don't think it's on long enough for it to get hot. But something is wrong and I have no idea what it is. I, literally, took the phone apart, put in the speaker and put it back together in less than 5 minutes. Could it be I just bumped something and knocked it loose?
I searched for any information I could find both here and with google but there is next to no information on the LG K20 Plus. I did find some information on the LG V20 that had overheating issues, and that has been all the luck I've had. I watched several videos and it seems the solution is to apply thermal paste. But my phone doesn't have any evidence that thermal paste was ever on it. I went and bought some but I have no idea where exactly to put it or even if it's needed. Most videos showed people using some kind of aluminum foil but I'm not sure if that is safe. I have several old phone laying around and I managed to get some of the silver tape and a copper square thing but, again, my phone did not have these things to begin with. I don't want to start adding things only to make it worse.
There is a slight difference of the tape that is on my phone now (the display I just bought) as compared to the old one (broken display). Picture #2 Again, I have no idea if that means anything but I thought it worth mentioning. Picture #3 is how it looks now as if I were going to put it back together. Picture #4 is the part (don't know name) where the videos show to apply the thermal paste and the shielding.
I'm really at a loss as to what to do next and I can't really afford to take it in to have it repaired before next month. If anybody has any insight or answers as to what happened, I'd be very grateful for your help. I'm sorry for the long post. I just wanted to tell you everything I have done in detail. Thank you

If you're using Kernel Auditor or any other kernel adjustment simply reset to default and use only ondemand or interactive. There's also options for the thermal portion of the kernel, don't mess with those. If VCC or another thermal option was checked off turn it back on. Putting the GPS to the moderate setting (the one below high accuracy) will keep the temps down as well. Are you using a custom ROM? If you're on Discord you can feel free to message me SCOPE★ BRΞΛD #8460 . I am only offering that so we can get this resolved quickly for you, just copy and paste since I use special characters.

Omgosh, thank you so much for taking the time to respond! Although I'm sure everything you are saying is very smart, I have absolutely no idea what you're saying. I'll do my best to try and answer you. I don't know what SCOPE is or how to send a message there. I don't think I'm using any thing for the "kernal". Also, I don't know what VCC or Discord is. As far as turning off setting for GPS or any other app, the phone will not stay on. I get about 1 sec after the logo when it boots up, then the error message about overheating and it immediately shuts off. I did a factory reset so everything should be good to go as far as apps. I don't think I'm using a custom ROM. The only thing I did was install TWRP, unlocked the bootloader and rooted the phone a year ago but nothing since then. As I stated earlier, this happened right after I did a display repair. Is there something on the MOBO that can get bumped that will make your phone get hot or send a overheating error. My phone doesn't show any sign that there was ever thermal paste on it prior but should I add some now. Will that help?

Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.

HelpNeededPlz said:
Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.
Click to expand...
Click to collapse
Hey, I just wanted to say sorry this happened to you. The same thing happened to me. My LG K20 Plus, no matter what button combinations I push and for how long I hold them, will not turn on or go into download mode. Plugging it in to a charger or PC does nothing either. Before it got to this state, I got the infamous green screen of death/Demigod crash handler (google this--it's a known issue with some models of LG phones and it happens when they overheat). It's definitely a hardware/build issue, and especially since this issue keeps the phone from turning on or connecting to a computer, I don't see a workable fix short of buying a new phone, unfortunately. Again, I'm in the same boat so I'm not happy about it either. I would say XDA is by far the best site to find a fix to this sort of problem, so if no one here has any suggestions on how to fix it, I think you (we) may be out of luck.

Thank you for letting me know. I'm not sure of some of what you said but I did catch the bottom line. Basically, just hold onto the phone until someone here comes up with a fix or workaround? I have a question for you. Did your problem start after you did some kind of repair? I'm wondering if I bumped something on the mobo to make it give a false overheating error. Do you happen to know where that sensor might be located? Sorry you are having problems to. It really stinks when your phone breaks and no matter how much time and energy you put it to figuring out the problem to fix it, there just isn't any good answers out there. I wish you lots of luck and if you figure anything out, please update here so I can try it too.

You need a whole new phone.
That or you're gonna have to replace the hardware