Database Info

[Q] HELP !! Relay has no power ....

I have been rooted since I got the phone with no problems other than the minor annoyances of the echo or camera color being off. But I decided to try a different rom from the one i was using. I had a nightly # 32 (I think) 20130309. I decided to try Nardholio's experimental # 92 (I think) 20130423. Seemed to work fine, just like the other I had in there. But battery drained FAST, and if doing too many things at once it would reset. When battery got to 19% I plugged it in and pretty much at the same time it reset. It started to load the cyanogenmod bootloader (like normal) but then it died. Screen went black and have not been able to do ANYTHING since. Its been 5 days now. I've put my wife's battery in, and still nothing. Only thing it does do-- when battery is out and i plug in a charger, the red light comes on for about a minute, then off. My computer didnt even recognize it anymore. I had to install different drivers etc for devices not to have an exclamation mark. WILL NOT GO TO DOWNLOAD MODE, NOTHING!!!!! HELP

Was this one of the main nightly builds (apexq job) or one of the other ones on Jenkins? And what exactly does your computer register in device manager when you plug the phone in? Does it show something normal, like Android Composite Device or SGH-T699 or the like, or does it say something like QHUSB-DLOAD?
QHUSB-DLOAD is a very bad sign, it means your phone is essentially a brick. It means the phone can no longer boot from flash and is waiting for boot instructions over usb. Which means you'll need to find a repair shop with jtag or send it to T-Mobile or Samsung for warranty repair (don't let them know you rooted or flashed ROMs, they won't be able to tell anyway)
You might try a Samsung jig. If it works the phone will power up into download mode, at which point you can flash a stock rom with Odin. http://www.amazon.com/SainSonic-Dongle-Samsung-Captivate-Vibrant/dp/B0053H73JQ

correct
Yes. A main nightly build, ls(dot)infernix(dot)net/jenkins and I believe it was number #92. It was a passing, nightly rom it said. When plugged in it says QHUSB-DLOAD. I appreciate your help on this.! I am going to try to build my own jig and see how that goes and then I will ship it to samsung. Hopefully they ship me a new one and by then maybe jenkins will have some solid working roms.

REPAIRED
vulgarz said:
Yes. A main nightly build, ls(dot)infernix(dot)net/jenkins and I believe it was number #92. It was a passing, nightly rom it said. When plugged in it says QHUSB-DLOAD. I appreciate your help on this.! I am going to try to build my own jig and see how that goes and then I will ship it to samsung. Hopefully they ship me a new one and by then maybe jenkins will have some solid working roms.
Click to expand...
Click to collapse
UPDATE:
Thank you for all the info. I shipped the Relay back to samsung for repair and today they emailed me this:
Original Problem:
TECHNICAL INQUIRY - POWER - WILL NOT POWER UP
Solution:
REPLACED COMPONENT - REPLACED PBA
and is heading back today !! Now that it has power it should boot for me correct ? Am i going to have to upload all files to the phone ?

I just started having a similar looking problem, but not quite as bad. Phone had been working all but fine (aside from a few random reboots here and there (yes rev0 cpu)). I've been on the staging builds since #341 (previously stock rooted), and this morning updated from #351 to #352. Phone worked fine all day, then by the time I got home from work, it stopped booting. It'll power on long enough to show the samsung logo for a second or 2 when booting normally, or into recovery, and when booting into download mode, it will survive long enough to confirm and show the "Downloading..." screen for a second or so. (in other words, it shows the Custom Binary Download > 0 ) And in download mode, Device Manager detects the phone as "SAMSUNG Mobile USB CDC Composite Device" for the half-second that the phone remains on. Multi-meter shows >4v on the battery.
So, ...unfortunate hardware failure?
I suppose tripping the flash counter is irrelevant, as the phone's older than the 1 year warranty anyway.

Missing OS

I am hoping someone can help me here.
My notepro was working fine, except for the screen flicker issue. I wanted to root it in order to adjust voltage and a few other things to try and prevent the flicker.
I was able to install TWRP, and SU and verified it was now rooted. I then went and tried to install a custom ROM http://forum.xda-developers.com/gal...-civzp900lollipop-5-0-2-aroma-12-jul-t3155589
Everything seemed to install fine, the kernel, ROM, all that. However, when I restarted the device, i got stuck on the bootloader with the seanandroid red warning message. It would not load past this. So, i wiped and reinstalled everything several times over, and still no fix. I searched online and found a zip you could flash to fix the booting issue, but no help. I wiped everything except the extsd and reinstalled ROM and everything. Now TWRP says no OS and I am still stuck on the bootloader screen. i cannot do anything at this point.
After a bit it started flashing and flashing faster and faster. This was after sitting with the bootloader screen showing for a while. I assume battery ran out, but every time I tried to charge it, it either tries to show the battery charging from the off screen, but just gets frozen, and then starts to flash again.
I am letting it sit right now. I am thinking the temp or voltage spiked due to low battery power, but I am not sure.
Can anyone offer some advice?

