Develop Bugs

[Q] Remote wipe. Did it brick the phone?

Hi,
I received a LG GW910 from the DevConnections conference. I was playing with the remote services available through the live.com device center and performed a remote erase of the device. It seems like it did not complete as now all I get when powering on the device is a white LG logo, or I can enter the "connecting kitl" screen. When in either screen I cannot power off the device or anything else. Is there anything I can do to restore the device to a working condition?
Thank you!

I don't know much about how this works but I would try to remove the device from windowsphone.live.com so that your Live ID isn't associated with it anymore. Just a wild guess.

No joy, but thanks for the idea. I don't think its loading the 'OS' even. Is there a way to restore the 'OS' from anywhere?

There's usually a combination of hardware keys you need to press to do a hard reset. Check the manual for your phone.

Thanks buddy, but if there is, I haven't found them yet.
I'll keep digging..

There is a Hard Reset option:
Originally Posted by sutt359
If you hold down both Vol buttons at start-up you can hard reset
Click to expand...
Click to collapse
taken from the Tips and Tricks Thread.
Hope I could help you
L-Dani

dimitrii01 said:
Hi,
I received a LG GW910 from the DevConnections conference. I was playing with the remote services available through the live.com device center and performed a remote erase of the device. It seems like it did not complete as now all I get when powering on the device is a white LG logo, or I can enter the "connecting kitl" screen. When in either screen I cannot power off the device or anything else. Is there anything I can do to restore the device to a working condition?
Thank you!
Click to expand...
Click to collapse
I did this with the dev device I was allowed to borrow same one the GW910, I plugged it into the mains and had dinner, it was back at the OOBE screen when I got back, scared the crap outta me as the device is on loan and I thought I bricked it.

If you push both volume buttons at startup (on this device) it just takes you to the "connecting kitl" screen. At that point, what should I do to reset the device?
I tried connecting it to a kettle and a kitten and some cattle, but it didn't help, although I think I plugged it in the wrong port on the cattle

I just did this to my phone as I have to return it due to bad reception in my area.
Once reset it stayed at the HTC white boot screen. I pulled the battery and it reset just fine.
Back to setup again on the phone.

ckacey said:
I did this with the dev device I was allowed to borrow same one the GW910, I plugged it into the mains and had dinner, it was back at the OOBE screen when I got back, scared the crap outta me as the device is on loan and I thought I bricked it.
Click to expand...
Click to collapse
OK, I did this and it actually worked. Previously I had let the phone sit at the LG logo for over 20 minutes with the entire phone getting hot from driving the display and it never did anything. So I plugged it in to main power and left it while I went to lunch and low and behold it was at the OOBE screen when I returned.
Who woulda thought that it would take that long and that it wouldn't give a status message or anything...
Either way, my thanks to you for the suggestion.

My pleasure, I remember how scared I was thinking I'd have to explain to MS how I bricked their device, using Windows Live of all things. I don't think anyone should have to go through that kind of a scare.
I wonder though, could the extreme wait-time be a way to discourage "finders" in a repeat of the iPhone 4 bar situation? Nuke the device and it won't boot for quite some time while connected to wall power ...
It still wipes quickly when using the reset option on the about screen.

Screen does not respond to touch

All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!

i think its just a 4.3 software bug. i love the tablet but the new update isn't very good IMO. google needs to get this right.

luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
Since it has to be new I'd recommend just trading it in for another if a reboot or reset didn't fix it. I'd hate to see a fellow get stuck with an unreliable device. It could be many things though such as a bad digitizer or loose LCD ribbon flex cable or just a software glitch. To check the flex cable you would have to disassemble the unit which of course could potentially cause problems when trading it in. I dropped a tab one time though and it Jared my charge flex cable loose and just reinserting it fixed it. Good luck

