broken SDCard - how to fix? - Desire Q&A, Help & Troubleshooting

My HTC Desire started misbehaving earlier in the year, it would crash and reboot, when it rebooted the SDCard would not be detected, a few days later, it would crash again and the SDCard would re-appear.
When it was visible, the SDCard would work ok a long as you didn't use it much, listening to music for any length of time would cause it to fail again. The SDCard will stop working a day or so after boot, all by itself without any use.
Sometimes it was visible but apparently needed formatting (which isn't true). The card tests fine in computers and I've used two different cards with the same issues.
I figure the issue is with the SDCard controller, although I'd like to get other's views on what the issue might be. I'd like to repair the phone by replacing whatever is necessary, but my knowledge of the hardware build is non-existant right now, could anyone advise where I might start?

dnel said:
The card tests fine in computers and I've used two different cards with the same issues.
Click to expand...
Click to collapse
Do the cards misbehave in recovery also? Have you tried a different rom ?

handy5876 said:
Do the cards misbehave in recovery also? Have you tried a different rom ?
Click to expand...
Click to collapse
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I've wiped and reloaded the rom, recently I successfully updated to the latest Cyanogenmod 7 but the procedure is too risky if I lose the card while flashing so I wouldn't do it again.

A link for HTC Desire disassembly if you are up to it
http://www.formymobile.co.uk/desiredisassembly.php
Never opened my desire. More details in this Nexus one teardown also http://www.ifixit.com/Teardown/Nexus-One-Teardown/1654/2

dnel said:
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I/QUOTE]
check the contacts first before doing a disassembly . it might just need a spray contact cleaner on both card and phone.
Click to expand...
Click to collapse

or you could try this before disassembling your phone http://forum.xda-developers.com/showthread.php?t=691187
it might be an "usb brick".

Thanks for the replies, I decided to try a few things before I took a screw-driver to my phone and so far it's good news but I'm not sure why...
I remembered that a couple of weeks before the SDCard failed, I used alpharev to s-off and flash hboot to CM7r2. So a few days ago I reverted this change.
I re-flashed the stock hboot and then switched from Cyanogen 7.2.0.1 to the last MIUI gingerbread. This process nearly bricked my phone, at one point it wouldn't even boot into recovery and then the 4GB SDcard I was last using in the phone failed completely, but interestingly it failed while it was in my computer and not my phone. After this I switched to a 32GB class 10 SDCard that was in my phone when the SDCard originally started to misbehave so although the 4GB SDCard failed I don't think this is related to the problem because the problem presents with both cards.
After I flashed stock hboot and loaded MIUI, the problem hasn't presented itself, not once.
I then flashed back to CM7r2 and reloaded MIUI and the SDcard worked but I couldn't install any market apps, complaining of a lack of storage. This is with nothing in /data except for the dalvik cache and 250MB of "free space".
I then flashed to the Data++ hboot and reloaded MIUI and the market now works and the SDcard is working.
I don't know how the partition table on the MTD may have caused my SDCard to fail, the best I can guess is there is some bad memory area which when CM7r2 is loaded, corrupts an important system memory area.
I'm leaving it stable right now and will see whether the problem arises again before making further changes. I would be interested to know if there's any fsck-like apps that I could used to check the MTD for errors?

Related

[Q] Help with reboots

