Develop Bugs

How to revert back to WM after flashing Android to NAND?

Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!

aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?

deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?

Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.

Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...

I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.

Is there an Android OS with everything working on the Kaiser?

Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works

I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.

Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!

I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.

The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.

zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.

Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out

Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?

If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.

I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.

zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.

The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?

Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.

Lingering EVO issues (SD Card, Camera, etc.)

I'm having some lingering issues with my EVO even after running OTA updates. I am running a rooted stock ROM, currently software version 1.32.651.6 (I have not attempted the latest OTA update yet).
In particular are two problems - SD card issues have remained even after the OTA update. This was present even before rooting but after installing the first update (I went to a "full-service" store on opening day and they set it up themselves, assuming everyone would want it - luckily I could still get root). Issues include the Camera application reporting permissions problems randomly when trying to save pictures to the SD card, HTC's music application freaking out and coming to a near freeze trying to crawl the SD card during one of its troublesome spurts, and files disappearing from file explorers. So basically run of the mill, pre-first-OTA sd card problems. But occurring after the update and both before/after rooting.
Second is a problem with the camera itself. When first booting, HTC's included photo/video application will instantly crash after showing the camera icon on the black background. Google Goggles freezes for about 10 seconds then reports it was unable to connect to the camera. After the phone being on for about half an hour, these issues (seemingly) go away until the next reboot.
Last, and least frequent but still troubling, is a problem with the device powering on. At least twice I have been unable to get the device to turn on after powering it off, forcing a pull and replace of the battery to get it working again.
As far as I know, all of these issues could be either hardware or software. Even the power problem - my best guess is that the phone never powers off fully, but is instead locked inside of a deep sleep state and thus can not turn on until a battery pull forces the entire system off.
The questions being - first, are there any known solutions to the above problems? I have found many threads in particular regarding SD card issues, but none that seem to report these problems post-update. The others I have seen little to nothing about.
Second - if there are not known solutions, would it be prudent to return the phone as it may likely be a hardware problem?
Since it seems I'm forced to take the last update if I get a replacement, I may likely have problems getting a full root back. I'd like to avoid that if possible - having root works wonders for doing application development using non-native (unexposed) API's (Which - side note - since I'm developing for 2.1 at the moment, other than hacking for direct access to a Surface, does anyone know of a _fast_ way to do direct blits from native code? glTexImage2d is insanely slow).
Thanks all any help. Again, apologize if any of these are solved and gone problems, but I wasn't able to procure anything myself.

I'd go for the replacement, sounds like a defective unit..
Be sure that the folks here at xda will get root working regardless of OTA.

replace the unit, i'm very particular about my phones, if there is anything wrong with it I replace it.

I too have the SD card issue, I have updated, i have rooted, re-rooted, flashed new rom, different roms (fresh and sd) and it has always given me the sd card issue. Sometimes it wants to be a pain and not work at all, sometimes its good for at least a week or two. I am waiting for a little longer to make sure when I get a replacement its a newer version.

SD card permission errors --- POSSIBLE FIX
I hope/think/believe I fixed this error for those interested, I use my EVO for work and need it to work without a hitch....
Here goes (**Note i am a noob with smartphones with a dangerous amount of IT knowledge - disclaimer for those brave enough to browse around the root files and SD card files; I am not responsible for you bricking your phone, I am only trying to help those in need and putting in my 2 cents_)
Download and open the app ---> Root Explorer (or any other root explorer for that matter) from Android market.
Once Root Explorer is open (look up top/left it will say) Mounted as r/o (means read only) - press the white button to mount it as r/w (read & write)
Press and long hold on the SD card directory (folder) - you will get another window from which you must select the permissions option.
Under top option USER - check all marks -- READ WRITE AND EXECUTE & click OK.
VERY IMPORTANT - Click on the (white button) Mount as r/o to write protect your root files on your phone again.
I just applied this fix about 45 mins ago and seems to be working......updates to come if issues persist or re-surface. (**Note I could not see photos or play music and some apps were also giving me FCs (intermittently) due to permission or write errors to SD card; and now it seems to be working like nothing ever happened.)
What I have ::: stock ROM on EVO supersonic with recent HTC updates applied - standard 8Gig SD card provided with phone / had rooted but put back stock ROM for preference issues.
Hope this info helps some folks...very frustrating issue.
Cheers

SD card permission errors --- POSSIBLE FIX
ONE LAST SIDENOTE COMMENT -
I transfer data to my PC often (running Win 7 32bit_)
It is crucial that you right click on "safely remove hardware" icon on the lower right side (next to date and time) and WAIT until windows tells you
..."It is now safe to remove your hardware" --- I was just taking the plug out when done and it appears as if that could have started or compounded these issues with the SD card.

