Database Users

[Q] Phone will not charge, can't get past boot screen

I'm using donut with NAND. This morning my phone seemed to have drained the battery overnight, and was completely off. When I plug it in it in the charge light will not come on. The battery has enough juice to almost complete the boot, but always dies just as the lock screen comes up.
I've been trying to search for possible solutions. Some posts seem to say that it is normal for the phone not to charge while off or booting (thought I thought mine did), but I definitely have this now. One suggested going to the coke bootloader screen to charge. this does not work for me. I tied flashing back to WinMo, but my PC can't see the phone through usb. I also tried a hard reset. One suggestion said to have a Verizon store charge the battery. So I guess I'll try that next and report back.
Any help or confirmation that my phone is bricked and I should just give up, is appreciated!

try going into boot loader, you know power+camera+rest button, and let it charge in that for 5 min, then try and boot

Thanks for the suggestion. I did try that and it didn't seem to be working (I didn't see a charge indication led come on). Maybe it is charging and it just does not indicate it? I'll give it a try again. I'm just worried that if I completely drain the battery then I'll have no chance to start it up and charge at all.

nope that killed it alright. guess it wasn't charging after all. Guess my only hope now if Verizon, or finding another working vogue to charge it.
And it still makes me wonder if the not charging problem will remain. If I could only flash back to Winmo. Is there a way to do that without a usb link to the PC?

Flash back windows via sd
copy the nbh file of windows rom to the /sdcard
rename it to VOGUEIMG.nbh
press camera button
connect usb
4 color screen appears
release camera button
press power
restart
connect the phone to power source all the night
flash back android.

The charge light will not come on when in bootloader mode, but I assure you the phone will charge. I plugged it in and put it in bootloader mode for about 20 minutes, then was able to continue.
I had the EXACT same problem a few months ago.
NuAngel

In boot loader mode it doesn't charge, you need to flash windows and then reflash android.

l1q1d said:
In boot loader mode it doesn't charge, you need to flash windows and then reflash android.
Click to expand...
Click to collapse
Again, I've been through this myself. The light may not come on, but the battery DOES charge when in bootloader mode. Please do not misinform. The OP does not have to re-flash - and, in fact, it may be impossible to re-flash without a healthier charge to the battery.
NuAngel

Sure? I test it in polaris and in kaiser and it doesn't charge.
Probably vogue has a different power connection inside.
Good to know

l1q1d said:
Sure? I test it in polaris and in kaiser and it doesn't charge.
Probably vogue has a different power connection inside.
Good to know
Click to expand...
Click to collapse
i have done it too

In my case the phone was not charging in boot loader mode. I let it sit plugged in like that and it completely killed the factory battery as well as my extended one.
I went to Verizon but they said they didn't have a vogue phone anymore and so couldn't charge my battery.
I ordered one of these, but had to wait awhile to get it from Hong Kong. I just got it today and was able to charge my battery, but even after booting into android my phone will not charge the battery its self. I've tried with the AC cord, and usb which I know is a good cord. Maybe something in my phone got fried? I'll try going back to windows next.

My solution (which is using the same phone NuAngel more then likely had an issue with, since he gave it to me) was to go out and get a new battery charger. The chargers connector itself had become worn out. I was able to pickup a fantastic generic Touch/Touch Pro/Touch Pro2 charger at Walmart for $15 or so, Now the phone chargers fine (although it still touchy when flashing via USB).
In short, the USB port is really getting worn out on this thing, but I can still do data at times, even though its not getting a charge (via USB).. its odd at times.

