Database Info

i727 w/ICS 4.0.3 freezes when shutting down..?

I just updated 4.0.3 tonite, rooted, installed titanium backup, and started one by one installing my backups. I don't have anything crazy yet...angry birds, facebook, etc...(other than a couple of apps I needed like lucky patcher, busybox..etc.)
Anyway when I restart or shut down the phone, it gets stuck at the "Shutting down" screen...with no reboot.
Any suggestions or ideas before I resort to reflashing?

BRIMS7ON3 said:
I just updated 4.0.3 tonite, rooted, installed titanium backup, and started one by one installing my backups. I don't have anything crazy yet...angry birds, facebook, etc...(other than a couple of apps I needed like lucky patcher, busybox..etc.)
Anyway when I restart or shut down the phone, it gets stuck at the "Shutting down" screen...with no reboot.
Any suggestions or ideas before I resort to reflashing?
Click to expand...
Click to collapse
Known issue/bug. You can shutdown by holding the power button for 12 seconds, or install the 14 toggle mod to shutdown and reboot.

hcyplr29 said:
Known issue/bug. You can shutdown by holding the power button for 12 seconds, or install the 14 toggle mod to shutdown and reboot.
Click to expand...
Click to collapse
Wow awesome...the 12 second thing works fine. I was worried there for a minute, I really appreciate it!
Does it matter which mod to use? I see there's a few...

Fix for shutdown/reboot lockups
Install the updated Clockworkmod Touch 5.8.1.3 Odin from this thread
http://forum.xda-developers.com/showthread.php?t=1566613
Then install your ROM as usual and the shutdown/reboots should work!

xiralos said:
Install the updated Clockworkmod Touch 5.8.1.3 Odin from this thread
http://forum.xda-developers.com/showthread.php?t=1566613
Then install your ROM as usual and the shutdown/reboots should work!
Click to expand...
Click to collapse
hmm...it's about 50/50 on ppl with issues...not sure about that..
Question though...is it safe to flash this cwm over the one I currently have?
..and once I do, I shouldn't have to reflash the rom right?

BRIMS7ON3 said:
hmm...it's about 50/50 on ppl with issues...not sure about that..
Question though...is it safe to flash this cwm over the one I currently have?
..and once I do, I shouldn't have to reflash the rom right?
Click to expand...
Click to collapse
Yea i had problems with 5.8.1.3. Unresponsive.
Yes you can flash recovery over each other in odin . Im using 5.5.0.4 cwm touch and its working fine. Able to do nandroid and fix permissions. This recovery is actually flashed in cwm.
No you do not need to reflash your ROM.
Sent from my SAMSUNG-SGH-I727 using xda premium

hcyplr29 said:
Yea i had problems with 5.8.1.3. Unresponsive.
Yes you can flash recovery over each other in odin . Im using 5.5.0.4 cwm touch and its working fine. Able to do nandroid and fix permissions. This recovery is actually flashed in cwm.
No you do not need to reflash your ROM.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Will this one do?
http://forum.xda-developers.com/showthread.php?t=1472954

Yep. That's it. You even have the option to test it out first.
Sent from my SAMSUNG-SGH-I727 using xda premium

I flashed it...and according to what i saw someone else say, fixed the permissions..but the restart button still freezes up..
Is there something else i need too do?
Sent from my SAMSUNG-SGH-I727 using xda premium

BRIMS7ON3 said:
I just updated 4.0.3 tonite, rooted, installed titanium backup, and started one by one installing my backups. I don't have anything crazy yet...angry birds, facebook, etc...(other than a couple of apps I needed like lucky patcher, busybox..etc.)
Anyway when I restart or shut down the phone, it gets stuck at the "Shutting down" screen...with no reboot.
Any suggestions or ideas before I resort to reflashing?
Click to expand...
Click to collapse
This question has been beat to death. Try searching instead of making a pointless, and inappropriately placed, thread.
Sent from my SAMSUNG-SGH-I727 using xda premium

BRIMS7ON3 said:
I flashed it...and according to what i saw someone else say, fixed the permissions..but the restart button still freezes up..
Is there something else i need too do?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Are you on the odin one click leak? This is the only "version" that i didn't have any issues with shutdown.
Sent from my SAMSUNG-SGH-I727 using xda premium

