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...
Related
Hello everybody.
I am having serious trouble with my phone and I was hoping some of you might be able to help me out.
I just bought my SGS 3 days ago. It came with android 2.1.1 eclair installed.
I had read that that version was not the best ( the first thing I saw when I opened the phone actually was an error screen, and the lag was horrible) so when I got home I decided to try and upgrade it using the official software for it (Kies).
Unfortunately Kies would simply disconnect my phone when I told it to upgrade, after which it would ask me to upgrade again >.>
So I decided to use Odin to flash one of the newer 2.2.1 versions.
I flashed a 'JS3' version with a repartition to 803 pit , but it crashed after rebooting with the dbdata error (which as I learned later was caused by not flashing a full firmware).
I flashed JPU after which worked great. It was fast and responsive.
However my phone kept crashing. Whether on standby, using apps, or just trying to dial a number, it would freeze, start vibrating, and sometime reset, other times just stay frozen until I force shut down it from the power button.
I flashed JS5 afterwards, with full cache clearing, factory reset etc. Still crashed.
Then I tried flashing Darky's 9.2 Ressurection. Loved it but I couldn't even set up my google account because it crashed constantly.
Then I went back to what I believe is the current official version for my location and carrier (Vodafone Romania), JP9 .
After flashing it didn't crash, but after a while (one night), it started crashing like crazy, even wound up with weird gray lines and a freeze in the morning.
I was hoping someone here might know what is wrong with it. I already sent it back to be serviced but I am thinking maybe I broke it somehow and would like to know how so I don't do it again.
The phone is network locked, which I later learned is usually a bad thing for flashing, unfortunately I didn't know about that when I started.
well first of you want to remove the network lock so try these:
http://forum.xda-developers.com/showthread.php?t=761045
http://forum.xda-developers.com/showthread.php?t=913681
next step is to register on www.samfirmware.com (its free) and here is where you will get all the latest official firmwares from samsung..
what you want to do is download (XWJS5) with all 3 files and PIT and flash that through odin with RE-PARTITION..
Before you do that, put your phone into recovery mode (volume up + Home button + Power button ) and do a factory reset / wipe cache ect...
so when you have done that and flashed the new firmware. let me know what the outcome is..
another thing.. ALWAYS MAKE SURE KIES IS CLOSED.... EVEN IN THE ICON TRAY... AND MAKE SURE DRIVERS ARE UP TO DATE.
other than that you shouldn't have any problems
hi, thanks for the advice.
I already did most of that however. I did a factory reset numerous times, and I also did a full repartition flash more than once, to no avail.
I am waiting to get it back from warranty service now but I am wondering what went wrong.
Was it broken when I bought it or did I damage it somehow by trying to flash it while network locked ?
flashing with network lock wouldnt make everything force close. the worst thing that could happen when flashing with network lock is not picking up a signal and possible IMEI corruption.
i think you may have just flashed the wrong ROM, it happens to us all, but the more you do it the more experienced you become and you soon learn methods to restore things..
dont worry too much it will be fine when it comes back from samsung, just be sure to read up properly if you have any doubts.. or ask a question first you will get a reply quicker than you can Unbrick your phone..
My phone seems to hate the 803 pit file. Lots of force closes when I used it. Try using 512, see if that works any better.
Hey guys,
So ever since i got my phone for the first few days everything was fine
After i unlocked it and installed the latest stock at that time from
this thread
HTML:
http://forum.xda-developers.com/showthread.php?t=2183023
I started getting a random problem that people couldn't hear me during calls. but i could hear them. Sometimes it worked if i turned loud speaker on and then off. but usually i just had to recall.
I went to the 2.17.401.1 completely stock no changes and i still have the same problem.
Is this something that is common or a handset problem?
Please help
ReWipe/ReInstall
Ramis93 said:
Hey guys,
So ever since i got my phone for the first few days everything was fine
After i unlocked it and installed the latest stock at that time from
this thread
HTML:
http://forum.xda-developers.com/showthread.php?t=2183023
I started getting a random problem that people couldn't hear me during calls. but i could hear them. Sometimes it worked if i turned loud speaker on and then off. but usually i just had to recall.
I went to the 2.17.401.1 completely stock no changes and i still have the same problem.
Is this something that is common or a handset problem?
Please help
Click to expand...
Click to collapse
Did you already try to reflash the stock kernel from HTC??
When I got such a problem, I completely wipe the phone (system, cache, data, sdcard, dalvik,...) and reinstall everythink, Recovery, Rom, Gapps, Kernel and there's generally no problem anymore :laugh:
I hope you'll be lucky to get it back working :laugh:
Hi Guys
My phone is 2 weeks old (refurbishment)
I have rooted my n7000 with PhilZ-cwm6-XXLTA-ATL-5.15.0-signed.zip
on stock ROM N7000XXLT9_N7000XXLT3_N7000OXXLT3_HOME.tar.md5
Then started my problem with my phone.
Initially i thought that just my signal goes off and on and i did not checked anything else as this was just for a short time period. Later, the period was getting longer and longer till signal was back on again. Later i had to hard reset my phone in order to retrieve my signal. After a few hard reset i realized that baseband is unknown and IMEI is is uknown. when dialed *"06" it shown null / null. Also i tried to flash different stock ROMs
I thought its problem with efs so i replaced it from backup but nothing changed. sometimes IMEI and baseband goes on and off again and again.
Would you suggest that is hardware issue or software isue?
It does not bother me much as I will have replacement in 3-4 days. The question is could this happened to my next n7000 again?
I have read may topic on this server but nothing was same issue as mine
I have been flashing and playing with ROM for last couple of years and never had any problem.
I have the same problem before when I started using 4.2 Custom Rom but later after revert back to stock JB the problem disappear..
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
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
koolkeith said:
Hi all, love this forum but dont post often.
Heres the problem: My HTC One m7 (international version) is acting strange:
* Sometimes when I turn on the display I have to enter my sim pin, as if it had rebooted itself, only I know it hasnt. It also happens regurarly when Im using the phone *poff* all of a sudden "enter sim pin".
* When switching from wifi to 3g/LTE it lags for minutes. It drops all connections, including regular gsm, and I have to enter sim pin maybe half the time I swith from wifi. Switching from 3g/LTE to wifi doesnt present the same issues.
* Its extremely laggy when these things happen, otherwise it works fine.
What I have tried so far:
* Old backup of Liquidsmooth 4.4. Works fine for a few days then these same problems starts occuring.
* Uninstalling apps. Thought I was onto something when I uninstalled SwiftKey and it worked perfectly for about 3 days! But then the problems came back...
* Tried other roms but I usually end up with the "unfortunately the process com.android.systemui has stopped" when the rom is up and fully booted. Its a loop that just continues (when pressing ok) so I cant do anything but reboot and try again. I tried probably 5 versions of Liquidsmooth but also Beanstalk and other aosp roms, even Lollipop versions (the liquidsmooth one worked but the same sim pin problems occurred). Havent tried any sense based roms. Also tried several versions of TWRP, official and unofficial. Still ends up with the com.android.systemui problem.
* Tried resetting permissions, wipe cache/dalvik and also wiped the entire sdcard. Used adb/flash to transfer new rom for installation.
So I'm basically out of ideas and pondering going back to stock and sending it in for repair, unless someone here has some tips since I'd rather try myself first.
Thanks for any help or input!
Click to expand...
Click to collapse
maybe your sim is faulty. try to get a new one from your provider. or it just has a bad contact in your phone.
about the lagging: did you try a clean flash? is your storage full? my phone gets pretty laggy when my storage is nearly full..
Hey thanks for your reply! However I dont think its the sim card, and as I mentioned I clean flashed several times with several twrp version and also twice with wiping all data on my sdcard...
Sorry if I can't offer a concrete solution, but I had similar issues (especially the first one, but also lag when switching networks) on my HOX+. Turns out it was the sim.
Try to test another sim before returning, and at least try a sense based rom. Since you say that it works without problem for a few days with Liquidsmooth 4.4, and then it starts breaking again, it may be rom (aosp?) related. But then again, it may be just random.
Hope you figure it out soon
Thanks akpe! I ordered a new sim card, if that doesnt help I suppose its something hardware related...
Well, the new sim card didnt help. My problem seem very similar to this: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/
Basically my whole radio disconnects and restarts itself when turning off wifi. Reading that androidpolice thread leads me to thinking about flashing an earlier firmware, from 4.2.2. I have no idea which one, or if I can use the one in that thread or not.
Any suggestions? I'd appreciate it, googling for hours and reading catlogs for days isnt getting me anywhere..
HELP!
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
akpe said:
Hmm wasn't that a Google issue which got fixed by HTC in the latest OTA? Try a ROM which has the hotfix (like latest ViperOne, 7.0.2) and see if you still get this
Click to expand...
Click to collapse
Hi akpe! I took your advice and am now running ViperOne 7.0.2 and so far it WORKS! So it seems it was indeed that google bug. HUGE THANKS!
Is it possible to have the aosp lockscreen when at the same time using a pin? I can't seem to figure that out.
Thanks again!
Glad it worked
As for the lockscreen, no idea mate, I'm using the stock one :/ Ask around in the ViperOne thread, maybe someone there knows
Ok, thanks again!
Another thing I cant find is profiles? Need it to make whatsapp notification sound silent when listening to music..