Database Users

XDA Mini S Screen problem - Photo's now available

I've got a problem with my XDA Mini S. It's been sitting in a box in my shed for about a year, before I got it out yesterday to have a play around with it, and possibly try some software I found on it.
I put my sim card in, plugged it in to charge, and turned it on. It worked absolutely fine.
I haven't done anything with it yet, but I've turned it on now, and the colours are messed up on the screen. For example there is a red hue over the today screen, and on certain screens (like in bootloader mode) the colours appear to be inverted (I will post pictures later if needed).
I've tried reformatting the device, but this has not fixed the problem. I thought I would try reflashing the rom on it. I used to have the original o2 rom on my old laptop, but lost that when I had to reload windows.
I downloaded the original rom from here, along with the Rom Update Utility, and attempted to reflash it. It gets as far as 'verifying the information on your PDA phone', then crashes with the error: Rom update utility MFC application has stopped working.
I'm running windows vista on my laptop, and read that the RUU won't work until the drivers are updated. Following the instructions on mrvanx.org, I have downloaded the driver for vista and installed it, but i'm still getting the problem when I try and reflash the device.
I've also tried running the RUU in compatibility mode for XP as it worked fine on my old laptop which was running xp, but it still crashes, every time.
I'm beginning to wonder if reflashing it will even work though, since the colours are messed up in bootloader mode as well, which leads me to think it may be a hardware problem.
I know next to nothing about repairing these though, and probably wouldn't bother if it's a hardware problem, but until I can reflash the firmware, I won't know whether this is a case.
I'll get the photo's of what the screen is like uploaded to my server later on, and post the links here, so you can see what the problem is.

Photo's now available
I've uploaded a couple of photo's to show what the screen is like:
http://csc2ya.co.uk/images/bootloader.jpg
http://csc2ya.co.uk/images/startup.jpg

Update
i've got my old laptop out, reloaded xp on that, and attempted the flash using that. However, I get the message 'rom update utility MFC has encountered an error and needs to close'
I just want to get it to reflash to see if it fixes the screen, but so far i'm having no luck at it.
I've sucessfully reflashed it in the past with the o2 rom using my old laptop, so I can't figure out why it isn't working now.
Update: I didn't have activesync installed on my laptop which was why the updater was crashing. I've installed activesync, but now i've got another problem that is preventing me from reflashing it. I start the updater, and click through the prompts. It gets to 'verifying the information on your pda phone', stays like that for about 30 seconds, then activesync disconnects, and I get the error: microsoft activesync cannot recognize this device for one of two reasons: then the other information that the dialog gives. I'm not going to bother typing it all out, as i'm sure nearly everyone has seen it at least once before.
Additional info: No idea if this is relevant or not, but the extended rom has been formatted using the service tool.
Another update: I have now managed to get the device to reflash, but it boots up afterwards as if I had just turned it off and back on again. I have tried a hard reset afterwards, but cannot seem to get any of the o2 stuff back. It appears that the screen problem is hardware related though, as it is still present even after reflashing.
I can also no longer get it to go into bootloader mode, but the phone will still boot normally.

csc2ya said:
It's been sitting in a box in my shed for about a year.
Click to expand...
Click to collapse
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.