fix-this! said:
i think its just a 4.3 software bug. i love the tablet but the new update isn't very good IMO. google needs to get this right.
Click to expand...
Click to collapse
Thanks.
Any idea about how to fix the problem (factory reset did not work) other then sending it back for a replacement?

Wait for Google to release official image then return to stock to see if it fixes it.

conan1600 said:
Since it has to be new I'd recommend just trading it in for another if a reboot or reset didn't fix it. I'd hate to see a fellow get stuck with an unreliable device. It could be many things though such as a bad digitizer or loose LCD ribbon flex cable or just a software glitch. To check the flex cable you would have to disassemble the unit which of course could potentially cause problems when trading it in. I dropped a tab one time though and it Jared my charge flex cable loose and just reinserting it fixed it. Good luck
Click to expand...
Click to collapse
Thanks.
I have a feeling it is a software problem. It was perfectly working and few minutes after it was not. Nothing, hardware-wise happened in the middle.
Software-wise, I noticed, on the top of the screen, the notification that a keyboard update was installed. Could have it broken something?
I thought a factory reset would have handled that possible problem but it did not.

luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
I had the problem last night and a reboot fixed it. Haven't seen the problem since.

mi7chy said:
Wait for Google to release official image then return to stock to see if it fixes it.
Click to expand...
Click to collapse
Mi7chy,
thanks.
A question: I started reading this guide (http://forum.xda-developers.com/showthread.php?t=1907796) to understand how to flash the factory image and I am worried I cannot perform step 1 of the Driver Installation section (I am unable to unlock the lock screen...).
Any suggestion?
Contemplating of returning this back for a replacement...
Thanks!

luigig said:
All of the sudden the screen of my new Nexus 7 does not respond to touch.
I was looking to my emails, then stopped using the tablet for 10 mins and, when I tried to use it again, the lock screen did not recognize my swipe motion. I then tried to reboot it: pressed the power button, touched the Power Off option and nothing, also here it did not register my touch.
I was able to enter into recovery mode (using power and volume keys) and perform a factory reset but that did not solve the problem.
I am stuck at the lock screen and I cannot unlock it.
Any suggestion?
Thanks!
Click to expand...
Click to collapse
I was in staples and their floor model had the same problem, I tried to fix it but it just sat there in a frozen state.

Touchscreen Stopped Working! Please Help!

I was using my phone last night. One second it was working fine, then next second the touchscreen stopped working. The two touchscreen buttons on either side of the Home button work (back arrow and tabs button), but the rest of the screen will not respond. Here are the steps I have taken to no avail:
1) Held down the volume down + power button to do a soft reset.
2) Rebooted into recovery mode and did a factory data reset.
3) Removed the screen protector.
None of it worked. I contacted Samsung through their live chat. He had me do a factory data reset a second time, which didn't work. He said I have to fill out a warranty claim and send the phone back to Samsung for repair and I will be without the phone for up to 14 days since I have had the phone longer than 30 days and I don't have ins. The phone is practically brand new and has no damage and was working fine until this. Sprint pushed out an update within the last 5 days and it seemed to be working fine until this (G920PVPU2BOH1). I am not rooted. Any help you can give me would be much appreciated.

HannahBanana27 said:
I was using my phone last night. One second it was working fine, then next second the touchscreen stopped working. The two touchscreen buttons on either side of the Home button work (back arrow and tabs button), but the rest of the screen will not respond. Here are the steps I have taken to no avail:
1) Held down the volume down + power button to do a soft reset.
2) Rebooted into recovery mode and did a factory data reset.
3) Removed the screen protector.
None of it worked. I contacted Samsung through their live chat. He had me do a factory data reset a second time, which didn't work. He said I have to fill out a warranty claim and send the phone back to Samsung for repair and I will be without the phone for up to 14 days since I have had the phone longer than 30 days and I don't have ins. The phone is practically brand new and has no damage and was working fine until this. Sprint pushed out an update within the last 5 days and it seemed to be working fine until this (G920PVPU2BOH1). I am not rooted. Any help you can give me would be much appreciated.
Click to expand...
Click to collapse
Sounds like your best bet is to follow the warranty procedure. The device updating to OH1 should not have caused a touchscreen issue. You would be able to try and Odin back to OGA but as far as I know there is not a tar available for this.
*Edit....Try flashing the OF7 tar via Odin and see if that fixes your issue.
Sent from my SM-G925P using Tapatalk

