ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
matthewjulian said:
ok, i am hopelessly stuck. I ran the unlocker and after I click the last button to start the process, it says it cannot read a file. Anyways, I check to see if it worked by chance, and it does say security unlocked. But every time I try to flash a rom from the computer it starts and gets to the point where my phone goes to the color bar screen and says usb at the bottom, then it tells me that it cannot communicate with my phone???HELP
Edit: Really Guys??? I have posted twice here, I have been in the android forums for a long time and I can get a response to anything there in 5 min., I thought this was part of our community but I guess I was wrong.
Click to expand...
Click to collapse
I haven't had this problem, but is the driver installed for when it is in the bootloader screen?
Another way you could try is flashing it from bootloader mode. Just go into bootloader mode then plug it into your comp and run the romupdate utility.
Odd
Never personally ran into it but check your USB cable. Try a different cable. Try a different USB port. I had some issues with them being a little touchy.
I dont know if anyone cares, but I figured it out. I am using a Early 2010 Model MacBook Dual Core running Parallels instead of dual-booting Win XP.
When I am in Windows XP, OSX is running in the background, when the rom update utility turns the phone off then on into the bootloader, the phone is off for that split second and parallels cant keep up with it, and the Mac trys to grab the USB connection in that split second before Win XP says "No, thats my connection", so in that split second exchange the connection with Windows and the RUU gets droped! Kind of simple once you know whats happening. No matter, I used my brother in-laws Vista Toshiba( infected with viruses to the max), it worked fine and I am now running Moonscapes 1.6 with android as well! Thank You to the people who took the time to help!! Remember guys this is a community, it doesnt work unless people respond, without participation we may as well be talking to our dogs!
You never mentioned you were doing something crazy like trying to flash your phone from a virtual machine. That never works, because the usb passthrough driver doesn't detect the windows low-level bootloader mode. How are we supposed to help you when you don't provide details?
Lol, my bad, I got sloppy!! My son dumped a Sonic drink on my dell so all I could work with was my trusty Mac, I am going to dual boot it later today. I have to say after a day with Moonscapezx's 1.6, I like WM, dont know if I like it enough to swap it out for good, I still love my Hero(at least for another 3 months when I get an upgrade, EVO!!!). Ok, well Thank You again guys, I love XDA, you guys are great
Good evening! This post is meant to serve as a (hopefully) comedic recounting of what wonderful maladies one can concoct using a simple recipe of two parts impatience and one part ignorance (pro tip: add a dash of overconfidence for added goodness!).
First the ignorance. I am a Mac user. There, I said it. I've always considered myself a bit tech-savvy, and at various times over the past twenty-five years or so, I've dabbled in operating systems ranging from my first Commodore 64, through MSDOS, Windows, BSD, Linux, and finally on to Mac OS X. I've been quite happy and comfortable here. When my iPhone suffered a tragic death at the hands of a hardwood floor this past summer, I broke from the family and purchased a Captivate. Aside from the GPS, I've loved it. I rooted it the same day, and as soon began flashing ROMs onto it. Most recently, I was running Cognition 2.3b6. I realize now that my previous experiences do not serve to make me a "power user," but rather simply a dangerous amateur.
Now the impatience. When I upgraded to Cognition 2.3b6 from 2.4.1, I tried downloading directly to my phone via the browser, but I was informed that such a download was not supported. Today, I decided to try out 2.3b7, and I thought I'd outsmarted that pesky limitation by downloading to my computer and transferring it to my phone via Dropbox (which I just obtained, and which seems awesome so far). I could have waited until I got home and transferred it via USB, but then I had an entire 50 minutes of class remaining, and who wants to suffer through class and then a train ride under such anticipation?! I rebooted into recovery, chose the correct option, navigated to dropbox/ and selected my .zip file. A minute or so after it began flashing, I received an error, advising me that a path was incorrect, or something to that effect. Ah yes, I remembered, when flashing a ROM, I need to copy the file to the root directory of the SD card. I'll just do that n-- AT&T World Phone screen. Hmm, this is taking some time. Hmm, this has taken ten minutes. Hmm, this is apparently the new limit of my phone's capacity for operation.
Now is a wonderful time to be a Mac user. Since, you know, we lack Odin support. Thankfully, I was a beta tester for a previous version of Windows, which I will have to install via Boot Camp and attempt to clean up the mess I've made. I'll post a followup after I've attempted this. Hopefully anybody reading this will find a bit of humor; I sure am laughing at myself
TL;DR - Mac user who screwed up his device, now having to Boot Camp Windows to fix it.
So ideally, you should have flashed back to JF6 before trying to flash 2.3B7. Although I guess that's easier said then done for you since us Windows users can use Odin to go back to JF6 before a flash.
Hopefully you can put your phone in Download Mode and recover it with Odin!
Goodluck.
I have not got it working yet but I am a real novice. Heimdall will allow you to flash stock with mac. It is more involved then odin but if you know your way about computers it should be useful
http://forum.xda-developers.com/showthread.php?p=9675809#post9675809
Sent from my SAMSUNG-SGH-I897 using XDA App
Yeah, I was looking for that! Had some trouble with Boot Camp, so I'm giving it a shot on a friend's Windows PC right now.
mcord11758 said:
I have not got it working yet but I am a real novice. Heimdall will allow you to flash stock with mac. It is more involved then odin but if you know your way about computers it should be useful
http://forum.xda-developers.com/showthread.php?p=9675809#post9675809
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Okay, resolution!
I followed the Odin3 One Click option from a friend's PC. Took a few tries to get the correct combo to get my phone into download mode, but eventually got it (I believe it was volume up&down + plug in, but I've had a few glasses of wine, so I forget now). Flashed back to JF6, then flashed Cog 2.3b7. Everything appears to be working fine!
Cheers! If anybody needs further detail, please feel free to reply to this or PM me.
All the best,
Randy
Astro has the ability to enable all file type downloads in the browser.
.zip included.
its sooo true.. its the most dangerous when you have a little bit of knowledge because then you often dive into something you don't completely have a grasp over, but you think you do ;D. i know firsthand but with my car, which quickly became a more expensive hobby than phone flashing lol...
at the same time, you can't be discouraged by failing or messing things up, or you'll never learn. i guess the underlying lesson is to do all your research about a topic before you jump into anything that could potentially destroy the object haha.
glad you got it to work!
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 had whatever, that updated to 7.3 as soon as I turned it on. Rooted fine with KF First Aide. Installed ES File Explorer, Google Play, etc. All was well. Then I read a post here how hard it was to copy/paste with ES File Explorer. I was joking about it with my husband and showing him how easy it was and copied random file... literally just randomly long pressed a file to show him the options, picked copy, and then went to another directory and *meant* to point to but touched paste instead... it was one of the Google Play files.
Kindle fire hd 7" immediately started freaking out. A mac address type error flashing so quick I couldn't do anything else. It was the same low letters and numbers you'd get with a mac address but said error and just an OK button which did nothing when you manage to tap in while flashing. Restarted, thinking if I was lucky Google Play just would't work... got the red triangle and neither option helped. So I ordered one of SkOrPn's cables which works flawlessly and boots right into fastboot. Yay for SkOrPn! Not so ya for me... (not their fault!).
It shows up as "Tate-PVT-08". I've tried every variation of driver I can find. Uninstalling all old things I can find, complete with the command line command to show ghost hubs/devices and what not and removing them and shut down/start up fresh too... no joy. Also removing and restarting between each driver try... neither of the Amazon drivers work for fastboot for me. I've tried so many things at this point my brain is fried.
So I'm hoping someone can help direct me how to fix this. . I won it in an online giveaway, so I'm not out anything, but it'd sure be nice to use it! As messed up as the Kindle crap is I'd be pissed if I bought it... but I'm majorly spoiled on Sony (Ericsson) and their "ya, play with it, screw it up, we don't care, here's how to fix it online just plug it in"... even before they had the online thing they'd let you send it back (and paid shipping both ways for it!) would reflash firmware and send it back with paper ticket that said "No problems found" lol... even on a device you actually bricked (wouldn't turn on... not the cute "brick"="I screwed it up but it's fixable" that people use now).
Any help or advice would be greatly appreciated. Especially if you could steer me to drivers that work for 2nd generation HD 7 inch in fastboot on Windows 8. Thanks for reading if nothing else!
Try The SoupKit found here.
This is a Kinology HD using XDA Premium
Swap cables. Boot with the factory cable then switch to a normal one.
Thanks for the reply, but I've been doing that. Great advice for anyone who doesn't know though!
You couldn't have damaged anything by just copying a file unless either:
You cut the file
OR
You overwrote a system file
OR
You filled up your system partition.
If you still need help, I might be able to do some researching.
Sent From my Kindle Fire HD running CM10.1
I'd say your fast boot driver didn't install right mine showed up like that and I had to keep playing with drivers to get it to work
Sent from my Amazon Kindle Fire HD running CM 10.1
Same Problem
I'm having the same problem! If you fixed it please let me know!
FIXED!!
It's fixed! You have to use KindleFireAide. Just follow all of the directions and it's perfect.:laugh::laugh::laugh::good::good::good:
Shawnsch said:
I'd say your fast boot driver didn't install right mine showed up like that and I had to keep playing with drivers to get it to work
Sent from my Amazon Kindle Fire HD running CM 10.1
Click to expand...
Click to collapse
Thanks, I was hoping there was a better answer than just keep uninstalling/reinstalling various drivers in various ways til it works lol.
I've got a pc I haven't plugged it in to I'll try this weekend, if that doesn't work I'll do the Linux Soup Kit.
Deviantelf said:
Thanks, I was hoping there was a better answer than just keep uninstalling/reinstalling various drivers in various ways til it works lol.
I've got a pc I haven't plugged it in to I'll try this weekend, if that doesn't work I'll do the Linux Soup Kit.
Click to expand...
Click to collapse
Use Kindle Fire Aide. It comes with all of the drivers.
Geckodudes said:
Use Kindle Fire Aide. It comes with all of the drivers.
Click to expand...
Click to collapse
That was my first thing to try. Unfortunately one of them says stopped by user (preferred one) and the alternate won't install, gets to the end of installing and says didn't install, do manually... which has the same results. I'm getting the same results on another pc. Fun times lol.
Edit... I give up, it's Linux time. Will report back later.
My husband did the Soup kit (correct version, followed directions, etc.) with it for me while I was at work today on an pc he put Linux on (so nothing phone/tablet/adb/driver has ever touched it for anything). He's more savvy with Linux, I haven't used it much since the 90s while he regularly has it as a dual boot on his main pc. He used Ubuntu, followed the Soupkit directions and still no Linux love either.
I'm pretty much down to just sending it back, worst case they send it back and tell me I'm screwed. Both of us are so spoiled on Sony (me) and Google/Nexus (him)... that this some things only works sometimes and just keep bashing your head into the wall and something you already tried three times will work thing is out of our frame of reference (which is what it took to get it rooted lol). I've already spent more time trying to fix the stupid thing for something that shouldn't have even caused an issue than I've spent on both my Sonys combined... even though I've borked both more than once... crazy.
My only advice ... buy a real tablet lol. Luckily I won this so I'm not out anything if Amazon won't swap it... but I really like the 7" size for book reading.
I'll fix it for you...
Deviantelf said:
My husband did the Soup kit (correct version, followed directions, etc.) with it for me while I was at work today on an pc he put Linux on (so nothing phone/tablet/adb/driver has ever touched it for anything). He's more savvy with Linux, I haven't used it much since the 90s while he regularly has it as a dual boot on his main pc. He used Ubuntu, followed the Soupkit directions and still no Linux love either.
I'm pretty much down to just sending it back, worst case they send it back and tell me I'm screwed. Both of us are so spoiled on Sony (me) and Google/Nexus (him)... that this some things only works sometimes and just keep bashing your head into the wall and something you already tried three times will work thing is out of our frame of reference (which is what it took to get it rooted lol). I've already spent more time trying to fix the stupid thing for something that shouldn't have even caused an issue than I've spent on both my Sonys combined... even though I've borked both more than once... crazy.
My only advice ... buy a real tablet lol. Luckily I won this so I'm not out anything if Amazon won't swap it... but I really like the 7" size for book reading.
Click to expand...
Click to collapse
If you're gonna send it anywhere, if you pay for shipping I could try to fix it. No guarantees, of course.
If you are on Windows 8 to install kfhd drivers you must advanced boot with unsigned drivers install mode active
Sent from my KFTT using xda premium
KindleFireGuy said:
If you are on Windows 8 to install kfhd drivers you must advanced boot with unsigned drivers install mode active
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Ya did all that fun stuff, repeatedly with various drivers with all the 20 steps in between to remove others, lol.
Husband spent quite some time with Linux and SoupKit to no avail also. He could get his phone to work (making sure he had all the rules and steps correct), but it never would do anything with the tablet.
I gave up and called Amazon late Monday. They had me turn it on and verify the red triangle screen then sent me a new one that arrived today. Take the new one out of the box and put the old one in they said. They paid shipping both ways. If they complain I'll tell them send me the old and I'll send the new one back lol (at my expense). If they want to make the thing such a mess to deal with what do they expect? They know there's a whole group of people that won't live with the crappy launcher mess they have .