Database Users

Bell Vogue keeps rebooting

Hi everyone,
I have had some trouble with my Vogue. At first it simply would not turn on. I would get a red light when I plugged the phone in to charge it. I have been using my old phone for several months now. Today I went out to the nearest Bell store and it seems like anything new is going to cost in the $500 area because I still have 1 year left on my contract. So I have renewed my interest in getting my Vogue working again
The original thread describing my original problem (with the red light) is here:
http://forum.xda-developers.com/showthread.php?t=546674
I purchased a new battery and now when I plug it in on the USB I can turn it on (no lights, red, green, or otherwise) but it does turn on. It boots up just passed the blue “Bell” splash screen and then reboots. It does this over and over again.
I am able to get into the boot loader screen by holding down the power and camera buttons and pressing the reset button.
Any ideas on what I can do? Any suggestions are welcome.
Regards,
The Fish

Reflash your rom when you get to the bootloader screen.
If you are unlocked flash nfsfan or whatever, just rename the nbh file to 'VOGUIMG.nbh' and it will flash.
If you were on stock you'll need the nbh from the stock package.

OK, here is an update
I have tried a hard-reset (press Send and End buttons at the same time and press reset button). This worked but the phone still kept rebooting. Tried the original battery, phone booted a little further up before rebooting.
I got the phone into boot loader mode and left it plugged in on the USB cable for a few minutes. This time when I rebooted I became ecstatic. I got all the way to the “align your screen” stage before hearing the “phone is dying” sound and the phone turned off. So here is what I think may have happened:
I have long lost the home charger kit. So I have, for as long as I can remember, been charging it by plugging it into a PC via the USB. This is fine except that Windows will only power the USB for the device if there is a driver installed. The device/phone looks different to Windows when it is in boot loader mode then when it is fully booted up. If the device is so dead as to not even have a flicker of life I don't think Windows sees it.
I have been doing this tonight under Linux. Linux seems to either have the driver, a more generic driver or powers the USB all the time for any device. I noticed this same behavior when charging my Moto Razr the same way. Under Linux it just worked by plugging it in. Under Widows I had to install the driver. So maybe here is what happened.
The battery got SO dead that it was not able to boot the phone up far enough for Windows on the PC to see it, recognize it and begin powering the USB port. Perhaps leaving the phone in bootloader mode and plugged into a Linux box got the battery a little more charged till I got to the point of being able to align the screen.
Anyway, I am more then ever convinced that this is some kind of battery/power issue. The phone is now lying here powered up and charging (already at 20%). The carrier customizations ran, rebooted while I crossed my fingers, and came back up. I even called *BELL and got a message about activating my phone. Tomorrow if the phone is charged up and behaving normally I will get an ESN change done and be back in the world of decent smartphones. Man have I ever missed my Google Maps
The next step is to flash a more up-to-date ROM... if I dare mess with a good thing.
The Fish

[Q] Mt4G won't boot AT ALL

I went out for a while with my battery at 20%, when I came back it had drained out. I put it to charge, but when I tried to switch it back on, it refused to boot. On a normal power button press, it would vibrate 3 times and then the red notification light would start blinking. Same thing with power + volume_up. If I press power + volume_down, it would vibrate 5 times and the green notification light would stay lit. Nothing comes on the screen, whatsoever.
I was rooted with S=off, and was using the Operation Inferno ROM (which I have been using comfortably for the past month or so).
I did try some stuff with ADB, such as using it to reboot into bootloader and recovery (same 3 vibrate + red notification light), pushed the Operation Inferno ROM again to the sdcard and tried to restore the ROM from that location (for which I got adb: unable to open file /sdcard/backup.zip).
I haven't yet gotten around to downloading and installing the factory image some have suggested for the eMMC issue (PD15IMG.ZIP) but I wanted additional opinions considering most people with an eMMC issue have been able to open HBOOT at least.

When the phone doesn't power on, neither ADB nor fastboot will help you. There is no device on the other side, so all your attempts went to the drain, and it was expected. Nothing to do with eMMC issue or anything else. Your phone just doesn't power on.
Put your phone to charge, if the light turns orange - just leave it to charge until it's green, then disconnect and try to power on.
If the light doesn't turn orange, or it doesn't power on even after charging - remove the battery for 10 min, press Power button for 1/2 min, release the button, reinsert the battery, put to charge. And again, let it charge before you try to turn it on.

I did charge it earlier (for about half an hour or so) and the orange light does come, but it didn't boot after that either.
I'll just give it a try by charging it through the night and see.

I think a key thing is to take out your battery for 10 min, as Jack_R1 suggested. Then proceed with the charging.
Sent from my HTC Glacier

Still doesn't work. I dissembled it and kept it like that for quite some time, then put everything back and charged it for hours. Still the same issue happening during boot.

Connect the phone to USB, powered off, see if the PC recognizes "QHSUSB_DLOAD" device. Try to power it on, see if it happens.
If it happens - it means your primary bootloader is screwed, in another words - no repair (actually, repair is theoretically possible, but no guide, no information and no sources exist for MT4G).

