Database Info

FUZE flashing problems! DPAD screwed up!

So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?

petard said:
So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?
Click to expand...
Click to collapse
Did you try flashing back to the stock ROM? If that doesn't work, I wonder if flashing back to stock everything (ROM, radio, SPL) might kick out the bugs (?)

Did you hard reset after flashing? That might be your problem. And what programs/settings did you install? I would hard reset-don't run UC-then see if the dpad is working fine.

I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
EDIT: It started doing it again but if I put the phone to sleep and bring it back, it normally fixes it. What an annoying problem. I am going to try to flash a different radio and see what happens. I just like this radio so much its GPS actually works decently.

petard said:
I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
Click to expand...
Click to collapse
No, it doesn't do a full hard reset when you flash. A lot of crap is left over, and if you just start using the ROM, you get a bunch of random bugs, like, say your DPAD doesn't work. You're supposed to hard reset when the the phone asks you to align the screen. It's a must. Seriously, hard reset and start over and all of your problems will go away.

I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.

petard said:
I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.
Click to expand...
Click to collapse
I have no idea how anything is left over, it just is. Here's what mskip's thread says:
mskip said:
[FONT=&quot]Flashing Via ActiveSync[/FONT]
[FONT=&quot]1. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT=&quot]2. REMOVE SIM and microSD CARDS!![/FONT]
[FONT=&quot]3. Turn phone back on and wait until it syncs with your PC.[/FONT]
[FONT=&quot]4. Run the Raphael_RUU.exe (or [/FONT][/SIZE]RaphaelWrapper.exe if thats included instead) [FONT=&quot]from the Roms Folder.[/FONT]
[FONT=&quot]5. Once phone finishes flashing and gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT=&quot](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT=&quot]6. Follow onscreen instructions to set up your New Rom.[/FONT]
[FONT=&quot]7. Once phone has gone through the customisation procedure then replace Sim and microSD Cards.[/FONT]
[FONT=&quot]8. Turn phone back on and set up as required.[/FONT]
[FONT=&quot]Flashing Via MicroSD Card[/FONT]
[FONT=&quot]1. Make sure your microSD is Formatted to fat32 using a PC (you dont have to delete all files but it is safer if you do).[/FONT]
[FONT=&quot]2. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT=&quot]3. Goto the Roms Folder and rename the .nbh file to RAPHIMG.nbh[/FONT]
[FONT=&quot]4. Copy the RAPHIMG.nbh file to the root of your microSD Card.[/FONT]
[FONT=&quot]5. Plug the microSD Card into the phone.[/FONT]
[FONT=&quot]6. Press and hold the volume down button, then press the reset button with the stylus. Release the volume down button when bootloader tricolour screen appears.[/FONT]
[FONT=&quot]7. Follow the onscreen instructions to start flashing.[/FONT]
8. Once phone finishes flashing and says Update Complete, reset with the stylus
[FONT=&quot]9. When it gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT=&quot](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT=&quot]10. Follow onscreen instructions to set up your New Rom.[/FONT]
Click to expand...
Click to collapse
Here are flashing instructions from At0mAng:
Install Instructions
Read The Flashing Your First GSM ROM Guide
Make sure your battery is 50% charged or more
Power off & Remove SIM Card
Power back on and sync with PC
Flash ROM
Hard Reset where it ask you to align screen
Click to expand...
Click to collapse
They're not telling you to do the hard reset just for the heck of it; there's a very good reason for doing it. Not following the standard flashing instructions and then posting in the chef's thread that his ROM is buggy is just not cool.