Shadeslayers said:
This question has been beat to death. Try searching instead of making a pointless, and inappropriately placed, thread.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I did search..and its been beatin to death in threads not specific to that problem. I got my answer so whats it to u?
Sent from my SAMSUNG-SGH-I727 using xda premium

hcyplr29 said:
Are you on the odin one click leak? This is the only "version" that i didn't have any issues with shutdown.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yea i am
And...thanks for not biting my head off for being new.
Sent from my SAMSUNG-SGH-I727 using xda premium

Do a battery pull. Boot into recovery. Clear cache. Problem solved.
Sent from my SAMSUNG-SGH-I727 using xda premium

BRIMS7ON3 said:
Yea i am
And...thanks for not biting my head off for being new.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Have you done any mods since, meaning no other flashes of other ics Roms after or in between. My problems all started after i flashed the cwm nandroid backup in another thread. The issues followed me until i did a darkside wipe then did the odin one click and all my issues went away. Im staying here for a while. Did my nandroid backup of this to always revert to.
Sent from my SAMSUNG-SGH-I727 using xda premium

This is one of the known problems that sometimes occurs with the ICS leak and most things based on it. The problem is people that think they have the "know all" answer for a fix because something they did worked for them. Just because something works for you doesn't mean it will work for averyone! So it's ok to say "well, this is what worked for me...", but it IS NOT ok to tell others that it is an overall fix or that they did something wrong because it didn't work for them like it did you.
What I have found is that everytime you flash the ICS leak (or related) you might get different results, so if you really are interested in trying to get everything working, just keep flashing until it does. It might take several tries, but keep trying. This seems to be the case for many people, but I cannot promise it will work for you.

I experienced similar results, first flash was lagged to insanity. however second flash fixed this and restored the home button funtion.

The only other thing i did after the first flash was a factory reset, which in my case fixed the home button issue. Not sure if it was freezing prior to that. I may try the cache thing but its not a burdensome enough issue to reflash again. too many workarounds to redo everything again..
Didn't realize this was so common when i posted this thread..thought it was random. Now if only someone could delete it...
Sent from my SAMSUNG-SGH-I727 using xda premium

hcyplr29 said:
Are you on the odin one click leak? This is the only "version" that i didn't have any issues with shutdown.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Same here, though I haven't tried them all, I just went back to stock, manual debloat and a couple other mods and it's good enough for me, at least until we get real CM9 or AOSP roms.
I'm really not the type to wipe my phone and flash a new ROM twice a week. I'd rather just have something that's stable and functional, and only upgrade for big stuff.

I didnt have the shutdown problem the first time I installed the original ics leak install.
But I did after I restored a backup of it.
mitchdickson said:
Do a battery pull. Boot into recovery. Clear cache. Problem solved.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Didn't work for me on NexusMod ICS.

[Q] HTC One XL flashed with the newest Viper XL ROM...

So recently, I flashed ViperXL 2.0.0 to go along with the Beastmode 3.0 kernel. Everything has been going well, but I've been encountering some sort of bug...that doesn't really seem to be a bug, but there's something definitely up with my phone.
About once or twice a day, my phone will just get up and reboot itself completely randomly. I'm not sure what, if anything, is actually triggering it. The weird thing is that other than these reboots, my phone runs extremely smoothly - without lag, freezes, or anything of the sort. I'm not sure what the problem is, and I can't really replicate it because it happens so rarely. Anybody else encountering the same sort of issue?

Wrong Forum. Try clean wipe, cache and dalvik cache as well and re-flash the rom.

So recently, I flashed ViperXL 2.0.0 to go along with the Beastmode 3.0 kernel. Everything has been going well, but I've been encountering some sort of bug...that doesn't really seem to be a bug, but there's something definitely up with my phone.
About once or twice a day, my phone will just get up and reboot itself completely randomly. I'm not sure what, if anything, is actually triggering it. The weird thing is that other than these reboots, my phone runs extremely smoothly - without lag, freezes, or anything of the sort. I'm not sure what the problem is, and I can't really replicate it because it happens so rarely. Anybody else encountering the same sort of issue?
Click to expand...
Click to collapse
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app

