6.1 ROMs have SD Issues - anyone find a fix? - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

All of them that I've tried, thus far.
You MAY NOT see this, by the way, depending on your access pattern, but it is DEFINITELY HAPPENING.
The problem is that its really, really ugly - your card's data is slowly being DESTROYED.
When it hits the "wrong" file, you will find out - the hard way.
This is NOT a "cooked ROM" problem - AT&T's base 6.1 load does the same thing (!)
The EASIEST way to find it is to use Advanced Config to move the IE cache to the card, then play a while. Suddenly the device will lock. You soft reset, and all "appears" well. Its not.
How do I know its damaging data? Because it has scrambled my TomTom map files "just enough" that TomTom comes up "No Maps" (!) - but the file names ARE THERE. The signatures are destroyed - it only takes ONE BYTE of change in the wrong place to do it.
Now what the ##$)! is PIE doing writing in that directory? Its not - on purpose.
The RSS reader will reliably do this too.
If you point them at main memory, no problems. Its SPECIFIC to the SD handler.
Its also SPECIFIC to 6.1 ROMs. 6.0 does NOT exhibit the problem, yet EVERY 6.1 load I've tried can be provoked into doing this.
The only fix is DON'T WRITE TO THE SD CARD via programs. Well.... that's not the WORST thing in the world on a Kaiser as it has a lot of internal memory, but....
Anyone know what the #@#$ is going on here - or have a fix for it?
PS: If you think you're not running into this, don't say I didn't warn you when you find one of your files destroyed without warning. I have run byte-wise compares of SD images and the corruption appears to be almost completely random. And yes, its across both SDHC and non-HC cards (2GB) - both are hit by it, and I've got three, all from different manufacturers. This is VERY reproducable and its not hardware either since 6.0 does NOT exhibit the problem.

Quite interesting... which rom build are you using ?

Have tried several - the most recent being the Hyperdragon 11/15 build.
The stock AT&T 6.1 build did the same thing as soon as I switched PIE's storage to the card. Its not instantaneous but if you browse for a significant length of time it WILL do it.
Flashed to 3.29 HardSPL to be able to load the various cooked ones here, all that I've tried so far do the same thing. Flash back to 6.0 AT&T, no problems.
VERY consistent.
I just put 3.28 HardSPL on to see if that changes anything. Can't imagine why it would, but....
Its pretty subtle if you don't browse heavily - if you get a "lockup" with PIE while its set to write to the card YOU ARE SCREWED. You may not know WHICH file got smashed but I guarantee one did. If it smashes the MFT then the fun really begins (the entire card's contents are gone), but I would prefer that to a RANDOM file getting destroyed!
I have run sector-by-sector compares and have found that where it "scribbles" when it happens appears to be completely random.
And again - 6.0 does NOT do it, and if you only READ from the card, its fine.
I suspect that its a "per-event" risk and so anything that runs from the card and writes data back there EVENTUALLY will screw you - its just a matter of time.

Genesis3 said:
The EASIEST way to find it is to use Advanced Config to move the IE cache to the card, then play a while. Suddenly the device will lock. You soft reset, and all "appears" well. Its not.
...
Click to expand...
Click to collapse
thats why it is strongly recommended NOT TO store ie cache to storage card. Keep it on device memory. There is no fix for this problem yet except keeping ie cache on device.

Sounds pretty easy to bypass the problem, eh? Don't store stuff to the card. No big deal. I mean, c'mon, it's not like we're going to run out of memory storing the IE cache on the device.
Beside that, it must only be IE as I've always used the card to store my email and attachments and have never had a problem. However, I am using a 16GB card...perhaps that makes a difference. I've been running various 6.1 ROMs (including some questionable betas) for almost a year now and have experienced ZERO corruption. Also, if it makes a difference, I perform so much data transfer with my card on a weekly basis. Pretty much filling and emptying about every third day.

It is NOT only IE.
The RSS reader that is in there (RSSHub) that HTC stuffed in the later roms does it too.
I managed to trigger it last night with RssHub; thinking IE was the only culprit cost me (another) reload of my SD card.
Be careful - if its per-event risk then ANYTHING you store on the card (e.g. pictures, etc) could cause it, and apps like TomTom that write places you set as destinations to as a cache can cause it too - its just that being data dependant the more often you write, the higher the risk.
BTW this is a 6.1 issue that does NOT affect the Wizard - I have had a custom (I cooked it) 6.1 ROM on my Wizard for six+ months without a single screwup. But I've yet to find a 6.1 ROM for the Kaiser that DOESN'T have this problem.
BTW, is there a 6.1 ROM around WITHOUT the new PIE? God I hate the new format on that thing...