It turned out to be the radio causing my problems not the ROM. I have never hard reset after flashing a ROM and never had a problem (and that time wasn't a problem because it was due to the radio ROM)
Not that I am asking for it, but unless there is actual proof that you need to hard reset, I don't think there is a point of doing it.

Ok the problem is back! So annoying. Does flashing the SPL hard reset the phone? I want to try going back to the stock SPL since that is the only thing it could still be, but I would rather not now if it hard resets.

Just get it over with and do a hard reset. Jeez, it's not that complicated.

roms and radios will not adjust the dpad i used the same rom u talk about and never had an issue

Hey petard, did you ever fix the issue with the D-pad ?
I have the exact same issue with my Fuze and can't figure it out.

It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago where it just started to act up. I called for another replacement a couple days ago and should get it tuesday. They offered me a different phone (Epix or Incite) but I declined but told them to note it that I was offered a different phone.
In about 3 months (when my warranty ends) I will call for another replacement. If they have refurbed Touch Pro 2s by then I will ask for that, if not I will get another FUZE which will extend my warranty for 3 more months (you get 3 months or whatever was left of your original warranty, whichever is longer) and by that time they have to have refurbed Touch Pro 2s where I will then try to get one.

petard said:
It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago ...
Click to expand...
Click to collapse
It figures, no easy fix. It's strange how it started to act up, mine crapped out right after a flash as well.
Good luck on aquiring the TP2 though.

Infinite Reboot Cycle, Please Help.

A bit of info to start off:
AT&T Fuze running an Energy ROM (March 10th I believe). No problems with the ROM and nothing changed on the phone before this.
Earlier today I felt my Fuze vibrate in my pocket. I figured it was a text and, because I was in the middle of on conversation, I ignored it. A few seconds later and it did it again. And again. And again. It was putting out these 1 second long vibrations every 2-3 seconds. The screen was black and it wouldn't respond to any buttons at all. Not even the soft reset. I had to pull the battery.
Now when it boots it seems to stay on the AT&T screen a bit longer than normal and when it finally boots up it makes it about as far as the HTC animated screen and then reboots instantly.
I tried a hard reset. It hard locks at the screen that says it is configuring, please wait. Have to pull the battery here too.
I get home and drop it in to the boot loader and try to slap the same Energy rom on it. This time it makes it to the same "Please Wait" screen then reboots. It is stuck in an infinite reboot cycle.
I figure I should try the stock rom and it does the same thing. It gets to the green Windows screen that says it is configuring TouchFLO and then it reboots. As soon as it gets back to that screen it reboots again. Infinite reboot cycle.
I tried the updated Energy ROM. Same issue. At this point I figure it is a hardware issue and it is probably dead. Before I throw it into a wall do you fine folks have any suggestions?

I had that once, too.
Second or third ROM after a hard reset every time worked.
There seems to be something wrong with the ROM you flashed.

Try running task 29. Just put a splash screen in the task 29 folder, run it, then re-flash the nrg rom (or any other rom of your choice). It should fix the problem. There's a task 29 thread in the raph rom forum.

shadow# said:
I had that once, too.
Second or third ROM after a hard reset every time worked.
There seems to be something wrong with the ROM you flashed.
Click to expand...
Click to collapse
I'm on ROM eight or nine now. Same thing. Even the stock ROM. At this point I'm almost convinced it is a hardware issue. Ah well, it was good while it lasted. At least I still have my backup HTC Wizard. That thing is a workhorse.
Farmer Ted said:
Try running task 29. Just put a splash screen in the task 29 folder, run it, then re-flash the nrg rom (or any other rom of your choice). It should fix the problem. There's a task 29 thread in the raph rom forum.
Click to expand...
Click to collapse
Would this be any different than flashing a new ROM at the bootloader?

Taelon said:
Would this be any different than flashing a new ROM at the bootloader?
Click to expand...
Click to collapse
Task 29 wipes the OS partition clean, so you no longer have an OS rom. A re-flash will give you a clean rom, and possibly the bugs will be gone.

Farmer Ted said:
Task 29 wipes the OS partition clean, so you no longer have an OS rom. A re-flash will give you a clean rom, and possibly the bugs will be gone.
Click to expand...
Click to collapse
Excellent, thanks for the info. I'll give it a shot momentarily.

With Task 29 I make it to step 7. and then I can't progress because my reset button is not responding. If I pull the battery and then enter the bootloader I can flash a new ROM but I still have the same problem.
If I use the stock ROM it makes it to the green Windows Mobile 6.1 logo screen that tells me to wait while it sets up TouchFLO, hangs there for a few seconds and then reboots. It makes it to that screen again and reboots. Infinite cycle.
If I use the newest Energy ROM it makes it to the Energy version of that screen and locks up and no buttons, including reset, respond.

Ok, let me get this straight-you ran task 29, and it worked? If it worked, then the device should've flashed, and then re-booted and just hung on the splash screen (no red numbers or anything appears). Then, you were able to re-flash a new rom. Is that correct? But, you run into issues because your reset button isn't working. Well, it sure sounds to me like you've got a hardware (not firmware) problem (edit-duh, just re-read your first post, and that's what you concluded a while ago). Maybe your reset button is stuck. Did you drop the phone recently, or get it wet? Try looking in the hole of the reset button and see if anything is stuck there.
If worse comes to worse, flash back to stock rom and then spl and return for warranty (may be too late for that, I guess) or repair.