So maybe that's my problem, the usb port has worn out. I can't seem to get a charge or data.
So now I'm having trouble flashing windows from the sd card. I tried to follow the above post:
l1q1d said:
Flash back windows via sd
copy the nbh file of windows rom to the /sdcard
rename it to VOGUEIMG.nbh
press camera button
connect usb
4 color screen appears
release camera button
press power
restart
connect the phone to power source all the night
flash back android.
Click to expand...
Click to collapse
and I found this in another post:
WnG88 said:
If you want to re-flash your nand back to wm, here is the instruction:
1. find your wm rom, it will be the RUU_Singed.nbh
2. copy the RUU_Signed.nbh to SD card as VOGUIMG.nbh, pull the battery, replace, press power and hold camera button and reset hole, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not be finding the VOGUIMG.nbh.
Even simpler:
- put the phone into boot loader mode (power + camera + reset pinhole, you should see the tricolor screen)
- plug into USB of computer
- Flash the windows mobile rom right from windows using whichever rom install file you want.
Click to expand...
Click to collapse
I downloaded NFSFAN's 6.5 in a rar file from here, opened it with 7zip, copied RUU_signed.nbh to the root of the sd card (FAT32), changed the name to VOGUEIMG.nbh .
I assume I can't use any of the instructions that involve the usb port, and I can't figure out if I am supposed to be doing something different with the button holds. I'm just holding power, reset, and camera at boot up to get to the boot loader screen right? After that screen pops up I get a quick flash to a white screen that says something like "Loading... File not found!" then back to the 4 color screen that says Serial.
Can anybody tell me what I'm doing wrong?
Thanks.

The nbh should be renamed to "VOGUIMG.nbh" not "VOGUEIMG.nbh"
However, I am not sure if it will actually help fix your problem.

Thanks for that correction. I was using VOGUEIMG.nbh, but sadly changing it to VOGUIMG.nbh did not seem to fix anything.
Now I found this thread which says to flash from sdcard
egzthunder1 said:
Your SD card has to be:
*Formatted for FAT32
*Be 2GB or less
*Not be SDHC
Simply do what you are doing (rename file and drop in the root of the SD card, put the device in bootloader, and the device takes care of the rest.... it should work.
Good luck!
Click to expand...
Click to collapse
My card is 2 GB so I assume it is not SDHC. The HC stands for High Capacity right? (not Host Controller which shows up in the properties for the card in windows)

I would plug the phone into a wall charger if you are going to use the SD card method. I haven't tired this method, but I would assume it would work best when not plugged in at all, and the battery is +50% charged.
If the phone doesn't have a valid image installed, you should automatically get the three screen on first startup, so there shouldn't be a need to use the key combo. You should only have to pull the battery if you plan on leaving the phone off.

Just to clarify, using the wall charger does not charge my phone, but I did buy an external battery charger, so I can make sure it is above 50%. Also I do have android installed as NAND so the bootloader is not automatically loaded on start up. I have to use the key combo. I'm just trying to flash back to Windows to see if it fixes the usb/charging problem. I've tried a couple of nhb files now in case one was corrupted, but the bootloader still does not see the files as valid. I'm using CoKe 2.31. I'm not sure what else to try.

[Q] Strange problem

As the title says I have a strange yet very annoying problem. I am running my HD2 with hyperdroid cm7 Nand build (from april 29th). The problem is that when my battery is deleted, as is the case now, and I put my hd2 in the charger it will automatically boot. I think this is due to a setting or something. However since booting drains energy faster than the hd2 charges, the phone will by turned of before it has completely booted. After a while it get's stuck in a pattern of starting to boot and turning of. I don't know why this is the case because I think my phone just used to boot fine before when connected to a charger.
So my questions are:
1. does anyone has a suggestion how to turn on the phone?
2. this automatic booting, can it be turned off?
3. Why is it actually happening?
Maybe it's a very stupid or obvious problem, but I hope someone can help me though.

Do you have installed MGLRD?, it's a Known fact, search in the forum for answer (I'm sorry, I'm with SD Builds and don't use MGLRD, so I can not help you anymore).

I had the same problem with some rom i used earlier. The only way i could solve the issue was to remove the battery and put it back, then I could insert the charger without the phone booting up. Charge it for a while and start it.
Hope this way works for u 2.
Sent from my Desire HD using XDA App

I guess this is what I used to do as well. However now, if I remove the battery and put it back in it keeps automatically booting. Also if I put the charger in the phone and then remove the battery same thing happens. But thanks for the help though.

I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.

slbenz said:
I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Well, this cycle I think is caused by the fact that the charger is not strong enough. Normally if plugged in the phone would just boot. The reason that it fails to boot is that is doesn't have enough power to complete the boot cycle even though the phone is plugged in (don't know if booting consumes a lot of power?).
A month ago I bought a new usb cable. Maybe that's where the problem lies? Because I have been using the hyperdroid rom for a while now. Although I don't know if one cable can be stronger than the other.
I have found a solution btw: Though it is a bit hit and miss cause it didn't work a few hours ago. When booting I let it go into mgldr and let it charge there. After a while I'll let it boot when it has enough power to complete the boot.