absolutelygrim said:
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Actually it does work - there was an issue with the cam but a fix was posted.
Sent from my HTC One XL using xda premium

absolutelygrim said:
Beastmode doesn't work with 2.0.0
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
false works fine with the camera fix

beankid said:
Wrong Forum. Try clean wipe, cache and dalvik cache as well and re-flash the rom.
Click to expand...
Click to collapse
I was hoping to avoid that actually, because I've set up all my apps, settings, etc. all nicely after migrating from the stock ROM. The problem is that the reboots are sparse enough so that it's not a hindrance, but it happens enough such that it's a lingering annoyance.

crazylilazn said:
I was hoping to avoid that actually, because I've set up all my apps, settings, etc. all nicely after migrating from the stock ROM. The problem is that the reboots are sparse enough so that it's not a hindrance, but it happens enough such that it's a lingering annoyance.
Click to expand...
Click to collapse
l
wrong forum ... and thats the simplest way to fix the reboot problem im on viper and have not had any troubles
also get a backup app saves time..
backup only the data when doing a backup in recovery wipe and reflash 2.0 and them restore data . if the reboots are still there then i would say its an app causing the reboots

CheesyNutz said:
l
wrong forum ... and thats the simplest way to fix the reboot problem im on viper and have not had any troubles
also get a backup app saves time..
backup only the data when doing a backup in recovery wipe and reflash 2.0 and them restore data . if the reboots are still there then i would say its an app causing the reboots
Click to expand...
Click to collapse
I normally use Titanium. So you're saying to not choose "App+Data Restore", install the apps directly from the market after a flash, and then load the data in?

crazylilazn said:
I normally use Titanium. So you're saying to not choose "App+Data Restore", install the apps directly from the market after a flash, and then load the data in?
Click to expand...
Click to collapse
I use app + data but only for market installed apps, I don't backup system apps or any of the apps installed with the rom. I personally have not had any problems doing it this way. I have not had any reboots or major lags on Viper XL btw.

I was seeing this as well, are u oc to the max 2.1? If so bring it diwn to 1.8, and see if it fixes ur problem. It did for me. One of my hox phones can run 2.1 no issues, but the other one........as soon as i try 2.1 i get all sorts of problems. Try a reflash of the kernel, with 1.8 speed. Post results.
Sent from my HTC One XL using Tapatalk 2

thejosh86 said:
Actually it does work - there was an issue with the cam but a fix was posted.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
CheesyNutz said:
false works fine with the camera fix
Click to expand...
Click to collapse
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\

absolutelygrim said:
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\
Click to expand...
Click to collapse
Checkout post #3 of the BeastMode kernel thread.

zounduser said:
I was seeing this as well, are u oc to the max 2.1? If so bring it diwn to 1.8, and see if it fixes ur problem. It did for me. One of my hox phones can run 2.1 no issues, but the other one........as soon as i try 2.1 i get all sorts of problems. Try a reflash of the kernel, with 1.8 speed. Post results.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I actually flashed the 1.8Ghz version, and I have been running it at 1.7Ghz only.
However, I have all the voltage-step frequencies set to the default. Global voltage is also set at "0 mV". Does anybody have any suggestions for the Voltage Frequency Steps?
Also, although I have the "Use Separate Voltages" unchecked. I noticed two separate settings for Frequency steps that seems kind of odd.
On one, the frequency says 0MHz, with a corresponding voltage of 852mV.
However, right underneath, the frequency says 0MHz again, but with a voltage of 0 mV. Is that something I should change?

absolutelygrim said:
When was the camera fix posted? Thread still says Updated Sep 9th, so I thought it was still broken :\
Click to expand...
Click to collapse
At least two weeks ago, I only found it because I was flicking through the viper thread.
Like redpoint said check post #3 of the thread.
Sent from my HTC One XL using xda premium

Can't flash Beatmode v4, any suggestions?

I've tried flashing v4 probably 4 or 5 times now. I've even tried v3 a couple times. Neither stuck... Ove contemplated just factory reset then going through the whole process again..
What am I doing wrong/not doing?
All caches get wiped before flash.
EDIT: I was just able to flash over the ElementalX kernel just fine. I'm still confused on why Beastmode isn't flashing. When I go to install from TWRP, the .zip install time is no less than 2-3 seconds long and then it says finished.
Sent from my HTC One XL using xda app-developers app

