Related
Ok i just got a free g1, im acually on att and all my phones have been winmo htc phones, even done a few custom roms for myself.
Anyways i got this phone thinking #1, i can unlock like any other htc phone fairly east to work with att? Second of all it keeps booting up and i see a triangle and a ! in the middle. When i hold down alt l and try to restore factory settings then reboot it goes to the same screen the error im getting is E: cant open /cache/recovery/command. So idk what to do from here i dont want any custom roms or anything honestly just want to unlock the phone and play with android, guessing something is horribly wrong with the rom on this phone.
Also this probably sounds really dumb but i dont see an SD slot on this phone its a t-mobile branded g1. Im not sure if its suppose to have one or what? The only thing i see is a place to insert the sim card right below the battery. If this phone doesnt have an sd slot am i screwed as far has getting it all fixed up.
Basically i know nothing about android this was a free phone figured it would make a good back up or replacement to my ATT fuze if i ended up like Android better than WinMo. Sorry for all the lame ass questions but im pretty clueless and would just like to get this phone running as quickly as possible so i can start playing with android and learn what im doing.
boorishid said:
Ok i just got a free g1, im acually on att and all my phones have been winmo htc phones, even done a few custom roms for myself.
Anyways i got this phone thinking #1, i can unlock like any other htc phone fairly east to work with att? Second of all it keeps booting up and i see a triangle and a ! in the middle. When i hold down alt l and try to restore factory settings then reboot it goes to the same screen the error im getting is E: cant open /cache/recovery/command. So idk what to do from here i dont want any custom roms or anything honestly just want to unlock the phone and play with android, guessing something is horribly wrong with the rom on this phone.
Also this probably sounds really dumb but i dont see an SD slot on this phone its a t-mobile branded g1. Im not sure if its suppose to have one or what? The only thing i see is a place to insert the sim card right below the battery. If this phone doesnt have an sd slot am i screwed as far has getting it all fixed up.
Basically i know nothing about android this was a free phone figured it would make a good back up or replacement to my ATT fuze if i ended up like Android better than WinMo. Sorry for all the lame ass questions but im pretty clueless and would just like to get this phone running as quickly as possible so i can start playing with android and learn what im doing.
Click to expand...
Click to collapse
when you open the keyboard there is a little latch by the green call button that's where the sd card goes
boorishid said:
Basically i know nothing about android this was a free phone figured it would make a good back up or replacement to my ATT fuze if i ended up like Android better than WinMo. Sorry for all the lame ass questions but im pretty clueless and would just like to get this phone running as quickly as possible so i can start playing with android and learn what im doing.
Click to expand...
Click to collapse
You probably wont like this answer but you posted in the wrong forum. You really need to figure out how to search because the answer you seek is not a simple one. I would first start searching (maybe try Google) as to where the SD slot is located.
http://www.google.com/search?aq=f&q=g1+user+manual
would have saved you some confusion
as an xda member, i'd expect you to post in the right forum... LOL
the sd slot is underneath a cover below the green (send) button.
I find it easier to open the keyboard and pull on the tab on the upper left corner of the chin.
As to the rom, I'd suggest that you go into fastboot and flash a rom from there (boot while holding camera)
to flash in fastboot, use
Code:
flash_image (type) whatever.img
jcarrz1 said:
as an xda member, i'd expect you to post in the right forum... LOL
As to the rom, I'd suggest that you go into fastboot and flash a rom from there (boot while holding camera)
to flash in fastboot, use
Code:
flash_image (type) whatever.img
Click to expand...
Click to collapse
Seriously, he had no clue as to where the sd card was located, do you expect him to have downloaded the SDK and have fastboot setup? I really think he needs to search as it is more complicated than it seems.
bkmo said:
Seriously, he had no clue as to where the sd card was located, do you expect him to have downloaded the SDK and have fastboot setup? I really think he needs to search as it is more complicated than it seems.
Click to expand...
Click to collapse
i did that on purpose
note my inclusion of whatever.img
jcarrz1 said:
i did that on purpose
note my inclusion of whatever.img
Click to expand...
Click to collapse
And I thought I was trying not to sound cruel. Well at least you have hinted as to what he needs to search for.
seriously....can ANYONE read the rules? or even use a little bit of common sense before posting?
c'mon man, how could this possibly belong in the development section?
Moved as not Android Development.
sorry, if i posted in the wrong forum i googled xda g1 forum and just clicked it.
As for slashing the ting im really trying to avoid that. Like i said i know nothing about android. The first few times i turned the phone on on it worked fine, just told me to insert sim card. Then i got home turned it on to really start messing with it and it just wouldnt boot and has kept giving me that error, i have no idea why i didnt try to flash the thing or anything like that. Ive held down alt l, as per searching the net went to the restore factory defualt option the phone seems to format then when i reset it i get the same error and can only turn the phone off by removing the battery.
Sorry like i said i know these are all idiot questions, sorry about posting in the wrong forum originally, like i said just did a quick google and posted i was on my way out the door. I just want to get the phone working stock and go from there. Phone seemed to be just fine at one point, i didnt do anything to it, i couldnt even get past please insert sim, so idk why im even getting this error at all. Basically the little searching i did do a few days ago made it seem like it had to do with flashing and updating which i definately did not do.
from what I understand in your post you only "half setup" your phone
( got as far as being asked for sim )
try pressing ALT+w when at the " triangle ! "
this should do a factory data reset, and next time you boot it will set up your phone from the begining
boorishid said:
As for slashing the ting im really trying to avoid that.
Click to expand...
Click to collapse
Yeah I would want to avoid that too lmao
Thank you for the help but ive alread tried alt w and going back to defualts with alt l. Everytime the thing reboots after reseting defualts it goes back to that triangle screen. and when i press alt l it shows the error i mentioned before..
try this
http://code.google.com/p/android-roms/wiki/Unbrick
The "triangle screen" is the recovery mode. That error about recovery/command always shows up, it's no big deal.
Are you holding any buttons while you boot? Holding home while turning the phone on gets you to recovery (your triangle screen), holding camera gets you to fastboot. You just want to boot normally.
If the G1 isn't rooted, you won't be able to get past the initial setup screen unless you've got a T-Mobile sim in it. Once you get to the sim error, you've made progress from what you've said here though. If you can get back to that, search around. I seem to recall that some people here run their G1 without a sim, so perhaps you can find out how they did it.
Hey everyone, I'm trying to upgrade from Myn's Warm Eclair [BETA 1] (I know, I know, lol I should check here more often...) to Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS10] [7/8/10] (the download link that says "DOWNLOAD RLS10" in large orange font underneath the "What Doesn't Work" secton on his 1st post.
I'm doing what I usually do to install android, which is:
download the .nbh (which is voguimg-240x320-froyo-08-07-10.nbh)
rename it to RUU_signed.nbh
place it in the ROMUpdateUtility
add the ANDBOOT folder to the root of my SD card
placing the androidinstall.tar file inside
holding the power and camera buttons to boot into the RGB 'usb' screen
then running the ROMUpdateUtility to install it and boot up the linux
in linux I hold down the center button to get the the install menu
then install both system and data to the NAND (since I don't have partitions on my 8 gig SD
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!
this happens to me all the time. the question you need to ask is "is the device getting to the desktop?" and "is the operating system fully loading to a usable state?"
in my experience answering either of these questions 'yes' puts you in a good position. there have been reports of boot sequence taking up to 20 mins. personally, i can make it to desktop in about 10 mins every time.
hope it helps.
sometimes you just need to format the sd card to fat32 again then try reinstalling after putting the files back on the card of course. if the sdcard is formatted wrong then it wont be able to read the directory and will give you that error
Darkstarrdp said:
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
It's not a problem - this is the permission setting - ignore the messages
Just let it get back to the install screen, and then hit Quit or soft-reset device.
Then wait about 10-15 minutes for first boot and go through startup setup
Reboots are quicker, maybe anywhere from 2-4 minutes.
I overclocked my vogue to 496mhz with no issues & I guess some people hit 510mhz safely.
Just to add, Ive been running at 520 for a month now without noticing any major adverse effects...Sorry to chime in
I second wisconsinated's note -- I had this problem last night. I reformatted the card as FAT32 and things went as expected after. Not sure why they tanked in the first place, but I suppose that's not important, right?
ill third that. a reformat of my microsd did the trick.
i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.
ericbond said:
i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.
Click to expand...
Click to collapse
oddly enough, with an experimental operating system, one needs to exercise extreme patience at times.
glad its all in order for you now
Thanks guys, I got it to finally install after the third try, I guess it was just having hiccups trying to install. Everything's good now.... OS installation side at least.
Now I have a different problem... my touch sensitivity is kinda out of whack.
it's like touch screen is dead half the time, on my stock sprint ROM it will work perfectly, but, on the newer builds of android (2.1's) the touch screen won't react most of the time. Like, I'll have to hit the screen over and over a few time's before it'll finally pick it up. I've used the calibration tool to get it all lined up, but when I go to test the calibration I notice that it will only recognize my touch between the .50's and .60's range, it's like it's locked into that area and won't pick up anything else. I also drew a circle around my screen about 10 times once I got it to recognize my pressure and out of the 10 circles 4 or 5 drew a line directly to the bottom right corner of the screen then it would bounce back to where I was actually pressing. It makes it really hard to get anything done on a touch phone if the screen doesn't want to pick up lol.
Like I say, when I move back to my original sprint rom everything is fine and dandy using WinMo 6.1 but who wants to use 6.1 now adays
So, is there any way to fix my touch sensitivity? or is my screen just crapping out on me?
Digitizer going bad
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)
Darkstarrdp said:
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)
Click to expand...
Click to collapse
I am not sure this can help, are you familiar with terminal?
open terminal or adb and type
Code:
cat /sys/module/tsc2003/parameters/sensitivity
to see current setting, it usually is 8192
write it down and change the param to lower value like 3072
Code:
echo "3072" > /sys/module/tsc2003/parameters/sensitivity
check the result
Code:
cat /sys/module/tsc2003/parameters/sensitivity
it should now display 3072
HTH
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