slbenz said:
Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Humm, now you making me think lol, the 1st time I installed Android on my HTC HD2 was the NexusHd2 rom one and he had the same problem, no battery but once I plug it to the wall charger it would do the full(normal)boot, I thought was the rom so I changed to Hyperdroid Cm7, but, still does the same..
The wipe you talking is the one, wipe data/cache right?

if it happens to you a lot, I think it's time to invest in a third-party battery charger. you can charge it out of the phone for a bit, and then you're safe to put it back in a continue charging using the phone

Tried some different roms and all them do the same.. so I reckon its normal.. Thank You.

Pleaseee help. Big problem. Nook stuck in sleep

Ok this is weird. So my nook color is stuck at the battery too low to power ON screen. I had it rooted to HC installed on my device memory. The nook died completely and now this happened. The weird part about it is this. When i have my sd card in, it boots up just fine to clockwork recovery mode. Without the sd card, it wont boot up. I have tried everything in clockwork. Data wipe, re install, everything. This is really pissing me off.
Btw one more thing. I am using the black plug that goes to the wall that came with the NC but the plug coming out of the black plug is the one for the original Nook.

I've read on the NC info sheets that come on the device and also on the B&N nook forums, you cannot use a charge/usb cable from an original nook on a NC. The two devices use different voltages, and they warn you can damage your battery. You'll need a NC cable.

Plug it in your pc and leave it on for overnight, it takes a few hours to start up with a non stock charger.

What is wrong with my HD2? It would not turn on when on battery power but....

I was trying to delete every files/folders on the SD card while it was still in Android OS and when it was connected to my desktop via usb cable but then when I finished deleting the files/folders and when I take out the battery to reboot the HD2 it would not turn on at all.
Then when I plugged the HD2 into a charging cable via the electrical outlet, the HD2 would turn on at the "Stick Together" logo then turned off after about 3 seconds. It repeats this pattern of turning on and off continuously when the HD2 is plugged in. It would be completely dead and would not turn on if it is disconnected from the outlet and just be on battery power.
How do I fix this? Did I just brinked my HD2? Is there a way to fix this?
Thanks.

i had this happen when my charger cable went bad one night and my phone drained down to nothing. just the boot logo like you described then it reboots.
i hope yours is the same. that the battery has too low a charge to start the phone further.
I let mine charge for a half hour then it worked.
also check to see if the battery terminals are bent a little and not letting the battery charge.
good luck

Earthbrain said:
I was trying to delete every files/folders on the SD card while it was still in Android OS and when it was connected to my desktop via usb cable but then when I finished deleting the files/folders and when I take out the battery to reboot the HD2 it would not turn on at all.
Then when I plugged the HD2 into a charging cable via the electrical outlet, the HD2 would turn on at the "Stick Together" logo then turned off after about 3 seconds. It repeats this pattern of turning on and off continuously when the HD2 is plugged in. It would be completely dead and would not turn on if it is disconnected from the outlet and just be on battery power.
How do I fix this? Did I just brinked my HD2? Is there a way to fix this?
Thanks.
Click to expand...
Click to collapse
Were you running an SD build possibly?
Also as previous poster states check for bent battery pins where all 3 contacts need to be straight in line.
Sent from my HTC HD2 using Tapatalk

It is not the battery problem. I have two HD2 and I can check the battery power. Both batteries is at 100% full charge.
I just don't know how to fix this problem. Please help.
Oh, and yes, I was running the SD build prior to the problem.

Earthbrain said:
It is not the battery problem. I have two HD2 and I can check the battery power. Both batteries is at 100% full charge.
I just don't know how to fix this problem. Please help.
Oh, and yes, I was running the SD build prior to the problem.
Click to expand...
Click to collapse
SD Android should never affect WinMo, but that has to be one of the stupidest things ever. Why on Earth would you delete the files key to the system whilst in Android?