Really... 151 views and not one person has a suggestion?
Sent from my HTC One XL using xda app-developers app

The kernel didn't stick or the CPU settings?
I went into setcpu and it said min 384 max 384 after flashing the kernel.. so I sent min to 384 and max to 1809 and applied set on boot. That worked for.me, but I notice a few bugs. Like the lockscreen won't unlock so I have to hard reboot
Sent from my HTC One XL using xda app-developers app

The kernel...
Sent from my HTC One XL using xda app-developers app

Myrder said:
I've tried flashing v4 probably 4 or 5 times now. I've even tried v3 a couple times. Neither stuck... Ove contemplated just factory reset then going through the whole process again..
What am I doing wrong/not doing?
All caches get wiped before flash.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Don't post threads unless you've tried full wipe. No one knows what's wrong if you're doing a dirty flash.

Myrder said:
The kernel...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Works for me and I use SetCPU..

Might just do a factory reset and see if that won't solve my problem.
Sent from my HTC One XL using xda app-developers app

work yet? I have the same problem and i am on stock .....wiped dalvik,cache, before i flashed it....it just says sucessfully installed...it flashes very quickly for some reason when I know it should not...did a recovery before i flashed, recovered....still nothing..

Literally just did the factory reset and didn't do a thing. So I just rebooted my backup and am now going on about my business. I'm almost to the point of giving up unless something else pops in my head besides running my RUU and then trying to flash again... too dang lazy for that right now. been trying to think all day and now I have quite a few beers in me, it wouldn't be safe.

Myrder said:
Literally just did the factory reset and didn't do a thing. So I just rebooted my backup and am now going on about my business. I'm almost to the point of giving up unless something else pops in my head besides running my RUU and then trying to flash again... too dang lazy for that right now. been trying to think all day and now I have quite a few beers in me, it wouldn't be safe.
Click to expand...
Click to collapse
Don't do it! IceColdJelly isn't worth it!

absolutelygrim said:
Don't do it! IceColdJelly isn't worth it!
Click to expand...
Click to collapse
Lol, I should say that it would only be a test.. There is no way I am getting rid of ViperXL 2.1.2. Love this ROM.
You think I may have done something with my phone to where it wouldn't install v4 when I tried to flash over the ViperX ROM do you? I keep thinking about that, I don't know if that would have any effect on anything considering I was able to RUU back to stock and flash my current ROM.

Myrder said:
Lol, I should say that it would only be a test.. There is no way I am getting rid of ViperXL 2.1.2. Love this ROM.
You think I may have done something with my phone to where it wouldn't install v4 when I tried to flash over the ViperX ROM do you? I keep thinking about that, I don't know if that would have any effect on anything considering I was able to RUU back to stock and flash my current ROM.
Click to expand...
Click to collapse
That brings up a good point.. but since your RUU'ed it should have gotten rid of any corruption applied by the international ROM..
edit: btw, IceColdJelly is an international ROM that will brick your phone,, currently there is no fix (for 2.20).. don't even try it buddy

absolutelygrim said:
That brings up a good point.. but since your RUU'ed it should have gotten rid of any corruption applied by the international ROM..
edit: btw, IceColdJelly is an international ROM that will brick your phone,, currently there is no fix (for 2.20).. don't even try it buddy
Click to expand...
Click to collapse
This I know, I saw that when I found ViperX 2.6 in the international thread... Going to try the stabilizer from the v4 thread and see if that will work. read a post about page 14 +/- a page said to try the stabilzer and see if that would work.
Edit: Speaking of no fix for bricked 2.20, how's that coming? Jtag looking like the only method so far? Haven't read your WIP thread in awhile.
Edit2: Stabilizer didn't do a thing. I really want to be able to flash this kernel... :crying: Seems like it does a really nice job for everyone that has it working... Might end up with going back to RUU again, when I feel I am competent in flashing everything correctly, in the next day or so.

So I've tried another option..
Trying to pull the boot.img from the kernel using "adb pull /tmp/abootimg". Since that looks like where it makes the boot.img in Aroma. Didn't work.
Just flashed ElementalX v1.14 and that works just fine.