Jack_R1 said:
Connect the phone to USB, powered off, see if the PC recognizes "QHSUSB_DLOAD" device. Try to power it on, see if it happens.
If it happens - it means your primary bootloader is screwed, in another words - no repair (actually, repair is theoretically possible, but no guide, no information and no sources exist for MT4G).
Click to expand...
Click to collapse
When its plugged in, its recognised by the ADB (even when powered off), and I can do some basic commands (mentioned in the first post). When I power it on the same thing happens as when it wasn't plugged into USB (ie, the vibration and the blinking LED).
I'm also worried about water damage, since a very tiny amount did come on it as I was sweating profusely. Although the indicators in the battery tray and on the battery itself don't signal damage (they're completely white) I've just decided to try and keep it opened up in a bowl of rice, just in case, until someone is able to come out with some idea.
As I'm in India, taking it to T-Mobile is not an option. If nothing works out, I might take it to HTC and see if they can help out.

[Q] S4 shuts off after splash, any ideas?

My S4 has finally kicked the bucket. It turns on long enough to display the "Samsung" splash screen with the padlock icon that says "Custom." After about two seconds it instantly shuts off, and can't be turned back on.
Pull the battery, the phone automatically turns on, shuts off again, rinse and repeat.
At this point I just want to salvage my pictures and music from the phone; is there any way I can mount the internal SD in the state that it's in? I'm sure this power issue is hardware-based; I can't get into recovery or download mode before it shuts off on me.

I was having this same problem recently as well. It happened on two separate occasions with about a week in between. The first time it came back after a few battery pulls and attempts to boot to recovery as well as download mode. The second time I fiddled with it for about an hour with numerous battery pulls and attempts to boot to recovery and download mode. I even swapped batteries to no avail. I don't know why exactly it finally decided to boot, but I haven't had an issue with it since. Maybe keep trying and hope for the best?

Can you boot and stay into recovery or download mode?
If not, then it very well might be a button issue. Have the phone checked out or you can do it yourself with a voltmeter if you have the knowledge and tech. Otherwise take it to a professional. I paid around 15$ to a button replaced. Which kinda seems a lot, considering a set of 4 buttons costs about 5$ and then you can do it yourself since it doesn't appear to be that hard, especially if you've done soldering before.

Droid/Milestone 2 does not power up

Hello.
This is a long shot, but i'm going to ask it anyway...
Some years ago I owned a Droid/Milestone 2, that decided to die apparently.
After a bit of searching, I decided to purchase the XT1058 I currently use and forgot about the droid.
But I've found it again lying around, and tried to start it with no success...
On its finals days, if for some reason you needed to reboot the phone, it would take some minutes for it to power up again. Once it was up and running, it was just fine.
Until some day, minutes became hours, hours into days, and the phone never worked again. While it was in this state, nothing appeared on the screen.
It was just dead... And then, after a minute or so, after pressing the power button, it would boot up and everything would be ok.... until the next reboot at least...
Now, if I connect it to the USB port, the white led on the side stays on. It's not recognized by windows nor RSD, but if you leave it like that, Windows makes the sound of an USB device connection, a few seconds pass and the sound of usb desconnection appears. So there seems to be a bit of life (not much)
I cannot charge the battery because when I connect the charger, white led by the charging port is not on.
It only stays on if I remove the jack just a bit, so it's not fully seated. I do not think it's battery related since when it died I tried different batteries...
Holding the power button does not do anything...
Question is, do you see any hope on this enterprise?. Idea would be to have this as a backup...
Or should I just throw it away?.
Thanks in advance.

Help! Essential PH-1 no longer powers on?

Essential PH-1 has continued to be my daily driver for almost 5 years now.
I haven't backed up the data, not even to GDrive. Yes, quite dumb. I finally found time to start to look into backing up recently, with the ADB route.
For the past 2 or 3 years, rebooting was problematic where it'd take 5+ minutes or required pressing the Power button down for a second buzz from off state, releasing it only when the animation with small circles would start. It'd then boot up to completion.
Recently, after fully charging and booting up from off state, it started showing new symptom where it'd be stuck indefinitely the Essential logo splash screen. At that time, I was still able to go into bootloader/recovery menu.
I rebooted and let it continue stuck on the Essential logo, hoping maybe it'd just take longer. After an hour, I forced it to shut down and rebooted again and put it aside to wait for it.
Within less than 2 hours, I noticed the display went blank/black.
After that, regardless of how long I press the Power button, the phone would never wake up anymore.
Plugging in the Essential OEM power adapter also does not even show the LED turning on. Can't tell if the USB port was busted or not but would be surprised if it did as charging and data transfer had always gone through a magnetic plug that's permanently plugged-in to the USB port.
Bootloader was never unlocked and, as such, also never attempted to gain root access to Android.
It was running the official Android 10 ROM from February 2020 (?).
There was no smoke or any unusual smell.
1. Is this a known/previously reported problem? I'd like to read on what others who experienced the same may have tried to resurrect.
2. If, let us say, the problem is actually with the battery, would the phone not show any signs of life when plugged-in to power adapter?
3. What are the chances some other electronics may either have slowly deteriorated or have gotten fried inside that casing?
4. If it's never powering back on, are there instructions on how to de-solder the internal storage component to try to recover the data?
5. What other possibilities can cause an Android device to not even show any signs of life?
6. Any other ideas?
Appreciate help from the community, including any pointers even if referring to a different Android device.