Well, I was using NVFlash to go back to 2.2.2 WiFi from 3.2, and during the process, the screen went white. When I unplugged it, the white screen was gone, but now, I can't turn it on. Not even into CWM. When holding down the power button, the charging light flashes 3 times, and it won't turn on. Any ideas what could be causing this and how to fix it?
EDIT: Tried it again. The screen goes white while flashing p11. If that helps at all...but I don't think it will. I've also tried flashing 3.1 RC3, and I get the same "Flashing light" problem.
EDIT 2: Wow...flashing battery light. I'm guessing it might just be dead. I'm gonna recharge it and try flashing again and see if that help.
EDIT OF DOOM: And...whatever I try, I get "Error Mounting /data" and stuck at the Dell logo.
the 3 flashes does indicate low battery. If it's completely dead, it won't boot, even hooked up to a charger.
Ok, I charged it up, but can't boot CWM. I've heard the 3.2 flash replaces it, so I tried to install it through rom manager, which says it installed, but I still get 3 flashes when I try to boot into recovery.
Ok, I got recovery working. Does anyone know where I can find update.pkg for the WiFi version? I already have the image files for the WiFi only version, but not the update.pkg
Related
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
since you have tried a lot of things already, you may need to flash the rc29 image in bootloader and re-root your phone, if it still will not work after the rc29 flash, then it is hardware related altogether.
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
themoebius said:
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
Click to expand...
Click to collapse
to unroot you flash the DREAIMG.nbh file because it will overwrite everything.
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
Try adb, USB debugging is usually on with these modded ROMs. See if you can get a logcat to someone who is much more knowledgeable.
Hold on...not to call you out, but im pretty sure cm 4.1.999 HAS NOT been out for 2 weeks...please clarify...did you flash the newest update THEN had problems?
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
I am having the EXACT same problem with CM4.2.4. I certainly hope its not hardware, but it sure "feels" like it. Especially when my G1 is even shutting down from the Recovery Menu. I'll try to unroot and see if that resuscitates it.
Another one....
Have a look at my current issue on this thread: http://forum.xda-developers.com/showthread.php?t=582576. Check to see in bootloader mode what your board type is (it states it at the top for those who don't know).
Mine is currently showing an EVT board, which doesn't exist. I've pulled the battery out and am leaving it for a while. It could be a hardware issue, but I'm not sure. I was having the "fading screen" issue and eventually got back to RC7 (when I could get into recovery).
Which recovery are you using?
Very strange problem..
Running King's Eris2G1 ROM (latest). Been running it for quite sometime without problems. However, just a few hours ago, it refused to wake up when I hit the 'menu' key. It would vibrate when I got a message, etc, but wouldn't wake up. I managed to get it to respond once, and then it did it again.
So I rebooted, and I get a blank screen. No G1 logo, nothing. Try to boot into recovery and fastboot, again, nothing. Pull the battery and try again, eventually get it into recovery, wipe and begin to flash a new ROM and then.. it does it again. And now I'm stuck.
Keep in mind I've changed nothing. It just happened, out of the blue.
I even tried swapping the SD card, to no avail.
Any ideas?
ok so weird problem here..
my NC is fine besides this one problem.
ive rooted with autonooter to 1.0.1
if i turn my NC completely off and leave it all night, when i wake up in the morning it gets stuck on the "touch of... " screen. The only way to get past this is to reboot to recovery and select reboot..
any idea why this happens? if i just restart the NC, or just let it go to sleep this doesnt happen, only when its been fully off for a couple hours.
ive tried reverting to stock/rerooted all that to fix it, but nothing seems to work.
i know i can just let it sleep and problem solved, but id like to know why this happens or if anyone experienced anything like this before.. thanks!
Try holding down the "n" button while turning on the unit...
Other wise you might have messed up your boot partition, go to development and search for samelhaff's thread on a flashable zip where you can fix the boot.
it reboots to recovery (power+n) just fine... just doesnt reboot normally (just pressing n) .. gets stuck on touch of.. screen
after getting into CWR and selecting reboot it then boots up correctly..
dont know why it just wont reboot normally to begin with.
Same problem here.
After some testing with HC and CM7 roms i recovered to the 1.0.1 Eclair rooted with autonooter version. I turn it off and on some times and everything worked allright. Left it all night off and when i turn it on in the morning i was stuck at the "Touch the future...".
I flashed the stock boot repartition and it started normaly.
Yesterday i flashed the custom Froyo 0.6.8 and everything was allright untill the morning when i stuck again athe " touch..." screen.
I booted with CW and rebooted normally.
Same thing has happened to me twice. I've only been able to get it to boot by booting from my bootable cwr and selecting restart.
Also been noticing some oddities with it charging fully, sometimes while plugged in the status is simply "not charging", not "charging" or "dischargin" and the N symbol on the end of the cable is yellow, not green.
Now it's even worst. Every time i try to boot i get stuck in the "Touch..." screen and i can only boot through CW recovery.
Any ideas?
Glad I finally found some people with the same problem
So initially I took my stock nook (1.0.1) and ran autonooter. Worked great but I noticed it would randomly reboot. Also , same as the other posters, if I powered it all the way down it liked to automatically power up and get stuck on the boot screen. Only way to reset was boot into CWR and select the reboot option from there. I loaded CM7 and same problems so i thought it may be some kind of hardware issue.
Reverted to stock, no problems.
Back to autonooter and this time ran dual boot from EMMC with stock as main partition and HC v4 on second partition. So i don't have CWR anymore but have my SD card handy in case I need it.
Well after a couple days of normal usage the random reboots are gone. Left the unit on during the whole time. Last night I turned it off to apply my Phamtomskin and this morning woke up to find it stuck on the boot screen. Must have been doing that for a while because when i stuck in the SD card for CWR it gave me the low battery warning. After 15 minutes it rebooted to CWR and i was able to reboot normal from there.
Hopefully since a couple of us got the problem we can find some sort of fix. I would like to know if it is some kind of hardware issue or as poster #2 suggested its a simple matter of flashing the boot file. Would I loose my dual boot partition if I flash this zip? Any help appreciated and thanks what a great XDA community.
I think that it has to do with CW and boot. Can i remove CW recovery without affecting my configuration?
no change.
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
bump this?
pilotbluemike said:
im at least relieved that others have this same problem and it isnt a problem with only my NC.
last night i went back to stock, rerooted 1.0.1 and all that jazz and opted NOT to install CWR and power it down over night (thinking maybe clockwork was the problem) ...
well that didnt work b/c this morning it is stuck on the "touch of" screen and worse yet, i obviously cant even boot into recovery to just reboot.
looks like another revert/reroot this morning for me...
very frustrating.
Click to expand...
Click to collapse
Just get the bootable cwr, then you'll always have it handy. The stuck at touch of reading screen has happened to me twice, pulled out my bootable cwr, selected restart and all was well.
I've never heard of anyone having this problem with V 1.0.1. I know that a lot of people are having this same problem with V1.1. Apparently CWR and V1.1 don't coexist well. I had this problem after doing Stock Nook 1.0.1 --> Autonooter 2.12.25 --> Sideload to rooted V1.1. Some people also have the problem when going from stock V1.1 and using Autonooter 3.0. The fix in both cases is to uninstall CWR using the CWR removal tool mentioned here:
androidtablets.net/forum/nook-color-technical/6386-how-installing-using-clockworkmod-rom-manager-nandroid-backup-custom-kernels-20.html#post48469
(sorry, I can't post links yet.) It leaves the device rooted. It worked for me.
So, I was running CM7 no problems. Then one day the ax just fell. I tried re-flashing the ROM and it hangs on the boot animation...so, I removed CWM, made a bootable CWM SD and flashed a few different "return to Stock.zips." One finally worked, but when I connect to Wifi, it says it can't connect and shows that my device doesn't have a serial number or a model number, so I can't get beyond that screen, and it is on version 1.0.1. So I tried using the CWM SD again to update the Firmware. When I did that as soon as I turned on the device, it locked up on a screen that says, "Install Failed, please power Off and the Back on again." So I tried completely wiping and re-installing CM7 to eMMc, and now, again it just hangs on the boot screen.
Oh, and 8 boot interruptions doesn't work for me and when I try holding the power +N keys I go directly into the "Install failed please press off and power back on to try again," screen.
My head is going to explode. Please help. I think my next attempt is going to be trying to flash an alternate kernel.
Use this .zip to get full stock 1.3: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
patruns said:
Use this .zip to get full stock 1.3: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Click to expand...
Click to collapse
Hey I tried this, and when I flash the .zip, as soon as the device powers on it goes straight into the "install failed please turn off device and the turn back on to try again," dialog. On this screen it is black with a white stenciling of the NC. I have grown to despise this screen.
Also, anytime I have tried to factory reset, it goes directly into the install failed screen.
I have managed to get into the stock 1.0.1 homescreen by bypassing the Out of Box Experience, and even when I try to Erase/Deregister there, it stops and says device not registered, and therefore it cannot wipe. Also, when I check device info, every single one has red 000000000.
I suppose that since I'm at least to the homescreens I could try ADB, because it wasn't working either the last two nights.
Also is there anything in the LOST.DIR that could help? What the hell is a LOST.DIR?
So, another interesting thing here...whenever I go to install ADB the softkeys show up in the status bar, like its already rooted and running the stock 1.0.1 launcher bar, as soon as I unplug the USB, they disappear, so I can't even enable debugging.
Also, the NC isn't showing up on the ADB device list.
I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......
Put it in d/l mode and flash one of the stock roms with Heimdall.
D
i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help
Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.
how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode
done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753
Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.