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?
Ive installed the "HTC Sense" ROM numerous times.
(http://forum.xda-developers.com/showthread.php?t=837042)
After installing everything works good for a while, things start messing up after i leave the phone down for a while or restart the phone. After the phone restarts i constantly GET FC's.
android.process.acore has stopped working
android.process.swype.inputmethod has stopped working
Occasionally GMail will FC to but that stopped after a factory reset.
Ive installed this ROM a good 5 times. IM coming from a deodexed STOCK android ROM.
Ive Wiped Dalvik
Did a factory/data reset
Chose the ZIP file
and booted back into system
and it works good until i leave the phone for a bit or restart it.
I flashed back to stock since i cant use the phone with the constant force closes.
I REALLLY would love to use the Sense ROM. Any help would be appreciated.
Thanks!
I thought I'd try out a USB Host Mode patched kernel (even though my new Note II should be here Monday) but that stopped the wifi working for some reason. I tried flashing another kernel (no host mode) to fix it and the wifi is now working but shortly after booting the signal disappears completely.
It's fine when the phone boots and can ring/access the net but very quickly I get "No service". I also flashed a new radio just in case and still not working,
I'm running CM7 on it, tried flashing Tiamat kernel and ManU but both do the same. Any ideas how to fix it?
Hmm, even going back to the host mode kernel I tried first isn't giving me signal now. I did start to think it might just be a coincidence and be something to do with an upgrade I ordered today but my old Kaiser is working with my SIM card.
Odd.
I reflashed the CM7 zip and its working again now.
Hey guys,
I have been happily running Android revolution HD JB sense 4+ for a while now.
Today I was playing around with some other ROMS and after that I decided to reflash Android revolution HD JB sense 4+ again.
So I did, but afterwards I have nog signal or wifi. Long pressing the powerbutton says that Airplane mode is on (though no icon appears) and when I look it up in the settings it is grayed out, saying 'disabling airplanemode', yet it is frozen at that state. Turning on data connection gives an error that it can't find a network, turning on wifi just gives 'error'.
I tried reflashing the rom again, making sure to erasing and clearing everything, yet no succes.
Any ideas for a way to fix, or does it need to go to HTC?
This happened to me recently too after a flash.
You'll need to reflash the ROM again.
The-Last-Hylian said:
This happened to me recently too after a flash.
You'll need to reflash the ROM again.
Click to expand...
Click to collapse
Yeah, I tried reflashing the rom, didn't work. At this very moment flashing another rom compatible with this Hboot.
EDIT: That fixed it.
Hi there, since I'm not obligated to post replays under development thread here's the place to do it.
I just installed newest version of LiteROM (used 0.7 previously) and I found some unpleasant behaviors.
First of all - I couldn't get wifi connection to work. Password was ok but it continuously tried to authenticate or get proper ip. Re-flashing with stock rooted rom, then gettin literom over it worked like a charm.
But, after installing newest LiteRom I'm getting message every time I reboot device: ... android.process.acore has stopped working.
Also, when trying to set lockscreen wallpaper it gets me a message: ... TwWallpaperChooser has stopped.
So, is there any proper fix to get things right or maybe I'm doing it wrong?
(I did full wipe before all installations but it does not resolve issues)
First, you might try downloading the ROM again(preferably from a pc) to see if maybe the download was bad.
Sent from my jelly monster.
Already did. Then reflash with FULL wipe - nothing. As long as sim card isn't on, there's no issue with .acore (it happens even when switching airplane mode on/off). I also tried to wipe contact and contact manager data but with no good solution.
Another thing is - I've tried IcePop rom and it worked fine. IMHO, there's something in literom that causes such bad behavior.
I would be grateful for helping me resolve that :good:
Hmmmm. The only problem when i flashed literom is if i didnt install the stock gallery then it seemed to crash the lockscreen wallpaper when trying to choose a wallpaper from settings and did not give me and option in quickpic.
Sent from my jelly monster.