[Q] Sense based ROM's won't work on my HOXL

Hi every one ! since I rooted my hoxl I have only flashed aosp ROMS not sense based roms , so yesterday I decided to flash one (Hakataxl) when the phone booted up I cooldn't pass from the lock screen when I tried to slide the ring , boom reboot I even flashed the ROM twice !
and flashed another rom (VIPER) the same thing happend please help me

Also did you do a full wipe in twrp? Factory reset, system, cache, dalvik cache?
Sent from my HTC One X using xda premium

I'm on 1.09 hboot and after I switched From liquidsmooth Rom to viper, viper wouldn't boot. I actually has to flash kernel separately. And instead of the viper boot screen liquid smooth screen kept popping up. The Rom would boot but crash and reboot once I tried to do anything with the phone.. so maybe try flashing a sense kernel after Rom install regardless of your hboot. Also make sure you wipe everything venomtester said
Sent from my HTC One X using xda app-developers app

31ken31 said:
I'm on 1.09 hboot and after I switched From liquidsmooth Rom to viper, viper wouldn't boot. I actually has to flash kernel separately
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Maybe that's what the problem is with my fiancé's phone!
Sent from my One XL using XDA Premium

timmaaa said:
Maybe that's what the problem is with my fiancé's phone!
Sent from my One XL using XDA Premium
Click to expand...
Click to collapse
There was more I was typing hit submit by mistake when my dog jumped on me
Sent from my HTC One X using xda app-developers app

remulacha said:
Hi every one ! since I rooted my hoxl I have only flashed aosp ROMS not sense based roms , so yesterday I decided to flash one (Hakataxl) when the phone booted up I cooldn't pass from the lock screen when I tried to slide the ring , boom reboot I even flashed the ROM twice !
and flashed another rom (VIPER) the same thing happend please help me
Click to expand...
Click to collapse
Is your screen not working at all? Are your volume buttons still active at the welcome screen?
If this is the case it sounds like you need to downgrade your touchscreen firmware. This can be done here -> http://forum.xda-developers.com/showthread.php?t=2159863
If they're not working well I've got no idea

Eios said:
Is your screen not working at all? Are your volume buttons still active at the welcome screen?
If this is the case it sounds like you need to downgrade your touchscreen firmware. This can be done here -> http://forum.xda-developers.com/showthread.php?t=2159863
If they're not working well I've got no idea
Click to expand...
Click to collapse
Wtf?
Sent from my One X using xda app-developers app

yup
Scozzar said:
If you aren't S-OFF, did you manually flash the boot.img?
Click to expand...
Click to collapse
yes , I always flash it manually

well
Eios said:
Is your screen not working at all? Are your volume buttons still active at the welcome screen?
If this is the case it sounds like you need to downgrade your touchscreen firmware. This can be done here -> http://forum.xda-developers.com/showthread.php?t=2159863
If they're not working well I've got no idea
Click to expand...
Click to collapse
Everything is working, im telling you after y swipe the ring and pass a couple of steps of the first set up it just reboots

What version of twrp?
Sent from my Sony Tablet S using xda app-developers app

!
Venomtester said:
Also did you do a full wipe in twrp? Factory reset, system, cache, dalvik cache?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
isn't it system the same as Factory reset? any ways, yes I did all that! like a normal rom flash

twrp
exad said:
What version of twrp?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
2.4.1.0 by the way what does the "system" in Wipe menu deletes?

Its a blessing to be able to use only aosp lol!
Sent from my One X using Tapatalk 2

"System reboots on Sense" is almost always "out of date firmware".
You need to flash a firmware.zip for Jellybean ROM's.
There is one floating about in the ViperXL thread that contains a few things you need and avoids things like hboot 2.14 etc.
http://forum.xda-developers.com/showthread.php?t=1868236
"WiFi Partition Updates".
The other way to do it is to get a first round 3.17/3.18 ota and flash the firmware.zip in RUU mode.
I say first round as many carriers are now onto their second 3.17 and they are not complete firmware.zip and lack many of the firmware files.
The first round ones are all complete.

