Database Develop

Has Flashing wiped my Micro SD??????

First of all thanks to all on the forum for all the useful tips and tweaks.
I finally took the bold step of my first flash two days ago to Dutty's latest Rom.
As he advised I have slowly added programmes and tweaks to make sure there were no bugs. Last night I was playing around with different wallpapers after a day of the phone being stable. Waking up this morning I found a lot of my tweaks for the today screen had reset themselves. Using file explorer i tried to open my storage card (I kept all the cabs i have been using on it) and it wasn't found. I took i out and have tried to open it through my laptop and it keeps asking to 'insert card' i.e it can't see it either. I tried a hard reset on my HD to see if it was anything I had installed and still nothing!
I have most things backed up on my PC and yesterday set up microsoft myphone so hopefully I haven't lost anything...BUT. Has flashing caused this or is it just coincidental that my storage card has gone tits up!
many thanks in advance.
P.S Off topic. has anybody else found that the Virgin advert causes a stuttering effect when scrolling down a page?

Hi Mate,
take a look at this link
http://forum.xda-developers.com/showthread.php?t=506560
Should explain all, it looks like when you upgrade to one of the newer roms not based on the 1.14 it kills the SD card, you could try formatting it again..
Happens quite randomly , so ...
Bloke

Cheers Bloke
Although the cause doesn't seem to be very clear. I flashed my HD without the SD card in. I have a sandisk card. It came with the phone but it was a replacement phone so not exactly bundled per se. (after getting the phone on an upgrade last Dec with Orange actually paying me a fiver for it, I lost it/had it stolen after owning it a month and had to then fork out £160 for it )
Sods law that i haven't been backing up my SD card as the majority of it was music that i have on my laptop anyway.
Thanks once again

I've never lost any info on my SD Card from flashing any roms, and I've flashed a lot. Even when going from 1.14 roms to 1.59 roms. No probs
However I have heard others have had similar problems and unfortunately only remedy was to format card. Once formatted problem shouldn't arise again

So to update:
tried out spare sd. Not a problem although only looked at it rather than file swap etc
Hard reset: still didn't find card
flashed stock 1.14 rom. Had colours go strange on screen whilst first installing but then touch flo started and colours as norm. Put SD card in and it wasn't found. Soft reset with card in and once booted funny colours came back (all kind of negative and opposite original colours, kind of cool but obviously not good). Still not finding card. Took card out and soft reset, all good and colours back to normal.
So, it seems, I will have to format. Bye Bye data!
I tried to look at the card from command prompt on my PC (xp pro) and it still couldn't see it. Muchos corruption me thinks. Not sure how I am going to format it now?
I hope HTC will look into this and release some sort of fix. Unless they know it's a hardware fault on the card reader and realise it will cost a small fortune to fix everybodies HD not to mention the bad publicity.

Okay, maybe not the most common method to do this, but when I had this happen to me, I also couldn't format the card anymore in my PC (Vista). What I did wat put the card in an old Samsung phone I had lying around, and the phone initialised the card for itself. After that it was also readable again on my PC and in my HD.
Since this happened to me I always take out the SD Card if I flash my phone. Just to be on the safe side.

HD7 SIM and MEMORY ERROR

Hi all!!! yesterday my phone fell to the floor with carpet but nothing serious and after that the phone intermitent recognize the SIM and Memory card. I did a hard reset (power on and volumen up and down) and things told me that don't have memory when I tried to delete the welcome sms and don't recognize the sim. Some bootup the phone recognize the SIM but neve the memory I changed the memory but nothing Any idea?

I removed the SD Card and I can't format.... any idea?

i am actually in the same boat.
went through almost all the pages here looking for some answers, but all i found was this.
my theory was the same, i thought it was the card had something to do with it, but then i realized that should affect the sim card.
this is the 2nd phone i go through with the same problem. nothing sounds broken, so what is it?

Actually, now that i did a little more research (after most of it just came from the "UPGRADE YOUR MEMORY" bandwagon ) i found that the way the antenna is set up i guess if it hits the ground hard it causes it to detach, thus rendering the phone pretty much useless. HTC claims its irreparable, but i don't think its true.
h ttp://ww w.engadget.c om/2010/10/29/htc-hd7-has-hidden-microsd-slot-user-replacable-card/
(breaking the rules a little but its not spam at all)
i got a replacement, but damn, its still a lot of money to pay.

[GUIDE] [BRICKED] Loading Roms/CWR via SD Fails - Black Screen of Death (28/02)

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.

[Q] Having problems with my HD7

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!

[Q] SD Card random deletion issues.