I too get the could not connect problems at times. And I have lost access to the SD card a few times. Some say its Fring that causes the problem. But after removing it I still have camera issues. I noticed that having the LED Light on while trying to open the camera will cause this problem.
I am running CM6 RC1 so this is to be expected from Release Candidates. Sit tight. It will get fixed.

Well after a full 24 hrs...no issues with the read write error on my EVO SD card, I think that when the phone is removed from PC incorrectly (i.e. pulling USB cable out in mode other than "Charge only" i.e. HTC sync, Disk Drive, Internet sharing - it causes it to "corrupt" the permissions on the SD card - It is still working like a champ and i am waiting impatiently for my EVO Froyo update ... feedback appreciated for those whom tried this fix and had it work....txs

@LF142
Hi there. So I followed all of your instructions above and downloaded Root Explorer. However, every time I change the permissions, they don't save. User, Group and Other is always switched off at root level. Do you think this may mean my SD card is corrupted?
I rooted it with BakedSnack.
I now want to un-root it as I miss taking shots, looking at my shots, listening to my tunes etc.
But I want to keep all my apps. All my texts and everything else. Whats the best way to go about this? I am also a bit of a n00b and I apologize if this is in the wrong forum, but when Froyo releases tomorrow (apparently) do I have to unroot to receive the update?
Thanks

[Q] htc Desire -USCC I think I REALLY made a mess!

I've never tried to do anything beyond readily available 3rd party apps. I've never jailbroken anything or rooted. I don't know how to work with ROM's and I've never used command prompts beyond installing difficult software on my desktop. (I'm using Win 7 on my PC) and I have no linux or coding experience. That said, I'm smart, I research things fully b4 I actually DO anything & I follow directions exactly when i do something unfamiliar.
I bought my Desire about 45 days ago thru USCC. Stock it's running 2.1. On Fri using UnREVoked 3.21 I tried to root. It appeared to work. I have the Superuser file at least...
However, when I followed unlockr.com's tutorials for downloading & flashing ROM's it became obvious that something was not right (screens weren't the same, options weren't the same or even close in some cases, & controls, like pushing power to go back after recovery didn't work.) The screen turned black, I had a minor heart attack & then the phone finally rebooted into it's original USCC configuration.
Now, I DID have an option to "install from SD card" but nothing that said "flash from sd card" and I'm assuming -maybe incorrectly- that there's a difference??
After 4 days of searching sites, I know there are too many posts on USCC rooting & Desire for a noob like me to know what to do. I have a mess that I need help to untangle.
Prior to my failed ROM attempt, I had installed save to sd... which I think may have moved everything to my SD card. Since rooting, I tried using Root Explorer to remove facebook, twitter, City ID etc.... EX: I can see bloatware files on my SD card, and the program SAYS it deletes them, but it reboots on exit and there's CityID again!
I can mount the SD card as a disk drive on my PC and look thru the SD card files. (some of which appear 2B duplicates. When I rooted, I installed the Hboot drivers and followed the unrevoked directions exactly. I renamed the recovery file as update and left it as a zip... but there are now two "update.zip" folders on my SD card. They are different sizes and neither contains all of the files of the other; although some of the files in each of the zip's are duplicates.
I don't know what files SHOULD be on my SD card and what is extraneous material. I don't know what I need to install to get to where I'm ultimately trying to go... which is running 2.2, getting rid of these "extra" files and gaining the ability to wifi tether my phone.
I do NOT know if I have S-off or not... and I'm not sure how to tell. AND, I'm not sure if this is the base cause of the other issues or not.
Is there anyone willing to get me thru the vast amount of material & help me to get my Desire running the way it is capable of functioning?
At this point, I'm even willing to switch carriers to get what I want if the issue is USCC's proprietary nature...
Thanks in advance to any1 willing to help out

Bethyk said:
I've never tried to do anything beyond readily available 3rd party apps. I've never jailbroken anything or rooted. I don't know how to work with ROM's and I've never used command prompts beyond installing difficult software on my desktop. (I'm using Win 7 on my PC) and I have no linux or coding experience. That said, I'm smart, I research things fully b4 I actually DO anything & I follow directions exactly when i do something unfamiliar.
I bought my Desire about 45 days ago thru USCC. Stock it's running 2.1. On Fri using UnREVoked 3.21 I tried to root. It appeared to work. I have the Superuser file at least...
However, when I followed unlockr.com's tutorials for downloading & flashing ROM's it became obvious that something was not right (screens weren't the same, options weren't the same or even close in some cases, & controls, like pushing power to go back after recovery didn't work.) The screen turned black, I had a minor heart attack & then the phone finally rebooted into it's original USCC configuration.
Now, I DID have an option to "install from SD card" but nothing that said "flash from sd card" and I'm assuming -maybe incorrectly- that there's a difference??
After 4 days of searching sites, I know there are too many posts on USCC rooting & Desire for a noob like me to know what to do. I have a mess that I need help to untangle.
Prior to my failed ROM attempt, I had installed save to sd... which I think may have moved everything to my SD card. Since rooting, I tried using Root Explorer to remove facebook, twitter, City ID etc.... EX: I can see bloatware files on my SD card, and the program SAYS it deletes them, but it reboots on exit and there's CityID again!
I can mount the SD card as a disk drive on my PC and look thru the SD card files. (some of which appear 2B duplicates. When I rooted, I installed the Hboot drivers and followed the unrevoked directions exactly. I renamed the recovery file as update and left it as a zip... but there are now two "update.zip" folders on my SD card. They are different sizes and neither contains all of the files of the other; although some of the files in each of the zip's are duplicates.
I don't know what files SHOULD be on my SD card and what is extraneous material. I don't know what I need to install to get to where I'm ultimately trying to go... which is running 2.2, getting rid of these "extra" files and gaining the ability to wifi tether my phone.
I do NOT know if I have S-off or not... and I'm not sure how to tell. AND, I'm not sure if this is the base cause of the other issues or not.
Is there anyone willing to get me thru the vast amount of material & help me to get my Desire running the way it is capable of functioning?
At this point, I'm even willing to switch carriers to get what I want if the issue is USCC's proprietary nature...
Thanks in advance to any1 willing to help out
Click to expand...
Click to collapse
i cant tell you how to fix it, but what i can say, is if you really borked it, you can take it into a uscc store saying you have no idea what happened. i used to work for uscc until about 2 months ago. until that time, out of the 3 corporate stores i was working in, not one associates knew what rooting was. and none of the "smartphone team" had either. so they would most likely just send you a replacement. good luck

I thought about that... And I really don't even mind paying for it if I need to replae the phone, I will... But I figure at this point, worst case scenario I have aphone I can "play" with and figure out IF I can do any of this stuff successfully. I've discovered in the last year that I sort of have a talent for figuring this stuff out. This is the first time I've ever needed to find help with a problem and I've built several complete systems. I'm hoping there's someone who might be willing to suggest a course of action. If you have any ideas- even if I brick the darned thing- I'm willing to give it a try!
Thanks to anyone brave enough to reply!
Bethyk

Sounds like the second tuturial you were following was trying to root your phone again, but with the older method.
Turn on your phone holding volume down. You will get a white screen with some options in the middle, select recovery (it says at the top of this screen s-off or s-on, yours should say s-on, this is how to find this out.)
When recovery loads it should say clockwork recovery, a custom recovery flashed by unrevoked during the rooting process.
Use this recovery to flash a zip of whatever rom you want. Be sure to wipe data also if changing roms or any problems arise.

I've figured this much out at this point... I did root my phont with unREVoked 3.21. However, I did NOT S-OFF the device. So I'll try what mercianary suggests & let you know how it goes! Thanks a ton!
Bethy

Are you using the mouse button at bottom of phone to select in black and green recovery screen? If you are using power button to select it will give you a blank screen.

[Q]Phone randomly shuts down using Virtuous Unity 2.35

For a few weeks i have been getting these total random shut downs of my DHD running the latest Virtuous Unity 2.35.
I saw that happening live 2 times on specific occasions/functionality calls:
1)After switching the DHD on and inserting the PIN to unlock the sim card...few secs and BAM....everything goes down. This happens from time to time.
2)Few secs after running the camera app...some loading goes on and BAM...here we go again...cell goes off
What the hell is happening, should i worry about the phone hardware or is it some wipe/format i didn't do properly prior to flashing the rom.
The problem is i noticed it also with other custom roms...but with those it never happened while i was using it, instead it happened getting the phone out of my small shoulder bag.
I am really afraid my cell has something wrong with the hardware...i was angry as hell and i tried to do some "heavy shakin" to see if the battery was not retained to its place as it should have but nothing happened...cell always on...
What should i do?
PS: i must say i tried almost 15 roms last 2 weeks but always used the related full wipe files/used a decent format/wipe procedure.
plz help me
---------------------------------------
Some tech stuff maybe you need to know
Device: Desire HD
Rom: (current) Virtuous Unity 2.35 (those days i flashed more than 10 roms, MIUI included)
Status: S-OFF HBOOT-0.85.2007 (CID-11111111)
Radio: 26.09.04.11_M2
RIL: 2.2.0131HM
Kernel: Stock that comes with VU
So that you know that's what i always did prior to flashing any ROM (currently using 4EXTRecovery 2.1.3 RC2) :
1)format system
2)format cache
3)format data
4)wipe data/factory reset
5)FLASH ROM
--------------------------------------
EDIT1: I noticed, just to keep you posted, that on the recovery menu the SD appear to be "not well partitioned", i don't know if it may be the cause.