Myrddin Wyllt said:
Not to be flippant, but there's your problem right there. Two things: extreme temperature, and moisture. Both are the enemy of electronics. Chances are very good that you're screwed.
The first thing I'd do is buy (or even better, borrow) a new battery. Yours is probably done for.
If that doesn't fix the problem, I recommend disassembly and thorough cleaning with isopropyl alcohol, followed by at least 24 hours of strong, dry airflow between 50-80 Fahrenheit. Any floor or desk fan would do. Reassemble and pray. If that doesn't do it, you're going to have to find your fun elsewhere, I'm guessing.
Click to expand...
Click to collapse
The battery appears to be fine. I charged it overnight, and it still seems to hold a decent charge.
I haven't really got the tools to dissasemble it fully, but I will give it a go sometime in the next few weeks (i've got a copy of the service manual on my computer, so that shouldn't be a problem).
I only really got it out to play around with it again, and possibly try some apps on. It still appears to work fine apart from the screen (and the o2 applications now missing due the extended rom format, but i'm not bothered about those). I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Thanks for the suggestions anyway.

csc2ya said:
I've installed the my mobiler screen program on my laptop so I can at least view the screen properly using that.
Click to expand...
Click to collapse
Well, this certainly changes things. You have a bad screen, or a bad connection to the screen. You can get replacement for around $100USD, or you can try to get a broken unit with a good screen for less (maybe). I'd still disassemble it first, though, in case it's just a weak connection.

Samsung Focus (Rogers) - Post NoDo; screen stays lit

Around 24 hours after upgrading my Samsung Focus (on Rogers) to Nodo, the phone started having a weird notification bug... I think it may be a hardware issue unrelated to NoDo but thought I'd post here in case any one else is seeing this or in case anyone has ideas on how to test/fix it.
Effectively the screen won't stay off and the phone keeps making a notification sound. If you push the screen off button within a second or two it re-lights and makes a "de-de-de" sound (and keeps repeating that sound randomly - anywhere from every half second to every few seconds...). This sound is exactly the same sound as when you plug the phone into the charger. I think the phone must somehow be triggering a charger notification for some unknown reason (note: the battery doesn't show changing nor does it drop down when it makes the alert sound).
What I've tried so far to debug this:
- Removed Battery, restarted phone
- Turned on Airplane mode incase there was some push notification causing it
- Tried fully charging phone (notification started happening when battery was around 1/3rd charged but still happens fully changed)
- Did a hard-reset - still get the sound with no applications installed/setup
- Checked the battery diagnosis menu (doesn't show anything unusual)
Only other step I can think of would be to do a restore from Zune... suspect this won't change a thing though. The phone had worked flawlessly for 4 months and this error started 1 day after installing NoDo - suspect that is just a coincidence though...
For some reason the alert seems to stop for a while (e.g. 5 to 10 minutes) and then restart. I can put the phone in vibrate mode to make it bearable, but battery life is getting drained...
Any one else see this before or having any ideas? Guessing the phone needs repair but thought I'd check.

Battery Icon
Yes, I have seen it. My Focus did the same thing, but I believe it may have been a battery icon notification. It has something to do with the mini USB port that is used for connecting to the PC. AT&T told me it is a known problem on Samsung phones but was supposed to be fixed in the update. Mine has stopped doing this but I know it can reoccur at anytime. I am waiting for the AT&T US update to see what happens. Try attaching to your PC, let Zune launch, turn off Zune, turn off your phone screen, disconnect your phone. You may have to do this a couple of times. For me, it stopped doing this whenever the plug was inserted in the phone USB port.

Did you happen to get the firmware update package that should be available after installing the March 2011 update?

GrayWolf said:
Did you happen to get the firmware update package that should be available after installing the March 2011 update?
Click to expand...
Click to collapse
A firmware update? where?

I didnt get this update. Any rogers users that did? I unbranded nodo then rebranded and nodo again and nothing....

Update
When I was troubleshooting with the AT&T Tech Support Center for devices I was told it would be in the upcoming AT&T update for the Samsung. I had the impression it was the NoDo release specifically for the Samsung. You need to ask this question of Samsung users who got the NoDo release, more importantly, those users who may have had this problem.

Thanks for the post James - good to know I'm not the only one! For me this only started after installing NoDo. I think your PC USB connection might be right/related as shortly before it happened, I had run the windows update checker again to see if there was a firmware update with the phone connected to Zune... (nodo had run fine for 24 hours before - there wasn't a firmware update so I'd just disconnected). Think the problem happened very shortly after that.
Still very odd that removing the battery and even doing a factory reset didn't fix it!
I have a call in to Rogers now to see if they'll swap the phone... may just be a configuation bug but travelling on business and figured if a hard reset didn't fix there must be something off in the hardware - now you have me wondering though! (the bug had stopped for a bit today... that said the notifications where somewhat intermittent).

Plug into USB
markcr said:
Thanks for the post James - good to know I'm not the only one! For me this only started after installing NoDo. I think your PC USB connection might be right/related as shortly before it happened, I had run the windows update checker again to see if there was a firmware update with the phone connected to Zune... (nodo had run fine for 24 hours before - there wasn't a firmware update so I'd just disconnected). Think the problem happened very shortly after that.
Still very odd that removing the battery and even doing a factory reset didn't fix it!
I have a call in to Rogers now to see if they'll swap the phone... may just be a configuation bug but travelling on business and figured if a hard reset didn't fix there must be something off in the hardware - now you have me wondering though! (the bug had stopped for a bit today... that said the notifications where somewhat intermittent).
Click to expand...
Click to collapse
This does not help all the time, but when it starts that crazy "boinging" sound and the battery icon flashes, plug the USB port into ANYTHING. Charger, PC anything. It will always stop when plugged in, but sometimes, after removing the USB plug, it will remain "fixed" for a while.

My Experience
A couple of weeks ago, this started on night and continued off and on thru the next day so I ran out of battery before I got home.
About a week later, it happen again.
When it happened the third time, I called AT&T Warranty Support. After a hard reset, the battery icon showed I was charging when I wasn't plugged in. They sent me a new phone, which is working fine, so far...

I'm sorry, I know this is an older thread. I had this problem pre-NoDo and it is still persisting after NoDo. Has anyone found any sort of fix, or even just a way to turn off the battery notification? The only thing I've seen is to just plug/re-plug it in, try cleaning the port, and making sure the prongs aren't bent. I had figured NoDo would fix it, but no such luck. Is this more of a hardware issue or a software issue? Thanks for any info.

Hi Kassi - I was fortunate enough to get my phone replaced under warranty (hasn't happened since). My thoughts are this is a hardware issue. Out of curiosity, do you (or the few others who had this issue), use any after market chargers (any cables that didn't come with the phone)?
I had a Monoprice Micro USB cable and wondering if it caused damage to the phone's connector port. The flat side of the cable's plug has bumps on it that are larger than the OEM cable and it makes a tight fit in the focus. I wonder if that somehow bent the port... what makes me suspect this is the problem started shortly after upgrading to NoDo and I'd used that cable for the upgrade.... (thinking it might have even started immediately after checking for a firmware upgrade using that cable...)
While it is handy to have extra cables I won't be using those again!

I have the same problem on my Samsung Omnia 7. Just suddently started happening when I didn't use the phone (many weeks after getting NoDo). Haven't found any fix for this (I'm in the US with a European phone, so a warranty replacement is a little bit tricky...)

Running Mango on the Surround

I just followed the instructions here.
All in all, I'm very pleased with the results. Angry birds is a bit choppy and the 16 bit color still exists. Post here if there are any issues specific to the Surround.

It's actually smooth for a beta . I'm let down with the whole wp7 thing still tho.

Everything worked fantastically (well as good as could be expected for beta software at least) for a day and a half until the device auto-rebooted and is now permanently stuck on the white HTC screen. Whether this was caused by the Mango beta or it was just coincidence I'm not really sure as this screen error usually occurs from an SD card error from what I understand. All part of the game with installing beta software right?

hey lostinbeta,
I had the same issue as u did, i updated my ohone to mango and it worked for 3 days until it randomly rebooted and got stuck at the htc screen, i tried flashing a ROM for OS 7004 and also tried retoring it through the zune software, it restarted my phone and for the next 3 hrs my phone was still on the HTC screen and zune did not throw any error and was still continuing a never ending restoration, pls pls pls help me , thanx in advance

nikhil90 said:
hey lostinbeta,
I had the same issue as u did, i updated my ohone to mango and it worked for 3 days until it randomly rebooted and got stuck at the htc screen, i tried flashing a ROM for OS 7004 and also tried retoring it through the zune software, it restarted my phone and for the next 3 hrs my phone was still on the HTC screen and zune did not throw any error and was still continuing a never ending restoration, pls pls pls help me , thanx in advance
Click to expand...
Click to collapse
I wish I could help, but I could never get my surround working again. I considered it hard bricked and went back to my captivate. I never called HTC about it though, so you can try to see if you can send it in for repair if its still under warranty. No guarantees they wont catch why it happened and refuse warranty service and charge you though.

Did you try to install RSPL/HSPL then install stock ROM?

tuankm said:
Did you try to install RSPL/HSPL then install stock ROM?
Click to expand...
Click to collapse
I did. It just hangs at the white HTC screen forever (well til the battery dies lol) the only thing i haven't tried was changing the sd card inside the phone, but that's because I don't have a spare one and if it was a big enough deal I could just trying sending it into warranty to see if they will fix it for free instead of buying a new card.
Edit: I should say that I did not install an HSPL, but I flashed the official signed stock rom without a hitch.

Fwiw, I have had this happen on one occasion on the original 7004 build. I was able to get it working again, but not before I reflashed. The best you can hope for is to return the device and get a warranty replacement if flashing didn't do the trick.

problems with being stuck at logo screen
Hello All,
I bought my surround used (only 3 months old) and a month later it re-booted several times and finally ended stuck on the logo screen. Tried different methods of reviving the phone listed on here.... called att about warranty, they wouldnt warranty the phone because they said it had 3 sim registered to it, they said good luck but we are not going to help you. called htc and they had me send it in, couple days later, got a call saying water damage and it would be 170US and shipping for the repair. I had them send it back because i wasnt going to spend anymore money on it.
3 months later...
I opened up the phone last night and removed the internal micro sd card, left the slot empty and did a hard reset. viola... it booted up. Now, i was limited because there was no (at least not very much) memory available for photos, apps, or anything else, but the phone worked for calling
Went to the local walmart and purchased a sandisk class4 16GB card for about 30US. Opened the phone back up and installed the sd card and did another hard reset. Phone booted and I checked the memory, around 14.xxGB free after format. I have made 2 updates from zune, installed several apps, texted, called and sync some zune data, setup my gmail acct and sync'd my contacts. Phone has been working great, only 2 days but I think HTC has put in a bad bunch of micro sd cards in these phones because many people have had the same problem.
I just wanted to share this in case anyone has had the same problem. I am lucky as I had the torx and small phillips head drivers to dis-assemble the device.
Hope this helps. -thejaxster

thejaxster said:
Hello All,
I bought my surround used (only 3 months old) and a month later it re-booted several times and finally ended stuck on the logo screen. Tried different methods of reviving the phone listed on here.... called att about warranty, they wouldnt warranty the phone because they said it had 3 sim registered to it, they said good luck but we are not going to help you. called htc and they had me send it in, couple days later, got a call saying water damage and it would be 170US and shipping for the repair. I had them send it back because i wasnt going to spend anymore money on it.
3 months later...
I opened up the phone last night and removed the internal micro sd card, left the slot empty and did a hard reset. viola... it booted up. Now, i was limited because there was no (at least not very much) memory available for photos, apps, or anything else, but the phone worked for calling
Went to the local walmart and purchased a sandisk class4 16GB card for about 30US. Opened the phone back up and installed the sd card and did another hard reset. Phone booted and I checked the memory, around 14.xxGB free after format. I have made 2 updates from zune, installed several apps, texted, called and sync some zune data, setup my gmail acct and sync'd my contacts. Phone has been working great, only 2 days but I think HTC has put in a bad bunch of micro sd cards in these phones because many people have had the same problem.
I just wanted to share this in case anyone has had the same problem. I am lucky as I had the torx and small phillips head drivers to dis-assemble the device.
Hope this helps. -thejaxster
Click to expand...
Click to collapse
Good tip. How long did it take for you to take the phone apart in order to get to the microSD & then put it back together?

[Q] Focus Bricked During Mango Update

Hey guys,
I was updating my Focus earlier today. It went through the process fine until the last restart step of the last update(there were 2 or 3 in total), when it seemed to just hang on the Samsung loading screen. I left it for about 10-15 minutes, but I had to go catch a bus so I had to unplug the phone and go.
Bad choice on my part. Reading online after the fact informed me the Focus could hang for a while on the Samsung loading screen at that step of the update. And now, since I interrupted the update process, its been bricked for me. Whenever I turn it on, it just stays on the Samsung loading screen. It will not be recognized by Zune, or my computer at all. I can get it to go to the hard reset screen, but nothing seems to come of that (I let it go for intervals of 15 minutes, as a few sites advised, to 45, with nothing occuring).
I'm trying leaving it on the Samsung focus screen for a few hours. If that fails, I'll leave it on overnight in the hard reset download mode. I dont have much hope though, and I'm wondering if any of you guys know anything I could try to fix it.
Thanks a bunch.

I'm pretty sure you can get to download mode and flash one of the original focus roms. Just head over to the Focus development section and reflash the rom. Make sure you flash the right one in regard to rev version. The thread will give you all the directions you need.
Figured i'd include the link just to make it a little easier. I hate bricking phones haha. Good Luck
http://forum.xda-developers.com/showthread.php?t=1131022

I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.

neibl said:
I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.
Click to expand...
Click to collapse
The low storage issue from adding a mSD card would have been resolved with a simple HARD RESET.
Right now you need a backup of your phone, made before the flashing with Omnia bits. Someone else had this issue, read here. This is also for the specific thread you opened here.

*noob*
My phone froze during the update for 7.5... Zune gave me an error code but wasn't able to write it down. The phone froze on the left arrow and the red "do not remove" symbol for about 30 mins before i unplugged it and turned it off. When i turned on the phone it stayed on the samsung logo and did nothing. i did a hard reset i still got the same thing. Then i took out the memory card and reset, still the same stuck on samsung. Then i called samsung and the walked me through a reset/reformat By pulling out the sim card then Holding down the camera/volume/power at the same time until it vibrates then after just hold down the camera and volume down, click the windows icon to reformat, still stuck on the Samsung logo!!!!
I'm going to try this flash thing... We will see how it goes i'm a noob

Interesting Samsung gave you that advice.
First thing you should have done is connect it with Zune started and it should have continued the process as long as there wasn't a fatal error.
Flashing UCJK2 should work in your case (assuming you have 1.3 hardware).

Flashing any and all ROMS will not work, keeps freezing at the samsung logo screen after seeming to finish, can't get god damn phone to lauch up, then I could connnect it to zune and exhaust mroe resources. samsung just sent me a bad phone and it stinks.

neibl said:
Flashing any and all ROMS will not work, keeps freezing at the samsung logo screen after seeming to finish, can't get god damn phone to lauch up, then I could connnect it to zune and exhaust mroe resources. samsung just sent me a bad phone and it stinks.
Click to expand...
Click to collapse
As I said and the per the info in the thread above, you need to restore from backup. Most likely flashing any rom is not working.
If you tinkered by flashing unknown bits and without taking precautionary measures, don't blame others.

I was not blaming anyone, the only reason i started flashing was because a microsd card ruined the phone down to 15 mb and no matter what method i used to reset the phone it would not leave that state, i tried for month before resorting to drastic flashes.
It does not matter anyway what is done is done, just exploring if there is any moving forward. If restoring is what I have to do to have a chance, is there any way to restore without being able to connect to zune. Also I do not have a backup is there one available anywhere?

neibl said:
It does not matter anyway what is done is done, just exploring if there is any moving forward. If restoring is what I have to do to have a chance, is there any way to restore without being able to connect to zune. Also I do not have a backup is there one available anywhere?
Click to expand...
Click to collapse
Zune creates backups of stages before the last update. If you're on Mango, you should have a NoDo backup in Zune. There is no way you can restore without Zune. You can check by going in Zune (when phone connected), Phone (near Marketplace/Social - top left), then "Settings", then "Update". Now Zune should tell you you have a Restore. Good luck!

[Q] Dell Venue Pro Stuck at Dell Logo

Well the worst has happened...
I have been running a DVP since March w/o any major hassles. Updated to NoDo fine, updated to Mango Beta (legit) fine, updated to Mango fine...
Then last night I wanted to setup my old phone to tether so I took my SIM out and when I put it back in the DVP it wouldn't boot - it was stuck at the logo screen.
I took the battery out and tried a couple of times but it never got past the Dell logo screen.
So having my restore points backed up from previous upgrades I decided to revert back to my previous restore point. I turned it on holding down the volume/camera button and Zune saw it no problem. I began the restore and it got to 49% then gave me an error saying it could no longer communicate with my device! So I started the process all over again and then it gave me a error stating that there is no restore point available!
Luckily I had a backup of my restore point, so I tried again but now Zune is stuck at 0% trying to restore!
Anyway I contacted Dell last night via their website but haven't heard back yet. The problem is that I purchased the device in the USA but I live in Australia so no local customer support! If I don't hear back from Dell soon does anyone have any direct Dell customer service email addresses I could try?
Thanks!

I have same issue! And I can't solve it anymore...
Have you tried to restore your phone with an oldest version of Zune before the mango update for exemple?

No I haven't... I no longer have the phone in my possession.
I contacted Dell and managed to get them to take a look at it (I'm in Australia so not officially supported under warranty). They think that it may be hardware fault with communication port. Anyway it is going to take a few months before I get a replacement model...

OK!
Can you tell me how you contacted them?
I tried many times but I have some trouble, DVP is not supported in France and the US support told me to call Germany support....

Any updates?
I know this is a really late reply, but I have the same problem with my DVP and even used this thread to "unbrick" it for no fault of mine. Had the problem reoccur 2 days later. Same old, same old, for no reason, out of the blue. Did the same things again to restore and took a backup of the entire phone this time using the "WP7 Easy Backup Tool" after installing all the apps. And last night my DVP died again (again 2 days after the last restore). So I'm doing the restore for the third time now and have no idea what the local (India) Dell Service guys will say about it, coz the phone was bought in the US (but it's been less than 5 months, still under warranty there for such things I guess.
Can you please tell me what happened with your respective countries and if you managed to get your phone replaced at all?
Thanks a million!

alienne said:
I know this is a really late reply, but I have the same problem with my DVP and even used this thread to "unbrick" it for no fault of mine. Had the problem reoccur 2 days later. Same old, same old, for no reason, out of the blue. Did the same things again to restore and took a backup of the entire phone this time using the "WP7 Easy Backup Tool" after installing all the apps. And last night my DVP died again (again 2 days after the last restore). So I'm doing the restore for the third time now and have no idea what the local (India) Dell Service guys will say about it, coz the phone was bought in the US (but it's been less than 5 months, still under warranty there for such things I guess.
Can you please tell me what happened with your respective countries and if you managed to get your phone replaced at all?
Thanks a million!
Click to expand...
Click to collapse
You know that probably could be the SD card being bad. I have a HTC HD7 that is doing that when it boots up and through some testing on the HD 7 I found out the sd card is bad. Try putting a new sd card and then reflash the unit. Good luck.

It's funny that all other WP7 handsets that I know of have a key combo for hard reset. With the DVP you actually have to replace the card and reflash it. Thank god someone took the time to post the DVP unbricking thread, because otherwise anyone with a dead SD card would be outta luck.
I'm not entirely sure what this guy is experiencing is a dead SD card, though. Every time I've booted a Windows Phone with a SD card not installed or not seeded correctly, it always booted to a "cannot read storage card" screen.

I just experienced that with a hd7. As any storage device ex hard drives, sd cards, ssd ... they all have potential to go bad in many ways. Bad sectors is one or just doesn't physically turn on anymore , which is what you were describing. Hey technosquid thanks again for the dvp rom you helped me in the other thread.

Technosquid said:
It's funny that all other WP7 handsets that I know of have a key combo for hard reset. With the DVP you actually have to replace the card and reflash it. Thank god someone took the time to post the DVP unbricking thread, because otherwise anyone with a dead SD card would be outta luck.
I'm not entirely sure what this guy is experiencing is a dead SD card, though. Every time I've booted a Windows Phone with a SD card not installed or not seeded correctly, it always booted to a "cannot read storage card" screen.
Click to expand...
Click to collapse
I just don't get how dell could miss that. It's a vital way to "rescue" your phone if you somehow mess it up. Dell should just stick to computer hardware.