Phone was working fine, could make calls/text, and could use data. I unfortunately didn't realize that the different versions of rumrunner were specific to your phone's software version, and instead thought they were simply different revisions of the program. I realized this after waiting about 20 minutes as it kept restarting my phone and kept saying ''waiting for device'', and decided to try a different version of the program. At this time I noticed I didn't have data and couldn't make calls. I was hoping that running the correct rumrunner would fix this problem, but that doesn't seem to be the case...
I've tried installing CM and seeing if maybe the stock rom was somehow corrupt, doesn't fix the issue. I'm back on the stock backup again, and still having the issue. I tried flashing the radios for my software version, doesn't seem to have any impact...
I thought it would make more sense to post this question in the actual rumrunner thread, but new account limitation are not allowing me to do so. Hopefully I can get a solution to this problem...
Related
Hy everyone!
I have found a very interesting problem regarding my kaiser130 and android...or maybe the problem is in the user?
Anyhow my problem is that no matter which android build i try,no matter which kernel and which radio i dont have working wifi and data connection.
At first everything worked fine but then i had some problems and i didnt have time to fiddle around with android because it wasnt too stable and i had many FC-s so i had to go back to winmo.I had 6.1 on it before,have put on hardspl3.34 then started flashing android and after that i put back winmo from a shipped package with ruu . Now i have more time and i started to experiment with android again.I wanted to use cyanogenmod 6.1.2 but had the wifi-error problem but as i saw many other people had the same so i thought i'd go back to another build,namely incubus26jc's super froyo rls16 i used that for days but then when i had to use the apn or wifi it didnt work...or actually wifi worked but only with static ip,i tried switching kernels from a base one downloaded with atools to clemsyns and scoots but nothing worked for me better yet it even got worse it started producing the wifi-error again.I use the most recent radio tried both the emo version and the atw to no success tried installing both to nand sys on nand data ext2 data.img but nothing seems to be working and now no matter which build i try everytime i get the wifi-error and apn isnt working.Can it be that my bootloader is tarting to fail?Or is my kernel getting corrupted?
Oh and i always applied the appropriate module updates for each kernel.
Can somebudy suggest something useful or i was thinking that is it possible to very hard reset the phone i mean to put it back the way it was?Format the nand put back a normal spl,i dont mind trying thing again but i need the data connection and the wifi.
Oh and i forgot to mention the most interesting thing,when i turn on data it actually turns on and in the modem i can see that it even gets an ip address from my phone provider.
Hello,
I had my p970 for about two years with no problem, I switched between roms pretty often but about a month ago this error started to appear.
when I get a call and I try to answer the mobile wouldn't respond and it keeps ringing till it turns to a missed call, it doesn't matter if it was originally locked or unlocked, and when I try to make a call myself afterwards I get this error "reorganizing internal processes. please try again later" and only rebooting the device fixes it.
I tired everything I could think of, tried flashing a different version of the firmware, different baseband, different rom, going back to stock unrooted with gingerbread, and also tried updating to ICS...nothing worked...
I always had v20c as the firmware I flash when needed, this never happened before but now it's happening all the time...with almost 80% of the calls I get! and only recently it started to happen on its own and I'd only realize if I tried to make a call.
I'm currently on IZS 1.1 which is the rom I had when the problem first appeared. It started two weeks after using it though.
I'd really appreciate any help to fix this. It's frustrating...
For some reason, playing around with (flashing) different ROMS, sometimes I get the error "com.android.htcdialer has stopped responding..." and NO data follows not matter what I do to try and fix this; deleting caches, switching different signal modes, etc.! What causes this? Anyway, I've found that the error returns even after flashing a different ROM and/or kernal or even restoring my backup. I've also found that flashing the radio again fixes this. Just in case anyone finds themselves in same situation.
jasonbiggs said:
For some reason, playing around with (flashing) different ROMS, sometimes I get the error "com.android.htcdialer has stopped responding..." and NO data follows not matter what I do to try and fix this; deleting caches, switching different signal modes, etc.! What causes this? Anyway, I've found that the error returns even after flashing a different ROM and/or kernal or even restoring my backup. I've also found that flashing the radio again fixes this. Just in case anyone finds themselves in same situation.
Click to expand...
Click to collapse
I started receiving this error after I attempted installing a rom that said "Sprint support" but didn't actually support Sprint. After that, I started getting the dialer error whenever I use a Sense based rom. I re-flashed the radios. Sense based roms still don't work, but Cyanogenmod 11 does. Today, I tried flashing the Viper rom and the problem returned. I restored Cyanogenmod, the problem resolved without having to flash the radios again.
Have you learned anything more about this issue? What needs to be flashed to restore/reconnect the dialer??
I believe at this point your only option is to reflash a stock RUU....I had the same issues with mine and reflashing stock was the only thing that fixed it for me
jasonbiggs said:
For some reason, playing around with (flashing) different ROMS, sometimes I get the error "com.android.htcdialer has stopped responding..." and NO data follows not matter what I do to try and fix this; deleting caches, switching different signal modes, etc.! What causes this? Anyway, I've found that the error returns even after flashing a different ROM and/or kernal or even restoring my backup. I've also found that flashing the radio again fixes this. Just in case anyone finds themselves in same situation.
Click to expand...
Click to collapse
Found that this works too:
http://forum.xda-developers.com/showthread.php?t=2634256
Fount 1 trick that fixes this problem.
So I turn on airplane mode, then I make hot reboot, after reboot turn off airplane mode and bam it works
Mine does this if i flash any rom but viper rom or any kernel. i Need a fix
Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc
I have been using CM11 (14-03-2014 I believe), without major problems until yesterday. Sometimes my phone seemed to disconnect from my SIM and I had to re-enter my pin code to reconnect to my operators network. But as of yesterday my device doesn't seem to recognize the SIM card, It doesn't ask for a code at all and can't make any connection whatsoever. I didn't change a thing, this problem started out of the blue.
I wiped cache and dalvik, updated to the latest CM nightly (08-05) but that didn't make any difference. In other threads I read about the baseband that might need an update, but I can't check which version I have now because when I try to enter the hidden menu I get the no network connection error. The strange thing is that CM11 has worked with (I guess) the stock baseband.
Is my phone tripping or could it be that my SIM card is broken?
Help and thoughts will be very much appreciated
Try it on stock to be sure about it.
After some searching I found a phone that could fit a regular SIM card, a Blackberry 9900. My SIM worked perfect in this phone, so that is not the problem.
I Also did a complete wipe and installed a stable version of CM 10.1.3, but that didn't seem to help. I hoped that a downgrade would have done the trick. I might try a ICS ROM or the stock firmware, but I kind of lost hope and i'm starting to think this problem is hardware related in stead of software. I'll report back with results on stock firmware and the ICS ROM.
How can I make sure the SIM reader in my phone is working properly?
Sorry for double posting, but I got an update:
SIM wasn't working with ICS so I decided to go back to the stock ROM. However, when I tried to flash V20B.kdz with KDZ_FW_UPD, the program got stuck at wParam=2010 and iParam=210. The phone is now stuck in S/W Update mode, and I haven't found a way to restore it yet. I will argue a little more with my phone when I get back from work, I'll open a new thread on how to unbrick when I can't do it myself.
Beunhof said:
Sorry for double posting, but I got an update:
SIM wasn't working with ICS so I decided to go back to the stock ROM. However, when I tried to flash V20B.kdz with KDZ_FW_UPD, the program got stuck at wParam=2010 and iParam=210. The phone is now stuck in S/W Update mode, and I haven't found a way to restore it yet. I will argue a little more with my phone when I get back from work, I'll open a new thread on how to unbrick when I can't do it myself.
Click to expand...
Click to collapse
My good friend i know i probably come 2 late but here is the anser 4 future users!!
http://forum.xda-developers.com/showthread.php?t=2069723
its supose to freese in ther!! (not ther but ....)
I have the same problem, and exactly the same error at reflash.
Dead end. Buy a new phone .
I tried to flash it about 80 times. One guy from a gsm repair has a bit luck and make it work at the first, but then, when he wanted to repair my imei, the phone stucked again in S/W Upgrade.