Yup, it does look like a hardware problem. I was just really hoping it wasn't. The phone itself hasn't gone through any major drops and has never been wet. The reset button looks clear of debris and I can feel the button push in. Sadly, she is out of warranty. She was a refurb to replace one that had the screen go about a year ago. She was a good girl, I'm gonna miss her.

what do you mean by task 29 ?
where can i find task 29?

Look in the rom forum, just like it says above. Or, and I know this will sound crazy, try searching "task 29".

Same exact thing happened to me. Not sure what causes this...
I was at Bestbuy when I felt my phone vibrate, took it out of my pocket but it was off so I turned it back on and put it back in my pocket. Felt it vibrate again a few seconds later and figured the battery must have died so I took the battery out and didn't turn it back on until I got home. That's when I found out it was doing the same exact stuff as yours, constantly rebooting no matter how many times I flashed it. After many many hours of tinkering I was at least able to get a stock ROM and after even more hours, a stock SPL and call ATT for replacement. $50 and 1 day later, new Tilt 2 at my doorstep

[Q] Can't Access HBoot, Random Startup

Hello,
I am posting in this forum for a few reasons.
First of all, I rooted my phone the day I bought it and took it home. I originally rooted it with a simple one-click method from a webpage I randomly found online.
Unfortunately, I do not remember the name of the hack, and I'm beginning to think that it has permanently affected the boot for my phone. After installing the hack, I found the CynoagenMod (or however it is spelled) custom ROM. I took some time into researching more about custom ROMs and installing with advanced settings, etc.
After I did my research, I found it best to flash with the new ROM and have had trouble with my boot since.
I did everything step by step from the website, and ran everything to the best of my abilities. The problem I am having now is that I can not access the HBoot menu.
In fact, every time I restart or shut off my phone, the screen goes black and will not respond to me holding down the recovery mode buttons. It stays pitch black and even battery resetting does nothing.
It will randomly turn on, vibrating for about a minute or two straight with the HTC splash screen, and then boot into my phone with the current ROM.
It seems strange that this is going on, and I have been searching all over the internet for weeks now trying to figure out what's wrong. I have reinstalled the stock RUU for my Inspire multiple times to no avail. It still sits at a black screen and will randomly boot into the splash whenever it deems to do so.
Is there anyone with any suggestions or advanced technical knowledge that could lead me to a solution? It is most unfortunate because I can't access for viewing s-on, s-off. I'm really debating whether to take the phone back to the rep and replace it. I'm just afraid they will discover the security off and tell me to suck a ****.
Thanks.

Run this nice little tool to factory reset, s-on your device
http://forum.xda-developers.com/showthread.php?t=1208507
Then reroot with the Hack Kit here. Read the "effen manual"
http://forum.xda-developers.com/showthread.php?t=952352

Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.

Also, is there a way to go about doing this procedure straight from the Terminal since I can't run HBoot and recovery directly from my phone?

I have sucessfully restored s-on on my previous inspire so I can rma it for a signal issue I was having.
So I consider myself savy enough on this task. I rooted that inspire using a method available on here and not some random site. Doing that, u accept the possiblility that you may not get support on xda for using a root method that was not posted here. However, I do remember reading somewhere on here that certain inspires will go to a black screen at somewhere during the rooting process. My advice is to search the inspire threads for this topic, using keywords black screen, and see if this can provide a solution for you.
Sent from my HTC Inspire 4G using XDA App

Thanks soldier, but I've already searched through every black screen forum topic on this site for the inspire, all of which require reboot to HBoot, which I can not access from my phone without terminal access.
It seems like my phone is permanently soft bricked or something, or maybe the key commands don't do as they are supposed to. I can never get into the HBoot menu or recovery by holding down vol. - and the power button.
All it does is boots into the splash screen after about five minutes or son, and once the splash screen comes up, the phone vibrates for about 2 minutes straight.
During this time, my phone is not recognized by adp until after the phone stops vibrating.
I can't seem to find any forums ANYWHERE that propose a solution to this problem, let alone anyone that has the same issue as me.