I have been beating on PIE stored on the card, plus RSS stored on the card now for over an hour - after loading HardSPL 3.28 (was running 3.29) and SO FAR I haven't had it happen.
Now this doesn't mean much, but that I got a solid couple of hours in without it blowing up - when I was pretty reliably able to do it previously - might be significant.
Or maybe not.
I'll run this way for a week or so and see if I can get it to misbehave.... I have card backups

yah i have learnt to back up my sd all the time cause im CONSTANTLY getting corruption..but corruption i can see like messed uop names and folders which ive found more consistant when i have sd power settings set to enabled in advanced config..

I have also witnessed RSSHub destroying my card several times
I remember this problem when WM5 came out on the Artemis. It was linked to the power state and the device going into sleep mode. It never occured when you used the power button, only when it went into automatic sleep. I think there are options in schaps advanced config regarding this - might be worth a try.

Genesis3 said:
Have tried several - the most recent being the Hyperdragon 11/15 build.
Click to expand...
Click to collapse
I mean CE build number and aku. We have now many available builds from which to choose, and we could investigate whether it's a problem related to an HTC driver alone or if there's something in the SYS services too which has to be patched. I'm not talking about workarounds at all.

20931.1.5.0 (assuming the SYS and XIP were ported)
I don't have the numbers from the AT&T load handy.
Downgrading the SPL MAY have fixed it. I haven't had a lock/trash since last night when I changed the SPL. Hmmmm..... that "hotfix" may have been a "hotf$ck" instead.
Will update as/when I learn more.

This is NOT WM6.1 problem, if anything - it is WinMo's problem in general (all versions).
I have witnessed exactly same problem on WM 2003, WM2003SE, WM5, WM6 and WM6.1 - and I bet its the same on WM2002 and WM2000 (I just never had any of those ancient devices).
Solution is very simple:
DO NOT move IE cache to SD card, that's all.
Unless you have to (i.e. my iPAQ 6515 have literally no space left on Main Storage and I have to use SD for IE cache etc) then simply make at least weekly backups of your SD on your PC, its not a big deal, but it is annoying like hell (specially when it happens "on the road").

I have same problem several times!
Most offen it's happend in A***OS Smart Rom (don't remember full name), then i flash into wm6.1 off and it happends only one time. I use StorageTools to ix My Card after that (not data, only card)...
Is this heal????

Just use Opera browser. I dont have that problem in my tilt, although i did had problem with hermes, and scan and fix errors for the card made it go away. And i also a 2GB card, maybe it is an issue with higher storage capacity cards.

hi there, i have similar problem with my vario 3, i have installed all my application on sd card including tomtom. I have about 500 mp3 and pictures. i can listen to music all day at work but when turn my tomtom on, it says no maps found and then everything disappears on the sd card. it still shows in memory status that i have used 70% of my sd card but it doesn't show anything in win explorer.
i think it might have caused by installing tomtom on sd card.
can anyone help please?

mohsin_75 said:
hi there, i have similar problem with my vario 3, i have installed all my application on sd card including tomtom. I have about 500 mp3 and pictures. i can listen to music all day at work but when turn my tomtom on, it says no maps found and then everything disappears on the sd card. it still shows in memory status that i have used 70% of my sd card but it doesn't show anything in win explorer.
i think it might have caused by installing tomtom on sd card.
can anyone help please?
Click to expand...
Click to collapse
To recover that files you can use de windows tool error checking that will recover your files but to the found.000 folder (hidden), but the files are useless because is will be on the wrong extension and name
you have now 2 solutions:
1 - is guest the extension of that files and rename it
or
2- use the program named "getbackdata for fat" and it will correct the name and the file extension but not the correct name of the folder where it was. but better than nothing.
hope i could help

I saw this many times with RSSHUB - finally moved to main mem and have not seen it since. I also don't use PIE. It will be interesting to see if its 3.59 causing the issue, please keep us posted. I went a bought a new card thinking that it was a bad card:

If you're running 3.29 get it off your device - in fact, there should be a WARNING on the page for the various HardSPL versions. This may be device version specific (are there multiple hardware versions of the Kaiser as there are with the MDA?) but on MINE, 3.29 does this repeatedly.
I have now been running 3.28 for a week with ALL power management enabled, RSSHub and PIE caching to the storage card, and all my user-loaded apps running from the storage card, and I have been intentionally pounding the everloving hell out of it to try to get it to misbehave.
ZERO ISSUES.
The ONLY thing I changed was the SPL. I didn't even reflash the ROM (just the SPL) when I changed it - just used Jump to get back into the "superCID" mode and flashed 3.29 down to 3.28.
If you're running something other than 3.28, try 3.28.
So far, one week in, it has completely fixed this problem on my Kaiser.