Nigeldg said:
SD Android should never affect WinMo, but that has to be one of the stupidest things ever. Why on Earth would you delete the files key to the system whilst in Android?
Click to expand...
Click to collapse
I did not know that it would mess things up. I thought that WinMo would take over once I take out the battery.
So what happened to WinMo? How come it cannot boot back to WinMo now ?
Any fix for this?

I had the same problem when installed Winmo 7,5. turned on only with cable and restarting every 5 sec.
I took out battery for 10 mins and when plugged in worked normal.(but after every turned off i had to take out the battery) and because of that i turn back to winmo 6.5 and ics android sd card (haret) and until now working perfect.

Earthbrain said:
I did not know that it would mess things up. I thought that WinMo would take over once I take out the battery.
So what happened to WinMo? How come it cannot boot back to WinMo now ?
Any fix for this?
Click to expand...
Click to collapse
Unfortunately I have no clue. I, like you, wouldn't have expected that. Just try re-installing if all else fails I guess. Unless by some miracle it begins working again I would think this would be the only way, sorry
Also try reformatting your SD Card to FAT32 format and see if this has any effect.
boglefkas said:
I had the same problem when installed Winmo 7,5. turned on only with cable and restarting every 5 sec.
I took out battery for 10 mins and when plugged in worked normal.(but after every turned off i had to take out the battery) and because of that i turn back to winmo 6.5 and ics android sd card (haret) and until now working perfect.
Click to expand...
Click to collapse
In this case your issue is normal. Windows Phone (not WinMo which is seriously sh*t but Windows Phone 7.5 which looks to be amazing) runs through MAGLDR which does not support cold charging (charging when phone is off) therefore when plugged in the phone just begins to boot up in order to start charging, but cannot charge until it is booted into the OS and there wasn't sufficient battery to do that, hence the bootloop.

[Q] Battery Not Charging!

I have updated and installed CM 10 with TWRP and JB gapps but my Nook will not charge when powered on. I previously had CM 10 just on the SD card running it from there and thought if I put it directly to the EMMC it would fix it but no luck. Any Ideas?

scott6779 said:
I have updated and installed CM 10 with TWRP and JB gapps but my Nook will not charge when powered on. I previously had CM 10 just on the SD card running it from there and thought if I put it directly to the EMMC it would fix it but no luck. Any Ideas?
Click to expand...
Click to collapse
Are you using the stock BN charger and cable? If so does the n light up when plugged in?

hwong96 said:
Are you using the stock BN charger and cable? If so does the n light up when plugged in?
Click to expand...
Click to collapse
Yeah I am. It charges when completely off, but not at all when on.

scott6779 said:
Yeah I am. It charges when completely off, but not at all when on.
Click to expand...
Click to collapse
What CM10 version did you install? It seems the charging signal vbus is not turning on when your Nook is on or in sleep mode. Another app may be interfering with the charging function.

same exact issue I am having. I've tried many CM10 builds, paranoid android which I know is CM10 based, but it wont charge with the stock charger setup unless I turn the nook off. also having issues with win7/win8 not recongnizing in any fashion my nook when I connect it. I followed install steps 100% too.

so does anyone have an update on this problem or what to check or look into? no matter what nightly I flash it will not charge while powered on. if I power it down it charges just fine. this is using the stock charger, though using a normal microusb cable charges the unit fine on or off. if I flash stock 1.4.3 software charging while on works just fine. this is driving me crazy.

corporal_hades said:
so does anyone have an update on this problem or what to check or look into? no matter what nightly I flash it will not charge while powered on. if I power it down it charges just fine. this is using the stock charger, though using a normal microusb cable charges the unit fine on or off. if I flash stock 1.4.3 software charging while on works just fine. this is driving me crazy.
Click to expand...
Click to collapse
How do you know it is not charging? The color of the lights, or are you counting on some software to tell you.
Sent from my Nook HD+ Running CM10

corporal_hades said:
so does anyone have an update on this problem or what to check or look into? no matter what nightly I flash it will not charge while powered on. if I power it down it charges just fine. this is using the stock charger, though using a normal microusb cable charges the unit fine on or off. if I flash stock 1.4.3 software charging while on works just fine. this is driving me crazy.
Click to expand...
Click to collapse
Were you on CM7.x using Nook Tweaks host mode (not host/vbus mode) prior to CM10?

