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.

[Q] Help!! a100 Blackscreen

i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible

wondering if anyone can help me...

frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.

pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged

frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.

Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.

i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen

same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks

A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!

Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia

same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.

If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.

This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.

I highly doubt they even CARE when sending these in. They will void for physical damage most likely.

tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.

Galxy s2 Vibrating and crashes at loading bar.

So i've looked around and no one that i've seen has the same exact problem as i do. Here's my post in another forums about my problem.
Here's my story about my Galaxy s2 for T-mobile. My phone randomly turned off 2 days and whenever i tried to turn it on, it would restart and basically never get pass the blue loading bar screen. Second, i found out about this boot loop sequence and i was able to do a factory wipe.
After i factory wiped the data etc off the phone, i was able to use it until it ran out of battery, but then after i found out it ran out of battery, it wouldn't let me turn it back on, it wouldn't get pass the loading screen, once again. On the other hand, i am able to go to recovery mode or download mode, but the phone shuts off before i can even try and click on the options i want.
Today, i found out that if i kept pressing power button consecutively on the phone, I'd be able to go to my home screen and basically act as if nothing ever happened, it'd function as a new phone! I then had the nerves of turning off my phone just to make sure it finally works now, but my hopes were crushed and now the pressing the power trick does not even work anymore. It would probably work one out of 10-15 times, and in the end it'd still restart. I am using a gingerbread galaxy s2. My friend tried using the usb jib on my phone, and it worked but whenever he tried to plug in the usb, the phone would just restart. I am extremely frustrated with this, and if you can help, please do so because it's important that i fix this phone. If you have any questions, please feel free to ask!
Hi there, thank you for the welcoming me to the forums. No, my phone is not rooted, it has always been gingerbread etc i never tried rooting because i never knew how:/ I believe this started when i was just browsing around facebook, so i'm not entirely sure what happened... Uhmm i tried going to download mode through the volume keys and power button when it's connected to usb to the i think it's odin3? and it'd be in the download mode but as soon as the computer says it's connected, the phone would just turn off again and bam, it's like nothing ever happened. My phone does charge when it's plugged in, but it doesn't show it's being charged but i remember my battery was dead last night and i charged it till today and now it's got power. ANd no i don't have a warranty:/ i really hope you can help me

Sounds like a faulty power button. Check out Mobiletech video for thier power button repair service.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile-power-button-repair/
Sent from my SGH-T989 using xda premium

[Q] Stuck in recovery mode; no buttons working

I have a Google Galaxy Nexus and was using it last night (8/11)--it was a bit slow, as it has been for a few weeks, so I shut it down and hope restarting may help. When I started it back up, it was stuck on the "Google" word for about an hour and then I suppose lost power. I was not near a computer to plug it in.
When I got home, I plugged it into my pc to charge, then read online to hold down Power + Up + Down, which I did. I got to the Recover console with the "start" and little Android guy and the white arrows. However, no matter what I press (power, up, down) nothing happens. I cannot get past this screen. Also, my pc was trying to find drivers for it and couldn't. What should I do? And is there a way to preserve anything on the phone? I have not modified the phone in any way (rooted or whatnot).

I think you cannot move between options because the bootloader is locked. Can't say 100% that's the cause of it though.

Thank you for replying. If that is the case, how do I fix that?
And after it ran out of power, I charged it again and tried starting it normally and it started. So I have no idea what is going on. However Im now afraid to restart it in fear it will be stuck on the logo again. It still runs a bit slow.
So I guess I have 2 questions:
1) If I have to load it into recovery again and no buttons work, how do I fix that?
2) Since it did start again, but runs slow, what could be going on? Any tests I can run?
Thanks!

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.