I have a Cingular 3125, working fine for weeks, happened that two days ago, I was charging the phone and transferring files to my computer via Bluetooth, nothing unusual, then it just got frozen, nothing responding, so I just took out the battery to manual reset the device and reinserted it, then tried to turn on the device, but it refuses to boot, no lights at all, also when I attach the phone charger, it doesnt show the usual orange led when charging, but I can feel that the phone gets warmer because the charger is attached and then after a while it gets a bit cooler, just like when it finishes charging, the usual behavior, but again, no lights at all trying to boot it or even attaching the charger, I've tried taking the battery off for hours and nothing also, and I wasnt overclocking the phone... would you say it just died? or maybe someone had same issues and solved it someway? thanks.
try this
OK, I don't remember where I read this, or the exact procedure, but give this a try.
remove the battery, press and hold the red call end key (power key) for 30-45 seconds. insert battery and do a hard reset, IE.. power on holding the 2 top soft keys while powering on the phone.
this method is supposed to clear any mother board issues and reset the phone. It has been a couple of years since I read the procedure so I am not sure if this is the correct way, if it does not work, try the same thing, only try taking the battery out, then put it back in and press and hold the power key for 30 - 45 seconds.
may or may not work, but can't hurt to try.
i had the same problem with startrek which i had bought from eBay
one more advice - try to hold record (notes) and camera buttons and insert an USB cable to your PC, it should enter to Bootloader mode
well, I have dissasembled the whole thing, I havent reached anything, even disconnected the backup battery, nothing, have checked battery with a multimeter and is full loaded... in short, someway the cell phone seems has just died, Erofich, to enter bootloader mode, the phone must turn on, it just doesnt want to start at all, no lights when connecting charger or USB cable... I'm sad because it was working fine with no problems for three months and more sad because it's the end for me to windows cellphones for a long time, I've invested a lot in this phone, accesories, unlocking, and even the same day it died also bought more memory and a neat skin cover and I'm not in mood to invest more in a cell phone so I'll use a spare crappy feature phone.
Thanks for your support.
one last effort
You could try one last thing, this has worked for me with a couple of startreks,
take the phone apart, and take the motherboard out, use a hair dryer to heat the motherboard, don't get crazy with it, but using the hair dryer on the high setting for about 30 to 45 seconds at about 3-5 inches, might revive the phone. (don't heat the battery, just the motherboard)
Put the phone back together while it is still hot (but not so hot that it will burn your fingers) and try to fire it up.
This has worker for me in 3 cases (phones that I bought off eBay that had the same symptoms as you have described)
good luck
big problem!!!!!!!!
I have been struggling to flash (again) the great pro V2 rom, but I always used my VMWare based XP windows version on my Vista laptop. Today I could use a genuine XP Laptop and I could make a connection and start the upgrade!
Sounds good? That's what I thought too, until the upgrade stopped at 70% (and I didn't touch anything), because of a connection error. I followed the text on my PC screen and I finally it started flashing again for a few seconds and then my startrek suddenly restarted, but it stops at the first splash screen! I tried to get my device back to bootloader mode (push 2 soft buttons and start), but no bootloader mode, only the 1st splash.
I solved the problem.
Technically this is about the New Padfone Infinity (A86), but I'm not sure where else to turn...
So I forgot to charge my phones battery over night, so the next morning it was turned off, I put it inside the station, it booted, but when it got to the lock screen, Android nicely shut down the phone...
From that point on I haven't been able to turn on the device:
-No screen
-No recovery
-no fastboot
-No vibration
-Nothing
So first thought, a dead battery right? But when I connect it to my PC, it's recognized as an Unknown Device...
I tried pretty much every Asus driver/Google Driver that I could find, but nothing...
Does anyone have any suggestions?
After reconnecting the battery it's recognized as QHSUSB_BULK. A Google search tells me that this is a Hard Brick, any advice which tutorial I should use since there are several...
My LG V10 died all the way back in July I think, due to the bootloop bug. Now it refuses to even bootloop, nothing comes up on screen. When plugged into PC while holding power Qualcomm 9008 comes up, which gives me a start. I am using an LG-H900. So can't flash that boot.img that only uses 4 cores. However, I do have an SD Card (idk how that would help just lettin ya know). Any way I can fix this? Right now I use a OnePlus 3 instead.
*edit* was playing around for a bit, and plugged it into wall and it said charge more before turning on. It has been plugged into the wall for a bit and still says this, and tries to turn on every time its plugged in instead of charging. Any ideas?
Yes annoying feature on many newer phones,
They try to turn on automatically when they think they've got enough juice.
Even tough once they start booting the battery level plummets and the phone just stops and goes charging again and repeat the story.
I've got no idea if it can be turned off. i don't think so.
Send it to LG. They've extended the 1 year warranty to 27 months from purchase or 30 months from date of manufacture.
Hey there. I found a bit old phone in my house, Huawei G730-U10 with MTK6582. Here's problem:
Phone won't turn on at all (no reaction) with battery in and USB out.
With battery in and USB in (connected to charger or PC, no matter what), at first it turns on red led that stays still, and after some time it starts vibrating with interval of about 10 seconds and PC sees it for 2 secs (it connects and after 2 secs - disconnects), then everything repeats. I assume it's bootlooping, but there's no anything on screen (it doesn't even turn on, full darkness). This continues even after taking out USB, only way to stop it - take out battery and place it back.
With battery out and USB in, red led starts blinking with very quiet beeping (very very very quiet).
As you could guess - recovery, fastboot and other things aren't working.
I've checked main board, everything is ok, connected and working fine.
I think there's problem in ROM (not firmware ROM, but ROM that's read-only memory). Something's wrong, maybe there's wrong preloader (or there's no preloader at all), maybe boot partition is damaged, I don't know.
Service center tried to fool me on buying new board for 100$ (althrough it costs 40 on aliexpress), I think they didn't even look at it, so I can't trust them.
I don't need suggestions like "try to flash new rom", you think I didn't try? How is this possible if I can't make PC to see phone for more than 2 secs? Flashtool isn't working even without battery mode.
Do you have any ideas?
Thanks for help.
My S9+ was acting quite weird this morning. Some apps continuously crashed or wouldn't start.
So i rebooted my phone (just from the normal power button menu) and then it went completely black.
It doesn't charge (or at least, it doesn't show it charging), it doesn't respond to forced resets and the screen is completely black.
The only thing it does, is briefly show a USB device when connecting it to a PC.
I've connected it to a Linux dev computer i have laying around and i see the following device connected briefly:
VID: 0x04e8
PID: 0x1234
It stays connecting longer if i hold the power button (about 8 seconds before power cycling).
The only things i could find online were some very old threads about Samsung's DNW mode, but nothing from this decade.
I think my Flash chip might be cooked, but i hope i'm wrong.
Anyone got any experience with this?
Update
I've sent it back to Samsung for repair under warranty.
The flash chip was gone. It started corrupting writes and finally it was so far gone that it couldn't load the bootloader.
They've replaced the main board and battery (probably because they tested it and saw it was going bad), that fixed it.