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.
Related
I have done hours of searches and can't find the answer to my problem. Hopefully someone here can help.
My GT-N8013 is stuck in the Samsung Galaxy Note 10.1 logo screen. I can't even turn it off without it bringing this screen right back up. It only goes dead when I unplug it and let the battery run out of juice.
I can get it to restart into Odin Download mode, but not into the recovery mode. I can install roms and CWM and stock roms using both Kies and desktop Odin3, and I get "pass" status with no errors, most the time, when I do rom update, but I can't get to the restore screen with the power + volume up button, then releasing the power button and holding down the volume up button only. It just stays on the Logo screen.
I hold down the power + Volume down button and it will restart into the Warning screen that allows me to hit the volume down to go to the download screen or volume up to cancel and restart. Both the volume up and down buttons work for this action so I'm sure the buttons are working okay.
I thought maybe the battery wasn't charging right and that was preventing it from going into recovery mode, but I can charge it for a while and unplug it and the screen will stay on the logo screen for a long time, so I think the battery is okey.
Samsung just said I should send it in, but it is out of warranty and I don't want to put much more money into this devices since it is old and a new version is out now, but I hate to think a great device like this that worked so well for so long is now going to be worthless because I can't figure out how to fix it. Hardware seams to be working fine and just a few days ago, the software was working fine. I'm so confused.
Leading up to these events, I had it turned off for a few weeks because I was traveling and going on airplanes and never ended up using it on the trips so it remained turned off. When I turned it back on, there was a OTA system update that I wasn't sure what it did. Didn't appear to do anything noticeable. Still worked normal. Then a few days later I did a personal data wipe because I was going to sell it and get the new Note 10.1. I went through the new setup process without problems, everything was fine. I sold it to a guy and a day later he contacts me and says it isn't working properly and I've been dealing with this ever since. It didn't appear to have any physical damage and the custom binary download count was at "No" so I don't think he tried to load any custom roms. I don't think this guy is tech savvy enough to do anything but plug it in and use it normal, so I don't suspect foul play.
Any help would be greatly appreciated. Thanks.
Check this
http://forum.xda-developers.com/showthread.php?t=2477626
Sent from my GT-N8013 using Tapatalk HD
I have the exact same symptoms. (No recovery mode / stuck on boot screen even after fresh stock rom installed). Out of the blue after working fine the day before.
Anyone know:
a) of anything further that I can try to resurrect this
b) if I might still have any joy getting warranty service from the shop I bought it from in the UK / Samsung if they send it back to them. I have more than a year left on the 2-year warranty they provided, and have only ever run/attempted to run stock. However as I have been out of the UK my custom binary count has increased to 7 as I have tried to reinstall Stock Roms myself to fix the problem. (However OS version still shows as Samsung Official, not custom)
Thanks so much if anyone can help me
Custom binary 7 = warranty void .
I would try flashing Philz recovery tar through Odin and try recovery mode .
Hi guys,
I recently bough two S6-G920F really cheap (~80 euros each) that appeared to be functional, but with software issue (one wasn't booting up, the other was bootlooping), in hope of repairing them.
From the start, I'll tell you that the phones are currently at a GSM Service, at a hardware guy. I haven't heard from him yet (leaved them today in service). I tried all possible software solutions, no luck. I'm more interested to see if anyone else encountered these issue, what are the possible causes and maybe if someone managed to fix these kind of issues.
Device 1 : No physical damage on the phone itself or the board. The phone doesn't charge when plugged in, but (tries) to boot up as soon as it's connected. It gets stuck on the "powered by android" screen. I am able to enter download mode, but not into recovery (the button combo doesn't work). The battery itself charges ok externally on a jig. I'm not able to flash any kind of firmware on it with Odin, it always fails at system.img at random percentage. I can flash custom recovery / bootloader / kernel, but has no point, I can't get into recovery or past the the boot logo. If left plugged in on the download screen, the phone gets a bit hotter than normal (not sure if it's because of the screen always being on). While plugged in, the board draws constantly 700mah, not letting the battery charge. The guy I bought it off told me that it died suddenly while gaming and never turned on again.
Device 2 : Was dropped, cracked screen glass and back glass. It charges, I can get into download / recovery mode, i can flash any firmware I find. Doesn't get past the samsung logo (in case of 5.1.1) or the "installing system" screen (in case of 6.0.1). It either bootloops or it freezes. Tried custom rom, custom kernel, original firmware, they all do the same. Tried going into recovery and wiping cache & dalvik, and the phone got stuck on a black screen with the blue led always on. Had to disconnect the batter (key combo didn't want to work anymore). The guy I bought it off told me it worked fine with cracked screen until the 6.0.1 update kicked it, then it started bootlooping and it stayed like that.
What my best guess is :
Device 1 : a short somewhere on the motherboard. Didn't figure out yet where. Maybe caused by faulty charger?
Device 2 : faulty eMMC chip. That's the only thing I can think of that would make any kind of firmware I put on it freeze.
Did you guys ever encounter any of these issues before?
Cheers.
Seems your guesses are right, no i didnt encounter these problems before.
Hi guys,
Small update. Got the devices back from the GSM service, they didn't manage to do anything.
For device #2 I managed to get a stable recovery (that doesn't freezes) by flashing arter97's recovery. From here I proceeded to installing custom ROM/kernels, but no luck, still freezing on the Samsung logo once it reboots after install.
I have access to the terminal via TWRP. Any commands that I can use to do some memory / cpu checks?
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
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
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