Yeah that sux man. Well I would say, if you are within your warranty exchange, I would go that route first. Worst thing they can say is no. Although I still have yet to find a story about how someone was denied a warranty exchange for a phone that does not have physical damage. The next route is to suck it up and pay the deductible if you have insurance on it. (I always recommend insurance on any modern touchscreen smartphone) If that is not an option, then start saving up for a new phone, and lesson learned.

Ya, that seems like the only available option at the moment since my phone can't access HBoot even though I rewrote the root files to the device.
I just bought the phone this weekend, so I'm thinking of hard bricking the phone in case they decide to do an on-the-spot check. Hopefully they'll believe some bull**** story I can come up with and just give me a replacement.
Would any of you still recommend rooting again with a new phone? And what would be the best way to do so without the consequence of a soft or hard brick?
I'm just thinking of rooting and keeping the original stock OS on the device instead of running a custom ROM. That's what seems to have effed my phone.
All I really wanted to do was cut all the crappy useless programs and services out of the original Google Apps package with a fresh install to get the most out of my hardware.

FYI...if you haven't figured it by now, xda is the BEST site there is for android hacking/modding. This website IS the centralized location for all android developers/modders. Sure there are plenty of other android community sites out there, but this is the direct centralized source for all android hacking/modding.
My suggestion is to go ahead and root the next inspire you get using the hack kit in the development section. That is a long time proven and supported rooting method for the inspire. As far as roms go, from what you are saying, i would recommend you install a custom rom that is based on stock. (ex. Android Revolution) It was not the custom rom that effed up your phone, it was the questionable rooting method that did. Custom roms, by default, are superior to true stock roms, because they are modded, tweaked, and optimized far beyond the stock rom.

Awesome, I appreciate the information.
I'll keep that in mind. So which exact ROM would you suggest for my Inspire that's completely like Gingerbread?
I wasn't too fond of the CyanogenMod ROM because the GUI was a little sketchy. I like having a professional looking GUI, and I love the Gingerbread screens and menus.
Oh, one more thing. I had some success a little while ago getting into the HBoot menu from the terminal. Now I'm having a new issue:
I get into the menu at which the phone freezes and I can not use the arrow keys or power button to make a selection. Any tips?
I also believe that it is in fastboot, since it says fastboot at the top and has the Androids on the bottom skateboarding. Is this an issue? And am I screwed because I can't access the OS to turn the option off?

When you see the fastboot at the top of the screen and the androids skating at the bottom, that is perfectly normal. That is the pre screen before actually going into the bootloader. If your keys work, u press the volume down button to select which option you want, which will highlight in blue. The first option is the bootloader, so if you press the power button, it will load into the bootloader. The bootloader looks exactly the same as this screen, but with different options. This screen will show hboot at the top and have the options of fastboot, recovery, factory reset, simlock, and image crc. I have never heard of the keys not working at this point, so i couldn't help you there. Search around the forums if you haven't already.
If you want to compare this to something more familiar, think of these two screens as your motherboard bios to your PC. (What you see when your pc boots up, before it loads the OS, windows, mac, etc) On a pc, you can install any OS you want, like on the inspire, you can install any custom rom you want. But the motherboard bios is the highest level of permanent software that is directly written to the motherboard itself, like the bootloader/hboot is on the inspire. When rooting, you are essentially altering the motherboard bios on the inspire. When you install a custom rom, you are just installing an OS on the inspire.
There are plenty of custom ROMS that are based off of stock in the development section. I use and like Android Revolution. But when choosing custom roms, its always a matter of preference, and what works best for you.

digitalism said:
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Click to expand...
Click to collapse
It sounds like you may have the bad combination of a newer Inspire and the older ENG hboot. This is a problem dealt with commonly on the Aria/Inspire IRC channel. If you want to jump in, we can probably get you straightened out.
http://webchat.freenode.net/?channels=#liberatedAria

Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.