HannahBanana27 said:
I was using my phone last night. One second it was working fine, then next second the touchscreen stopped working. The two touchscreen buttons on either side of the Home button work (back arrow and tabs button), but the rest of the screen will not respond. Here are the steps I have taken to no avail:
1) Held down the volume down + power button to do a soft reset.
2) Rebooted into recovery mode and did a factory data reset.
3) Removed the screen protector.
None of it worked. I contacted Samsung through their live chat. He had me do a factory data reset a second time, which didn't work. He said I have to fill out a warranty claim and send the phone back to Samsung for repair and I will be without the phone for up to 14 days since I have had the phone longer than 30 days and I don't have ins. The phone is practically brand new and has no damage and was working fine until this. Sprint pushed out an update within the last 5 days and it seemed to be working fine until this (G920PVPU2BOH1). I am not rooted. Any help you can give me would be much appreciated.
Click to expand...
Click to collapse
Today this happen to me as well I try everything and nothing works then I flash the firmware G920PVPUOF7 and when it boot up again everything works again just fine at least at he moment . Oh and by the way it didnt erase my settings

G4 bricked, possibility of resurrection?

This is embarrassing, but I was trying to install Pokemon Go on my G4 and the phone got really hot and rebooted. It never came back. Just went into a boot loop. I found instructions online on how to do a master reset with the power button and volume down letting it up briefly when seeing the logo and then pressing it again and letting it boot. I answered the question about deleting all user data and then answered it again. It said it was erasing data, then froze for a few hours at "optimizing apps" on one of the steps while I left it plugged in. I eventually pulled the battery to get it to respond again and now it just shows the LG logo and then goes dark. While dark it doesn't respond to button presses or let me try again to power it on, etc.
Any chance of me getting this phone working again? Is there anything else I can try aside from the master reset that I've already tried?

Hello if you look under the battery and your serial number starts with 505 or close its dead.
Sent from my LG-H815 using XDA-Developers mobile app

Eudmin said:
This is embarrassing, but I was trying to install Pokemon Go on my G4 and the phone got really hot and rebooted. It never came back. Just went into a boot loop. I found instructions online on how to do a master reset with the power button and volume down letting it up briefly when seeing the logo and then pressing it again and letting it boot. I answered the question about deleting all user data and then answered it again. It said it was erasing data, then froze for a few hours at "optimizing apps" on one of the steps while I left it plugged in. I eventually pulled the battery to get it to respond again and now it just shows the LG logo and then goes dark. While dark it doesn't respond to button presses or let me try again to power it on, etc.
Any chance of me getting this phone working again? Is there anything else I can try aside from the master reset that I've already tried?
Click to expand...
Click to collapse
send it back for reapir.

hi, mine was 509. It died 2 weeks ago, showing only "LG life is good" if trying to boot it. No way into recovery. (did boot one time very slowly to lockscreen before the definitive death)
This seems to be the same for you.... dead CPU I suppose. I'm still waiting for the repair.
(curious about the 505 asserted here, since mine was higher)

Hello the first 3 digits of serial number indicate date of manufacture, and the early ones have a manufacturing defect.
Sent from my LG-H815 using XDA-Developers mobile app

Hello,
mine was 510 and died on me 4 weeks ago, (boot loop with only LG logo) as it died from overheating (or at least was very hot when die occured), I tried to cool it and it was "succesful"
It put it in the freezer for some time and then could boot it on TWRP and make a full backup (I left it in the freezer the whole time)!
boot at normal temp lead to black screen in 10-15secs. I sent it back for repair (motherboard replacement was made in less than 1 week by Lg France), I am now waiting the answer from Lg developer to unlock the bootloader again.
I guess you can at least try and see if you can have the same result as me.
Marc

