A few days ago i looked at my phone and it was powered off, when i powered on it had the asus logo and a small yellow message in the top left corner that said something along the lines of the rom is corrupt (i cant remember exactly). I then did a hard reset and when powered on again it said the same message. I then plugged it into power supply, the red led came on to indicate it was charging and i went about my business. Then yesterday i looked at my phone and the led was still red, i unplugged it for a moment then plugged it back in but the led did not light up. I then tried to power on but there is no response, at this point i would assume it is hard bricked but i decided to plug it into my computer. At the point of plugging it into my computer a quick succession of windows opened up all saying "you need to format the disk in drive (I through to Z): before you can use it", it also showed all of these as local disk (I through to Z) on "this PC" in windows explorer, plus a local disk(H entry which states 8.07MB free of 63.9MB. Inside this is 2 files, one named image and one named verinfo, the one named image contains files with extensions B01, B02, B03 ETC and MDT files. also if i hold the power button whilst plugged into the computer it registers the device as connecting and disconnecting. I have spent a few hours going through the posts on this and other forums but could not find any posts that describe this set of circumstance. Thanks!
Now, the phone won't power on?
Related
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
So I was donated a Droid 2 as the original owner claimed it wont turn on and so must be dead. I happily took it hoping I may be able to revive it.
Quick rundown:
- No indication of water damage ie the watermark stickers have not changed
- Wont turn on, even when replacing with a Droid 1 battery (they are the same, i checked)
- Does not seem to hold a charge (via usb computer), however I can get the charge "white" light to come on, sometimes this happens, sometimes it doesnt...
- Pressing and holding "X" while powering had no effect
- I do not have an actual wall charger but will order one based on what I discovered below...
-Something interesting happens when I have it plugged to my pc AND I am able to get the white charge light to come on. If I quickly press the power button a few times (not pressing and holding mind you), my computer makes an error tone which it usually makes when it detects hardware improperly. I did it again while I had Device Manager on and sure enough, after the error tone started on the computer the words "OMAP 3630" popped up in my list of devices (under "Other Devices" category) and then disappeared.
This gives me hope that this device is salvageable! I read around and it seems like charging these moto devices with their own motorola wall charger (not usb) seems to help charge the device when its not charging so I went ahead and ordered one online which will arrive next week.
So what are your thoughts? Has anyone gotten OMAP 3630 to show up in their device manager? Am I wasting my time? Is there hope that this device can be resurrected?
Any assistance is appreciated
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.
Hiya,
So my colleague gave me an USB stick for me to copy some photos on to, and it seemed to of killed my N7.
Here's how it all went down:
I have an Intel MBP and when I plugged the USB drive in, it didn't recognise it (it didn't even show up in the Disk Utilities). And yes, it was directly connected to my laptop, no USB hubs involved.
I tried even the other USB port, and even with a USB hub, no difference.
I've installed a program to write onto NTFS formatted drives, and OS X natively can read just about all the Windows file formats (in my experience any way). And so, just for the giggles, I popped the drive into my updated and rooted N7 via a Motorola USB OTG cable (which has worked for a long time and no flaws) and then my N7 could read it. No worries.
I copy all of files into a separate folder on the drive, and then pop it back into my MBP. It then detects it. Very strange. I copy over some files, and unplug. Later on in the day, I remember that I forgot some files, so I plug it back in, and my laptop starts going into some crazy lag mode as if it just got Parkinson's. Unplug the drive, and then it freezes (i have to do a force shut down) and when it boots back up, it's seriously FUBAR'd.
I felt the drive belonged in the pits of Mordor with what havoc it was causing.
I didn't plug it back into anything else after that. Told my colleague and he did a virus scan on his Windows work comp: nothing.
Battery dies on the N7 (ie, ran out), and when I go to charge it. Nothing. Okay, something happens. The backlight goes on, but no battery symbol. Just see some sort of light leek (which I had before, but nothing dier.)
It's a 32GB CC0K "generation".
Any clues, tips?
Thanks for any and all help!
TL;DR version:
A) Big long story about MacBook Pro and a wonky USB drive.
B) Separately, "Battery dies on the N7 (ie, ran out)", N7 won't start up.
Not clear from story if (A) has anything at all to do with (B).
Try charging battery for a while? Hold Power button down for 20 seconds afterward? If not, unplug battery connector, wait 10 seconds, plug it back in, charge device, try to reboot?
There have been a number of similar sounding stories on here. Some of them seem to self-resolve after charging, some of them are reported to respond to various voodoo operations (e.g. battery disconnect/reconnect), some of them the person making the report never checks in again. I suppose that leaves open the possibility that some devices never turn back on?
It isn't obvious if there is a single syndrome or mutiple problems that exhibit similar symptoms.
good luck.
Thank you for shortening it!
I tend to go a bit overboard with details and what not.
Ok, will try having it in the charger and see what happens.
Thanks!
I also find it strange that a USB drive could be so destructive. However, if you do have a wonky USB drive, what chance of is there for its faultiness doing harm like I just described?
Don't forget to make sure the internal battery lead isn't disconnected!!! It happens..
Ok, plugged it, it sat in for a while, held the power button for a few seconds longer (along with the bottom volume rocker) and it turned on!
So, thanks for the help!
Must be the 100th time I've read about grouper's funny little "death" because of drained battery. Hasn't happened to me but if it ever does I'm prepared and properly informed lol
Sent from my Nexus 7 using XDA Premium HD app
My tablet had 55% power at night WiFi/BT off and on sleep I woke up and it was so dead it wouldn't even turn on. Just glitches here and there with the battry
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2
Hi! I have a Sony Xperia X Compact, all stock... about 5 months old.
It began a few months ago; my phone would charge, but it would not be recognized by the computer. I couldn't browse the memory card etc. from the computer it was connected to. It did however charge.
Yesterday I was at a hospital, and by the time I got home, my phone had died. The last time I looked at my phone before it died, I saw a notification about an Android update.
When I got home, I connected the charger directly into the wall. however, nothing happened. I saw the red light, and it suddenly switched to green, then back to red again. Not blinking light..it's rocksteady.
After an hour or so, I tried starting my phone, but it wouldn't even vibrate. So I plugged it into my stationary computer, which told me it had only identified an "unknown device". I tried updating the drivers, but it said it had the newest ones. I tried a different computer, but same thing there. I even tried my linux server and my PS4. But still no go.
If I hold vol up + power, it vibrates once and the blue light begins to shine, but nothing more happens. If I hold the same keys further, it vibrates thrice and goes back to red + green.
I've been trying all different power supplies for hours, but it's stone dead.
I'd really appreciate any help!
I have the same problem
Were you able to solve it?