digitalism said:
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
Click to expand...
Click to collapse
You will not be able to use the volume rocker to select options if you have a PD98IMG.zip on your SD card.
Try booting into hboot with the SD card removed. That should let you move around the menu.
Sent from my Inspire 4G using the power of the dark side

Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.

digitalism said:
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
Click to expand...
Click to collapse
It's good to hear you're moving forward. Let us know how it comes out.
Sent from my Inspire 4G using the power of the dark side

[Q] Touchscreen stopped working on Nexus S

Hi all
Today I was trying to get my nexus s onto the official ota ICS update by flashing it manually, following guides other people had had success with.
I was on the cm9 ics beta, so I had to flash the full rom of 2.3.6.
This worked completely, however I think the ota update file I downloaded was corrupted, as flashing didn't work, it said something about signature verification failed. So I redownloaded it, from the same link, and the new one was bigger. I tried that, and the same error. I tried wiping data/factory reset etc, and I accidentally started to flash a cm7 rom I had on my phone.
I stupidly did a battery pull as it started to flash (the back cover was off already), and now my touchscreen doesn't work. I was able to successfully flash other roms including the 2.3.6 I downloaded, and I couldn't do the first setup procedure (touch the android to begin). I tried cleaning the screen very carefully with 90% isopropyl alcohol, the same stuff I use to replace thermal paste on cpus.
It still doesn't work. I am hoping it is a software issue that can be fixed otherwise I have to return it.
Someone please help
I have used the search function and none of the solutions I found worked.
(UPDATE) I rebooted again, and when the phone booted into cm7, the "internet" icon(the globe picture) on the bottom left of the dock was in the "pressed" state(orange). It was like the phone thought I was holding my finger on it, which suggested a hardware issue. I cleaned it again and nothing changed. Then I held the phone in the landscape position. When the screen rotated, the button stayed pressed. So the phone doesn't think "this part of the screen is being pressed" it thinks "this internet icon" is being pressed. Rotating the phone again and again didn't change anything, the icon was still pressed in.

Defiantly a software issue. I would try to unroot and reroot. Then if it is still not working, try to format the SD card. You may want to considering buying a USB to micro USB adapter to help you, considering then u could plug in a mouse. I have one just in case I need it.
Thank me if any of this helped
Also try and keep this updated with new info. If I can't help, maybe someone else can.
Sent from my XT862 using XDA App

Thanks techno-update, I will try that. I haven't "unrooted" before, Is that just typing fastboot oem lock or whatever it is instead of fastboot oem unlock?
Also, I found a youtube video with the EXACT same problem.
v=zpfE15Xw_os&feature=related
Skip to 3:15, and you will see when he opens the power menu, the phone thinks he is pressing on one of the options, but he isn't.
I will let you know how unrooting and rerooting goes.
Thanks
(UPDATE)
I tried unrooting and then rooting again. It still does the same thing.
Even in cwr I can't use the capacitive buttons to navigate menus, does that rule out software problems? I am really hoping its just a software problem :/
I need my phone for an outing tonight (im in australia, its 5pm now) and I would appreciate it if some genius could solve this
I am usually the "go to fix it IT guy" in my area, but I can't figure this one out. I have tried formatting the phone, reflashing the mod etc.
Is there some more aggressive COMPLETE wipe or something that fully wipes the phone?
UPDATE 2
Guys please help,
I just flashed zulugen mod, as it has the trinity kernel, I don't know much about android os, but I hoped that that might replace the touchscreen driver or something. The rom flashed correctly, but touchscreen and the capacitive buttons still don't work. Please help

Guys, is there some sort of system partition where the touchscreen drivers are kept or something? And when I pulled the battery as it was flashing cm7, it corrupted these?
Is there some way to fix this?

bump
bump. I need help with this urgently. Is it possible the connections for the screen came loose inside? I would crack it open but don't have screwdrivers for the 3 smaller screws on the last layer of plastic before the pc board.

How I've Installed CyanogenMod on the Motorola RAZR HD (GSM) - the "xt925"

