Hi,
I was previously running Quantum Rom until one of the recent builds (I believe 3.2) was having some issues so I switched to a Cyanogenmod Snapshot. When a newer version of Quantum was released, I went to flash it but I ran into some issues. When the setup wizard appeared, I kept getting spam "Unfortunately phone has stopped" messages that I could not go away. Thinking it was a problem with the rom, I went back to flash the previous version of Cyanogemod that was working fine before. But this time when CM brought up the startup wizard, I was getting the same spam message. All I can do right now is restore previous nandroid backups, but for some reason, every time I try to flash a new rom I get this message. Any ideas?
Thanks!
Did you clear cache, data, and Dalvik before and after installing the ROM? Did you try formatting the system before installing?
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?
I have been running CM 10.1.3 for quite a while, and 10.1.2 for a while before that, and out of nowhere last night I was on the browser and it closed, and wouldn't open again. Then every other app I tried wouldn't open, just forced closed right away. Next thing I know, trebuchet starts force closing over and over. So I reboot my phone, and no bootscreen. I used TWRP to recover back to stock and it works fine. But everytime I try to re-install CM it just bootloops. I didn't change anything on my phone for it to crash, i haven't even changed any apps for a few weeks. Anyone know why it would do this?
jamesclay89 said:
I have been running CM 10.1.3 for quite a while, and 10.1.2 for a while before that, and out of nowhere last night I was on the browser and it closed, and wouldn't open again. Then every other app I tried wouldn't open, just forced closed right away. Next thing I know, trebuchet starts force closing over and over. So I reboot my phone, and no bootscreen. I used TWRP to recover back to stock and it works fine. But everytime I try to re-install CM it just bootloops. I didn't change anything on my phone for it to crash, i haven't even changed any apps for a few weeks. Anyone know why it would do this?
Click to expand...
Click to collapse
Do you have TWRP version 2.6.3 by any chance? Most of the bootloop bugs have been attributed to that specific version.
If you do have 2.6.3, downgrade to, I believe, 2.6.1. Otherwise, did you forget to do a cache, dalvik cache, data, and system partition wipe before upgrading your ROM?
sagirfahmid3 said:
Do you have TWRP version 2.6.3 by any chance? Most of the bootloop bugs have been attributed to that specific version.
If you do have 2.6.3, downgrade to, I believe, 2.6.1. Otherwise, did you forget to do a cache, dalvik cache, data, and system partition wipe before upgrading your ROM?
Click to expand...
Click to collapse
Actually, I am running 2.4.4. Whats still odd about it though is that it ran fine for at least a month and had been on all day. The problem didn't start with a reboot, I had been on it for a while and everything forced closed on me. I am about to try to update TWRP to 2.6.1 and try that. I haven't tried any other roms yet either, I would really like to stay on CM though if I can get it to flash back.
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Are you still using the same version of TWRP you used to flash slimbean 4.1? If you are trying to flash newer ROMS with an older version of TWRP, that could be causing the problem.
supercharge1 said:
so heres my problem. i had slimbean 4.1 on my device and it worked great. but i got a new phone and left it in a drawer
decided to give my phone to my sister and the update message showed up in my notifications
i downloaded it and flashed as i have a million times before
then i was stuck in a bootloop.
i did the usual, full while, cache and dalvik, and no success, the same has occured with every rom except the miui rom for some reason that one works
i have noticed that i can not factory reset the normal way, i have to use the alternate under settings in twrp
i have also used the super scripts and i noticed that it gets stuck on clearing the cache, any ideas?
Click to expand...
Click to collapse
Try TWRP 2.6.1.0
Hello XDA,
Finally signed up after lurking around for too long downloading ROMs and flashing stuff up.
My phone, Galaxy Nexus I9250 has had Roaming problems since two months.
I will divide it into two parts, the detailed story and tl;dr
Detailed Story
Since January I had used XenonHD ROM(1-16-14) till February, when they gave a new update(2-21-14). I did a dirty flash (Cleaned /cache and dalvik only) and noticed my phone had gone into roaming, so I did a complete clean flash (Factory Reset,Data wipe,Cache wipe,Dalvik wipe) using the newer PA Gapps(20140217) and it gave me a weird error stating unusually large memory? so I used the older one which I had used in January(20140123) and it gave no problems while flashing, but the device was still in roaming. And the older version of XHD started giving me roaming as well.
Repeated the same process with other ROMs (Gummy, Carbon, Liquidsmooth) they all gave me roaming. Thought it was weird so I did a stock flash using Unified Android Toolkit, the issue disappeared. It appeared again when I flashed custom ROMs. So I reverted back to stock and did a unroot-Bootlock thing. Unlocked and rooted it, installed SuperSU and CWM. Flashed XenonHD(Feb) and while resetting I saw that it said "fix root (/system/xbin/su)" said 'yes' and continued, the root error has not gone, I was still on Roaming.
I gave up and tried installing AOSB and OmniMetal which worked great! :victory: I absolutely loved XenonHD and it seemed I was the only one with the problem. I waited for their next update.
Previous evening I noticed the new update and downloaded the new PA Gapps(20140318) and the new XHD (03-24-14).
This time I updated the CWM Recovery (Noticed the UAT was out of date) and did a recovery zip flash, Factory reset, Data wipe, Cache partition wipe, dalvik wipe, and proceeded to install XHD, Gapps, no root error was given this time.
Booted. STILL ON ROAMING!! I did a skip skip skip to copy the old AOSB for flashing, I hit 'Phone is ready to use' and it resetted into boot screen (Not the Google screen, but straight to XHD boot). Connected to WiFi and it booted nicely. Absolutely enraged I did a full Odin Flash(JWR66Y) after doing a search on Roaming issues.
It was of no help and XHD still gives me roaming so as with other ROMs...and absolute 12 hours of doing everything possible...any suggested fixes?
tl;dr
Used XHD in Jan, did a dirty flash on their Feb ROM update. Roaming.
Did a clean flash(Factory reset, Data wipe, Cache partition wipe, dalvik wipe) using new gapps, some 'memory too large' error. Used old gapps. Still on Roaming.
Did other ROM flashes I still got roaming.
Reverted to Stock.
Flashed XHD again and still got roaming.
Did a Unroot-Lock, unlock root. Flashed XHD again, gave me a "fix root (/system/xbin/su)" in CWM recovery, clicked yes, the root error hasnt gone.
Installed AOSB and OmniMetal and the network didnt give me roaming (Root error still there).
Waited for the next XHD update.
Downloaded XHD and new Gapps last night and did a CWM update (unified android toolkit was out of date) and it still was in roaming!!
Booted in XHD and clicked skip skip skip and after the last screen it resets into boot with XHD logo. Had to connect to WiFi to stop it from happening again.
Absolutely enraged I did a complete Odin flash JWR66Y as suggested in most of the roaming issues and the error still prevails.
-----------------------------------------------------------------------------------------------------
Any suggested fix?
Phone was originally bone stock, I then rooted & installed TWRP recovery, booted into TWRP and did the Backup option and saved it to SD Card, I then flashed CM 12.1 and used it for a little over a month, trying the various Nightly updates.
I decided to go back to the stock rom I had backed up previously, It restores successfully but when I boot the phone everything is crashing once it hits the home screen, "Unfortunately xxxx has stopped" is seen over and over, I can't load anything, even the settings menu crashes.
I then tried rebooting into TWRP and did Factory reset but when I do this It wont ever get past the Samsung logo on reboot.
Not sure what went wrong with the backup or if Im missing a step? I also tried enabling the verify MD5 check option for the Backup and it says everything is fine.
For now I'm back in CM 12.1, Any ideas appreciated!
mathesar said:
Phone was originally bone stock, I then rooted & installed TWRP recovery, booted into TWRP and did the Backup option and saved it to SD Card, I then flashed CM 12.1 and used it for a little over a month, trying the various Nightly updates.
I decided to go back to the stock rom I had backed up previously, It restores successfully but when I boot the phone everything is crashing once it hits the home screen, "Unfortunately xxxx has stopped" is seen over and over, I can't load anything, even the settings menu crashes.
I then tried rebooting into TWRP and did Factory reset but when I do this It wont ever get past the Samsung logo on reboot.
Not sure what went wrong with the backup or if Im missing a step? I also tried enabling the verify MD5 check option for the Backup and it says everything is fine.
For now I'm back in CM 12.1, Any ideas appreciated!
Click to expand...
Click to collapse
Have you tried the wipe option.. for a clean install?