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
Related
For the last week I've been forced to a life without my G1. This is the situation:
My phone wont boot. Not normally, not into safe mode (Menu+Power), not into Recovery Mode (Home+Power), not into the bootloader (Camera+Power). Whichever I try it just gives me a buzz and a black screen with backlight on. To power off I have to remove the battery.
Is there a way to bring this device back to life? Any hints are welcome!
Background:
My phone is bought from the US on Ebay (I live in Sweden, Europe) in November. It is not rooted (even if I have thought about rooting it for quite a while), but unlocked and set free from T-mo.
Trouble started when I inserted a new 8GB SD and the phone rang at the exact same time. After that, Android became extremely slow and a touch on the display took several seconds to process. Reboot didn't help, neither did safe mode. Tried with and without SD and/or SIM.
I managed to boot into recovery mode (Home+Power), but couldn't bring up any menu. I had to take out the battery to power off and after that I couldn't boot at all any more (yes, I did put the battery back...). What troubles me most is that I can't even start the bootloader.
Sounds like there is hardware failure, but I could be wrong. Also, can you check to see if the ribbon came lose for the screen? When you have the phone opened look from the bottom of the phone (where you charge) up towards the top and you will see a hole in the screen portion. There should be a ribbon connecting the screen inside this, see if you can make sure it is securely connected.
I'm with Neoobs... Sounds like the screen isn't turning on (you can't power it off without it plugged in).
If the ribbon cable is connected, somehow the screen has been trashed. How or why this occurred when swapping the cards is beyond me. Have you tried to ADB into the phone from your computer?
Was messing around trying to restore the phone back to stock using: [ROM] OFFICIAL T-Mo Vibrant JFD ODIN/Nandroid Backup Images 7/29/10 (Tested/Working)
Odin never got passed file analysis.
Phone showed yellow digger but not progress bar.
I gave up and ended up popping the battery out of the phone. Apparently that is a bad idea.
Now, when I try to power up or even plug in the usb cable, it is displaying a phone on the left, a pc on the right with a caution sign with "!" in between the two.
Any hope for me?
-Greg
Same thing happened to me....."twice" I'm a little more hard headed than most. Anyways, I went back to t-mobile and they exchanged both times - so maybe check that out. I haven't seen anyway yet to get past that "phone > pc" screen.
-Good luck
Wonderful... I got the phone used.
Been playing with it for a while. Trip to the T-mobile store... call to Samsung tech... was looking pretty bleak.
With the screen displaying the phone....pc, it wouldn't do a thing. Plugging in the USB, nothing (no beep beep notification from PC either). This told me for whatever reason, the USB boot loader was failing.
I tried a different approach. Rather than hold vol up and down then power, then connect USB (or USB before the sequence)... I decided to see if plugging in the USB as the power trigger would work. IT DID!!
So, to spell it out. Pull battery to get phone turned off. Put batter back in. No SIM, no SD. Hold vol up and down then plug in USB cable attached to PC. Voiala - Little digging guy ready to flash.
Flashed it with the stock ROM and am golden again.
-Greg
Greg you are a life saver. Thanks! Worked for me!
If it will do anything you can bring it back to life... a true brick wont do anything... wont even show the battery status when plugged in...
Sent from my T-Mobile myTouch 3G Slide using XDA App
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.
Had my N7 for well over a year, rooted, unlocked bootloader, all of a sudden it wont turn on... If I plug it in I get a blue screen, unplugged nothing..
Any Idea's out there?
mojimmy said:
Had my N7 for well over a year, rooted, unlocked bootloader, all of a sudden it wont turn on... If I plug it in I get a blue screen, unplugged nothing..
Any Idea's out there?
Click to expand...
Click to collapse
Try opening the back panel of your nexus and unplug and replug the battery.
Leonhan said:
Try opening the back panel of your nexus and unplug and replug the battery.
Click to expand...
Click to collapse
That did it...I usually just thump it on the side and it works...N7 flaw, thanks for your help..
I was reimaging my device from 4.4 back to 4.3 (since Kit Kit broke flash videos). Stupid me, I told it NOT to wipe my user data (even though I backed everything up, including the internal storage device). When it rebooted, the X logo was there, but it never would boot up. I'm assuming because it was because I should have wiped data. Oh, and it was fully charged before I did the reimage to 4.3.
Well, I tried to reboot it (did the reset) to try and get into the bootloader which I did. I wipe the cache only and then rebooted and that was it. Blank screen and nothing else. I can't tell if it's turned on or off. Plugging the charger into the wall outlet doesn't elicit any type of response on the screen. Usually, the screen turns on if it's already on or else, if it's off, you get the battery icon. Neither one happens.
The screen is blank (even when I press and hold power+vol up+vol down. I've hooked it up to the PC to see if I could hear at least the sound when it powers down on the reset and it does indeed do that. Then, it connects and then I get a different sound and the PC says it cannot identify the USB device connected when before all of this happened, it was working just fine (had to since I JUST used the N7 tools to flash back to 4.3).
I've also left it hooked up to the original wall charger for over an hour and nothing. Screen is still blank and never comes on no matter what I do.
I've also opened the back up (hopefully they can't tell if I've done this or not) and unplugged the batter, waited and plugged it back in. Still nothing.
I've uninstalled all the drivers, rebooted and tried it again. After it installed the drivers, still the same issue. It worked for almost a year. Luckily, I purchased the N7 on January of 2013, so I'm still under warranty.
Here's the problem: I unlocked the bootloader. Will this void the warranty? Am I hosed if I try to RMA it? I cannot get connected back to to an fastboot oem lock on it. N7 toolkit is useless (well, NOW it is since I have a non-functioning device), so I cannot do anything there.
I'm just trying to see if there is anything else I can do or is the N7 fubar'd? If so, does this mean they won't be able to keep my data (which is fine by me)? I would hate for them to boot it up and see the unlocked icon on the screen and then come back at me for money.
Okay so here's the story.
I was running pacman 4.3 nightly roms on my tablet.
At some points id have this weird issue where out of nowhere I would start bootlooping (and bc of some weird issue i couldnt boot into recovery from the bootloader unless i was plugged in to a pc. idk it was weird. the bootloader was like 3.13 or whatever)
anyway, yesterday my battery drained completetly and I would do what I would normally do, plug in to my pc, boot into the bootloader, boot into recovery and let it charge a little bit, then i would reboot into the system. but this time it would die during the splashscreen, so that was weird. Anyway, I eventually got it past the splashcreen onto my homescreen and my battery was apparently at 0 percent and then it would just die even tho I was plugged in.
i could leave my tablet in recovery for a while without being plugged in which was weird.
Anyway I tried flashing a newbootloader. 4.23 or something and it successfully flashed, now it wont boot up. fancy paperweight in my hands lol
lsusb command on my linuxbox gives me nothing. RIP nexus7, its been real.
oh and i did everything through adb
and before it died, whenever i plugged it in to usb or my power adapter, some strange sounds came from inside the tablet, like static lol
update, i had it plugged in and not even the charging screen was coming up so i was just there holding the power and volume buttons then the charging screen came up and went away. hmmmmm
The usb cable works fine for file transfers/being detected on my linuxbox on my s3 and evo so its not the port or cable
another update.
charging screen now comes up and stays on for a while. guess its an issue with a port on the tablet, but whenever i power it on or try to get to the bootloader the screen goes black for a second then back to the charging screen. so Im guessing this tablet is done for and shouldnt bother trying to fix the port?
deleted.
Is it still under warranty (less than a year old from when you purchased it)? If so, RMA the sucker. That's what I did and they replaced the motherboard for me.