Disclaimers
- First of all: if you want to use clockwork or have the latest android releases, do yourself a favor and get a Nexus phone. Or, maybe, a OnePlus. In worst case scenario, go for freaking Samsung. Don't think Motorola, LG or anything else will make things easier. It won't.
- Well, I just spent a whole freaking day stuck in a few points which could have been made much simpler if there was a few points better explained in a lot of good other tutorials I've found along the way.
- But, at the same time, I honestly think writing in this forum is too dreadful (at least I could find no way to write with some markup). Only reason I'm doing this here is lack of a better place for good visibility positioning. In other words, so someone who might need this info can actually find it. Sorry if this offends anyone. It's about the same reason I believe in using eBay first to sell my used stuff instead of craiglist or dropbox. Most people who'd want "stuff" will look on eBay first.
- Here's the same guide in my "blog / forum" by the way.
A "bad guide", with no revisions
The main reference to me was, as one might expect, from cyanogen mod wiki.
The real steps needed are very similar:
1. Unlock device
2. Install recovery using fastboot
3. Wipe every single thing
4. Install CyanogenMod from recovery
All steps but 3 can be found on that wiki. Step 3 can actually become really big. Making it as clean as possible could be very complicated. Or very simple.
The most important thing is understanding the concepts of what's being done and knowing how long each step can actually take. Specially the ones that give no feedback. Such as that terrible horrible loading screen, which I've learned to hate. The "spinning CM robot" should appear for 1 or 2 minutes at most, but that's way too far from clear and that info is nowhere to be found.
I won't repeat the tutorial, rather I'll explain it and correct it.
Unlocking Device
This is for allowing your Razr to be tweaked. And it's not rooting the device as it may appear (being somewhat a newbie and not too interested in rooting, I've mixed up the concepts).
Other than this, the steps on the wiki are pretty clear and complete here, I don't see how anything could go wrong if you just follow it.
I've got no screen that would be more than a few seconds without a feedback.
Recovery and fastboot
This starts to present apparently minor issues.
It says to use Clockwork Mod but all newest files to download on the other wiki page itself already bring a Recovery Image. Now, CWM is well established and used, but the versions linked there didn't work on my device. Only the new Cyanogen Recovery works. And it's not as complete as, although I really appreciate the higher simplicity there. Anyway, in the end CWM is just not needed, a version I could find that loads can't install any ZIP and it ends up just holding back because it offers a lot of useless options.
And "Volume Down + Power" doesn't work to boot into recovery. At all. You need to hold Volume Up + Power, or some sort of combination from Vol Up & Down & Power. It's easier to just look for videos of how it's done. I can do it quickly most of the times using Vol Down & holding Power to boot into fastboot, and then just hold Vol Down and quickly hold power for 1 second, release, and keep holding Vol Up until a menu opens up in which you can choose to boot to Recovery (or back to Fastmode as well).
Those misleading things there held me back 1 hour at first... But the CWM really screwed me up big, wasting time trying to use it to fix stuff. It's just not enough. I guess.
Maybe, however, there's one thing it could prove to be important. Backing up. Install it for this, if you're worried about trying to recover data without using google's own backups, after android is installed. To me, that was more than enough.
I've got no screen that would be more than a half a minute without a feedback.
Wipe every single thing
`fastboot -w`. That's all that took me, although it did give errors and I still saw many warnings through the whole process, if only I knew this command before, it would have saved me 20 hours or so.
Maybe it was the sum of cleaning up stuff with CWM, but I doubt it.
I really don't want to get into more details here, right now.
I've got no screen that would be more than a few seconds without a feedback for anything I've done in this step.
Recovery for CM
You probably also want to install google apps. Just take the nano OpenGApps. And if you're trying to use CM stable and it bricks, just get the nightly build.
If you're lucky, installing with sideload should be enough. All those options are just means to getting the zip files into the device for recovery installation and if you'd only have to use sideload once it's perfect. Having to use it again eventually is a pain, because it doesn't save local copies on the device.
Another 2 options: You could also have a SD card to USB adapter, or use CWM mounting SD card and transfer everything through the USB cable.
The biggest missing information in this step, however, is this: the loading CM robot screen, which appears after you boot, when that wiki guide is over and it thinks "everything is fine". It should be not more than 2 minutes, from my experience.
But google says otherwise. You might be led to believe it could take many minutes, maybe as much as 10. Which can easily be extrapolated by "well, maybe it takes 15". Before you know it, you're easily wasting hours waiting for it.
So, there you go. Hope this might have been of any help to you! ;P