I realize this is a *common* problem but I can't find any way to resolve this! I have been searching the forums for reboot threads and haven't been able to solve this problem yet. I am quite a noob but I apologize for the length of this thread, I'm just trying to be as detailed as possible.
It all started when I flashed CM 6.0.2 stable. It ran fine for weeks and then it started to reboot occasionally on its own. It appears as though it reboots when I am doing something intensive like watching NFL mobile or starting several downloads. I tried the nightlies as well as 6.1 RC2, same problem.
I decided to try another ROM..I have tried Virtuous, Redemptive, and SkyRaider, all of which reboot a couple times the phone first boots after installation and then, they reboot randomly on their own while I'm doing various things.
I've tried the stock and custom kernels for Virtuous as well as King's Kernel BFS #5 with Virtuous. "Stock" kernels for SkyRaider and Redemptive.
Before you say anything of course I have cleared data/factory reset EVERY time before flashing a ROM. I've also cleared cache as well as Dalvik cache before I flash a ROM.
I've tried removing the SD card before the phone boots and it seemed to have helped Redemptive but it still rebooted at one point.
I rooted it with unrevoked 3 but never used unrevoked forever, although HBOOT shows S-OFF, do I still have to use unrevoked forever?
Incredible (AMOLED)
HBOOT: 0.92
ClockwordMod Recovery: 2.5.0.5
Baseband Radio: 2.15.00.09.01 (I tried 7.28 with CM, but it also had the problem, I haven't tried it again since then)
My main questions are:
(1) Should you clear the data/factory reset, clear cache, clear Dalvik, format SD-card or any combination AFTER the ROM is flashed for the first time? Is there something I'm missing here?
(2) What is the most stable ROM and/or kernel. I really don't want to go to stock but from what I remember I never had this problem on stock. I could try it again just to see if it has the problem.
(3) Should I try unrevoked forever, does it do anything differently than unrevoked 3?
(4) Would setting up ADB/logcat help diagnose the problem?
Any other input would be appreciated on how to stop these reboots. Thanks.
same here. i'm running uncommon & KK#5 and i get reboots while listening to pandora and browsing apps.
its gotten progressively worse over the past couple days, not sure what to try. going to try flashing another rom and see how that works
SD?
Couple ideas, and answers to some of your questions.
Answers:
Unrevoked3 does S-Off for you, so you don't have to do that. If it shows S-Off in HBOOT, it is S-Off.
You don't need to format the SD card w/ ROM flashes. If you do, you lose what's on the SD card. This is typically only done once - see below.
Ideas & a question/something to think about:
1] Make a Titanium Backup of all your user apps - also d/l appbrain if you haven't already, set up the appbrain account and sync it with your device. Now you have a picture of what apps are on your device.
2] With the device on, unmount the SD card, power down, and take the SD out of the device. Copy the entire SD card contents into a folder your PC so you'll have them. Format the SD card as FAT32 on the PC. (assuming you are not a mac user, in which case I cannot help...) Put the newly formatted/clean SD card back in the device.
2]Download from ROM Manager + Virtuous' stable stock ROM/kernel (included), but do not install it from ROM Manager. Reboot into recovery. In CWM, not ROM Manager, wipe data/cache & factory data reset and clear Dalvik before flashing. (you have already formatted the SD card, no need to do it again) See if issue(s) keeps happening. If so, try flashing the radio off to 7.28, then do the Virtuous +all wipes from CWM again, reload Virtuous and again and see if the issue keeps happening.
3] Go to Settings>Applications>Manage Applications ~ look thru each/every app and see if one (or many) have a ton of info in their data and/or cache. If so, clear out the data and/or cache in those apps.
4] Once you have a stable Virtuous ROM/kernel, take a look at the handy list of apps you have on appbrain - incrementally in/uninstall them to see whether any of these may be the culprit... If once you reinstall XYZ app on Virtuous' stable ROM/kernel, you may have your culprit.
5] Try a different SD card - solving for whether the SD you have is wonky.
Yep, it's a lot to do, but you want to know what is causing the reboots; ya gotta start w/ a clean slate and diagnose incremetally.
Let us know what worked (or didn't) so others can benefit from your experience.
2] With the device on, unmount the SD card, power down, and take the SD out of the device. Copy the entire SD card contents into a folder your PC so you'll have them. Format the SD card as FAT32 on the PC. (assuming you are not a mac user, in which case I cannot help...) Put the newly formatted/clean SD card back in the device.
Click to expand...
Click to collapse
I noticed that (at least in) Virtuous the browser as well as other apps use the SD card for cache. When I tried downloading files off the internet with the browser then it would crash. I changed the cache location to the phone and then it has worked fine since.
I did as you suggested, unmounted the SD card and then formatted with FAT32. My SD card was actually FAT beforehand, I think I had heard somewhere that it needs to be FAT in order to flash radios so when I was installing 9.01. Although I did have a minor rebooting problem before with 7.28, that may have been attributed to Cyanogen itself since that was the ROM I was using at the time.
So far it has been good but unless I get an uptime of at least 3 days we won't know for sure (that was about the average uptime when I had Cyanogen). If I still run into problems I'll follow your other recommendations. Thanks a lot smtom.
You are most welcome! There's a very good "Official Radio Thread" here on XDA. If you decide to flash the radio (my personal recommendation, but ymmv) read thru that thread before you flash the radio.
Also, I didn't mention, but implied via flash in CWM, to read the notes you see when the various areas are wiped. Why? ROM Manager doesn't show you all the notes, nor can you see what exactly may be erroring, if anything. Flashing in CWM is more cumbersome, but it is a LOT more informative if/when you have issues w/ your device.