I know its not charging because one, the light stays green and does not change to orange, but two I go into battery in settings and it shows no charge taking place. If I plugin a regular microusb cable though it does show a charge taking place. As for CM7 and Nook Tweaks, no I was originally on stock 1.4.3 software and used manualnooter to root and get CM10 installed and had the same problem. I then proceeded to try out paranoid android which I know is based on CM10, then I tried a couple different CM7 roms but went back to CM10.

corporal_hades said:
I know its not charging because one, the light stays green and does not change to orange, but two I go into battery in settings and it shows no charge taking place. If I plugin a regular microusb cable though it does show a charge taking place. As for CM7 and Nook Tweaks, no I was originally on stock 1.4.3 software and used manualnooter to root and get CM10 installed and had the same problem. I then proceeded to try out paranoid android which I know is based on CM10, then I tried a couple different CM7 roms but went back to CM10.
Click to expand...
Click to collapse
You need to get some better software to tell you exactly what is happening.There are lots of them out there, some free and some paid. What you want is an app that tells you how you are connected, USB charging mode or AC adapter.
I use a paid app, Battery Monitor Widget Pro. It tells you how it is connected and the net current draw or charge rate.
Sent from my Nook HD+ Running CM10

As I've said in another thread regarding charging on CM10 based ROMs... I am having the same issue and am trying different configurations to narrow down the cause.
I currently have CM7.2 on SD... CM10 on eMMC... when booted to CM7 charges fine... prior to CM10 on eMMC stock would charge fine as well....
When I am booted to CM10 the light is green and displays discharging on lock screen... and in fact does discharge the battery... as soon as it goes dead... the light turns green.
When booting up... the ligh stays orange... right up until I choose eMMC Normal from Cyanoboot menu... as soon as it starts to boot CM10... green light and no charging. Using USB (non-nook cable... car charger... etc) it charges even in CM10, even shows charging on lock screen... and battery level does increase if I leave the screen off.
Software to tell how its connected is not necessary atm. And as I stated in the other thread... I cannot blatently state it is the ROMs fault at this time... I have too complex of a configuration to rule out other possible causes. But have no solution as of yet.

leapinlar said:
You need to get some better software to tell you exactly what is happening.There are lots of them out there, some free and some paid. What you want is an app that tells you how you are connected, USB charging mode or AC adapter.
I use a paid app, Battery Monitor Widget Pro. It tells you how it is connected and the net current draw or charge rate.
Sent from my Nook HD+ Running CM10
Click to expand...
Click to collapse
My battery charges very slowly. I'm using the factory nook cable and charger, CM7.2, light is orange while charging, charges all day and I get 2% charge increase. Currently at 12% charge, battery monitor widget needs at least 40% to work. Battery might have died, but then it's had a relatively short life if that's the case.
Edit: No idea what the problem is, but the solution is to plugin in the power cable, and then turn off the Nook. Charges rapidly as normal.

cm10 help needed
leapinlar said:
How do you know it is not charging? The color of the lights, or are you counting on some software to tell you.
Sent from my Nook HD+ Running CM10
Click to expand...
Click to collapse
bro i need ur help plz help me.....:crying::crying::crying::crying:
---------- Post added at 04:31 AM ---------- Previous post was at 04:30 AM ----------
DizzyDen said:
As I've said in another thread regarding charging on CM10 based ROMs... I am having the same issue and am trying different configurations to narrow down the cause.
I currently have CM7.2 on SD... CM10 on eMMC... when booted to CM7 charges fine... prior to CM10 on eMMC stock would charge fine as well....
When I am booted to CM10 the light is green and displays discharging on lock screen... and in fact does discharge the battery... as soon as it goes dead... the light turns green.
When booting up... the ligh stays orange... right up until I choose eMMC Normal from Cyanoboot menu... as soon as it starts to boot CM10... green light and no charging. Using USB (non-nook cable... car charger... etc) it charges even in CM10, even shows charging on lock screen... and battery level does increase if I leave the screen off.
Software to tell how its connected is not necessary atm. And as I stated in the other thread... I cannot blatently state it is the ROMs fault at this time... I have too complex of a configuration to rule out other possible causes. But have no solution as of yet.
Click to expand...
Click to collapse
need help