I am thinking at this point it might be the motherboard.
After it started flashing, it would get so bad that the screen would fade out and then back in. Now, it wont do anything, and wont even indicate charging. Sometimes it did, but would just show the battery icon with a loading circle in the middle and never actually show it charging. now its just dead.
There is no way that rooting and installing a rom could have done this. i am thinking it is a hardware issue.
My choice now is to part out the pieces that work and scrap the mobo or to replace the mobo

Have you opened it up and taken a look at the battery connector to see if resoldering would help?
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Sent from my SM-P900 using Tapatalk

batt connector seems fine. It seems that if I let the device sit for a white it will spark a little life and then die off again. Its rather odd.

disconnected the battery and plugged it in. was able to boot into recovery temporarily. however, it only works for a few min. tried to flash stock kernel and it had an issue, reloaded twrp itself and then would not read anything on the extsd and died.
i was to flash stock, but the stock file I have is .zip and odin will not recognize it to flash in download mode.
Ive rooted and flashed many devices before, but its been a long while since I did. A year at least, and not on this device.
At this point I am assuming that the mobo is the issue, but I am not sure. It was having the screen flicker issue before, which seemed to be heat or voltage related.
If I cannot fix this, i will likely just sell it off for parts. The screen, batt, all that should be fine otherwise.

Will not finish booting up (pretty sure its NOT the pwr button)

ok so im working on a nexus 5. i was already all too aware of the potential power button issue so that was the 1st thing i checked out, ive cleaned it twice now and made dbl damn sure i can feel it both click in and click out when being pressed.
on top of that i can boot into twrp both temp boot and flashing recovery for it. it does not cut off when in twrp (as i imagine it would if it were the power button being stuck)
previously i could not boot into twrp or flash anything at all so i ordered and installed a breand new battery.. now i can flash twrp via fastboot (progress right?)
however when it is powered off, on teh charger it shows the battery full with lightening bolt, then that fades and is replaced with a hollow battery being filled, then goes black and starts over... leading me to believe its not taking any charge in..
ive tried stock 7.1.1, stock 7.0.1, stock 6.0.1, cyanogenmod 14 and even ran the NRT by Wugs... i have wiped everything, i formatted data and made sure the partition was correct pre-flashing by running NRT to return stock values n such, i have also tried different approachs to flashing. fastboot flash system, adb sideload, twrp install zip and NRT...
with my small (yet excessive) experience so far with android im led to believe this is being caused by some sort of conflict inside the system memory, it almost has a rythym to when it cuts off, like when it hits block such n such it goes "OUCH DAMMIT" and retreats for safety (powering off)
you'll have to forgive me for starting a new thread, the only info i can find pertains to the power button which i am fairly confident it is NOT, and after hours of searching tonight alone im really not for diffing thru every thread, i did however do a quick search prior to posting....

Where did you get the battery? Tried different USB cables and chargers? The phone boots and runs properly on stock?

I had a similar problem. I talked to LG customer support and they were aware of this issue and suggested that the whole logic board needs to be replaced. Apparently this is common with LG devices.
A workaround that worked for me is to turn off the phone for 1 day (let it cool down), clean flash whatever rom you like, then flash ElementalX kernel with the CPU under-clocked to minimum.

I have tried various ports and cords, battery from a top seller on ebay (checked reviews prior) and I cannot boot into stock Android either... During my extensive tweaking of the device last night I relocked the bootloader while returning to complete stock... After doing such I later tried some thing I saw suggested on the forums, removal of the power button.. so I desoldered it.. didn't change anything so it's def not the button... However now I cannot click the screen to confirm unlocking the BL again so I'm close to boned as far as flashing options ATM... Lol fail...

If it is a motherboard problem, and it sounds like it is, the cheapest solution may be to buy a used Nexus 5 with smashed screen and working motherboard. Swapping the motherboards is quite simple.

That's probably gonna happen, I don't see many other viable options .... It's not my phone so imma be putting money into someone else's to save face. U don't get a broke device back from me
Thanks guys

S7 died, no response at all anymore. (Black screen)

Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!

Cloud2F said:
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Click to expand...
Click to collapse
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.

cooltt said:
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
Click to expand...
Click to collapse
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?

Cloud2F said:
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Click to expand...
Click to collapse
the way to test if it has power but blank screen is to hold power+volume down+home. If it has power it will turn off and boot into download mode

After the Forst Crash all such combinations didnt Seen to work either. Once odin recognized is while having a black screen. At that point I flashed stock :/ but still, not even the led was showing something

Poco X3 NFC - Can't access bootloader, fastboot or system (bootloop)

Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])

Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.

Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway

Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...

Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.

CaptainFedora, did you solve the problem? I have the same issue...

Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.

Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.