InflatedTitan said:
Its a blessing to be able to use only aosp lol!
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Actually, YEEES! but I need battery more than anything and aosp roms don't offer that kind of battery life that sense roms give you

I get crazy battery life on cm 10.1 official and all roms based on it.
Sent from my Sony Tablet S using xda app-developers app

No Kidding?
exad said:
I get crazy battery life on cm 10.1 official and all roms based on it.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Well tell me your tweaks or kernel or whatever you use cause I get 7-10 hours normally

No tweaks. I just use greenify to nullify any wake locks and disable any radios I'm not using.
I get about 16 hours checking texts, listening to tunein radio to and from work.
Web surfing. About 3-4 hours screen on.
Sent from my One X using xda app-developers app

exad said:
No tweaks. I just use greenify to nullify any wake locks and disable any radios I'm not using.
I get about 16 hours checking texts, listening to tunein radio to and from work.
Web surfing. About 3-4 hours screen on.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yeah I think im a more heavy user any ways will install greenify and flash that jacob rom ... any cpu governors? or just on demand

I just use on demand. Though I have used smartass v2 and Wheatley in the past which also yielded good results.
I only use the Jacob kernel for swipe to wake, otherwise I would probably use stock.
Sent from my One X using xda app-developers app

sense 5 r3 problems

I have flashed sense 5 r3 multiple times, and also did a ruu twice. No matter what i do, that rom's callling app wont work. I have twrp 2.6. Its not a bad download either. Any tips or ideas on how to fix this? currently on pacman rom and calling works fine. When I click on the calling app when i dial a number and call it says "com.android.htcdialer has quit" I have looked around for a while, but could not find a solution.

jeffcojake said:
I have flashed sense 5 r3 multiple times, and also did a ruu twice. No matter what i do, that rom's callling app wont work. I have twrp 2.6. Its not a bad download either. Any tips or ideas on how to fix this? currently on pacman rom and calling works fine. When I click on the calling app when i dial a number and call it says "com.android.htcdialer has quit" I have looked around for a while, but could not find a solution.
Click to expand...
Click to collapse
Missing lots of vital info. What hboot? S-off or S-on? If S-on, did you remember to flash the boot.img seperately via fastboot?

fastboot erase cache, then use recovery to format cache.
Worked for me.
Sent from my One X using xda premium

redpoint73 said:
Missing lots of vital info. What hboot? S-off or S-on? If S-on, did you remember to flash the boot.img seperately via fastboot?
Click to expand...
Click to collapse
So off. Hboot 2.14. And I have tried to erase cache dalvik and system and data and android secure. I have tried all of that
Sent from my One X using xda premium

He did say fastboot erase cache, completely different.
Sent from my Evita

jeffcojake said:
So off. Hboot 2.14. And don't tell me to erase cache dalvik and system and data and android secure. I have tried all of that
Sent from my One X using xda premium
Click to expand...
Click to collapse
Did you have cwm on there previously?
Sent from my One X using xda app-developers app

exad said:
Did you have cwm on there previously?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I ha be had clockwork mod on there a few days ago, but I did a RUU last night.
Sent from my One X using xda premium

jacobas92 said:
fastboot erase cache, then use recovery to format cache.
Worked for me.
Sent from my One X using xda premium
Click to expand...
Click to collapse
So I flash the ROM then erase and format cache?
Sent from my One X using xda premium

Check out this thread op
http://forum.xda-developers.com/showthread.php?t=2192929&highlight=com+android+htcdialer&page=4
Sent from my One X using xda app-developers app

jeffcojake said:
And don't tell me to erase cache dalvik and system and data and android secure. I have tried all of that
Click to expand...
Click to collapse
No offense, but it sounds a bit rude to day "don't tell me . . . " when folks are just taking their free time to help you. If you did it, you should tell us exactly what you tried in the OP (which you did not, OP was lacking much basic info). If you want proper help, list as much detail as possible in your OP. Otherwise we can only guess at what you did/didn't do. And it makes a lot more sense to raise the seemingly obvious/easy hints, rather than assume (and have the "easy" stuff go overlooked). Its not unheard of that the "helpers" on here start going into more complicated or drastic fixes; when it turns out the solution was something very easy or basic.
As Occam's Razor says, the simplest solution is often the correct one.