Model - HTC desire
Android version -2.3.1
Mod Version - Oxygen-2.0-RC6
Build number - GRH78
Hi,
After flashing Oxygen ROM 2.3.1 to my HTC desire i keep getting messages on my htc desire.
"com.android.phone has stopped unexpectedly" - i keep getting the messages until i turn on air plan mode. if i try to disable the airplan mode the message appears again.
After some amount of time that the device is in airplan mode (with no special action taken), if i disable the airplan mode everything works normally.
did anyone encountered this issue ?
Regards,
Eyal Rif
Next time post questions directly related to a rom in the corresponding rom thread or even better don't post it at all cause i'm 99% sure you did not do a full wipe. Which should always be your first though when flashing a new rom and running in to problems.
So if you haven't done a full wipe, boot in to recovery, wipe user data/factory reset, wipe cache and wipe dalvik cache, then flash oxygen again.
Related
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
Hi Guys
I have become a victim of the dreaded "unable to scan for networks" wifi issue and need some suggestions.
The problem originally occured when I upgraded my phone to MIUI-Au, I also upgraded the radio to the recommended version.
When I enabled the wifi after the reflash the phone went into a reboot loop which I could not get out of. I reflashed the phone again with MIUI, everything worked fine until I enabled the wifi and then ended up in the loop again.
I did some looking around and found the suggestions to rename/delete the /data/misc/wifi/wpa_supplicant.conf file which I tried to no avail. I gave up with MIUI and decided to go to another Rom and decided to try out InsertCoin CM7/A2SD+. I installed the rom as per the recommended procedure i.e. Wiped Malvik and normal cache partition & data/factory reset. I also tried both of the recommended radio's on the Insertcoin thread.
My system now no longer gets into a reboot loop when trying to enable the wifi but simply comes up with a "unable to scan for networks" message and then switches the wifi off. I have tried resetting data/ factory resets, Cache and Malvik settings and everything else I could think of.
Has anyone got any other suggestions as to how I could try and sort this out as I have followed all the suggestions I could find on the site?
Thanks
JohnB
Did u try only a factory reset without data wipe? Usually a factory reset solves the problem...
Maybe this might help:
MasDroid said:
First, perform a Nandroid Backup via Recovery Mode, which you can later restore, just incase anything goes wrong.
Try flashing the modified kernel 2.6.29 in Recovery Mode (MCR_oc_v14-signed.zip ), it should work then.
Here is the link to the kernel thread: http://forum.xda-developers.com/showthread.php?t=682419
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=705214&styleid=16
Thanks for the suggestion MatDrOiD. Yes,I have done a factory reset, if that means setting/SD & Phone Storage/factory data reset (tried with "erase SD card" ticked and without ticked). Have however tried your suggestion again but still comes up with the "unable to scan networks" message.
I have also reflashed several new roms (in default settings) in an effort to try to find something that would work, all seem to have the same problem.
I also tried with a different SD card with nothing on it and have reformatted it several times.
System info
Kernel version 2.6.35.10-gdd56551 [v03]-snq-is-still # 1
Build Number: IC GS A2SD+ V20
Software number 2.36.405.8
Android Version 2.3.3
Rom version: InsertCoin_GB_Sense2.1_A2SD+_v20
Radio: 32.56.00.32U_5.17.05.23 tried 32.56.00.32U_5.17.05.08 as well
Would changing the radio make any difference? I have tried the versions recommended for MIUI as well.
Anything else I could try?
Changing radio could work. At first, i would do a full wipe and flash the original htc froyo rom. If the issue still exits, wifiadapter could be broken.
Sent from my HTC Desire using XDA App
Thanks for the suggestions Mat, I tried to reflash the 2.6.29 kernal as suggested but my phone seems to just sit with a black screen with white stripes on the edges when trying to restart with the new kernel. Left it for 1/2 hour but just sits there. Also tried a few other versions of the kernel but all seem to just sit with the white stripes on the scree.
I am going to carry on trying over the weekend and if I don't get it sorted will switch back to the orginal HTC froyo ROM and see if that sorts out the problem. If not will send it back to manufacturer
Thanks again for the suggestions.
JohnB
Hi.
I'm running CyanogenMod7.1.0 on my Moto Defy, and recently, when I turn on mobile data the phone crashes (restarts) within a few seconds.
After restarting, the phone boots regularly, and then reboots every few seconds.
The last lines (before the crash) taken from adb are at: gist(dot)github(dot)com/1134269
a much longer logfile is at gist(dot)github(dot)com/1134231 (new user, can't post urls..)
each crash is marked (by me) with '=======================' and some newlines.
any help would be greatly appreciated.
As this works for almost everyone running CM7 (not seen any other reports of mobile data crashing/causing instability) it would seem sensible to clear cache/dalvik cache from Recovery (reboot, 'vol -' when the blue light shows) then Recovery - Clear Dalvik cache is under Advanced....
Also, if you're overclocking, reset to stock clocks/voltages and see if that fixes it..
You could also try the latest nightly builds - I'm using 'cm7-110809-0713-NIGHTLY-Jordan' without any issues (think I've tried almost every nightly build they guys have created!) and would strongly recommend it over your version.
Working brilliantly so far. THANKS russtyd.
And thank you for the detailed explanation, I didn't know about this recovery in cm7.
Sent from my MB525 using XDA App
I'm glad it was that easy to fix
As it turns out, I spoke too soon..
clearing the dalvik cache worked for about an hour, but than the problem came back.
Here's what I know so far:
using 2G network (with data) is OK.
Installing the 2 latest nightlies (110809 and 110806) - does not crash the phone when data is enabled, but it does kill all 2G/3G network connectivity.
Right now, I'm afraid of a hardware issue, so I'm gonna flush some stock sbf (any recommendations? would love a good tutorial, since it's my first time going back..) to check if it works there.
Anything else I might be missing?
If you want to go back to a 2.2 froyo then the CM7 FAQ is helpful for links to the sbf and drivers etc:
http://forum.xda-developers.com/showthread.php?t=1065798
Just download the following two files (links are in the FAQ):
- RSD Lite and Motorola Drivers (updated)
- SBF 3.4.2-177-005 NORDIC
Install Motorola drivers and run RSDLite, and then follow the first 2 steps of "2) How can I install CM7 RC0?", ie
- Power your phone with Volume Down pressed to enter Stock Recovery, then do "Wipe data/Factory reset" and "Wipe cache"
- Reboot from Stock Recovery with Volume Up pressed to enter Bootloader Mode, then open RSD Lite and flash Nordic
There are more sbfs here http://forum.xda-developers.com/showthread.php?t=966537 but having needed to do a clean install myself of CM7 last week (stuck on 'M' logo after a messed-up nightly install) I know this one works and gets you back to 2.2.2....
Hi...
I rooted and flashed my Desire HD (android 2.3.3),
with this instructions
XDA video "how to root Desire HD"
and "The Advanced Ace Hack Kit"
http://forum.xda-developers.com/showthread.php?t=1259821
and i flashed it with Android Revolution HD
Everything went successfully
and DHD was working perfectly for 3 days...
But yesterday started my problem with LOCK SCREEN.
So, when i am not using phone and its screen is locked,
when someone calls me,
whatever i choose from ACEPT or DECLINE call
i get this massage:
"com.android.phone has stop working force close"
after that i am losing my network, and afer 5 minutes its coming back.
There is one more issue, but with option DECLINE:
When i choose DECLINE, sometimes, the lock screen FREEZES,
the phone is
keep ringing,
my power buton is not working,
volume butons are not responding,
everything on display that i touch touch isn't responding,
BUT the phone IS STILL RINGING and the only way to stop that is to pull batery from the phone and return it...
and everything after that is working perfectly until someone calls me when my phone is in lock screen mod...
I tried to reboot it,
wipe the cash
flashed it again with android revoltion HD,
and the same thing are hapening again...
Please help me
Android 2.3.5
htc sense 3.0
software number Android Revolution HD 6.1.5
Kernel version:
[email protected]#9
baseband version:
12.56.60.25U_26.10.04.03_M
thank you
Should i give you some more information about my DHD?
instaled applications?
Gradjevinac said:
Hi...
I rooted and flashed my Desire HD (android 2.3.3),
with this instructions
XDA video "how to root Desire HD"
and "The Advanced Ace Hack Kit"
http://forum.xda-developers.com/showthread.php?t=1259821
and i flashed it with Android Revolution HD
Everything went successfully
and DHD was working perfectly for 3 days...
But yesterday started my problem with LOCK SCREEN.
So, when i am not using phone and its screen is locked,
when someone calls me,
whatever i choose from ACEPT or DECLINE call
i get this massage:
"com.android.phone has stop working force close"
after that i am losing my network, and afer 5 minutes its coming back.
There is one more issue, but with option DECLINE:
When i choose DECLINE, sometimes, the lock screen FREEZES,
the phone is
keep ringing,
my power buton is not working,
volume butons are not responding,
everything on display that i touch touch isn't responding,
BUT the phone IS STILL RINGING and the only way to stop that is to pull batery from the phone and return it...
and everything after that is working perfectly until someone calls me when my phone is in lock screen mod...
I tried to reboot it,
wipe the cash
flashed it again with android revoltion HD,
and the same thing are hapening again...
Please help me
Android 2.3.5
htc sense 3.0
software number Android Revolution HD 6.1.5
Kernel version:
[email protected]#9
baseband version:
12.56.60.25U_26.10.04.03_M
thank you
Should i give you some more information about my DHD?
instaled applications?
Click to expand...
Click to collapse
Did you use the super wipe before you flashed your rom? If not then go back to that website and download the superwipe and place it on your sd card. Make sure you do a factory reset, dalvik cache wipe then do a super wipe and then flash your rom again. It is important to do factory reset and all the wipes. hope this works.
Super wipe?
No, or i think i didn't
I turned off, and then hold power buton and volume buton,booted into Recovery, cleared the cache, and selected 'install update from sdcard'.
So what i should do first?
1. factory reset?
(on my DHD setings/SD&phone storage/
factory data reset?)
2. dalvik cache wipe (don't know how to do this)
3. super wipe (also don't know how to do this)
Go here http://forum.xda-developers.com/showthread.php?t=840040 and down load " super wipe " to your sd card and the rom that you are going to flash. Go into recovery mode and select wipe dat and factory reset. Then wipe the cache. you then need to select wipe dalvik cache. If it is not on the first list of options scroll to advanced and select and then select wipe dalvik cache. Go back to first screen and select install from sd card, select choose zip from sd card and then select super wipe ( may be named a little different ) once that has wiped everything go back to main mene and select install from sd card again, choose zip from sd card and select the rom that you are flashing and install, once done reboot your phone.
Or alternatively, just download the "super wipe" script, boot into recovery and flash it. You don't need to factory reset, wipe cache or anything else before you run the super wipe script, because it automatically wipes and formats /data, /cache and /system partitions (among other things). Then flash your ROM, which will wipe the Dalvik cache anyway during the install process.
It won't do any harm if you wipe everything manually first then do the same thing again with the script, but you're duplicating work for no real gain.
ok i did this from dazzasky's post
thank you and you hopscotchjunkie
So far so good, this solved my problem
I have tested it with 10-15 cals in lock screen mod and i dont have any of issues above
Moderators if this thread could stay open, that if i found some more bugs to report it here. thank you all
Gradjevinac said:
ok i did this from dazzasky's post
thank you and you hopscotchjunkie
So far so good, this solved my problem
I have tested it with 10-15 cals in lock screen mod and i dont have any of issues above
Moderators if this thread could stay open, that if i found some more bugs to report it here. thank you all
Click to expand...
Click to collapse
Word to the wise. Dont follow any videos. They are normally out dated and cause issues. I will reopen this upon request from op but sense question is answered
Thread closed
I have been running CM13 for few months now. Yesterday the phone turned off and when I tried to turn it back on, it always kept on turning off once it gets to CM boot logo. Sometimes there might be few background flashes (the white circle that keeps on coming up behind sid, like normal boot) and then it would die.
I have since did a clean install with latest CM13 nightly with opengapps pico without xposed framework just to rule it being the cause of the issue. I am able to boot the first time after clean flash but if I reboot, the issue happens.
Installed fulmics 5.0 ROM for testing and it worked fine If I flash CM13 back again, the issue happens.
Tried to capture logcat by running adb logcat and turn on the phone. It still is stuck at waiting for device.
Does anyone else have issues with latest CM13?
Did you try older builds?
Just ask - Did you made full wipe?
halekhonza said:
Did you try older builds?
Just ask - Did you made full wipe?
Click to expand...
Click to collapse
The oldest build I could find is cm-13.0-20160422-NIGHTLY which I tried and same result.
Yes. wiped system, data, cache, Dalvik Cache & Internal storage partitions.