G4 bricked, possibility of resurrection?
Click to expand...
Click to collapse
No.

Nokia 6.1 seemingly hard bricked after reboot

I have a Nokia 6.1 TA-1043. I have not unlocked the bootloader, and it runs the default operating system (Android One, probably Nokia flavoured). It has gotten slower over the years, and it had a period where it crashed every now and then (sudden reboot). Anyway , some days ago I decided to reboot the phone because it was slow, and it instantly shut off. After waiting probably 20 seconds without response, I decided to hold the power button down to force it. I don't remember exactly what I did, but after trying to again hold the button down to turn it on again, it vibrated as usual but the screen remained black. I then most likely tried holding volume + and power to force another reboot, unsuccessfully. I then tried holding volume - and power to enter download mode. It might have vibrated, or I might have touched the cable making me think it vibrated, but nothing happened. I pressed some random buttons after I think.
Now, the phone does seem to charge. It gets warm when I plug in the charger. I've searched for hours on different forums, and some people say that their phone was magically resurrected after the battery went completely flat after few days. I have tried plugging the phone a bit and testing every button combination (including volume +, volume - and power at the same time) for a few days now. It's dead.
The phone is also seemingly not recognised at all on my windows 10 PC. Haven't tried on Linux.
I have a few theories:
1. The phone simply hard bricked itself due to some hardware failure.
2. I bricked the phone by (blindly due to screen being blank) entering recovery mode and unknowingly factory resetting the phone and shutting it off mid process.
3. The battery is messed up? Some suggest deconnecting the battery. It would require the use of a heat gun to even open the phone though.
I've seen some people suggest entering EDL-mode either by shorting some pins or using a modified USB-cable. However, that would either require opening a phone that isn't supposed to be opened easily, or plugging a modified USB-cable into my computer, nether of which seem safe. I've also seen people mention that whatever needs to be flashed in EDL-mode must be signed by Nokia, which I can't do obviously haha.
It's probably time to move on right? Has someone managed to get a phone in that state to work again?

Hi i can explain some of your theories:
The first one: It's impossible to make the phone hard bricked itself.
The second one: Factory reset is only wipe your data not the OS itself so if you Factory reset and force reboot it should get in to Download mode and you need to unlock bootloader to reflash the ROM. (I'm not in that situation so I'm not sure it's correct or not.)
The third one: No, I don't think so.
That's all so if you have any question ask me. Thanks!

alprtewwqfr said:
Hi i can explain some of your theories:
The first one: It's impossible to make the phone hard bricked itself.
The second one: Factory reset is only wipe your data not the OS itself so if you Factory reset and force reboot it should get in to Download mode and you need to unlock bootloader to reflash the ROM. (I'm not in that situation so I'm not sure it's correct or not.)
The third one: No, I don't think so.
That's all so if you have any question ask me. Thanks!
Click to expand...
Click to collapse
Thanks for replying My phone seems unresponsive, so I haven't managed to get in to download mode, at least not visually on the screen. Also, my phone is not recognised on PC, making me suspect it's not really turned on. I also tried holding volume up + power for 40+ minutes by stuffing it between a few books when making dinner haha, and it still didn't respond. Would you move on in this situation?

speedrocket2110 said:
Thanks for replying My phone seems unresponsive, so I haven't managed to get in to download mode, at least not visually on the screen. Also, my phone is not recognised on PC, making me suspect it's not really turned on. I also tried holding volume up + power for 40+ minutes by stuffing it between a few books when making dinner haha, and it still didn't respond. Would you move on in this situations
Click to expand...
Click to collapse
I don't know because I'm not in that situation, but I had a similar one but only boot to download mode.