Random reboot hard bricked my Robin - Nextbit Robin

May be unrelated but updated to the latest nightly of Lineage, ran into the camera issues and got some random reboots. Sent an email, and then put it in my pocket, pulled it out a few minutes later and it wouldn't turn on. Have done the hold down power and volume down button to no avail. Used the USB cable to hook it to the laptop, see it in QDLoader 9008 mode. If I hold down the power button and the volume down button I can see it disconnect and reconnect but it never turns on or shows anything on the screen.
Spent a few hours googling it and looks like you need some hardware specific files to the QFIL method, which I can't find. So is this device toast? Was really enjoying the device and so sad that it died after only using it for about 1.5 months.

**UPDATE**
So the leave it plugged in to the laptop overnight trick didn't work. So I took the phone a part, when it's in this mode it seems like there is is still power to system. I left it open until the battery died, and the regulation circuit cut power. Then plugged it in the laptop(although a charger would probably work). Let it charge for 10min and it came back. Seems like it get stuck somewhere in the boot and needs to be reset, but without a removable battery you can't cut power. So if anyone runs across.this, leave it disconnected overnight(or maybe longer) until what ever state it is in kills the battery. Then plug it in and it may come back. My booted after being plugged in for 10min and turning it on using the power button

So I have the same problem with my device and am thinking about doing the same thing. What tools do I need in order to perform this?

I also have the same problem, is there any help?

coll0412 said:
**UPDATE**
So the leave it plugged in to the laptop overnight trick didn't work. So I took the phone a part, when it's in this mode it seems like there is is still power to system. I left it open until the battery died, and the regulation circuit cut power. Then plugged it in the laptop(although a charger would probably work). Let it charge for 10min and it came back. Seems like it get stuck somewhere in the boot and needs to be reset, but without a removable battery you can't cut power. So if anyone runs across.this, leave it disconnected overnight(or maybe longer) until what ever state it is in kills the battery. Then plug it in and it may come back. My booted after being plugged in for 10min and turning it on using the power button
Click to expand...
Click to collapse
So this worked for your hard bricked phone? And you had no more issues after?

Related

[Mis-posted error]