[Q] Boot Loop...after memory card change?......Rooted Dinc

I have an unrevoked-forever (s-off) Incredible, running CM 6.0.2 (stable). I have been running an 8gb sd in, but recently I have been reaching the limits.... so I decided to upgrade it to 16gb.
I copied all the files from my 8gb to my PC, via phone USB. Then from my PC to a 16gb card, via card reader. When I unmounted the 8gb, and replaced it with the 16gb, it would not remount. I then started getting low memory warnings....but still could not get it to mount the SD card, old one or new one. So I rebooted and now I'm stuck in a boot loop, with either memory card, for some reason....
I tried a nandroid backup, and it says complete with one line saying "SD-ext.img not found- skipping...." then on reboot, it still goes into a boot loop.
Suggestions on what to try next are VERY welcome. I guess I should have not tried swapping the SD card while the phone was on?? I can of coarse boot into recovery, and I do have ClockworkMod 2.5.0.1.
Worse case scenerio, wipe? and run apply CM from SD card?
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
SynbiosVyse said:
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
Click to expand...
Click to collapse
I have no idea what SD-ext is for...I'm not "scared" of this error, I just want to get out of bootloop....if it's not related or important information, sorry....I assume I messed something related to the SD card....considering how/when this started happening....but of coarse I don't know exactly what I did, that's why I'm asking.
I don't get an "error" screen, I just get a boot loop. I don't even know where to begin to toubleshoot this....so thats what I am asking for...suggestions.
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
SynbiosVyse said:
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
Click to expand...
Click to collapse
The boot loop happens with, either card, and also with no SDcard in. I only get to the Cyanogen animation and it keeps looping......I will try formatting the cards on the PC and then pasting the SD card "copy/backup" from my initial try....
---if worse case----
I have never installed other roms, I have had relative success with CM....so I really don't know how to "wipe" and start fresh.
Are these steps close:
1. boot to recovery> ClockworkMod
2. select wipe data/factory reset
3. select wipe cache partition
4. select advanced> select wipe Dalvik cache?
5. install zip from SD card > select CM- 6.0.2
6. done?
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
SynbiosVyse said:
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
Click to expand...
Click to collapse
Well I downloaded a fresh 6.0.2 and 6.1 RC2 from Cyanogen....I followed the steps above to "wipe" and installed the 6.0.2....result= bootloop still
repeated steps to "wipe" again......selected to install 6.1 rc2......result= bootloop still
SO now I'm really at a loss. I figured with a wipe it would work....maybe my steps are wrong.....ANY suggestions now are welcome.
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
linuxmotion said:
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No I do not know how to use the "advanced from android ask." But I am willing to learn if needed.....Is this the SDK tool? I believe I toyed with this when I first used the Unrevoked method to root....but thats been months and I don't mess with roms much. I started playing around with SDK a few minutes ago to familiarize myself....but idk.....
Is there a simple way to get some kind of log file? Can I load another recovery, like Amon_RA style type, which has some different options....but I don't know if it will help......Thanks for all suggestions thus far.
See I'm not exactly sure that the SD card was what caused the malfunction in the first place.
If you have an AMOLED incredible your 3G radio or battery may be beginning to fail...as I said before the Inc is very sensitive and tends to reboot a lot for stupid reasons.
You can certainly get a log if you use LogCat from ADB, but if you cant figure out exactly whats happening, then most likely you need a replacement.
You can unroot, turn S-ON, and put a stock RUU and see if you still get reboots (I'm willing to be that you will). But if you still get reboots completely stock, since you're stock you can go to verizon now and get a warranty replacement.
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
- what apps had you moved to SD card?
Absent all that, try and d/l a non AOSP ROM, for instance Virtuous, place it on your SD card in Recovery, and see if you can flash it.
Why? Solving for whether the device boots and will load a ROM at all - AOSP ROM's utilize the SD card more than Sense ROMs.
smtom said:
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
Click to expand...
Click to collapse
Correct.
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
Click to expand...
Click to collapse
I did use a rooted app to move things to the memory card, but I didn't see any benefits so I moved it back, at least I selected too, whether the program moved them back or not.....hmm...
- what apps had you moved to SD card?
Click to expand...
Click to collapse
you know I'm not sure I moved apps back. I know again I didn't see the benefit of apps/cache on the SD card, so I moved it back to phone....
------
Status as of 12/06/10 11:18am est.......Things I have done since last posts.
1. I have wiped numerous times via ClockworkMod. And tried CM 6.1rc2. Still got loop.
2. I installed Amon_RA recovery, wiped everything, formatted SD card through Amon, partioned SD card through Amon.....installed Cyan CM6.1 listed above, and phone sat loading at the initial screen "htc Incredible." Let it sit for 10+min....still nothing....
3. Tried to repeat step above...same results, now just initial screen, NO bootloop.
4. Installed ClockworkMod 2.5.0.5. Wiped. Install Virtuous 3.1.0. Recieved an error during install....."E:\" unable to read data...followed by a string of numbers and other info.....
5. Wiped.
6. Installed Hboot 92. (upgraded from 77)
7. Tried MIUI v0.12.3. Rom installed "successful." Rebooted and stuck on initial screen. been 5+ min as of now....
So NOW I am not getting a Bootloop....just a frozen screen. I can still get into recovery, so hopefully I still have options. Your insights or suggestions are the only thing keeping me trying ATM....I'm running out of options of my own.....
Well I still haven't got past initial boot screen with MIUI, even though it said installed correct during flash.....
SO I tried to wipe, and install Virtuous 3.1.0 again. got the same error...wrote it down this time:
E: Can't chown/mod /data/app (operation not permitted)
E: Failure at line 8: set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation aborted.
I'm still at a loss, and taken any pointers or ideas. I may play around with other roms, but idk.
1. I tried Skyraid_333 and had the same results. Locked on initial white screen.
2. Wiped and tried a "stock" rom available from Virtuous.....http://www.virtuousrom.com/p/other-releases.html
It loaded and then it actually booted to the red eye droid (different from my original post which was the CyanMod boot anim)....yay....then it froze (eye stopped moving)....tried booting w/o SD card...same thing....
3. Wiped and decided to try Virtuous again. This time it loaded and installed "completely."
It booted again to the red eye animation....seemed to freeze, but I left it, and it finally started after 5+ min....I finally got a phone back.....
I do not know entirely what I did, in the process of loading all these roms. I do remember when I installed the "stock" rom, listed above, it had an install step which said installing "BOOT." (or something like that) I do not remember this listed step on the other rom installs...although they may do it and not list it....idk....
I have a feeling that the stock rom did something, but I don't know why a "wipe" does not reset everything, and why any rom wouldn't work....So I'm stuck back with HTC sense, due to the time I have been without a phone, I will live with it....I forgot how much I dislike this sense.......
Thanks to everyone who chimed in.
Congrats on you fixing your phone. I am still very new to this myself, but one of the first things I would have done would be install a stock rom again. It sounds like you lost or had some corrupt files which were fixed by going back to stock. If it were me I wouldn't be scared to wipe with a custom rom or nandroid backup, but thats just me.
i'm stuck with a similar problem: phone (dinc rooted, recovery CM 2.5.1.2, hboot .92) currently frozen on htc splash screen -
How it happened:
I was running MIUI 0.6 1.1.28.1, tried to re-format the SDcard to wipe it and start from scratch again. Did not nandroid beforehand (wiping SD) but pulled the 0.6 1.1.28.1 zip to my desktop. Tried formatting but phone wouldn't format it properly - wiped all info from SD, but no longer readable by phone or computer.
Used Mac disc utility to re-format and erase card to FAT32, still un-readable. Phone now only boots to splash screen, recovery works.
Brother has an un-rooted dinc so I grabbed his SD and mounted the card to the Mac via recovery, wrote onto it the MIUI rom I was previously using and did a full wipe (data, cache, davlik) and installed rom - rom installed correctly but still couldn't get past htc splash screen
Gave bro back his SD and tried mine again - got it to mount to the phone by partitioning through recovery, re-installed MIUI rom to my SD card and tried rebooting a number of times, still can't get past the splash screen (15+ mins)
Currently downloading virtuous "stock" rom as posted above and will try to wipe/ flash. It's a huge zip compared to the MIUI zip - maybe that's a good thing?
Here's to hoping.
Have tried flashing multiple versions of MIUI rom, packaged by n_i_x and warttack - no luck on either.
I just flashed the virtuous "stock" rom and got to the droid eye splash YES!! Mine may also be stuck in that screen though on the droid eye.
IT'S WORKING!!!!!!!!!!!!!!!
Can't even begin to say how relieved I am - I'm never getting rid of that magical virtuous zip.
So glad someone had gone though this before me.
AOSP interacts w/ SD
Handy information to know -
AOSP ROMs interact w/ the SD card quite a bit, whereas Sense ROMs not so much.
So, if a new SD and boot w/ AOSP, expect it to be wonky, particularly during boot.
hth
i dunno what caused it but mine has been doing this for about a month. Got my refurbished phone in today so HOPEFULLY that one will work better, but i dont really expect it, as this stupid boot loop issue seems to be a VERY common problem with inc's. I probably wont ever buy an HTC after this one, should have learned my lesson after the touch pro
anyway, even on stock rom, unrooted, with nothing extra, mine does this for no apparent reason

[Q] Half way through flashing rom - need urgent help

Hey, well I made a mistake (supprise). I was following a guide on here and mixing it up with cyanogen's own guide for flashing their rom and well basically I whipped my phone without having the rom on my ssd, i took the ssd out and put it into another phone to put the rom on and now when i put the ssd back in i'm getting:
E:can't mount /sdcard
when I try and install the rom from it.
Suggestions? Please tell me i've not bricked my phone. I only just realised I should have done a rom backup but it wasn't said it the guides I was following and i was so fixated on doing it word for word It only just poped into my head.
Cheers. Fast replies would be nice, I don't like sitting here with my phone in clockwork without anything on it.
:EDIT:
I have another ssd card current set up as a gold card. Could I use that? Both are htc supplied ssd cards.
Ok so i just pluged my gold card in and it could open it. Should I just use that or reformat my other ssd and use that instead?
:EDIT:
in the process of backing up my ssd and formating it, going to see if that fixes my problem. Figure I should probably start a new rom on a fresh ssd anyway.
Be nice to know for future if wiping everything is actually needed for roms
You said your goldcard was recognized correctly by the phone? Did you use another card before?
Where does the error occur, when downgrading or did you already downgrade and are already rooted and want to flash the rom already?
unhallowedone said:
You said your goldcard was recognized correctly by the phone? Did you use another card before?
Where does the error occur, when downgrading or did you already downgrade and are already rooted and want to flash the rom already?
Click to expand...
Click to collapse
I've done everything but the flash so far. I was on the final bit and I had "full wipe" zip on my ssd and it opened fine and then i reset to factory settings and cleared cache and then my ssd couldn't be read any more so I couldn't flash with my rom.
However my other ssd which I had to previously format to turn into a gold card can have the zip's read on it. So I figure if I reformat the ssd I wish to use (not gold card) and put the rom back on it will be fine.
Also can you charge the battery while in recovery? I think my battery must be getting quite low now as it's been stuck in it a long time and was only about 40% when I started. I presumed 40% was enough to install a rom, didn't expect this delay of a few hours.
I'm also presuming I can't boot into anything any more as I think i've wiped the previous rom no?
Ok now after formating it and putting the rom on it says "no files found" :/. Does it even matter if I use a differnt ssd to flash as to the one I wish to use long term? i was under the assumption it would install other things to the SSD but now I realise thats probably totaly wrong.
:EDIT:
Put the rom on my other ssd and now also says no files found. it appears the rom is causing the problems?
Put the rom on my goldcard ssd and now also says no files found. it appears the rom is causing the problems? It could read the zips on that ssd 10min ago
If you did a full wipe you have to get it going again by flashing a new one ^^ So yes, go ahead with flashing. The Goldcard was especially necessary for the DHD to load the downgrade-zip, because when I did that originally it gave me an error (had wrong goldcard). Of course, I now have a working one, still using it.
You could try twice, like 1. reformat the sd you wish to use and put the ROM onto it or 2. use the other one to load the rom. Think about it, worst would be "yo man, wrong card"
Edit: this is confusing, indeed. So you actually did a new format of the SD and tried to open it in CWM and it says NO FILES FOUND?
Just to confirm a few things.
DHD rooted, S-OFF , etc....
Full wipe
Removed SD
SD No longer recognised
Rock > YOU < Hard Place
My suggestion, would be to format the first SDcard in your pc, copy ROM to it, place in the phone, reboot recovery.
unhallowedone said:
If you did a full wipe you have to get it going again by flashing a new one ^^ So yes, go ahead with flashing. The Goldcard was especially necessary for the DHD to load the downgrade-zip, because when I did that originally it gave me an error (had wrong goldcard). Of course, I now have a working one, still using it.
You could try twice, like 1. reformat the sd you wish to use and put the ROM onto it or 2. use the other one to load the rom. Think about it, worst would be "yo man, wrong card"
Click to expand...
Click to collapse
Well aparently neither of my SSD's work. Is it possible to boot into clockwork without going into the software? Ie can i get into clockwork straight from boot? Because I might need to restart clockwork to get this to work now.
andyharney said:
Just to confirm a few things.
DHD rooted, S-OFF , etc....
Full wipe
Removed SD
SD No longer recognised
Rock > YOU < Hard Place
My suggestion, would be to format the first SDcard in your pc, copy ROM to it, place in the phone, reboot recovery.
Click to expand...
Click to collapse
Exactly, but tryed and the moment I put this rom on it apperas it cant read the ssd.
Its cyanogen 7.02 and google addon.
Ok then, my formated ssd (which is apparently empty according to clockwork) formatted and was empty on windows, put the roms on it. When i plug it back in to windows it has all my old **** back on which was several gig so there is no way I accidently copyed that over with the roms and didn't notice.
You can boot directly to the bootloader by holding volume down then pressing power.
Did you download the ROM from ROM Manager or direct from here/cyanogen
EDIT: What version of clockwork you using?
8igdave said:
Well aparently neither of my SSD's work. Is it possible to boot into clockwork without going into the software? Ie can i get into clockwork straight from boot? Because I might need to restart clockwork to get this to work now.
Click to expand...
Click to collapse
Sure, Power off the DHD then hold Volume DOWN and press POWER. It then boots into Recovery.
I dont think you will have bricked it. As far as I know you cant brick a phone by flashing a rom. Bricking is as a result of radio installation gone wrong. If your SD card is being recognised, just wipe it and put in in empty. Then install the desired rom using ADB shell on your PC. About charging in recovery I think it will work. If not just turn the phone off and plug it into USB.
EDIT. This is sounding above my level of understanding now. Ignore my advice. I was assuming clockwork is behaving itself
Downloaded from CM7 them selves, ah ok I will reboot. Yup now neither of my ssd's have data on them apparently.
Rebooted recovery and now not working. I click to use an option and it just goes straight back to the top of the list, even reboot option.
edcoppen said:
Ok first I dont think you will have bricked it. As far as I know you cant brick a phone by flashing a rom. Bricking is as a result of radio installation gone wrong.
Click to expand...
Click to collapse
Or by using CWM 3.0.2.5 to format the SD as I did 6 days ago - have a new DHD now
edcoppen said:
About charging in recovery I think it will work. If not just turn the phone off and plug it into USB.
Click to expand...
Click to collapse
I would suggest power charge instead of USB, because the real charger loads your phone faster due to lower power values over USB. Afaik.
OK, worst case scenario here is having to flash a 1.32 RUU and rooting, ENG S-OFF-ing again. I don't think your at that stage yet. Did you Radio S-OFF before this?
edcoppen said:
Ok first I dont think you will have bricked it. As far as I know you cant brick a phone by flashing a rom. Bricking is as a result of radio installation gone wrong.
If your SD card is being recognised, just wipe it and put in in empty. Then install the desired rom using ADB shell on your PC.
About charging in recovery I think it will work. If not just turn the phone off and plug it into USB.
Click to expand...
Click to collapse
The light on the dhd only comes on when the phone is turned off and charging for me atm.
Ok then how do I use ADB, i was getting real confused by that earlyer today.
OMGGGG I just restarted recovery for the 5th time and it's reading my ssd card!
YES!
:EDIT:
nvm got the right rom.

[HELP!!?!!?] SD Card and Recovery Problems

Here's a lovely and vague one for you all to try wrap your heads around...
Okay, so I started having trouble with my SD card about a year ago after my mate added a partition so I could flash A2SD ROMs (I believe - I was stuck and asked him to sort it and from what I can gather, that's what he did). It was fine for a while, then suddenly it became nigh on unresponsive to Android: I couldn't take photos, install apps to SD, basically any data transfer between the device and the SD storage was not happening. I think this was after I tried to delete some things to make room for videos and **** but I was stuck on about 300MB of the ~2GB available (this may have been my first attempt to delete after the partition, I'm not sure).
That was the birth of a problem I am still yet to fix. My dad needed a new phone and I wasn't using my Desire anymore. He's 53, and so the Sense UI was less than intuitive to him which lead to me offering to make it a bit simpler for him (flash a stock ROM and use a more information-centric launcher). The device badly needed updating anyways as I hadn't done so since my mate partitioned my SD card and some bugs had began to develop on the ROM I was using. So, I downloaded the latest CM build and set about reformatting the storage to see if I could solve some of the issues. In attempting to do so I think I performed a data, cache and dalvik cache wipe which removed the ROM I was currently using. The partitioning was successful, so I transferred the new ROM and attempted to flash - BOOM! Error message. Tried again, same thing. Now I have a phone that'll only boot into a recovery that's 5 full versions old (CM Recovery v2.5.0.7) without a way to flash an update img. I've tried on many different occasions to try and sort the problem and spent relentless hours trying to research a solution to the numerous different error messages this produces. Every error I can remember was a problem with read/write on the SD card, so I purchased a new one to no avail.
The phone CAN'T be bricked, surely. I still have access to things like USB mounting (which works absolutely fine), and most importantly, access to the recovery. Please don't tell me she won't live on, this is my baby and she's going down fighting! :'(
TL;DR SD card read/write issues. I only have access to recovery. I can mount the SD card via USB in CM Recovery, but every time I try to flash a new ROM I get numerous different read/write errors.
Go here:
http://forum.xda-developers.com/showthread.php?t=1408936
There you can download 4ext recovery that can be flashed via fastboot or using some flasher.
When you flash it repartition your sd card, choose only one sd-ext partition (not bigger than 1,5gb), no swap and fat32 for thevrest of your card.
After repartitioning try to flash some rom and see how it will work.

[Q] Rom not installing

Hi
I have a Desire GSM rooted and S-ON RA-Desire v2.0.1 stock HBOOT Ext 4 1Gb latest radio ends in 23
Have been running on a custom rom for over a year now and want to install the latest copy of the same rom. The md5sum is identical for the zip file to the source.
Booted into recovery wiped all data, cache and then devlik-cache.
I have turned off signature verification and then selected my rom zip on SD card.
Installed the rom rather there were no errors and it took about 20 seconds (seemed too fast).
Next in recovery I did a reboot.
Now the screen went white with green HTC logo in centre for about 1 minute then after this a black screen with android written logo for about another 2 minutes.
Eventually phone boots into rom but it is not the new rom it is the exact same old rom.
I can see from applications listed that I am still super user so not lost root.
In settings software information everything is listed identical to what I had before.
The contents of the zip files are different so it is not the same rom being flashed.
Choosen rom is
[ROM][Cool Sense][5 April]Cool Droid v3|2.3.4|FASTEST|Data++/Stock (currently have Icecream sense v2 installed which is an earlier version of the same rom)
I did not install the alignment zip as I had already setup to use an earlier rom version and ext4.
What have I done wrong in trying to install my choosen rom please?
I feel like I must have missed something.
Not sure which recovery you have, with 4ext I boot to recover, format everything except sd then install zip and it seems to work, obviously everything then needs reinstalling from the backup you'll have made
Sent from my HTC Desire using Tapatalk 2
Hi
Unrevoked 3, as I have one of those odd PVT4 Desire phones 4000 erase size using RA Recovery. (something like that sorry if technical references are not super clear).
I use Titatium backup so reinstalling wont take long just need the ROM to install.
This is a fast glitch free rom using sense so I do not want to try a different rom as it gave me a year without trouble. Only doing this to start again with the space issue needing a refresh.
I have cleared delivk cache again and flashed my original v2 rom and that worked showing expected progress reports.
So I thought would try flashing the new v3 rom, and see if I got any joy this time.
Still no joy, it looks like it starts as two lines appear then it says complete with no obvious error.
So I reflashed the original v2 rom again and will go with that as I need a phone more then I need to play.
Odd.
Maybe the new v3 rom needs sOFF but as far as I could read it does not.
Even installing the previous rom things are still not right.
The apps that normally come with the rom are not installed such as Demon controller, No adds and Busy Box. I can see that they are in the zip file they are just not been added.
I can manually install Busy Box from the market so I know it is not a permission thing.
Titatium Backup is seeing my Ext4 partion (it calls it an ap2sd but it is showing) so I don't think there is a problem with my SD car arrangement.
I stupidly do not have a nandroid of the previous install I can restore.
So any ideas please why the previously working and installed rom is not reinstalling fully with all it's built in apps?
Anything I could try please?
Looks like I have identified the problem, my SD card is flakey and Gparted reports sick partion table that wont fix so the Ext4 partion was not been seen which is probably why the install failed and the apps were not installing.
New Sd card will be ordered and then start again.
Thankfully I dod have an uptodate SD card backup.
Phone is working just as a phone for the next few days.
These micro SD cards do not last long at this rate I get 1 year from them as this will be my third ordered.
Go to S-OFF, is better and mandatory for a lot of rom.
New card and more fiddle work with Gparted and now waiting for setup to complete as old v2 rom is installed. It works fast and is smooth plus has HTCsense so I can keep my sync capability so will be staying with it so I can live without S-OFF
Gparted when I followd the recommendations I kept getting a corrupt card on my phone so this is what worked for me.
Format card on phone
Then put card into usb card reader and place in PC
Reboot PC onto Gparted CD
Select SD card and then I resized the fat32 partion already there and then added a new EXT4 partion.
This worked for me.
Dump gparted, format the card through 4ext recovery
Sent from my HTC Desire using Tapatalk 2

Categories

Resources