Do you have app2ext working?
I'm guessing here. Try backing up your SDcard on a pc (preferably via cardreader) and giving it a thorough format with one partition only. You may need to delete the partitions first. I can't tell you how unless I know your operating system. If you continue having the shutdown issue afterwards you would be able to cross out SDcard problems at least.

Hi ROBINGAZI, thanks for your fast reply.
ehm, what is exactly app2ext?
I don't have a card reader right now, does it really change if I mount the SD via the phone? Anyways, i got a machine running WIN 7 x64.
hope this step will clear out the problem

Plug your phone to the computer as disk drive.
copy everything you have on the sdcard to a directory in your computer.
then click start>control panel>administrative tools> computer management.
a window will appear and you should see "storage"
in storage you will find "disk management".
you should be able to see your phone's SDcard there. right click and then delete the partition into unallocated space. Then right click and create a partition (fat32). format the partition.
if needed remount the sdcard to your computer (not the phone)
copy only one zip file (the rom you want to flash) to the SDcard (preferably something reliable like stock or something very close to stock).
unplug the phone and reboot into recovery. Do a full wipe...format everything apart from the sdcard if you think it is proper.
flash the rom and see what happens.
this way you can at least rule out the SDcard for causing your problems.
PS: Dont restore via nandroid...you could be putting the problem back into your phone.
BTW: Does your phone shut down properly or the screen goes blank like it would if you unplug a computer. Anyway make sure you dont just have a loose battery cover or battery before you try this out.