I apologize, I freaked out because my phone would not turn on under any circumstances. However, I'm retarded. Apparently it wasn't actually charging while I had it plugged in with a mini-usb cord.
Okay, my battery was at like 10%, I turned off my phone and connected it with a regular USB to Mini-USB cord (not the normal power cord) -- I've done this all the time with this and my Mogul with no problem.
Sitting here on the computer, the phone powers on by itself. I unplug it, and set it aside. A few minutes later I go to turn the screen on, and nothing happens. I hit the soft-reset button and nothing happens, I hold down the power and nothing happens, I remove the battery and put it back and nothing happens, I plug it back in and try to power it on and nothing happens (though the light shows that it's charging), try the hard-reset combination of buttons and nothing happens.
What the hell just happened to my phone? I found one thread on XDA that reported a similar problem with no real responses. Did my phone just die? I think this might have happened before, and all I did was leave the battery out for a few minutes and then put it back and it worked, but I'm not sure if I'm misremembering. That hasn't worked anyways.
Any info on this problem? I REALLY don't want to send it in for replacement without even being able to back it up, nor do I want to unnecessarily buy a new battery (which might not even work).

[Q] sponteneously bricked EVO-4g

I have a rooted HTC evo 4g. I rooted it about 2 months ago and have had no problems.
I woke up this morning, and it is bricked. I have not recently flashed anything or done anything beyond regular phone use.
i cannot enter download mode, and the "charging" led does not come on.
Any suggestions?
What does your phone do when you press the power button?
Have you removed the battery and inspected for indications of damage such as discoloration or bulges?
Have you tried connecting a different USB cable that is known to be working?
Have you visually inspected the USB connector for loose/damaged conductors?
BobWalker said:
What does your phone do when you press the power button?
Have you removed the battery and inspected for indications of damage such as discoloration or bulges?
Have you tried connecting a different USB cable that is known to be working?
Have you visually inspected the USB connector for loose/damaged conductors?
Click to expand...
Click to collapse
the power button does nothing.
The usb cable and wall adapter works on my kindle, and i tried an additional one with no results.
The battery appears normal, however my next planned step is to try and get a replacement battery and see if that works.
Try taking battery out and then plug usb cable in only and try to turn on...
angryITman said:
Try taking battery out and then plug usb cable in only and try to turn on...
Click to expand...
Click to collapse
no dice.
also wondering about the cause... 2 potential things:
- I've noticed that the phone gets very hot. 40+ degrees even when not running much. Is this within normal tolerance or could i be looking at heat damage.
- I've been getting the pop-up asking me to do some sort of OTA update. I keep saying no, because i know these ota updates can be incompatible with rooted phones. Could it have pushed through somehow and if it did could it cause the problem i am experiencing?
phone is fixed.
A read on the sprint forum that sometimes holding down the power for an extended time can get the phone to be responsive... had to hold it for like 90 seconds. It then flashed the white evo boot screen and powered back down almost immediately.
After this, however, the orange charging light came on and i was able to get to boot loader. I let the phone charge for a while, then it boot up as normal.
One of the things i noticed is that the battery is practically completely drained... this is odd as it was plugged into the charger when it died. On the same sprint forum, others have speculated that sometimes the battery can drain to the point where it wont accept a charge anymore... so maybe thats the issue.

Galaxy S II Won't Turn On or Charge!!!

BACKGROUND:
At first, it just started turning off for no reason (probably a month and a half ago).
Then this week, it would start to randomly turn off, and start vibrating constantly when charging. After fiddling with the buttons, it would eventually find itself into download mode and then later turn itself on.
NOW:
Monday morning, after several days of draining the battery to 0% (due to me solely charging it for an hour a day), the phone went dead. Then, that night, upon trying to charge it and turn it on, it remained stuck on a black screen. After taking out the battery, it would continuously beep while still connected to the charger. As soon as I put in the battery, it would become COMPLETELY unresponsive, with and without the charger. After fiddling with it for over an hour, I put it down and slept, leaving the battery and charge in the phone.
Tuesday morning, I clicked the power button, and the phone flashed to the lock screen. It displayed it was at 0% battery, but I think it showed a charging sign. I used the phone for almost 2 minutes, checking my texts, before it again went completely black. The phone became completely unresponsive (no beeping or anything, regardless of anything I did). I connected it to a wall charger again, and left it there for the entire afternoon.
Then when I picked it up at around 6 o clock, I discovered that the continuous beeping stopped, and it would only beep after holding the power button for around 5 seconds. It could beep regardless of whether the battery was out or not.
After charging it all that night, I found I could make it flash the Samsung logo for a fraction of a second after holding down both volume buttons and the power button. I looked it up, and supposedly it brings you to recovery mode, but I believe my phone is switching off immediately after bringing up the logo.
At around 12, Tuesday night, I again decided to hold down the power button (just to reassure myself of it still somewhat functioning), and it powered on for around ten seconds (!!!) . It got all the way to the end of the pink loading bar screen, but then beeped and restarted. The second time, it lasted only around three seconds, without even getting to the loading bar screen, before powering off. It became completely unresponsive afterwards, no beeping, regardless of where it was charging and whether the battery was in or not.
Wednesday morning (today), after having left it charge all night, the phone still was completely unresponsive. I then left it to charge the entire afternoon (until now), and it was still completely unresponsive. I took it apart and played around with the power button, but it didn't seem to be stuck. I've now put it back together and leaving it connected to the wall charger once again.
What I've Tried:
Tried connecting it to Kies (computer doesn't even recognize it)
Tried putting into Recovery Mode (unresponsive)
Tried putting into Download Mode (unresponsive)
Switched chargers (unresponsive)
Held power button (beeps, now doesn't do anything)
Held both volume buttons and power button (beeps then quickly flashes samsung logo)
Cleaned off some of the micro usb lint with a tooth pick (coincided with the stopping of continuous beeping, not sure if it caused it)
What I think it could be:
Faulty power button (this is what I thought it was, but now it's not vibrating)
Faulty battery (I kept draining to 0%, but if this is the problem, it doesn't explain the phone not displaying anything when it's connected to a charger w/o battery inside)
Faulty usb charging port (I've heard it sometimes causes vibration problems. wouldnt explain the restarting).
Fried motherboard (phone has had some water damage, but I'm not sure if it's the MOBO, considering its symptoms)
HELP WOULD BE GREATLY APPRECIATED.
Not Alone
hey, this isnt really an answer, but maybe something to bump this up. Mine went last night.... won't boot, won't charge... goes into download mode but no matter how many times i switch cables, install Samsung drivers, install Keis, or anything imaginable- i cannot get it to communicate with my PC. if i could i would be able to fix this problem.
i really hope that someone will take a look at these issues and give some input. my call to Samsung was useless, i wasted hours with redundancy. I bought the phone used off Ebay in mint condition... have taken it apart and cleaned it with no avail. i fear that soon the battery will be dead and there's no way to charge it. sucks. Samsung really should recall/replace this because so many people have similar issues. whether it's the USB Flex or the battery or the motherboard they should be responsible. looks like ill be getting a nexus 4 afterall.
please let me know if you figure anything out.
sluchy523 said:
BACKGROUND:
At first, it just started turning off for no reason (probably a month and a half ago).
Then this week, it would start to randomly turn off, and start vibrating constantly when charging. After fiddling with the buttons, it would eventually find itself into download mode and then later turn itself on.
NOW:
Monday morning, after several days of draining the battery to 0% (due to me solely charging it for an hour a day), the phone went dead. Then, that night, upon trying to charge it and turn it on, it remained stuck on a black screen. After taking out the battery, it would continuously beep while still connected to the charger. As soon as I put in the battery, it would become COMPLETELY unresponsive, with and without the charger. After fiddling with it for over an hour, I put it down and slept, leaving the battery and charge in the phone.
Tuesday morning, I clicked the power button, and the phone flashed to the lock screen. It displayed it was at 0% battery, but I think it showed a charging sign. I used the phone for almost 2 minutes, checking my texts, before it again went completely black. The phone became completely unresponsive (no beeping or anything, regardless of anything I did). I connected it to a wall charger again, and left it there for the entire afternoon.
Then when I picked it up at around 6 o clock, I discovered that the continuous beeping stopped, and it would only beep after holding the power button for around 5 seconds. It could beep regardless of whether the battery was out or not.
After charging it all that night, I found I could make it flash the Samsung logo for a fraction of a second after holding down both volume buttons and the power button. I looked it up, and supposedly it brings you to recovery mode, but I believe my phone is switching off immediately after bringing up the logo.
At around 12, Tuesday night, I again decided to hold down the power button (just to reassure myself of it still somewhat functioning), and it powered on for around ten seconds (!!!) . It got all the way to the end of the pink loading bar screen, but then beeped and restarted. The second time, it lasted only around three seconds, without even getting to the loading bar screen, before powering off. It became completely unresponsive afterwards, no beeping, regardless of where it was charging and whether the battery was in or not.
Wednesday morning (today), after having left it charge all night, the phone still was completely unresponsive. I then left it to charge the entire afternoon (until now), and it was still completely unresponsive. I took it apart and played around with the power button, but it didn't seem to be stuck. I've now put it back together and leaving it connected to the wall charger once again.
What I've Tried:
Tried connecting it to Kies (computer doesn't even recognize it)
Tried putting into Recovery Mode (unresponsive)
Tried putting into Download Mode (unresponsive)
Switched chargers (unresponsive)
Held power button (beeps, now doesn't do anything)
Held both volume buttons and power button (beeps then quickly flashes samsung logo)
Cleaned off some of the micro usb lint with a tooth pick (coincided with the stopping of continuous beeping, not sure if it caused it)
What I think it could be:
Faulty power button (this is what I thought it was, but now it's not vibrating)
Faulty battery (I kept draining to 0%, but if this is the problem, it doesn't explain the phone not displaying anything when it's connected to a charger w/o battery inside)
Faulty usb charging port (I've heard it sometimes causes vibration problems. wouldnt explain the restarting).
Fried motherboard (phone has had some water damage, but I'm not sure if it's the MOBO, considering its symptoms)
HELP WOULD BE GREATLY APPRECIATED.
Click to expand...
Click to collapse
It may be your battery, u need to remember why they tell u not to run the phone that way, the batteries our phones run need to maintain a certain charge in order to work correctly, if like u said u only charged it an hr or so a fah for over a week and drained completely more than once u may have rendered ur battery unable to hold a charge, in effect not allowing the phone to run its boot process, I would try a new battery, because beyond that the only other logical explanation is a hardware failure, stuck power button wouldn't render the device unresponsive only when the battery was put in like that, it would bootloop, have u ever just held ur power button in? The phone vib an shuts down a. Vib again n shut down, not become unresponsive, I would try a new battery, and if it works, respect the charge lol
Sent from my SGH-T989 using xda premium
I would agree, seems to be the battery. I bought 2 batteries and a 110V charger on eBay for $30. They don't have the NFC antenna in them but I've never missed it. Not only that but charging that way saves the wear and tear on the USB port.
T989D
latest CM 10.1 nightly
latest Uber nightly
My Idea
Follow the procedure on this website
galaxys2root.com/t-mobile-galaxy-s2/how-to-unroot-t-mobile-galaxy-s2-jelly-bean/

[Q] Turned it off...Won't turn back on.

I did a soft shutdown and now it won't turn on. No response to Vol UP + Vol DOWN + Power. Nothing but black. Its connected to power and was at 80% when I shutdown. USB debugging was enabled. Any hints? Thanks, -RP
ronpandolfi said:
I did a soft shutdown and now it won't turn on. No response to Vol UP + Vol DOWN + Power. Nothing but black. Its connected to power and was at 80% when I shutdown. USB debugging was enabled. Any hints? Thanks, -RP
Click to expand...
Click to collapse
Ugh, I had to hold power button for 30 seconds. Its really excessive. Delete this please. Thanks.
funny thing is the old nexus 7 had the same issues
I received mine today and it wouldn't turn on at all. All I got was a flashing white light after holding the button to turn it on so knowing that the same thing was common on the previous generation N7 I tried the 30 second trick with no success so I figured I'd share my experience.
Turns out my battery was at 0% out of the box. It was so dead I had to do the following to actually get it to start charging unfortunately:
1. Open it, I followed the guide @ ifixit: http://www.ifixit.com/Teardown/Nexus+7+2nd+Generation+Teardown/16072/1
Note: The plastic bezel surrounding the screen is incredibly soft plastic I just learned. Even using plastic pry tools I ended up leaving marks the plastic, despite being extremely careful.
2. Disconnect the battery (follow the guide above)
3. Press the power button and hold down for 10 seconds, but don't release yet.
4. Using the supplied AC adapter, apply the power and continue holding for another 10 seconds.
5. Reconnect the battery while the AC adapter is plugged in​This should get you to the point where you at least see the battery charge icon on the LCD. I waited another 30 minutes before moving on and powering the device on. I intend to leave it charging to 100% before I do anything else with it.
I remember on some older devices I've had when they got into 0% state, they didn't want to take a charge from a high power charger and I needed to switch to 500ma USB 1.1/2.0 slot on PC and let it sit a while before it would trickle in enough charge to get some life.
After that it would take charge from any source again.
joshtheitguy said:
I received mine today and it wouldn't turn on at all. All I got was a flashing white light after holding the button to turn it on so knowing that the same thing was common on the previous generation N7 I tried the 30 second trick with no success so I figured I'd share my experience.
Turns out my battery was at 0% out of the box. It was so dead I had to do the following to actually get it to start charging unfortunately:
1. Open it, I followed the guide @ ifixit: http://www.ifixit.com/Teardown/Nexus+7+2nd+Generation+Teardown/16072/1
Note: The plastic bezel surrounding the screen is incredibly soft plastic I just learned. Even using plastic pry tools I ended up leaving marks the plastic, despite being extremely careful.
2. Disconnect the battery (follow the guide above)
3. Press the power button and hold down for 10 seconds, but don't release yet.
4. Using the supplied AC adapter, apply the power and continue holding for another 10 seconds.
5. Reconnect the battery while the AC adapter is plugged in​This should get you to the point where you at least see the battery charge icon on the LCD. I waited another 30 minutes before moving on and powering the device on. I intend to leave it charging to 100% before I do anything else with it.
Click to expand...
Click to collapse
mine was this dead too I just let it sit on charge for 2 hours and was up and running.
kpa2727 said:
mine was this dead too I just let it sit on charge for 2 hours and was up and running.
Click to expand...
Click to collapse
lol - this happened to me too. Except double whammy - as soon as it was charged enough to turn on, it wanted to do the system update and wasn't charged enough to do that. Back to the USB it went!
Well I got my replacement for the one with the dead pixels, it started up fine and I even configured just to check it had no dead pixels. I had to step away for a few minutes and it was off, completely dead. Tried ever variation of tricks and I get nothing, no white LED, no charge indicator, nothing.
I think I'm sending both the replacement and the original back for a refund, this is just unacceptable at this point.
I bought one but returned it after 3-4 days. Mine was fully powered and I would go through the shutdown procedure. The device would power off. Then I tried to turn it back on. It would not work. I held it down for several variations of time: pushed it quickly, help the power button in for 10 sec, 15 sec, 30 sec... I found that when I connected the device to power through the usb the screen would show 100% charge right away. I would then hit the power button and it would turn on fine. I immediately unplugged the device and everything was fine. i powered it down again and repeated this process 2-3 more times before I said the heck with it. Anyone else know of this issue or did I just have some crazy unit?

[SOLVED] [Q] Possibly bricked....

Hi,
my battery ran very low (~2%), and I put it in a car charger, and used it for a call. I've heard of car chargers or combination of different cables etc. causing problems, but I think I can rule out a burned out motherboard, as the phone was functioning for the call and a text was sent after.
About 5 min after I took it out of the car charger (got home) I noticed that the capacitive buttons were lit. I tried turning the phone screen on, nothing happened. So I held down the power button for 20 seconds or so, again nothing. Then I held down the power button and volume down, and it went into recovery (twrp)
Not sure why I did this, but I wiped the cache and dalvik cache, and hit reboot system. Now at this point I don't know if the battery died, or if it tried to reboot and didn't work. Either way, it is now dead
I have tried the following;
Hold power button, no response
Hold power button, and volume down, no response
Hold power button, volume down and volume up, no response
Left charger plugged in for an hour, no response
There is no led light on when the charger is plugged in
I have tried connecting to a pc, it makes the 'new device connected' sound, and soon after, the disconnect sound. Windows states that the usb device is not recognised.
Any ideas?
Forgot to mention I'm on Slimrom 4.2.2 build 8 official
Is it true that the phone can't be charged while in TWRP?
Any help would be appreciated, I need to flash KK!!
Shameless bump
I have tried the script to get the phone to charge/ get battery voltage here;
http://www.hackmyandroid.com/comprehensive-guide-on-unbricking-the-htc-one-x/4216
Also, I have read that there could be a script to get the phone to charge, post #4 here mentions that;
http://forums.androidcentral.com/htc-one-x/300271-htc-one-x-will-not-turn.html
Can anyone pls help with this script mentioned in post #4??
I've rooted/ custom rom'd about 9 phones, I can't believe that it can be bricked by losing battery power while in recovery... nothing has ever gone wrong like this, please help!!
Try leaving it charging for ~24 hours
Try unplugging the battery from the motherboard and plugging it back in, if not get a new battery HOX is only about 5 pounds or you can upgrade to a HOX+ battery for about 20 pounds.
tried charging overnight ~12 hrs, no joy, but thanks
I have it opened up now, so might try disonnecting and re-connecting battery, thanks
I have been speaking to the team at TWRP on irc chat. Somebody suggested to strip USB cable back and connect bare wires to terminals of battery to see if it will charge. Will this cause problems as USB is ~5v and the battery is 3.7v??
msc125 said:
tried charging overnight ~12 hrs, no joy, but thanks
I have it opened up now, so might try disonnecting and re-connecting battery, thanks
I have been speaking to the team at TWRP on irc chat. Somebody suggested to strip USB cable back and connect bare wires to terminals of battery to see if it will charge. Will this cause problems as USB is ~5v and the battery is 3.7v??
Click to expand...
Click to collapse
I wouldn't risk the USB thing. You might as well get a new battery. I have a spare HOX+ battery which is 2040mah bigger than the HOX, I could sell that to you for a cheaper price than everyone elses.
I have since replaced the battery, and also a new power flex cable (that I broke during disassembly!) and something has changed at least......
Beforehand, Windows did not recognise the device at all, sometimes the 'USB device not recognised' dialogue box wouldn't even appear, although it would make a sound
Anyway, now it says that it's not recognised, but in Device Manager, it says it is a APX device (before it was an unknown device)
Can anyone shed any light on this?
Apex mode unfixable with software I'm afraid... Needs a new main board
Sent from my HTC One using xda app-developers app
Stefan0vic said:
Apex mode unfixable with software I'm afraid... Needs a new main board
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, just been reading up on it, aaahh well, guess I can send it off for repair
Any idea what could have caused it?
phone is back up and running
thanks to everyone for their input
here's how it started working again
http://forum.xda-developers.com/showthread.php?t=2681730

Categories

Resources