Genesis3 said:
If you're running 3.29 get it off your device - in fact, there should be a WARNING on the page for the various HardSPL versions. This may be device version specific (are there multiple hardware versions of the Kaiser as there are with the MDA?) but on MINE, 3.29 does this repeatedly.
I have now been running 3.28 for a week with ALL power management enabled, RSSHub and PIE caching to the storage card, and all my user-loaded apps running from the storage card, and I have been intentionally pounding the everloving hell out of it to try to get it to misbehave.
ZERO ISSUES.
The ONLY thing I changed was the SPL. I didn't even reflash the ROM (just the SPL) when I changed it - just used Jump to get back into the "superCID" mode and flashed 3.29 down to 3.28.
If you're running something other than 3.28, try 3.28.
So far, one week in, it has completely fixed this problem on my Kaiser.
Click to expand...
Click to collapse
Does this happen with both cmonex’s & jockeyw2001’s HardSPL 3.29?

It happens with the ORIGINAL REAL 3.29 SPL that AT&T is shipping with their STOCK 6.1 ROMs!
That's not one of the hacked ones - that's OEM. I was able to REPEATEDLY lock the device and scramble the card by sticking PIE's cache on the card with the stock AT&T ROM.
I'm near 100% convinced its the 3.29 SPL that is FUBAR'd and not the hacking on it. I don't know why it should matter (its just a boot loader) but perhaps its doing something funky with the SD interface and whatever it does survives ROM initialization during the boot process.
In any event with 3.28 on my Kaiser I have had ZERO ISSUES with SD corruption or freezes of any kind, going on a week now. I've had no reason to reset it - at all - during that time.
I won't call this "conclusive" for another week or two, but given that with my usual usage I wouldn't survive ONE HOUR on 3.29, well, you tell me.

Related

Thought I saw every weird thing in wm6 guess not.

Hi, guys and gals, just wondering if anyone experience this with thier wm6, just the other day my MDA froze and like usually if it does I would have to take out the battery and reinstall it. But this time a very new experience came in, all the programs I installed on my SD card is missing, but I'm able to access the SD card and all the other files are there, except the files in Program folder odd eh? So I try to reinstall some of the programs to my SD card and the same thing happen, no files in the program folder after reboot? Oh yeah and also when I tried to use spb backup to restore a point didn't work too, still the programs that were install on SD card is missing so somehow the files just disappear on the SD card...on the files in the program folder. And now if I try to install on the SD card it still doesn't work.
Rom version 10.2.0.8 WWE
NBD v5.3
happened to me too.
I had this happen to me as well. I blamed it on the battery. I let it drain down to 2 or 3 % which I had never done. I was using one of the MUN variations, not sure which I must admit as I have been flashing almost daily. Besides the missing programs and inability to install either on the sd, or main mem , I was having my first instability issues. It was freezing, restarting by itself and not responding to controls. I flashed with the new crossbow 1.7 and reformatted the card. No problems in 2 days of use.
i've heard problems like this back when people were using wm5. sounds like something got corrupted on your card. actually...something like this happened to me once too...i think i just re-formated the card and re-installed the apps and it worked out afterwards. or if you're lucky the quick and easy...take the memory card out...and then plug it back in after a few seconds...and see if the card functions properly afterwards...sounds simplistic...but for some reason every now and then some cards use to get corrupted...

DON'T do this.. it may help!