Thanks again.
Yeah my phone screen just goes blank like it would if you remove the battery from it while on.
I restored the SD card and it works properly. installed Revolution HD 5.2.6
As i stated earlier i also tried to shake the phone to see if the battery had some kind of faulty retention system but the phone stays on.
So i really can't understand what is the problem.
PS: I was curious, is there an application that tells you the entire life of a battery? meaning since when it started to operate?

NEW UPDATE ABOUT THE MATTER:
It's DEFINITELY the battery...i don't know why, i don't know with what criteria but it's the battery.
Yesterday i switched it with my brother's phone, obviously another DHD. Since then i have had absolutely no problem of any sort. He, instead, is experiencing random shut downs...
i think that the "problem is sloved" so to speak
the question about the battery app remains...or maybe there is a way to see the battery entire life cycle with a system file.

[Q] Internal memory "access denied"

I have been trying for two days to access my internal memory (aka sdcard0). I have flashed all the way down to Roger's stock rom . I have formatted it, tried using the "restore-sdcard-after-downgrade" tool several times. I have flashed modem, core, and ROM several times with different modems and kernals. I have tried to mount/unmount the memory using various methods; recovery, numerous apps on Google Play, changing it's permissions. I have done everything that I have found worked for others with this problem, except use ADB code to rewrite the reparations. This stuff is Greek to me (and I don't speak Greek).
Can someone take me through this process, step by step. Assume I have no idea what you are talking about, because I don't now the first thing about how to use code/script/whatever it is called. Internal memory is intact; it works fine, because odin can access it and write to it. I have written several back-ups to it. The phone can't see it and cannot use it. I can't seem to figure out how to use my extScCard to install apps, despite trying things that worked for others. This leaves me with an extremely limited amount of memory to use for apps. Stock ROM has taken most of it. Also, I have lost USB connectivity, thus cannot use PC for odin functions, tool kit, or even file transfer. I have mobile odin and recovery. If I need a file I have to remove extSdCard, put it into an adapter, insert it into PC, transfer files, and then reverse the process in order to get them onto my phone. Just to clarify, I am unable to download files directly to my my phone via wifi, due to lack of internal memory. However, phone is currently stable (no bootloop or brick issues issues.
You can expect a generous donation if you can help me get this thing working again.