So I took the windows phone plunge and purchased the Lumia 1520 Friday when they became available. Finally had a phone available I wanted with a memory card slot, which was a must have, and top end hardware, which was also pretty important.
I'm running into the same problems that most everyone else who changes from Android has with things being different, and not being available...but nothing major.
I have, however run into 2 pretty big things that may have me turning this phone in before the 30 days I have to do so are up, but I wanted to ask if anyone else is having these problems to determine whether it's just my phone, or a known issue.
I've added a Sandisk 64G SD card to the phone to store data, music, videos and pictures. Turns out it's kinda useless for data because of the lack of a file explorer ap, and the purposeful design to prevent such a thing. Ok...I can cope with that...that's what a USB key is for.
However...what I'm finding is that the pictures/videos/music I am putting on the SD card are being randomly deleted after I put them on the card. I've tried formatting the card using the phone, even going so far as to do a hard reset of the phone and bringing it up with the SD in it, and then formatting it immediately. It still randomly deletes files, mostly photos. I store a few thousand photos of family etc, and some of them are not things I am comfortable storing in skydrive...so that's not really an option. I've tried putting them directly into the folders using Windows Explorer on windows 8, and using Windows Phone Ap for Deskto and syncing through that interface. In both instances, everyting I put on the phone makes it there, and is viewable on the phone...until it randomly disappears. And it's not all of the files, but just most of them...particularly when the phone reboots.
In addition, I've had 3 or 4 times where the phone has randomly shut itself off.
So the question then, is this something that's a known thing with windows phone 8, or is this likely just a bug with the 1520, or perhaps just my phone in particular?

Aielman said:
So I took the windows phone plunge and purchased the Lumia 1520 Friday when they became available. Finally had a phone available I wanted with a memory card slot, which was a must have, and top end hardware, which was also pretty important.
I'm running into the same problems that most everyone else who changes from Android has with things being different, and not being available...but nothing major.
I have, however run into 2 pretty big things that may have me turning this phone in before the 30 days I have to do so are up, but I wanted to ask if anyone else is having these problems to determine whether it's just my phone, or a known issue.
I've added a Sandisk 64G SD card to the phone to store data, music, videos and pictures. Turns out it's kinda useless for data because of the lack of a file explorer ap, and the purposeful design to prevent such a thing. Ok...I can cope with that...that's what a USB key is for.
However...what I'm finding is that the pictures/videos/music I am putting on the SD card are being randomly deleted after I put them on the card. I've tried formatting the card using the phone, even going so far as to do a hard reset of the phone and bringing it up with the SD in it, and then formatting it immediately. It still randomly deletes files, mostly photos. I store a few thousand photos of family etc, and some of them are not things I am comfortable storing in skydrive...so that's not really an option. I've tried putting them directly into the folders using Windows Explorer on windows 8, and using Windows Phone Ap for Deskto and syncing through that interface. In both instances, everyting I put on the phone makes it there, and is viewable on the phone...until it randomly disappears. And it's not all of the files, but just most of them...particularly when the phone reboots.
In addition, I've had 3 or 4 times where the phone has randomly shut itself off.
So the question then, is this something that's a known thing with windows phone 8, or is this likely just a bug with the 1520, or perhaps just my phone in particular?
Click to expand...
Click to collapse
Sounds like an incompatible SD Card issue to me, despite the phone being advertised as being capable to be upgradable to 64GB, some SD Cards may not work and cause major issues like phone rebooting, files being deleted and other annoying issues. You can see if this is the case by simply removing the SD card and barrow a 32GB SD Card and see if you still experience these issues. You can also try leaving the SD Card out completely and see if the phone reboots itself during a test period without the SD Card.
I know this might put you off of continuing to use Windows Phone products (Android had never these SD Card issues on high end phones so long I can remember), but once you go Nokia Black (= firmware update of Nokia for WP8 phones), you'll never turn back, meaning there is more to WP then the eye can see (much smoother and more stable than lagdroid , although I myself find android 4.4 is improving, WP has the same smoothness on midbudget phones than Android high end phones even with cyanogenmod installed).

bruce142 said:
Sounds like an incompatible SD Card issue to me, despite the phone being advertised as being capable to be upgradable to 64GB, some SD Cards may not work and cause major issues like phone rebooting, files being deleted and other annoying issues. You can see if this is the case by simply removing the SD card and barrow a 32GB SD Card and see if you still experience these issues. You can also try leaving the SD Card out completely and see if the phone reboots itself during a test period without the SD Card.
I know this might put you off of continuing to use Windows Phone products (Android had never these SD Card issues on high end phones so long I can remember), but once you go Nokia Black (= firmware update of Nokia for WP8 phones), you'll never turn back, meaning there is more to WP then the eye can see (much smoother and more stable than lagdroid , although I myself find android 4.4 is improving, WP has the same smoothness on midbudget phones than Android high end phones even with cyanogenmod installed).
Click to expand...
Click to collapse
The only real issue I've had is the storage disappearing. The shutdown thing, and it's a shutdown, not a reboot, is annoying but wont' be a deal breaker.
I have a 32G SD I'll try and see if I have the same data retention issues. If I do, this phone is either going to be replaced with a new one, or I'm getting a note 3, depending on whatever anyone else has to say about this issue.
Thanks for the reply
*edit* - Changed the phone out yesterday. Seems to be holding photos and songs on the SD card, even through reboots. My journey to the dark side may be complete /nod