Hola....
I have the TP now 4 like 3 weeks....
In the beginning I installed a lot of programs on my STORAGE CARD!
After the installation I had a lot of problems with my device...like the broken screen issue...and the grey stripes....phone flippin...crashing....thinghs like that.
BUT then I did a hardware reset....took the easy way...
setting->system-> erase content..
After my reset I installed all the programs I installed before...
programs like advanced config, diamond tweak,, coreplayer,klaxon, tomtom etc...
BUT the difference was that I installed everything on my phone....
It worked great 4 me!
I never have issues with my phone anymore....
Everything runs smooth!
so DON'T install programs on your card...
It helped me....maybe it is gonna help you!
you might be on to something here!
thanx for sharing.
With the HUGE amount of storage on-board there's really no need to install programs to the storage card anyway. Plus stuff runs faster from internal storage and is still available if the card is ever removed, or if you connect to a PC in DISK DRIVE mode (which makes the storage card unavailable to the phone's OS).
Basically, always use internal storage until you start getting low, then use the storage card, but only for programs you use rarely.
Incidentally I think Tomtom always installs to the storage card, I don't recall ever having a choice to put it into internal storage.
Now that you mention after my "grey screen" issue i've never installed anything on my storage card and my TP is running fine ever since.
I never thought i could be something so simple and like Jim Coleman mentioned with that much memory on the device who needs the storage card for installations anymore
Great finding pensador
P.S. I will publish this on the wiki at the know issue's section
I have everything installed on my phone, and not the card (except TomTom) and I had the broken gray screen thing once about 4 days into owning the TP and never since. Ive had it weeks now.
Jiggs1337 said:
I have everything installed on my phone, and not the card (except TomTom) and I had the broken gray screen thing once about 4 days into owning the TP and never since. Ive had it weeks now.
Click to expand...
Click to collapse
Have you used any Tweak programs??
I have found that if you use any 'Generic' Tweak programs the unit starts to go squiffy..seems a few non-device specific Tweaks from older devices cause problems, especially BT (different hardware and even WM5, 6 and 6.1 specific!).
Just add the known working tweaks for this device via a reg editor ( most Diamond seem to be OK so far) and if you add them one-by-one you will know where problems occur..
Remember, everything on this forum holds the the 'Caveat Emptor' disclaimer..(except you usually get it for free!)
Here, use this from windows when connected via Async if you don't have an internal reg editor (takes up zero room also!)
Search for the thread with Raphael tweaks, before the device was even released someone who got their hands on a pre-release tested out every single tweak from the "Diamond tweaks" thread and gave feedback on if it worked or not, and how much it improved the device. That should narrow it down to the tweaks you should do and the ones you shouldn't bother with.
Thundarr The Barbarian said:
Search for the thread with Raphael tweaks, before the device was even released someone who got their hands on a pre-release tested out every single tweak from the "Diamond tweaks" thread and gave feedback on if it worked or not, and how much it improved the device. That should narrow it down to the tweaks you should do and the ones you shouldn't bother with.
Click to expand...
Click to collapse
Yup can't agree more..
Search and Ye shall learn.
lol, since i owned the TP i already installed everything on the phone itself and not the storagecard.
and like i mentioned in other threads, i have never hed a problem so far.
(still knocking on wood)
even TT works great, no GPS lag or what ever (the maps are on storagecard but program is not).
I have to say that I installed a ton of programs on my Storage card, and never had any issue. I am using a 2GB MicroSd card. Maybe the problem is with larger capacity cards or the SDHC drivers on the mobile itself?
I have the Touch Pro for a bit over a month now and never had any issues with the screen or anything else other than the GPS. Most of my applications are installed on the memory card, except WkTask and Pocket Wakeup. I have also used advanced config 3.2 to alter many settings. I have a 8Gb microSD Sandisk card which I purchased for my N95 many months ago when they first came out, which is formatted as FAT32. I don't know if these help but I guess other factors should be considered, like the SD card's format, it's speed and it's quality.
I got allmost all mt programs installed on the storage card (8GB SDHC) exept the advanced config. and my phone works like like a dream.. ok that was to exaggerate
But I never had any issues with it since I uninstalled sensor lock from the phone.
Farsquidge said:
Have you used any Tweak programs??
I have found that if you use any 'Generic' Tweak programs the unit starts to go squiffy..seems a few non-device specific Tweaks from older devices cause problems, especially BT (different hardware and even WM5, 6 and 6.1 specific!).
Just add the known working tweaks for this device via a reg editor ( most Diamond seem to be OK so far) and if you add them one-by-one you will know where problems occur..
Remember, everything on this forum holds the the 'Caveat Emptor' disclaimer..(except you usually get it for free!)
Here, use this from windows when connected via Async if you don't have an internal reg editor (takes up zero room also!)
Click to expand...
Click to collapse
I used AdvancedConfig to apply the speed boost tweaks as well as various other things, like power saving stuff. I did a registry edit to hide SIM contacts, that didnt save though after a soft reset.
I only had the gray screen once at a restaurant about 4 or 5 days after receiving it. Since then I have had a few freezes, but nothing major. TomTom works great for me too.
Also, something strange, when i got it new, it got very hot like i read on the forum from a few people, but since then, it doesnt do that. It gets a little warm, but not hot.
hey friends,
I installed Google Maps in storage card (4GB HDHC).
sometimes I feel it freezes. I have to close the app and restart it to make it work properly, or I have to do soft reset.
if I will install it in my phone memory, will Google Maps cache consume lot of space?
thehellraiser said:
hey friends,
I installed Google Maps in storage card (4GB HDHC).
sometimes I feel it freezes. I have to close the app and restart it to make it work properly, or I have to do soft reset.
if I will install it in my phone memory, will Google Maps cache consume lot of space?
Click to expand...
Click to collapse
... way to bring a post from last year back into action:[
no it will not you should just install it to your phone , there is more than enough room to hold 15 google maps if you wanted so don't fret about installing things to internal memory.

Kaiser performance: Slowing down few days after flashing

Hello,
Almost a year ago I purchased my Kaiser (an Orange Kaiser) ans started to flash my phone.
I have already used several ROM avaiable here: Dutty (sevearl versions), L26 (SEVERAL Versions), Hyperdragon, Mobile vista, etc, etc, etc. Have already tryed several versions of the Radio firmwares. 1.24, 1.57. etc. Also, have already tried almost EVERY Hard SPL avaiable and so far I had the same problem:
Few days after flashing the Kaiser starts do slow down its performence. For ex: I press the Call button and it takes 40 to 50 seconds to enter in the touchpad screen. Sometimes it don't even enter the the call screen.
It get worst: sometimes I get no signam from the phone even if i'm side by side to a antena (where any other phone have a strong signal).
The only solution: HARD RESET. I mean, after a hard reset it looks like its other phone. Strong signal, fast response.
I can't possible imagine that I'm the only one here with this kind of problem. Does anyone knows how to solve? Does anyone here knows ehy it happens?
PS: I have already tried configurations with diferent programs. I have already tried with and without S2L2, With or without HTC Home (most without), With and without pocket launcher, with and without today agenda and SPB calendar. Can only think that this is problem with something in the ROM or the radio since every single configuration had the same performance issues.
Can someone please help me?
Thanks
Dandare
I had a faulty SD card that was giving me similar problems to this. I think it was due to Coreplayer and Audio Manager scanning the faulty SD card for music and the read speed was really really slow on the card. Everything would grind to a halt. I bought a new card and everything was fine after that. You could also try formatting or removing the SD card to eliminate the card being the source of the issue.... but you'll probably turn around a say you don't have an SD card
Good luck...
Yeah recently I got this issue. The filesystem on my SD card for corrupt somehow, and I was unable to access anything on it via activesync (my pc) and my phone.
So I just installed some prob( i forget the name) and formatted the SD card, then re-flashed. And since then it's been quick as can be
Hey guys,
I've been having this issue as well. I have not found it to be my storage card as i have tried 4 different cards. i have put the cards on my BJII and it works without issues. I also have found that with some of my early L26 Flashes i would just ride it out and it would work again.
However i have not had my HDIII Pro for that long but i'm hoping that it would would do the same.
If someone does find a link to what is really going on i would greatly appreciate the advice.
Thanks
Also, I actually believe if you text message a lot (i mean basically excessivly) as my brother does, the device will slow down.
He has my older Hermes, and he has unlimited texting, but within 2 weeks he would have sent 1500-2000 text messages and recieved about the same ammount.
By that time his phone would start lagging and being a pain, so I would usually just do a new flash (or hard reset), since deleting that many texts normally would probably take 48 hours haha.
Anyway when it gets re-flashed everything runs normal and fine. But whenever the phone gets cleared everything is smooth again
So maybe it's the amount of text/emails you have? Idk
Going to test the SD card. I have a 4Gb SD card but I'm actually only using 1,4 Gb, so I can use a 2Gb with no problem.
This going to take a while since the phone starts to slow down after three or four days, but I'll let you guys know if it solved.
Thanks!!!!
stuff said:
Yeah recently I got this issue. The filesystem on my SD card for corrupt somehow, and I was unable to access anything on it via activesync (my pc) and my phone.
So I just installed some prob( i forget the name) and formatted the SD card, then re-flashed. And since then it's been quick as can be
Click to expand...
Click to collapse
If you have a vista based machine, It will correct the filesystem errors automatically, and you wont have to reformat...
Works great for me, My desktop is VU64, and my lappy is MCE2005. All the flashing happens on the laptop, and transferring files to the SD (Music & Movies) via WMP happens on the desktop.
Idem
I have same problem.
I try to found confirmation in italian dedicated forum , nobody has had the same problem.
After any minutes where the kaiser freeze , i do not have the same problem.
As is autoconfigured.
Now i used selfmade rom (by official italian rom, and hardSPL 3.29).
Sorry for my bad english

*resolved* sd card works again

since i bought my universal, it had maxstegi's german wm6.1 on it. it was becoming slower and slower, so i hard resetted the device with my 16gb sdhc card inside. apparently that started the problem. after the hard reset i couldn't get the card to work anymore.
since it possibly could have been rom related, i recently flashed thing's wm6.1 build 21127 v2.21 and still, i can't get a single sd or sdhc card to work.
is it possible that i actually harmed the hardware sd card slot by simply hard resetting, or is there any chance that there is a software solution to this. i wouldn't wanna open the device unless it is absolutely necessary and a sure fix to the issue.
thanks in advance for your help. if you need further information, please point it out.
It happened me long time ago but on that case my flashed-inside sd card did not worked again.
I done doc format then flashed another ROM and a new sd card was working perfecto.
i'll try a doc format, then. i just saw, the extended rom appears as a storage card, because i unlocked it in the previous rom. i guess a doc format would hide and lock it again, right?
i once used mtty to format my blueangel, and there the extrom partition was restored as well.
EDIT: no, that did not work. the extended rom is stil its own partition and nothing changed about the sd card recognition. is there any way to lock and hide the extrom again, then i would restart the process, doc format, flash, see again
Shame to hear not worked, perhaps if you PM Tomal or Thingonaspring they will be able to help you in deep.
Hope you get solved your prob soon
have you checked your sd card first? try to read/format it using your pc (card reader), otherwise, insert it to other ppc if it will be recognized. that way you could isolate if its a ROM or sd card issue....just my cent .. regards
of course i checked the cards first. i have no other phone to test the 16gb, but it works well in my pc, and in case it was just the sdhc driver, i tested normal 2gb sd cards too, e.g. the one from my blueangel. i suppose it could have something to do with the unlocked extrom, since it happened to more than just one rom too. let's face it, after upgrading (now to thing v2.3) the only software related things on the phone that did not change are the radio rom and the extrom partition, and since the extrom shows up as a storage card, i guess this would be more plausible.
back on the blueangel there were two extrom tools (see my sig) repart_doc and the unlocker. while the repartitioning does not work for the universal, at least i thought there was a proper unlocker somewhere offering the 4 options (unhide, unlock, lock, hide) but all i can find are tools to unhide and unlock it.
i want to go back to factory defaults, with hidden and locked extrom, maybe that will make the device read normal sd cards again, and if i re-upgrade, i will get sdhc support back.
does anybody know, where i can find a BAKED o2uk wm5 rom WWE? with radio and extrom and everything? maybe that will straighten things out.
I have this ROM: xda_exec_upgrade_v113188 WM5
Le t me know if this works for you and I´ll upload it for you
while i would have preferred that one, i took the imate WWE rom from the wiki (most of the others are down.) and actually, my plan worked. muhahaha.
i downgraded to a shipped baked rom, normal sd cards work, upgraded to thing's v2.3, now everything works.
now all i need to do, is upgrade the radio again and everything is back to normal.
Glad to know all is ok again
Remember to take out your sd next time
i still think it's strange. i never flash with the sd card inside or the sim card. i mean i write tutorials and always include that, because i saw the troubles people get into, when they forget to take out the cards but i never had trouble with an inserted sd card during a hard reset, in fact, for the blueangel, i always recommend it, because that's the way to install the custom extrom on the BA.
but whatever really caused it, i'm just glad it is resolved and not a serious hardware issue. spare parts are too expensive and i don't like opening the devices.
it has been repeatedly advised (wiki and tutorials) to remove sd and sim cards before flashing, which i did for fear of bricking my uni if i will not... but that was during those days when im still crossing my trembling fingers while doing the process
at present, (or since tomal's 7.7 as far as i recall) i remove it no more and simply flash whatever ROM i wanted to try, and no serious problems encountered for not removing it...
IMHO, card removal is not really the rule of thumb for that matter ..but of course there will be no harm if we observe such advice coming from experts. regards..
phezthie
Hello,
I seem to have the same problem with my SD card reader (doesn't work on any card I could try). I read this thread, but I am kinda noob and I am afraid I don't get it.
Could you please give some step by step instructions how to do what Chef_Tony did? I really like the XDA Exec, but this SD problem bugs me a lot. Thank you very much in advance and sorry to bother you with this n00byrequest.
I always flash my Uni with SIM and SD cards inside, no problems so far (2/4/8 GB cards), may be it depends on different devices

[Q] task rpcrouter:15 blocked

I have a HTC Fuze (AT&T GSM). I followed the instruction on (http://forum.xda-developers.com/showthread.php?t=951981) for FRX06 but it keeps getting stuck at "task rpcrouter:15 blocked for more than 120 sec". It never gets to the calibration screen... I even tried downloading and using a pre-made ts-calib file but the results were the same.
I also tried numerous other posts ROMS (FRX03, FRX04, XDAndroid 2.2 (rel 1.6).cab, even tried XDAndroid 2.1 (rel 2.5a).cab) but I still get stuck at the "task rpcrouter:15 blocked for more than 120 sec" error.
I read in another post back in Feb 11 that it was an issue and someone acknowledging it is an issue but no solution stated in the 19 pages of forums. Another user states this is a "bootloop" but did not offer any solution.
In any case, I never got to any graphical screens - never got past the text screens (white text on black background).
Help!
Actually the fix was to delete the data.img but that would be the "quick fix". This WAS mentioned under the troubleshooting section of THIS post. If you really want to see the calibration screen, download an older kernel package as stated HERE.
BE SURE TO SAVE THE FILE CALLED ts-calibration THAT YOU JUST CREATED!​Additionally, I want you to format your microSD and start over from scratch. Just to flush out any other issues that you and may not encounter; such as the "waiting on SD card" issue some complain about. When I say format, I mean use something other than windows to format your microSD. I use the free version of partition wizard and it seems to do the trick. IF you want something a little less program intensive, I would suggest using SD Formatter. Again, not required but it might help solve other issues you may encounter on down the line.
All of that being said, I have a RAPH110 aka at&t Fuze, so I know this process works. If it doesn't work for you, YOU are doing something wrong!
Also, if you insist that you would rather skip the calibration screen, you may use my ts-calibration file. Make sure you place it where the file called haret.exe is.
CLICK HERE for your viewing pleasure!
Same problem with FRX06 even after FORMAT with OVERWRITE of the microSD. I included the ts-calib file. Got past "Creating a new Data Store" then got stuck at "mdp irq is already 4 4 and above mdp_dma: busy" where it would retry after getting stuck for 120 sec.
I then reformatted again and this time tried "XDAndroid 2.2 (rel 1.6).cab". Got to "Creating a new Data Store" and it is stuck there for over an hour - so I gave up.
I then tried deleting the files for "XDAndroid 2.2 (rel 1.6).cab" and this time tried "XDAndroid 2.1 (rel 2.5a).cab". Same issue.
Next, I tried loading Android on the Device instead of Storage Card. Stuck at the same point... I waited 5 min then quit.
I read elsewhere possibility of problems using micro SDHC cards... do you have a microSD card in your Fuze? My card is a Patriot microSDHC 8GB.
As always, there may be a bad batch but have had no such luck with buying PNY nor SanDisk. You did download 1231 as mentioned earlier, correct? So, if you want to try that first, you'll need to delete the existing modules-xxx and zImage file and extract the contents of the downloaded file till you see the modules-xxx and zImage_xxx. Rename the one called zImage_xxx to just zImage and be sure to place them with the file called haret.exe and launch haret once more. Keep in mind, downloading the kernel packages may not be required but in order to test things out and to see what works best, it is. Good luck my friend!
So I tried again and let the install run overnight (>4 hr). In the morning, it was still looping so I stopped it. Today, when I looked at the microSD, I see 171 FSCH0xxx files... most are 32K. 170 was 192K and 171 was 1.81M total of these files were about 158MB. Does this indicate anything?
Anyway, I reformatted my microSD card twice using the SDFormatter (Overwrite, Size Adjustment on), loaded FRX06, replaced the set with the 2 files you sent and renamed the zImage file. Booting up, goes into text screen, still get the timeout error. This time I noticed that there was a line that says "INFO: task dd:91 blocked for more than 120 seconds." My guess is that it's creating those FSCK files again... meaning SD card errors?
Have you another microSD to confirm whether it is a bad card? I just started from scratch (for the 50th time today) and I am NOT seeing what you are seeing(I don't see any FSCHxxx files)... I don't suggest trying anything older than FRX06. If anything, I'd suggest you see if you can find another microSD and probably only use that card for temporary storage.
OK, I'll have to go get another card this weekend then. I do think it seems like the card has some kind of compatibility problem... what brand are you using?
For tonight, I've formatted the card twice and then am trying the "XDAndroid 2.2 (rel 1.6).cab" now... It is stuck in the "Creating a New Data store" line for >20 minutes now... (FXR06 passes that but gets hung up trying to fix the file system). I'll wait a while longer and see if it will miraculously finish creating the new data store.
Thanks for your suggestions.
I have a PNY and SanDisk both 4GB class 4. I think bestbuy has the PNY one for like 30 bucks (maybe cheaper?)
I don't know what the problem is but I'm willing to help out how ever I can
I downloaded MiniTool Partition Wizard and deleted the microSD card's partition then recreated it. Then, I recopied the files into the root of the microSD, installed into my FUZE, and clicked on herat... this time it got into the Android graphical portion (no calibration needed since I included the ts-calibration file), stayed at the ANDROID screen for a while then went blank. I waited about 6 minutes then turned it off. When I went to see what's inside the microSD, I found the data.img file 256MB and also messed up file system again - since I shut it off prematurely.
With a lot more confidence this time, I repartitioned the microSD again, placed my Android files under its own folder. Crossing my fingers...
Ah, so you've been using the file path method then? If that is the case all one would need to do is put rel_path=FRX06 in the startup.txt file, between the quotation marks. Additionally, if you prefer more ogranization and plan to run more than one build at a time, it is best to have that command in your startup.txt file for each build. Keeping in mind, once you do this, it pretty much sets the default path for that build to that particular folder. I wasn't aware that you were starting one folder deep, my apologies . It's best to use the root folder for troublshooting and what not. I prefer to only use one build at a time because I find it easier to keep problems isolated and it helps me troubleshoot at the same time.
Additionally, if you want a more easier way to troubleshoot Android issues and you don't mind waiting for the data store (aka data.img) to be recreated at boot time, then one would only need to delete the data.img file (keep in mind if you have any settings or contacts, these may be deleted as well). What I usually do is once I get a good data.img, I make a backup and zip them up (or use your method of archiving). I also make a backup before I make any changes, like if I am testing out a new rootfs or kernel package. Most of this has been discussed and mentioned in the Android forums.
That did not work so I reformatted again and went back to using the root of the microSD for Android... FRX06 was stuck on GUI but blank screen all night - I turned it off in the morning. Back to the drawing board. At least I got the microSD issue figured out... on to the next mystery.
Update:
OK, partitioned my 8GB to 7GB FAT32, 512MB ext3, 512MB linux swap. Loaded FXR06 into the root folder, booted and it works this time. However, once into Android, it would lock up.
Case 1: Boot up android, clicked on Gmail, screen is android but nothing in the screen except background. Took out battery to turn off.
Case 2: Boot up android, left it alone, screen turned off - will not wake up. Took out battery to turn off.
Case 3: Boot up android, went to settings to set up wifi, froze. Took out battery to turn off.
Case 4: Boot up android, went to settings to set up wifi, entered WEP key, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing). Took out battery to turn off.
Case 5: Replaced the modules and zImage files to the new ones you sent me (12/31/2010)... booted up android, went to settings to set up wifi, entered WEP key, shows connected, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing).
Seems my Fuze is locking up soon after Android boot. Tried numerous times... left alone, freeze. Tried calling, freeze. It seems to be time based. So close...
Strange, though, as the phone remains warm to the touch despite being frozen for some time.
Yeah, you lost me at partitioning your device as I don't even touch that stuff. I think you are using something different. Sorry but I can not help you, my friend!
Thanks anyway... the partitioning is just to make the partition "different". Probably no relevance unless it allowed me to exclude some bad sectors from use. As far as Froyo, I guess there is some kind of HW or SW problem with my phone. I may reflash my Fuze to another WM ROM - just to clean it up and isolate SW as the problem.
Let me clarify, I don't partition my microSD because XDAndroid builds simply do not require this. There are Neopeek variants that require partitioning of the microSD but I still think your method is slightly over exaggerated. I'm not sure why but I guess for some reason there may be an issue with your microSD and partitioning may be a way around this issue but I don't know enough about partitioning microSD/non-volatile flash. So, I couldn't say for sure...
Ok, so I installed Tael ROM (WM 6.5) then tried installing, it still freezes after 1-2 min of booting up (or during boot up). So it looks like it's a hardware (phone or microSD) issue for some reason. I guess hardware vs thinking kernel because the 2.1 installs also do not work.
On another note, it seems that the Android boot process corrupts my other files... I have folders for GPS and photo (DCIM) and it "corrects" those errors and kills my files.
Hmmm... I can't say for certain as I've never experienced that issue. All of my files remain intact before and after booting into Android and rebooting into winmo. Are you talking about the files on your phone or microSD. If you are talking about your microSD, you might be experiencing the hardware issue and the while you boot into Android, it is only attempting to "fix" these issues and in the process, kills the files contained with-in. Does this makes any sense?
Yes, the files are those I mentioned are in my microSD. So, yes, looks like some kind of interface issue causing Android to think the files are corrupt and then try to "fix" them. Strange though that WM does not try to fix the "errors".
I think it's kind of like the linux way to make sure there won't be any issues when you run the OS, since Android would run off the microSD and not from the phones storage. Currently, there is some development for this called NAND. Still really nothing solid as to whether it will work or not but always good to know, I guess?
Well, the thing is those files are pictures/videos/GPS maps... so I think WM is able to read them (so not an error) yet Android does during its pre-boot scan. Anyway, since upon successful scan and android actually loads, it would freeze in 1-2 min, so the problem may not be limited to the microSD. Yeah, perhaps the NAND will work better. I did get Warm Donut to run on my old Tilt, so I am still hopeful.
The issue that is stumping me is that I'm not experiencing the same issues you are with XDAndroid and I'm not sure how else to help aside from using another microSD to confirm an issue with your current microSD.. sorry

Categories

Resources