Related
Just wondering if anyone else has or is experiencing any of these issues.
Had a HTC TyTN II for about a year now (I think).
Sometimes turning it on, the screen doesn't sync properly. You get the waivy lines, and have to hit the power button a few times to turn it off and back on, eventually it turns on properly.
Device cannot read MicroSD cards.
I'm thinking one of the cables that connects the top part of the device to the bottom is coming loose, however, I knoticed that when doing hard resets, it lowers the frequency of this happening, until the device gets filled with data and apps... This is the second time ive done the hard reset to make it usuable.
Super odd... Typicly if a hard reset fixes it, it woulnd't be hardware issues, but I still have issues with the MicroSD card.
Just wondering if anyone has any hardware failure stories.
Tried changing spl's and radios yet ?
sorry for the hijack but do you or anyone else have an issue with a bluetooth headphone. i've tried different bluetooth devices and on incoming calls if i use the bluetooth to answer the callers hear a loud screeching sound for a second. but using the same headset if i press the answer button on the phone the screeching doesn't occur. i've tried 3 different headsets and all had the same issue. any ideas??
SPLs?
I havn't modified the firmware or anything whatsoever. Running HTC firmware. No special addons or mods..
Then your warranty should come to the rescue - see what they say!
Zhariak said:
SPLs?
I havn't modified the firmware or anything whatsoever. Running HTC firmware. No special addons or mods..
Click to expand...
Click to collapse
Then if it's a HTC TyTN II, the warranty is just over a year (I think it was about 15 months on mine) so it'd be worth contacting HTC pronto with your phone to hand to see if you can get it fixed under warranty. Let us know how you get on.
Wow,
So I noticed that the MiniSD card reader has been going lately. Card goes in, it doesn't recognize it. have to put it in 20 times to get it to recognize it.
ANYWAYS....
I decided to take the card out, cuz its pissing me off and almost pointles. BAM the phone became super responsive. When u hit the power button the screen turns on instantly. When your on a phone call and press hangup, it hangs up normally (there was a 10 second delay before that it would take to turn the screen back on and hang up the call).
So I think its JUST the microSD slot thats fried, i think since its kinda working, it was causing freezing issues and caused the phone to freeze, etc...
I don't care that it doesn't work. Ive sent stuff in for warranty before, I always get stuff back in worse condition then i sent it with new stuff broken. I cant go without exchange push for longer than 4 hours at night, so im going to live without the microSD card. lol
Thanks anyways guys!
Zhariak said:
Wow,
So I noticed that the MiniSD card reader has been going lately. Card goes in, it doesn't recognize it. have to put it in 20 times to get it to recognize it!
Click to expand...
Click to collapse
Wow indeed. Maybe the problem is related to the card itself or whats on it. Try backing up the card (using its usb reader) then reformat it in FAT32 and with the phone totally powered off insert it. Boot up and see how the phone then performs. If this still proves problematic and you don't want to get it fixed under warranty there's not much anyone can do to help I'm afraid.
Card is fine! Tried 5 others, lol.
maybe some pins are crossed or something inside the slot.
Mine is having same problems exactly. sometimes if i reboot with the slide open it will work ok sometimes not wtf
Weird... thats odd that someone is having the same issue...
OMG ITS THE Y2K9 bug!!!
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.
Hey All,
I decided to flash back to stock using the odin 3 method. Basically I was planning on getting rid of the phone soon. I cleared everything off the internal "SD" card, wiped all user data and cleared the cache. Booted back into the stock OS, everything looked fine. Checked the internal card again and it had written some new files. I assume these are just operating files for the stock OS.
So I power down the device correctly, pull the battery and install the sim card and 8 gig flash micro sd card. The micro card is completely clear. I boot the phone back up with no issue, it hits the network with no issues. I start looking though all the bloatware and go back into setting and turn the USB setting from Kies to USB storage. Then a get an odd alert telling me an update for my phone is available. So, I figure a stock update couldn’t hurt and let it download and install. It downloads to 100%, and advises it needs to reboot to install the update... Ok, so I let it... the screen come back with a progress bar and not much else. At 50% the progress bar stops and a message telling me the update has failed pops up... The phone then shuts off.......
Bricked..... I mean bricked bricked. 3-button doesn’t work, Jig doesn’t work. the 3 button battery pull doesn’t work. 2 button while putting in the usb cable with odin loaded doesn’t work. 3 button with battery out, usb in and then put the battery in doesn’t work.. This thing is dead....
Now my question....LOL... since I had cleared out any and all data, will AT&T give me crap saying I voided the warranty by flashing my phone?
Do they look at what’s stored in ROM? Because before the phone died I had flashed it to stock... I know how to call XBM (their exchange program) and I know they will send me out a refurb phone, to questions asked. But my concern comes in when I ship them back my device and start snooping around... what are they looking for? No liquid or physical damage. Normally I don’t try to get one over on the man, but it was their crappy update that bricked the phone, not my tampering….
any thoughts or experience with this matter?
Did you flash back to JF6 or something? That OTA was probably the busted JH2 they pushed out to all our devices last year, resulting in tons and tons of bricks. They shouldn't give you any crap over it - it was their own fault that your device got damaged - and if you flashed everything back to stock and formatted the internal SD, then technically your phone WAS at factory defaults, so they wouldn't be able to tell what you've been doing with it prior to that anyway.
Edit:
Also, if ATT gives you **** over it, mail it to Samsung. Tell them you were on eclair, got an OTA notification and it bricked your device. They'll ask you to mail it in without the battery and back cover, and swap the board for you. Takes about a week, but whatever.. beats having to deal with some dumbass ATT rep.
this is just good to know....dont flash to stock and try an OTA update.
This exact thing happened to me. My phone was replaced without question but the tech guy told me something interesting. Just to check things, he took the battery from my bricked phone and tried it in a new phone - nothing. The battery didn't even work anymore. Likewise, he tried a new battery in my bricked phone. Again, nothing. Anyway, I got the new phone and battery and all is well. He said it was junk now. They will never be able to tell what ROMS were flashed on there, I suppose.
jack man said:
This exact thing happened to me. My phone was replaced without question but the tech guy told me something interesting. Just to check things, he took the battery from my bricked phone and tried it in a new phone - nothing. The battery didn't even work anymore. Likewise, he tried a new battery in my bricked phone. Again, nothing. Anyway, I got the new phone and battery and all is well. He said it was junk now. They will never be able to tell what ROMS were flashed on there, I suppose.
Click to expand...
Click to collapse
Well I thought they do like a jtag, or am I wrong?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
nope, no JTAG, just a new motherboard
Hello guys! This is my first post after visiting xda developers everyday for the past two weeks so bare with me...
I recently purchased an HTC HD7 from ebay at a very good price. I thought all was well with the free shipping and all...until the phone started restarting after the first day. So I panicked, searched on google and up pops up xda developers forum! It offered alot of solutions to many problems regarding resetting and restarting.
However after extensive research for the past two weeks, I finally recognized that the problem was the 'internal' SD card. The sellers from HK from whom i bought the phone had voided HTC warranty to insert one of their low class, cheap SDHC cards (which explains the reduction in cost) causing it to fail drastically as a phone. I know this happened because of a shiny warranty sticker with a bunch of chinese symbols on it. Updates won't work, factory reset happens on it's own, restarting even when i simply open up the messaging app and of course the infamous "storage card not working" error.
I've decided I cannot and do not want to send back my phone back in exchange for a new one since i will encounter the same problems. I've decided to have them compensate me for any repairs I have to make. So I read an article on xda dev about upgrading memory to 32GB using SanDisk Class 2 SDHC. Problem is, it is quite out of reach in my country so I would like to know a full list of compatible SDHC cards (not necessarily 32 gb). Also, what other hardware problems might be causing the occurances mentioned? I doubt it's a software problem, but say it is, what might be causing it?
Thank you!
cabe0018 said:
Hello guys! This is my first post after visiting xda developers everyday for the past two weeks so bare with me...
I recently purchased an HTC HD7 from ebay at a very good price. I thought all was well with the free shipping and all...until the phone started restarting after the first day. So I panicked, searched on google and up pops up xda developers forum! It offered alot of solutions to many problems regarding resetting and restarting.
However after extensive research for the past two weeks, I finally recognized that the problem was the 'internal' SD card. The sellers from HK from whom i bought the phone had voided HTC warranty to insert one of their low class, cheap SDHC cards (which explains the reduction in cost) causing it to fail drastically as a phone. I know this happened because of a shiny warranty sticker with a bunch of chinese symbols on it. Updates won't work, factory reset happens on it's own, restarting even when i simply open up the messaging app and of course the infamous "storage card not working" error.
I've decided I cannot and do not want to send back my phone back in exchange for a new one since i will encounter the same problems. I've decided to have them compensate me for any repairs I have to make. So I read an article on xda dev about upgrading memory to 32GB using SanDisk Class 2 SDHC. Problem is, it is quite out of reach in my country so I would like to know a full list of compatible SDHC cards (not necessarily 32 gb). Also, what other hardware problems might be causing the occurances mentioned? I doubt it's a software problem, but say it is, what might be causing it?
Thank you!
Click to expand...
Click to collapse
I think your probably right, more than likely it is due to the cheap SD card!
The good thing is that almost all the newer manufactured SDHC cards will work in the HD7, class 2, through 10.
I would recommend at least the 8gb or the 16gb for storage capacity and a class 4 for read/write speeds.
Stay with a better brand like SanDisk or PNY.
Purchace it from someone that has a decent return policy, just incase you get a dud.
Run the CrystalDiskMark 4000mb test on it and post your results in the "upgrade your HTC HD7 memory to 32gb" thread here:
http://forum.xda-developers.com/showthread.php?t=883582
and they will be able to tell you if its a sufficient SD card for the HD7.
Thank you
xdrc45 said:
I think your probably right, more than likely it is due to the cheap SD card!
The good thing is that almost all the newer manufactured SDHC cards will work in the HD7, class 2, through 10.
I would recommend at least the 8gb or the 16gb for storage capacity and a class 4 for read/write speeds.
Stay with a better brand like SanDisk or PNY.
Purchace it from someone that has a decent return policy, just incase you get a dud.
Run the CrystalDiskMark 4000mb test on it and post your results in the "upgrade your HTC HD7 memory to 32gb" thread here:
http://forum.xda-developers.com/showthread.php?t=883582
and they will be able to tell you if its a sufficient SD card for the HD7.
Click to expand...
Click to collapse
Where can I hit the thank you button? I cannot find it :S Also the phone is deteriorating day by day....Now it is out of battery and when i charge it, it goes into a loop of the HTC splash screen and a windows loading screen. It then freezes and repeats. Is there anything else that might be contributing to this? thanks!
cabe0018 said:
Where can I hit the thank you button? I cannot find it :S Also the phone is deteriorating day by day....Now it is out of battery and when i charge it, it goes into a loop of the HTC splash screen and a windows loading screen. It then freezes and repeats. Is there anything else that might be contributing to this? thanks!
Click to expand...
Click to collapse
It's definitely possible and I wouldn't rule out a software issue, but I think the signs are pointing to a non- compliant SD card
The devices OS is reliant on the SD card to store user data and cache, contacts, SMS, emails and apps, without an SD card inserted or having a faulty SD card would cause these operations to crash and cause system errors when powering on the device, this in turn prevents it from operating and the system from loading and cause file system performance issues, device lockup, reset or boot loop.
Are you sure that they even put an SD card in your device? They or the original owner may have removed the SD card and not installed another one. Either way, I would start with putting a new SD card in your device and go from there!
xdrc45 said:
It's definitely possible and I wouldn't rule out a software issue, but I think the signs are pointing to a non- compliant SD card
The devices OS is reliant on the SD card to store user data and cache, contacts, SMS, emails and apps, without an SD card inserted or having a faulty SD card would cause these operations to crash and cause system errors when powering on the device, this in turn prevents it from operating and the system from loading and cause file system performance issues, device lockup, reset or boot loop.
Are you sure that they even put an SD card in your device? They or the original owner may have removed the SD card and not installed another one. Either way, I would start with putting a new SD card in your device and go from there!
Click to expand...
Click to collapse
Yes I am sure they put in an SD card because i removed the back panel and it is clearly visible. One thing I find annoying is that they removed the protective metallic paper used to protect and hold the SDHC in place. Is there a way to use an alternative to this protective paper? I have also noticed the phone does have some on board memory ( 11MB) to be able to run. However there is no place for anything, messages, contacts, even for running applications such as IE! I'm guessing it is some kind of emergency memory? Anyways, my worry is that i feel that metallic strip is somewhat important so I would like to know how to replace it? Your help is very much appreciated!!!
cabe0018 said:
Yes I am sure they put in an SD card because i removed the back panel and it is clearly visible. One thing I find annoying is that they removed the protective metallic paper used to protect and hold the SDHC in place. Is there a way to use an alternative to this protective paper? I have also noticed the phone does have some on board memory ( 11MB) to be able to run. However there is no place for anything, messages, contacts, even for running applications such as IE! I'm guessing it is some kind of emergency memory? Anyways, my worry is that i feel that metallic strip is somewhat important so I would like to know how to replace it? Your help is very much appreciated!!!
Click to expand...
Click to collapse
Glad I can be of help!
It sounds like it's not recognizing the SD card. Can you get the phone running and goto settings, about phone and check to see what it says for storage capacity. It should show, total storage and available storage.
As far as the metalic tape... I know that it's there to help prevent the SD card from coming out of the tray. Because WP7 Mango security locks the card to prevent any data from being removed from the card. So say you removed the card without unlocking it first, there is no way to extract the data from the card or format it with another device. If the HD7 is turned on without the SD card installed the card will no longer work in the device either.
Not a 100% sure if the tape serves any other purpose though. You could cut a piece of duct tape to fit and secure it in place use the good kind like gorilla duct tape.
xdrc45 said:
Glad I can be of help!
It sounds like it's not recognizing the SD card. Can you get the phone running and goto settings, about phone and check to see what it says for storage capacity. It should show, total storage and available storage.
As far as the metalic tape... I know that it's there to help prevent the SD card from coming out of the tray. Because WP7 Mango security locks the card to prevent any data from being removed from the card. So say you removed the card without unlocking it first, there is no way to extract the data from the card or format it with another device. If the HD7 is turned on without the SD card installed the card will no longer work in the device either.
Not a 100% sure if the tape serves any other purpose though. You could cut a piece of duct tape to fit and secure it in place use the good kind like gorilla duct tape.
Click to expand...
Click to collapse
I have successfully inserted a 32Gb SanDisk SDHC Class 4 in my phone just a few hours ago. I performed a hard reset as instructed. When I booted up, the HTC splash screen showed up and it froze. For roughly 5 minutes...I plucked out the battery and again performed a hard reset. This time the device loaded with an error saying: low storage space please free up some space from your device. I tapped 'ok' and all I had was a black screen, although i know the OS booted up because i could hear system sounds, the bottom buttons were responsive and the lcok screen was visible. However when I slide up, no icons are visible except the wifi icon, the battery icon and the sim icon.
I tried loading the bootloader and as far as storage goes it is only recognizing some sort of 64MB partition from an "sd sandisk". Could this be a faulty installation of the OS on the new card? was I supposed to allow the system to take its time to load the software onto the new SD card? I am also unable to obtain the bootloader version etc that would be required to flash an RUU. Help would be appreciated!
cabe0018 said:
I have successfully inserted a 32Gb SanDisk SDHC Class 4 in my phone just a few hours ago. I performed a hard reset as instructed. When I booted up, the HTC splash screen showed up and it froze. For roughly 5 minutes...I plucked out the battery and again performed a hard reset. This time the device loaded with an error saying: low storage space please free up some space from your device. I tapped 'ok' and all I had was a black screen, although i know the OS booted up because i could hear system sounds, the bottom buttons were responsive and the lcok screen was visible. However when I slide up, no icons are visible except the wifi icon, the battery icon and the sim icon.
I tried loading the bootloader and as far as storage goes it is only recognizing some sort of 64MB partition from an "sd sandisk". Could this be a faulty installation of the OS on the new card? was I supposed to allow the system to take its time to load the software onto the new SD card? I am also unable to obtain the bootloader version etc that would be required to flash an RUU. Help would be appreciated!
Click to expand...
Click to collapse
That's strange... The HD7 has an internal (primary) seperate memory for the OS, the SD card is a secondary memory for the device. Technically it's a non removable storage. So once inserted, you hard reset the device and the SD card is formatted and then it becomes a part of the device and it's integrated into the file system.
If you boot into bootloader mode (device off, hold down the volume down button and power the device back on, while continuing to hold down the volume down button) what's all the information on the bootloader screen? I'm wondering if it's bricked. Can you also get into USB host mode? Device off, hold down the volume down button and the camera button and then power back on.
xdrc45 said:
That's strange... The HD7 has an internal (primary) seperate memory for the OS, the SD card is a secondary memory for the device. Technically it's a non removable storage. So once inserted, you hard reset the device and the SD card is formatted and then it becomes a part of the device and it's integrated into the file system.
If you boot into bootloader mode (device off, hold down the volume down button and power the device back on, while continuing to hold down the volume down button) what's all the information on the bootloader screen? I'm wondering if it's bricked. Can you also get into USB host mode? Device off, hold down the volume down button and the camera button and then power back on.
Click to expand...
Click to collapse
The device was not bricked. I inserted another SDHC card I had used for an old MP4. It was an 8GB TEAM SDHC class 2. The device booted up the OS on this card after a formatting and everything worked better than previously. However some restats were still happening. I tried loading the bootloader in an attempt to flash a custom ROM for the device but no USB text was seen on screen although Zune was recognizing the device perfectly. I decided to leave the device as is. Yesterday, I migrated to my grandma's for a week and I have a room where reception is great always full and no interruptions. A curious fact was that the phone did not restart once no matter how much I used it... and I did use it extensively downloading apps for the first 3 hours, constantly chatting on facebook, emails HTC hub and also voice recognition for messaging and searches. It was working 100% great. When I descended down the stairs (my room is on the first floor) and went to the kitchen I recieved a call from my girlfriend. I picked it up and reception was pretty bad, so I told her to message me instead. As I cut I realized the reception bar was zero. After a couple of minutes, the phone restarted for the first time since my stay at grandma's. I came to the inevitable conclusion that the mobile restarts everytime the reception is bad. This conclusion was backed up by working fine in my room and restarting every time I went to a low reception room. It hit me then that my house does have pretty bad reception where I reside most of the times which causes all those restarts. I am almost sure this is the cause of the restarting. However I am not sure what it infers... Regardless I am sending the phone back in exchange for a new one. However I do wish to know if anyone encountered the same problem, what they did to tackle it (besides running around like a madman to find reception), what causes this and if it is a model defect or a rare case. Thank you for your help!
cabe0018 said:
The device was not bricked. I inserted another SDHC card I had used for an old MP4. It was an 8GB TEAM SDHC class 2. The device booted up the OS on this card after a formatting and everything worked better than previously. However some restats were still happening. I tried loading the bootloader in an attempt to flash a custom ROM for the device but no USB text was seen on screen although Zune was recognizing the device perfectly. I decided to leave the device as is. Yesterday, I migrated to my grandma's for a week and I have a room where reception is great always full and no interruptions. A curious fact was that the phone did not restart once no matter how much I used it... and I did use it extensively downloading apps for the first 3 hours, constantly chatting on facebook, emails HTC hub and also voice recognition for messaging and searches. It was working 100% great. When I descended down the stairs (my room is on the first floor) and went to the kitchen I recieved a call from my girlfriend. I picked it up and reception was pretty bad, so I told her to message me instead. As I cut I realized the reception bar was zero. After a couple of minutes, the phone restarted for the first time since my stay at grandma's. I came to the inevitable conclusion that the mobile restarts everytime the reception is bad. This conclusion was backed up by working fine in my room and restarting every time I went to a low reception room. It hit me then that my house does have pretty bad reception where I reside most of the times which causes all those restarts. I am almost sure this is the cause of the restarting. However I am not sure what it infers... Regardless I am sending the phone back in exchange for a new one. However I do wish to know if anyone encountered the same problem, what they did to tackle it (besides running around like a madman to find reception), what causes this and if it is a model defect or a rare case. Thank you for your help!
Click to expand...
Click to collapse
Yeah... If you can exchange it for another one I would!
If in bootloader mode the white section will display "serial" while not plugged in and "USB" while plugged in, if neither of these are present then the device is half/small bricked for sure, even if it's recognized by Zune. That can be fixed with the goldcard/ Y cable method too.
I have heard of some people having issues with restarts when on their network and while roaming outside of their network. One thing you can try is flashing different radio versions until you find one that gives the best signal. Another thing could be the OS build version and firmware version that your device is running on, it may need to be updated.
xdrc45 said:
Yeah... If you can exchange it for another one I would!
If in bootloader mode the white section will display "serial" while not plugged in and "USB" while plugged in, if neither of these are present then the device is half/small bricked for sure, even if it's recognized by Zune. That can be fixed with the goldcard/ Y cable method too.
I have heard of some people having issues with restarts when on their network and while roaming outside of their network. One thing you can try is flashing different radio versions until you find one that gives the best signal. Another thing could be the OS build version and firmware version that your device is running on, it may need to be updated.
Click to expand...
Click to collapse
While I wish to thank you for your constant support and very useful suggestions on the matter, xdrc45, I am going to send the phone back very soon. Chances are I will recieve a replacement in two weeks time. Aside from this, I am sure the seller at HK will send me a phone with similar issues (Cross-fingers he won't), But since I am able to handle some very basic technical issues such as these, and the phone is at a good price (160EUR) I do not wish to refund. I'd much rather tinker with it a little here and there to customize it to my liking, ensure maximum potential of the phone and prevent issues. So my question is this: What steps should I take the minute the phone arrives (assuming they send me an identical copy of the phone they provided)? Do I need to supply myself with any hardware or software to be able to install the phone to function as though I bought it officially from HTC?
In reply to your suggestion on the bootloader: yes, the white section was always empty no matter what...so I'm guessing the phone was slowly dying away anyways. I will definately look further into the goldcard/ y cable.
Thanks!
cabe0018 said:
While I wish to thank you for your constant support and very useful suggestions on the matter, xdrc45, I am going to send the phone back very soon. Chances are I will recieve a replacement in two weeks time. Aside from this, I am sure the seller at HK will send me a phone with similar issues (Cross-fingers he won't), But since I am able to handle some very basic technical issues such as these, and the phone is at a good price (160EUR) I do not wish to refund. I'd much rather tinker with it a little here and there to customize it to my liking, ensure maximum potential of the phone and prevent issues. So my question is this: What steps should I take the minute the phone arrives (assuming they send me an identical copy of the phone they provided)? Do I need to supply myself with any hardware or software to be able to install the phone to function as though I bought it officially from HTC?
In reply to your suggestion on the bootloader: yes, the white section was always empty no matter what...so I'm guessing the phone was slowly dying away anyways. I will definately look further into the goldcard/ y cable.
Thanks!
Click to expand...
Click to collapse
I think that's a good choice and hopefully the next one won't have the same problems for you!
The best thing to do when you get the new one is boot into bootloader mode and check the information, if you want post back all the info from the BL screen or provide a screen shot of it. Also go into settings, about phone, more info and post back all the information from there too. That way we can make sure everything is up to par on the device and functioning like it should and make sure it's not bricked and if it is we'll get it taken care of for you!
Hey guys!
I'm having some serious issues with my HD7... the other night I put it on my charger and went to bed. When I woke up the next morning my device was unresponsive, for one the alarms didn't go off on it. The charging indicator led was lit... I pushed the power button to wake it up and nothing happened (I thought ok, strange) I unplugged it from the charger, indicator light went off and still nothing, it was at this point that I noticed our cat chewed the crap out of the devices USB cable in the middle of the night. (Ugh!!) So I removed the battery and rebooted it and everything seemed fine. A little while later I went to use it and I pushed the power button to wake the screen and again not responsive, remove the battery and reboot and it seems fine. Later I was on it on XDA and I set it down for a min and it starts to go into sleep mode and freezes on a partially dark screen and none of the buttons work, power, volume up/down, camera or the soft keys, pull the battery and reboot its fine, this continues throughout the day so I did a hard reset and the problem still persists. So this continues on for 2 days, so I flashed back to stock rom and perform a hard reset before the first boot and i run stock for a day to see if this helps and unfortunately not it still has the problem. I'm back on DS v7.8 and have performed numerous hard resets now but I think there is a definite hardware issue from when the cat chewed on the cable while it was plugged in!
I have the insurance on the device and can make a claim but the chances of me getting a brand new one from Asurion are slim to none and will probably end up with a refurbished one and I would prefer to just keep mine!
So I'm turning to my great and knowledgeable friends here at XDA for any advice or suggestions on how to fix this problem.
Many thanks in advance!
you do understand that your v7.8 is a betta version and has a lot of bugs, right?
http://forum.xda-developers.com/showpost.php?p=17735584&postcount=3
so try a mango rom and let me know!
Meivoon said:
you do understand that your v7.8 is a betta version and has a lot of bugs, right?
http://forum.xda-developers.com/showpost.php?p=17735584&postcount=3
so try a mango rom and let me know!
Click to expand...
Click to collapse
I do understand that it's buggy and isn't the most stable rom... That's obviously a sacrifice with running a beta version!
As stated in the OP, I flashed my device back to a stock/shipped 7392 rom and ran that for a full day and a half. Then after my post yesterday I flashed back to 7720 Mango rom for a day now and still continue to experienced the exact same problems.
I was actually experiencing the problem before I ever flashed to DS v7.8... Just to clarify between flashing 7392, 7720, DS v7.78 and DS v7.8 the device experiences the issues evenly across the board... Unfortunately no one rom made it any better.
Thanks for the idea though!
I think I've just come to accept the fact that when the cat chewed the USB cable it caused some short circuitry which in turn caused some hardware damage.
After talking to Asurion earlier today, they have informed me that I'm not the first person to experience an issue with their device after a pet had chewed/damaged the USB cable while it was plugged in... They have had multiple claims for the same reason. I will be receiving my replacement device sometime tomorrow, well technically today now!
well, initially, my thought was a bad flash... but you reflashed.
so, my thoughts go to either battery or microSD card.
maybe try re-XSPL-ing.
if still same issue, would try another battery or microSD card.
honestly, though, unsure of a definitive solution.
regards.
I know this ones been a tough nut to crack... I've been racking my brain on it for a week now!
I've re-XSPL-ed twice now and have flashed it more times than I'd like to admit...lol
I have a backup battery and have tried that too with no success.
I haven't tried a different SD card yet - Good idea... It had crossed my mind but is such a pain in the "you know what" to unlock the SD card card and swap it out.
I am preparing for it though, I just downloaded Cab Sender and Storage Lock Cab. Guess I'll have to flash it again to a rom that supports Cab sender and since I'm getting my replacement device today, I need to unlock and remove my 32gb SD card anyway and that will give me the opportunity to try a different SD card in it and see how it performs.
I'm debating on whether or not to send mine back... I have 15 days to return mine after I receive the replacement, if I don't they only charge me $75 for it.. I didn't think that was bad at all and it's almost worth it to keep it for $75 and see if I can get it functioning like normal.
BTW Shadow... love your new avatar/forum pic!
xdrc45 said:
I know this ones been a tough nut to crack... I've been racking my brain on it for a week now!
I've re-XSPL-ed twice now and have flashed it more times than I'd like to admit...lol
I have a backup battery and have tried that too with no success.
I haven't tried a different SD card yet - Good idea... It had crossed my mind but is such a pain in the "you know what" to unlock the SD card card and swap it out.
I am preparing for it though, I just downloaded Cab Sender and Storage Lock Cab. Guess I'll have to flash it again to a rom that supports Cab sender and since I'm getting my replacement device today, I need to unlock and remove my 32gb SD card anyway and that will give me the opportunity to try a different SD card in it and see how it performs.
I'm debating on whether or not to send mine back... I have 15 days to return mine after I receive the replacement, if I don't they only charge me $75 for it.. I didn't think that was bad at all and it's almost worth it to keep it for $75 and see if I can get it functioning like normal.
BTW Shadow... love your new avatar/forum pic!
Click to expand...
Click to collapse
only $75 for a new, refurb HD7? that is a steal!
they still for about $150 on eBay.
good luck on your venture and don't forget to report back.
and thanks.
This is the exact same issue I've been having with my HD7s. And I was running stock Mango since AT&T had never pushed any updates when this started. Since it started happening I tried the manual upgrades to 8107 and 8773 and it's still happening during the charge, and a few times it's locked when I didn't lock the screen and it was attempting to auto-lock. Anyone figure out if it is indeed hardware or if it's just something else happening?
So, I think I located the source of the crashes. After I've disabled WI-Fi for three days I haven't had a crash. Would upgrading to the Mango v2 drivers possibly fix this? It's not a huge issue to turn on Wi-Fi as needed, but it did work for months without me having to disable Wi-Fi to get a reliable phone.
mancide said:
So, I think I located the source of the crashes. After I've disabled WI-Fi for three days I haven't had a crash. Would upgrading to the Mango v2 drivers possibly fix this? It's not a huge issue to turn on Wi-Fi as needed, but it did work for months without me having to disable Wi-Fi to get a reliable phone.
Click to expand...
Click to collapse
Did you ever get your HD7 working properly and did you try the v2 drivers?
Here's the update for my device....
I flashed Dynamics 7 to my old HD7 and installed Storage Lock cab via cab sender, (which Storage lock ran very well on D7 and didn't cause any problems with the rom) unlocked the 32gb SD card I had in it and removed it from the device. I re-installed the original 16gb SD card (that I was locked out of completely) and put the device back together, booted the device, performed a hard reset and what do you know... the device unlocked and recognized the SD card.
I then flashed it back to stock 7392 rom and ran the device on it for the next 2 days and the problem still persisted. So I flashed it to stock 7720 Mango to see if maybe the Mango rom would help...no luck still having problems. So I came to the conclusion that a new SD card in the device was no gonna solve the issue. I Then downgraded the SPL and XSPL-ed the device and re-installed D7 and Storage Lock cab, unlocked the SD card and removed it from the device.
Now I had already received my replacement HD7 and all new accessories. I downgraded the SPL from 5.xxx to 3.xxx via the goldcard method. XSPL-ed the device and installed D7 and Storage Lock cab, unlocked the 16gb SD card in the device, removed it and then installed the 32gb SD card. Put it back together booted it, hard reset and the 32gb was acknowledged fine in the new replacement device. I then flashed Deepshining 7.8 to it.
Since I just removed my 16gb SD card from my new HD7 and the old one was still disassembled, I figure I'd give this SD card a try in it. I installed the 16gb to the old HD7 and put it back together, booted it, hard reset and the SD card was acknowledged just fine but the problem still persisted.
I though well for the cost of keeping the old HD7 it might be worth it, I inserted the SIM card in the device and it wouldn't work... Once you activate the new replacement device Asurion deactivates the old device, so that you can't use it or sell it to someone, so the device becomes useless other than WiFi. So I unlocked the 16gb SD card, removed it and the SIM card. Flashed the device back to stock Tmous rom, removed the battery and back cover plate. They only want the device and none of the accessories. I shipped off the old HD7 to them and have been enjoying my new device ever since... Plus I have 3 batteries, 2 - 16gb SD cards, 2 back battery cover plates, 2 USB wall adapters and 1 USB device cable now. Not bad for the cost!