I have tried every forum and every article's tips on how to root and NOTHING is working. I have cupcake. I have formatted my SD card using a reader because when I try to mount it using the phone it unmounted. I installed the program onto the SD card and powered it down. I hold down the camera button and hit power. The screen with the 3 colors comes up and just stays there doing nothing. Am I just not waiting long enough for the gray screen?
PLEASE HELP!
fro0tlo0p said:
I have tried every forum and every article's tips on how to root and NOTHING is working. I have cupcake. I have formatted my SD card using a reader because when I try to mount it using the phone it unmounted. I installed the program onto the SD card and powered it down. I hold down the camera button and hit power. The screen with the 3 colors comes up and just stays there doing nothing. Am I just not waiting long enough for the gray screen?
PLEASE HELP!
Click to expand...
Click to collapse
The screen you want for flashing is the one with the exclamation mark, activated by holding down HOME + POWER, you then press alt+l to display the log or whatever. How far did you get in the process anyway, my info kinda relys on what uve given me
fro0tlo0p said:
I have tried every forum and every article's tips on how to root and NOTHING is working. I have cupcake. I have formatted my SD card using a reader because when I try to mount it using the phone it unmounted. I installed the program onto the SD card and powered it down. I hold down the camera button and hit power. The screen with the 3 colors comes up and just stays there doing nothing. Am I just not waiting long enough for the gray screen?
PLEASE HELP!
Click to expand...
Click to collapse
Oh sorry (ignore my old post) here is a good link, start from
Before We Begin on the page http://wiki.allshadow.com/index.php/G1_Root, and make sure you are on RC7 or RC9 first. You need the DREAMIMG.nbh file in the root of your memory stick
keemyb said:
Oh sorry (ignore my old post) here is a good link, start from
Before We Begin on the page http://wiki.allshadow.com/index.php/G1_Root, and make sure you are on RC7 or RC9 first. You need the DREAMIMG.nbh file in the root of your memory stick
Click to expand...
Click to collapse
Make sure your card is formatted to fat32. Make sure the file is DREAIMG.nbh and not DREAMIMG.nbh. Boot up by holding camera + power. If it doesn't boot right then redownload the DREAIMG.nbh file, could of been a bad download.
version I535 wont root or do any thin else help please. 4.4.3 kit cat yuk
I have a version Samsung galaxy S III I535 android version 4.4.3. I do not really care for Kit cat and wanted to root it like I did my girl friends. I have spent more then a month pouring over this site mostly this but others, I have tried a ton of programs with Odin, following directions to the letter. I still can not get the thing unlocked. Every program that says install with Odin fails The ones that say put it on your SD card go there but they wont install fully. hard to read fully but it says something about wrong or bad signature then more yellow letters follby more re and it quits and leave me a dead screen. So far I have gotten lucky, the only that has quite working is 4G and it does' n even show there is a router in the house so The tcpip is probably shot. Please folk Im begging for are some help my ST card runs out in two days and they are 45 dollars a piece. so hit me with the instructs, or constructive criticism. I am new to this Ive done it in a very old phone with CW on it so it was easy please from a desperate man how to get this thing to unlocked so I can rom it and put in ST card. And before anybody *****es about ST they have been great to me and mine.
Sure I went to version (worst mistake of my life except getting married,) like being married its great at the beginning then you get that first bill then it doesn't seem like a good idea for a while but after being lied to and having to pay $290.49 I gathered there crap brought it back to a version store and dumped it. The phone is mine I bought it from gur who fixes and resells phones. I have bought several phones from him both personal and to resell he does wonderful work but he is on vacation for 3 more weeks out west camping and
My phone did work great till I finger into it lol.
If some one has the time to speak English instead of android that would be even better. Please remember I am a phone retard so use small words and please oh please point me to software the will not fail while Odin is passing it to the phone, or off the sd card
Sincerely
Dan.
Sounds like you can use towelroot
http://forum.xda-developers.com/showthread.php?t=2784249
Look through this thread (page 6 and 7 seem like its been shown working)
If you have further questions ask there as they will be able to help you more than those of us watching the g1 forum
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
I rooted and installed Fresh rom on my Sprint Hero. Everything was working properly except the ability to move to the sd card. I then partitioned the sd card and rebooted the phone. Now its stuck on the Fresh rom loadup screen. Cannot press home and menu to restart. I took out the sd card put it in my computer, formatted it again and reloaded the Fresh Rom onto it and loaded it into my phone. Still stuck on Fresh rom loadup screen. Can anyone save my phone.
HHow long have you been waiting to let it load? once the files are writen and the rom is flashed the SD card stuff shouldnt even matter.
It took 20+ minutes for the first load of a new rom with a new framework every time I have done it. Try rebooting, waiting a little bit (30ish minutes) and if there is still no change, come back and see if you cant analyze the problem further
I let it load overnight, about 4 hours or so and it is still stuck on the loadup screen. The Fresh Rom screen has the animation and the sound effect but won't go past that screen.
I have no idea what I did but I got it reboot and everything is work as it should. Thank you for your reply and your help.
1st Question, Did You Make A Nandroid Backup? If So, Your Good... Just Pull The Battery Out, Put It Back In, & Turn It Back On Holding The Volume Down Button, Once You Have The Option, Press The Home Button To Access The Recovery Menu, Where You Can Nandroid/Restore Back To Your Previous Working (Rom) Phone!!
Sent from my HERO200 using XDA App
Completely irrelevant question:
The title of the post reads, "Newbie need help saving her Hero." Her = female.
But, your username is "dadof3". Dad = male.
So, what are you?
I'll have to ask the same question.reread op and now confusion is bubbling thru what little gray matter I have left.
c00ller said:
Completely irrelevant question:
The title of the post reads, "Newbie need help saving her Hero." Her = female.
But, your username is "dadof3". Dad = male.
So, what are you?
Click to expand...
Click to collapse
Sent from my HERO200 using XDA App
Guys its the internet. its also a tech board... think about it
Would you have a better chance of getting help if people thought you were a female, or a male?
I'd bet those with the double x chromosome will tend to have a slight advantage over their male counterparts. Seeing as I'm guessing the majority of users here are guys. Call it white knighting, chivalry or w/e you choose, it happens
edit: I'm not saying the OP is either one.. or neither for that matter merely pointing out a possibility of the why there's inconsistency
As we know, the Nook Color's SD slot will always take first boot priority. I'm in a situation where even booting via SD through known methods are not working.
The purpose of this thread is to:
1) Share with others who are in this similar situation, on methods which may result in the recovery of their own devices
2) Keep this discussion healthy so one day, I will be able to restore my own bricked device which I'm still striving hard to.
Click to expand...
Click to collapse
IMPORTANT: If you have a bricked device I need to emphasize on searching and reading very carefully what others have shared here in both General and in Development. This is a fundamental requirement, as with the ability to follow instructions and not panic by creating unnecessary threads. This will only make things harder to find, so thank you in advance for not doing that.
There are many useful guides out there, some of which the most helpful are:
Nook Color Restore to stock by samuelhalff
Dummies Guide to Fixing 'My Nook Won't Boot' by RileyGrant
Stock 1.1.0 Clockwork Recovery Image by brianf21
Nook 1.01 stock dd images by shad0wf0x
[RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD by thecubed
Click to expand...
Click to collapse
Anyway, in severe bricking cases where hardware is not at fault, many of the solutions to restore the NC begins with either:
1) Booting to CWR-SD via uSD
2) Booting to a rom i.e. Nookie Froyo via uSD
3) Having ADB access, if available
Till date I am not sure why the SD-loaded programs do not work for me, and here are the symptoms:
1) Without SD inserted, the standard BN splash appears, 'Welcome to the Future of Reading', then gets stuck there till powered down. Needless to say, the 8-times reset method doesn't work.
2) With SD inserted, the 'LOADING' screen will splash, then screen blacks out with device still powered on . You will know that the device is still running as you need to hold power down for around 20 secs before you're able to power it back up again. I call this the 'Black Screen of Death'.
Click to expand...
Click to collapse
To get your device up and running, try the following:
0) Do not panic. As long there's no hardware failure there will always be a solution. Look at me, thing's still a damn brick and yet here I am, still hopeful
1) Perform a search, read the useful threads created by the above members first. This thread is related only to failed SD-booting.
Once you've done that, prepare your recovery options with these in mind. The elimination process is part and parcel of problem-solving. In no particular order:
2) Sometimes, try powering on your device by connecting the USB cable from your PC or A/C source, instead of using the Power button.
3) Use only the original USB cable that came with your device.
4) Use the back USB ports of your PC, instead of the fronts as they may provide more consistent power and connection to your device. Try to avoid using USB hubs as they may not distribute the required power equally/properly.
5) Try switching to different USB ports, some may be hardware-gimped due to wear-and-tear.
6) Try to attempt the recovery on another Win, Mac or Linux computer. At least eliminate further possibilities of environmental hardware error.
7) Try charging the battery full.
8) Or, try discharging the battery completely, by leaving the device in BSOD state overnight until you get a message saying your device can't boot due to insufficient power when switched on. Once you are in this state, keep booting the device up until the screen does not appear. Then, recharge it back to full to see if the OS returns to stock (I am sceptical of this, but this was what others advised).
9) Try different SD cards. The device could be picky. Variety should be by class-type, brand, SDHC or non-SDHC. It's been discussed that faster cards perform better, as with more reknowned brands. Also, 16GB cards reportedly do not run Froyo (do read more by searching).
10) When loading anything via SD (CWR, roms), try different button combinations i.e. power + n + up, power + n, etc.
11) And/or, hold power for various timed-presses i.e. >30 / 45 / 60 seconds. Some members report CWR booting up after these periods, or even longer.
Note: funnily I tried holding power + n + up for > 60 seconds and the 'LOADING' screen just stays frozen. Still doesn't work, and I didn't get any ADB access.
12) Try formatting the card completely with native Win/Linux tools, EASEUS Partition Master or SDFormatter before each burn.
13) Try using both Win32DiskImager and WinImage, or dd-ing in Linux (search for more instructions). If you have Linux, you can check to see if the SD's /boot partition is indeed bootable or not.
14) For ADB access, try to unregister your hardware (go to Start > Run > devmgmt.msc), then unplug-replug device to have your PC detect it again. If a device with VID of 2080 shows up, that's the NC. You should know what this means, by now. If not, read more here.
15) Try different SD card readers, especially when experiencing failure on multiple computers. As opposed to multi-adapters i.e. 6-in-1s, try dedicated microSD readers like this one. Do not use those microSD-to-normalSD converters (usually packed together in the same shipping plastic as your card) just because you only have a reader that reads regular SD cards, they tend to fail a lot.
16) At your own risk, try cleaning the contact points on your SD cards (if you must, use cleaning alcohol and a cottom swap/q-tip - do not use water), to free them of dirt and invisible grime. If you have multiple SDs, try cleaning the least expensive ones first. Don't forget to leave them to dry completely before insertion into the NC. Credit to bonobomidwest, read his experience here.
Click to expand...
Click to collapse
17) Use Nooter 0.2 (recommendation from thecubed):
Here's my recommendation: use the stock charger cable (the one with the light-up N in it) when you try Nooter 0.2.
If the light goes from orange to green (or something like that) that means Nooter is booted and working.
My new thought: some file in /rom is missing, which controls the backlight and lcd controller. I can't prove this, but it seems logical haha.
All you need to do is get Nooter 0.2 booted and ssh'd in and you'll be able to dd over a complete 1.0.1 backup.
rawfish: I use Ubuntu, so sorry if I'm not able to provide instructions for Windows
Type:
Code:
sudo ifconfig usb0 192.168.2.1
Then:
Code:
ssh [email protected]
And you should be able to follow the directions for restoring on the wiki... either that or check around on IRC, if you tell them that you've got ssh access and you just need to restore your device, they'll help you out if I'm not around..
rawfish: I typed 'dmesg' in shell to see if the NC connected as a usb-ethernet device, and it doesn't show. If it does for you, then you should have progress and should ask around in IRC.
Click to expand...
Click to collapse
All these did not work for me, but hope this is useful to some. I've read testimonies from everyone that this is an unbrickable device, and I certainly hope it's true, and for a kind soul to help suggest more solutions. As I'm overseas, do you think I should call BN up to see if I can arrange to send my device back for fixing/replacement? It's been a month since purchase, and 3 weeks of failed restore attempts.
Disclaimer: I am not responsible if any of these methods get you in deeper trouble. Attempt at your own risk. Credit goes to thecube aka IOMonster, and the #nookcolor channel on irc.freenode.net. Thank you to everyone who created the recovery guides too.
This space reserved.
You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.
khaytsus said:
You sure you just don't have crap or badly burned SD cards? Sounds pretty much what happens if you boot s really slow/junk SD or burn it badly.
Click to expand...
Click to collapse
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.
rawfish said:
I tried on 6 different SD cards:
1. Transcend 8GB Class 6
2. Transcend 4GB Class 2
3. Wintec 16GB Class 10
4. Sandisk 4GB Class 4
5. Sandisk 2GB non-SDHC
6. Sandisk 256MB
I've burned stuffs like Autonooter and Honeycomb on these before, and they worked fine.
Click to expand...
Click to collapse
First of all - great job in pulling all the resources into one place (it's small consolation, but i think you've just helped a whole load of people )
Second, i apologise if I'm telling you stuff that's obvious, but in helping out on these forums often it's the LOGIC of troubleshooting rather than the particulars of the problem that are important... In other words, only vary one thing at a time, and ALWAYS swap out every piece of hardware involved at each stage... if you always rely on one piece of hardware this might be the weak link... so have you tried a different SD drive or adapter? and have you tried burning from a different computer?
Now, I'm not being insulting, because I had a virtually identical problem with my first froyo - it just wouldn't boot (as you describe) despite multiple burns, different cards, all of the standard formatting tricks etc. It wouldn't work in multiple computers - the common element being the SD/microSD adapter. It never occurred to me that such an electrically simple part could be at fault, but you bet it was - in fact i would say in my experience these things consistently fail! (I spent a day kickign myself, because we know ho unreliable they are from using them in other devices). They also all look alike so it's hard to keep track of which one you are dealing with They also fail unexpectedly, so if you used an adapter before there's no guarantee it's working now...
Sooo... Have you tried a dedicated microSD reader (rather than a simple adapter)? I now carry one with me everywhere (it doubles as the world's smallest thumb drive too)
http://www.amazon.com/gp/product/B002HGFKR8
Also bear in mind that froyo appears not to work on 16gb cards (i see you tried one)
Also, from my experience with other devices these cards are very sensitive to dirt and oil on the contacts. Certainly with enough frustrated handling you can get enough finger-grease on them to have them fail. Also they seem to be much less tolerant when writing than reading. I have NO idea how you would go about cleaning out the slot in the NC (and as someone who has ruined at least one DVD drive by blowing canned air where you shouldn't I'm not going to advocate for that). I have resurrected 'dead' SD cards before by cleaning the contacts with rubbing alcohol and a q-tip (on the card's contacts) - but again do so with great care (at your own risk!!!) and with your cheapest card, and make sure it si completely dry before you put it in the NC.
I have been generally a little scared that all this plugging and unplugging of the microSD might hurt the NC, so i have done everything i can to avoid that...
I am sure you can find someone local to you willing to help fix your boot issue but I assure you, its damn near impossible to brick a nook without physical damage.
@bonobomidwest:
No offence taken at all, in fact I am very appreciative of your contribution. I forgot to add the fact that I tried on 2 different card readers, plus indeed tried to clean the slot via an air duster VERY GENTLY as a last effort resort (I would not recommend this, it may cause permanent hardware damage). Once I'm free I'll go get a new SD reader (reads uSD only) and a new uSD which I haven't tried before. I'll try cleaning the contact points too.
*Thanks - I've added more checklists to the OP
@combustiblemonkey:
Thanks for the assurance.
I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.
Dr-Rockso said:
I convinced my friend to buy a nook, rooted it for him, and was bricked within 2 days. Here is how I fixed it
EDIT: I tried to post a link, but was unable. If you go to theunlockr(dot)com and search for how to restore nook color to stock, there is a detailed article.
This took me almost 2 days of reboots, black screens, and freezing. I would get into CWR, and it would freeze. Had to reboot, got the black screen of death. Literally, a couple hundred reboots before it said that the OS has successfully installed, and of course, it froze again. Many more reboots, and it was finally at stock. I figure getting it back to stock was enough to return it.
Click to expand...
Click to collapse
Thanks, this is the direct link:
http://theunlockr.com/2011/02/14/how-to-restore-the-nook-color-to-stock
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.
Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.
chrysilis said:
Hi rawfish
I also have this issue and have been trying many things. My nook did boot nooter 0.2 (the light went green) but I couldn't get Win 7 or Ubuntu to connect to it. My screen never changes at all, no backlight even. Seems this may be a larger issue than most believe it to be, especially for people like us who don't live in the US.
Click to expand...
Click to collapse
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.
rawfish said:
Thanks, this is the direct link:
All instructions were taken from XDA, plus no guarantee it's the most updated
Moving on, great to hear you've gotten it back to stock. Man, you've got GREAT patience, a couple hundred reboots?
1) Was the SD inserted in or not? Curious about the OS successfully installed message, which is the result of 8x unsuccessful reboots without SD inserted.
2) Could you also provide a more detailed account on what you did? Looking forward to hear - thanks.
Click to expand...
Click to collapse
When I finally got it to work, the SD card was installed with the 1.0.1 stock OS on it, and CWR. The problem was that that (+) and (-) would only occasionally work. And if they did, it would usually freeze. I would be able to format system, but it would freeze if I tried to format data. Powered off, and I would get the black screen of death (BSoD). Once this happened, I would plug it into my computer so that I could hear the chime indicating a new device was plugged in. I found that ejecting the SD and then rebooting would sometimes help get rid of the BSoD. Then another power down, plug in the SD, and start again. Also, holding the N, +, and Power would sometimes help in launching CWR. I would usually have to hold for 60 seconds, but it would finally launch. It seemed like the nook was trying to run a process that slowing it down and causing it to freeze, but I couldn't figure out what it was. If I would wait an hour, it would boot CWR and allow me to format system and data, but then it would freeze when I would try to install the zip.
The successful install message was in CWR. It said Install From SD Card Complete, or something like that. After that, I still had to do the 8 reboots. It would load up the stock welcome screen and freeze. 8 reboots later, I got the video lady. Good enough to return it to the store.
It really was just persistence. It would usually take an hour of reboots before I was able to try to install the zip, and it probably failed on me 15+ times. The status bar would get half way, and freeze. Then I had to begin again. If it had been my nook instead of my friends, I probably would have given up. I wish I could be more specific, but unfortunately I am new to all of this. My nook rooted just fine, and fixing his is really my only experience with CWR. I just kept going until it worked.
Good luck! It is a pain in the ass, but it can happen.
rawfish said:
If you can find a friend or person in your area having the same device, you can try to see if an SD you burned work on theirs. If it works on theirs, it's possible that your SD slot is defective - but then comes the question of it being in working condition before the bricking happened, right?
I still think mine's recoverable, as with yours. Could be a bad SD or reader, or bad contacts. I'm going to try out using another reader plus purchase an el-cheapo branded SD. I'm also going to try formatting it via another PC in a linux environment and messing around with the partitions.
I understand the trouble you may have taken to get the device - and this happens. All the best mate, and do cheer up, don't give up.
Click to expand...
Click to collapse
My wife has one as well so am able to test using that and the SD works fine in hers. The whole screen not turning on thing is weird though, does your screen turn on?
We bought them when on honeymoon in America so didn't have to pay a shipper or anything
Deleting the partitions manually with Gparted and using dd to burn the SDs and making sure the correct partitions are bootable doesn't seem to work. Last night I retried a lot of the previously attempted options, with no results.
It's weird to think that a working SD slot and a slew of cards will suddenly malfunction, but for now that seems like the most plausible reason why my NC can't boot anything off SD.
To think back how it all started, the device suddenly rebooted from HC preview v0.4 to stock BN 1.01 (rooted + installed CWR on eMMC) while the SD is inserted, then upon another reboot it simply stays dead, this gives me reason to believe that the internal boot partition is corrupted, and SD slot nuked hardware-wise.
Hmmm, really hoping to find someone else who has the same device, in my area.
Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.
Steelfan555 said:
Right now I am at the Black Screen of Death as well...
I think Barnes should refund me, but I am willing to do some tests for the good of society.
Click to expand...
Click to collapse
Sorry to hear that, and don't give up! Hope you took a look at the other threads, and this little pseudo checklist I made in the OP. Do share the outcome
Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!
FroztIkon said:
Thank you Rawfish. The first option, the Dummies Guide to Fixing 'My Nook won't boot'
was what I needed to get started on the right track again. Though I'm not sure anyone wants to know how I ended up here, I'm grateful to those that put in the time and effort to find any of these solutions.
Thank you!
Click to expand...
Click to collapse
Update:
Ok, so after running through it, I ended up getting stuck on the boot screen that shows N. If I powered off, it would restart and get stuck at that screen. I tried the 8 shutdowns (it installed new software), but afterwards, it was still stuck. So, I tried another method I found on the forums. I powered off holding the N button and power, which caused it to boot back up and do a factory reset. I now have a factory fresh Nook.
Okay, it's been a while since I kept this thread updated - I contacted BN and had the device sent back, apparently the SD slot failed so they sent me a new one. I'm just wondering if it's sheer concidence that it happened, as I was tinkering with Nookie Honey preview v0.4, when the hardware suddenly failed.
Oh well, I guess the NC still remains as a 99.99% unbrickable device - with the 0.01% being related to the ambiguous root cause to my case.
I now have 2 NCs (one from the RMA process, another one from the $199 eBay deal.
I ripped my SD slot out a few months back after getting a card stuck in it, I threw the Nook in a corner in disgust and left it there,
I've tried to get it back up and running over the last few days, I've charged it fully over two days using the wall charger but it refuses to boot - I have nothing at all displayed. when i plug it into my PC I hear the noise it makes when a usb device is plugged in but that's it - nothing..
So with all the methods of restoring it need the SD slot..I guessing it's a gonna??
Any ideas??
Could try to convert back to stock. There is a 3 finger method of restoring your nook back to stock. You can find the link here in XDA right here. http://forum.xda-developers.com/showthread.php?t=1461172
Then you can take it back to B&N for a replacement if its still under warranty. Don't be so hardcore with losing on game-mode next time
I tried that last night but will try again with a fresh head ....
Nope..not having it, Tried everything now, using the three finger method brings nothing up on the nook screen at all - totally blank although the pc ssems to respond by making a couple of bleeps so assumed this was akin to the nook being turned on , tried it eight times and nothing..I really do think it's dead...
There is a program in the sdk (/tools/ddms) that allows you to see what is on the screen (and take screenshots). I believe this pulls from what the system is pushing to the screen (not what is actually on the screen). If that is the case, you can hit the power button like you normally would to bring up the lock screen, refresh using the application and see if it is pushing anything. You'd have to be quick, because if the NC is in standby, it won't show anything.
Also, you may want to try pulling some logcats to see what is going on.
I think the nook should be unplugged from the computer when trying the 8 failed boots. Also make sure to hold down the power button at least 8 seconds to make sure the nook is really off.
Sent from my NookColor using xda app-developers app
Can't seem to get the pc to see the Nook, it asks for OMAP3630 driver??
DDms can't see the nook ..
tried the 8 failed boot method...
All is not well
Its now on a popular auction site for spares..I give in.
new one bought and on its way..
p2daz said:
Its now on a popular auction site for spares..I give in.
new one bought and on its way..
Click to expand...
Click to collapse
PM me... I can either fix it and send it back... or perhaps we can work out a price to buy it from you.
I have the same problem. The only way I could get it to recognize it was by holding power for 8 seconds and then would go away after a ssecond or [email protected]
DizzyDen said:
PM me... I can either fix it and send it back... or perhaps we can work out a price to buy it from you.
Click to expand...
Click to collapse
Thank you for the offer but I've bought another and might as well keep it for spares, the postage to the states and back alone would cost what I've paid for the replacement.
Or you could tell me how you would fix it ;-)
What I would wind up doing depends a lot on what is on it already, and what methods were used... first thing I'd do is modify ROM's to ensure mmcblk0p8 was seen as sdcard... then go from there...
I wish I could give you a definitive "Do this, then this, and finally this" type of answer... but there are so many variables in place there's no way I can without knowing more of what is there...
If you have a custom ROM on it... go to playstore and get adb wireless
Hello everyone, thanks for taking the time to read my thread. i'm really having a hard time here. I'm trying to take pictures, but it has become so unstable, and I can't reply. and it keeps saying i don't have any space in my SD. I've NEVER had this problem with my other ROM/Default.
There are 2 SDs, one is the one i bought and put it, so i can put all my music and i thought the other i would be able to have it for pics and other stuff. But I can't see it. i've taken out so much music to try and make space (like 10 folders/albums). But it's still saying it doesn't have enough space.
I'm right now rooted. used ClockworkMod then installed CM10 I believe. or CM11 and right now i'm running android (I went from a 2.3.6) to 4.1.2. on an SGH-T679 and the ROM is CyanogenMod version, Build date Apr 2, 16H EDT 2019, CyanogenMod version 10-20130402-UNOFFICIAL-Ancora_tmo. I hope that's enough info.
So I'm guessing if anyone from these forums. Has anyone been through this? Or has heard of someone else having problems. Because my #1 thing is just walking around NYC, taking pics. But when I can only walk around and like take 3 or 4 pics. i'm like :crying: all day. And i don't have the $ to just buy a camera like that.
P.S. and since yesterday, It takes longer to load the battery while charging unlike before. I thought that it was weird. But then to waste/discharge the battery.
Thank you
This may or may not solve your problem, sometimes there are hidden files that stay on your internal storage and eat up all your room. In your file manager enable hidden files, then look for things you can remove. One of hem right off the bat would be .thumbnails, I'm sure there are more but honestly you have to look around your storage, there may be old downloads or cache files that are still there. Hope this helps.
I think i flashed my ROM, data, cache, dalvik-cache and I think data was the last one. and since i've done that. I can't start my phone. It says samsung. then the samsung cyanogenmod start up screen, and it just hangs there. can anyone help me with this pls? I pressed
start button + down volume button. Then it says that it's going to download the OS for me. But i think that just hangs too cause it takes a while. and then it goes back to the start up screens that won't go anywhere.
Thanks D'vari, but unfortunately i think i'm passed that. Now i need to know just how to start my phone and get it past the phone.
You probably have conflicting data somewhere. Try power + volume up. That should get you into recovery. Then wipe everything except system and you should be able to boot up.
It took so long, because i read somewhere else to press vol down + power button. so i was trying. And It got me into Odin, and that said an OS is important, do you want to dl an OS now? so i said, well, i don't think i even have one left, so i chose yes. then it would say it was downloading for hours. but then it would boot up into the boot up screen loop. which was kind of good, but i didn't think so at the moment. Then i read how to get into cwm in my phone. so then i did it, and i had to do an advanced restore before regular restore was coming back MD5 mismatch. So It's like i flashed my old system, restored it to factory cyanogenmod factory. Tomorrow i'll flash cm10 and google apps and something else that had swipe working on this phone. maybe it was just upgrading to CM10, because now it's in version 9 and swipe is not working.
Thanks for your help
cyanogenmod issues as well
I had the same issue last week when updating to 10.1. but it did say that it may take a while to boot up. I didn't stress it. I just plugged it in by my bed and went to bed. when I woke up the next morning, I had it!
I did the volume up/power-wipe clean-reboot and then I slept. give that a try. maybe you are just like me and worrying that it is taking too long and you have F-ed up your phone!
On a different note, this 10.1 is awesome. But I can't get it to recognize my sd card. it does show that one is mounted but wont save anything and wont let me access the files. I have wiped the sd card clean and formatted to fat32. but that is doing nothing for me. any other suggestions here? I need my music and the space! this is taking so much time, it almost isn't worth the effort. but I love the cyanogenmod 10.1. but can't keep if it wont work right. ???
Deefex said:
It took so long, because i read somewhere else to press vol down + power button. so i was trying. And It got me into Odin, and that said an OS is important, do you want to dl an OS now? so i said, well, i don't think i even have one left, so i chose yes. then it would say it was downloading for hours. but then it would boot up into the boot up screen loop. which was kind of good, but i didn't think so at the moment. Then i read how to get into cwm in my phone. so then i did it, and i had to do an advanced restore before regular restore was coming back MD5 mismatch. So It's like i flashed my old system, restored it to factory cyanogenmod factory. Tomorrow i'll flash cm10 and google apps and something else that had swipe working on this phone. maybe it was just upgrading to CM10, because now it's in version 9 and swipe is not working.
Thanks for your help
Click to expand...
Click to collapse
I'm using pac 4.2 and I can switch were I want my pics stored from the camera settings maybe that ROM would help your situtation.
Thank you for all your help. But i decided to switch over to JellyBean. But i've been having some minor problems with it. I just flashed this ROM after doing something stupid in CWM (as you all know) while using cyanogen. I actually really like this ROM. I though CM10 futuristic looking. this beats that by a lot of points. I just have a problem now. The icons in the apps menu/section, are spaced too far apart. IDK what I did to cause this. Cause i was messing with those options of icons rows and colums for the desktop, but i set it back to default and that still didn't do anything to the apps section.
The other problem I'm having is with the camera. I try to open it, but it just says camera can't go on, 'wait-report-close'. That type of message. IDK what it is because the main reason for switching was to be able to take lots of pics. I love taking pics with my phone. And i found out what had my internal memory soooo clogged up. I had a .txt music cache file that was 848MB. Once I erased that, I know have 50% free space.
It looks really retarded . I know i'll fix it somehow, someday. I think there's even an upgrade now for slimbean, maybe I should try that. But right now i'm in google play store. in the 'my apps' list. and going through what i used to have, and installing my old apps, one by one. a grueling task, but I really want to use this ROM as my main rom.