[Q] the process com.android.phone has stopped unexpectedly - TouchPad Q&A, Help & Troubleshooting

I'm currently running the latest CM9 on it with moboot... It seems like every time it boots up it pops up with that error message and literally won't go away and you have to reboot the device.. the only way I've found to temporarily fix it is to just wipe cache.... but it always comes back.
Is there any way to prevent this from popping up? It happened when I was on Classicnerd BUTTA too.

Wipe the system and caches, then reflash

I had this problem as well a while back. Wiping caches and reflashing the ROM worked for me.

And you guys didn't have the problem again, after that?

Help manually moving contacts and choosing a JB ROM.
If a pro could help me out I would appreciate it very much. I have been trying to move from a dangerous ICS build to JB and I am having this same problem.
My N7000 previously had this on it:
android 4.03
radio 19220zclp6
kernal version 3.0.15-i9220zclp1-cl131270 (bad ics kernal)
build number midnote 2.0 iml74k.zclp1
So I used ODIN to flash it to a GB rom but I got the com.android.process error and my phone would lock up.
So then I found this link http://forum.xda-developers.com/showthread.php?t=1424997 and flashed this ROM "N7000UBLR3 N7000UVOLR1 - Download - Argentina" from the bottom of the page. I wiped only the the cache (not the phone reset) and flashed it again but I still get the process error and phone locking up. I don't even know if this ROM is a safe ROM!!
Am I even on a safe kernal now? kernal n7000ublr3-cl890184 build imm76d.ublr3
What I need help doing is the following.
1. Before doing a full wipe, I need to either manually save my contacts to my PC or back them up. (no apps work but my pc can browse my phone) If I knew where my contacts were located, maybe I can manually copy them to my pc? So any help saving data from a partially unusable phone would help.
2. Flash to a safe GB rom, so I can then do the full wipes safely and then flash to a stable JB rom. (I have no clue which roms to choose here and need help).
Thanks for any help..

Related

Boot Loop

Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help
If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?
Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)
when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse
Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.
Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App

[Q] Galaxy S Boot Screen hang meaning?

Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.

[Q] Questions after installing ICS

Ive installed ICS N7000XXLQ2_N7000XXLPT_N7000CPWLP4_HOME.tar replacing my old N7000XXKL3_N7000ODDKL1_INU. I have followed all the steps from STOCK roms page. But i have a few questions now:
1) I have performed a data and cache wipe, but i then turned the phone on back to check my CSC, i skipped all the Welcome to Android steps and just dialed up the CSC check code. Then i turned off my phone to install ICS. Could it smhow affect my phone in a negative way?
2) Although I have performed the cache and wipe data my Android folder Data still has all the Data files from games and apps which i had in my previous software. Is it normal?
3) when first launching the ICS even after a few updates I could not run any new app. Everything would keep crashing. Then I went back into the mode and did a factory reset and wipe thingie again. That helped and i can run newly installed apps. Need your comments about this situation.
Grateful,
QVA
1. Yes. Any wipe or restore on ics stock kernel can cause damage. You won't knoe until it's bricked.
2. Actually i had the same experience under lpy as this when it wouldn't clear the sd card when selected. My interpretation was that ics sd is mounted in a different section to gb and maybe they hadn't updated the kernel to look for this section? I'm probably way off there. I ended up doing a full wipe while connected to pc.
3. Mass fc's seems to be common. Firstly check your dpi setting, make sure it's above 213 as tablet not supported. If that doesn't solve, do a factory reset on a safe gb kernel before upgrading to ics again. Don't do any restores or wipes under ics kernel!
please hit thanks if i helped
Questionvsanswer said:
Ive installed ICS N7000XXLQ2_N7000XXLPT_N7000CPWLP4_HOME.tar replacing my old N7000XXKL3_N7000ODDKL1_INU. I have followed all the steps from STOCK roms page. But i have a few questions now:
1) I have performed a data and cache wipe, but i then turned the phone on back to check my CSC, i skipped all the Welcome to Android steps and just dialed up the CSC check code. Then i turned off my phone to install ICS. Could it smhow affect my phone in a negative way?
2) Although I have performed the cache and wipe data my Android folder Data still has all the Data files from games and apps which i had in my previous software. Is it normal?
3) when first launching the ICS even after a few updates I could not run any new app. Everything would keep crashing. Then I went back into the mode and did a factory reset and wipe thingie again. That helped and i can run newly installed apps. Need your comments about this situation.
Grateful,
QVA
Click to expand...
Click to collapse
How did you do it? I would have used PC Odin to do the flash, so you have a clean install.
If you already had a rooted ICS with CWM recovery, you would be best advised to either go back to a stock GB, root it and then flash the ICS of your choice after a full wipe.
Or you could use Abyss 4.2 to flash from an existing rooted ICS ROM.
now it s getting better
smaiitm said:
How did you do it? I would have used PC Odin to do the flash, so you have a clean install.
If you already had a rooted ICS with CWM recovery, you would be best advised to either go back to a stock GB, root it and then flash the ICS of your choice after a full wipe.
Or you could use Abyss 4.2 to flash from an existing rooted ICS ROM.
Click to expand...
Click to collapse
now after a factory reset and after usb storage format to remove all those files that were left behind durin softwasre reinstallation ICS seems to be working fine. No more fcs, it is working faster than Ginger. I used odin( the pc ver) to flash it.
should i do smth?
Games that used to lag are now not lagging or lag less. Sometimes menu gets a lag spike for half of a sec or smth but i dont mind that. So after that clean up and wipe which left sd files undeleted and then they got removed with a mass storage format i should not worry anymore? everything is fine and wont have any bad result in the future? I have a fully functional ics?
It looks like it. Its probably worth not doing any further wipes or restores under ics if you're happy with the performance. Samsung will be releasing updated kernels within hopefully a month or so, best wait till then.
please hit thanks if i helped

Galaxy S i9000 update

Hi all,
I'm still using my Galaxy S on Froyo and don't feel I need to upgrade to a new handset yet but I would like some advice on rooting and getting my phone updated to the latest and greatest F/W (Custom or standard) so that I can get the best out of my phone and give it a new lease of life. Can anyone point me in the right direction? I've already used Odin a while ago to update from Eclair to Froyo so I've had a bit of experience with this apart from rooting and loading custom ROM's Any help or advice would be much appreciated.
th3rmi1t3 said:
Hi all,
I'm still using my Galaxy S on Froyo and don't feel I need to upgrade to a new handset yet but I would like some advice on rooting and getting my phone updated to the latest and greatest F/W (Custom or standard) so that I can get the best out of my phone and give it a new lease of life. Can anyone point me in the right direction? I've already used Odin a while ago to update from Eclair to Froyo so I've had a bit of experience with this apart from rooting and loading custom ROM's Any help or advice would be much appreciated.
Click to expand...
Click to collapse
download 2.3.6 Firmware from this thread
http://forum.xda-developers.com/showthread.php?t=1102881
then download CM 9 from
http://get.cm/?device=galaxysmtd and flash
if you want JB , install any costum rom from development section
The Tox said:
download 2.3.6 Firmware from this thread
http://forum.xda-developers.com/showthread.php?t=1102881
then download CM 9 from
http://get.cm/?device=galaxysmtd and flash
if you want JB , install any costum rom from development section
Click to expand...
Click to collapse
Thanks for that. What is CM9? Will I need to root first?
I've just attempted rooting. Does this result from Odin look normal?
Hey, Tox. Thanks for the advice. Why CM9? There are later versions, is CM9 the most stable? I'd like to try Slim Bean. Do I need to install that CM9 before I attempt to put Slim Bean on? Also, will I need any other files/apps? I've checked that my i9000 is rooted ok by doing an su in a terminal emulator.
Could anybody point me to a straight forward tutorial which could help me from where I'm currently at?
I've now installed clockworkmod recovery and created a backup to the SD card in recovery mode. I'm guessing the next steps should be pretty straight forward. I just need to know which files I have to download. What's the best Slim Bean for me to try and what other apps should I install with it?
Ok, I've screwed up. I installed clockworkmod recovery and created a backup. I tried flashing the latest Slim Bean ROM and addon pak but my phone wouldn't connect to the cell network. I attempted to recover from the backup using CWM but my phone is now stuck in a bootloop with the Samsung splash screen. Can anybody help me please?
th3rmi1t3 said:
Ok, I've screwed up. I installed clockworkmod recovery and created a backup. I tried flashing the latest Slim Bean ROM and addon pak but my phone wouldn't connect to the cell network. I attempted to recover from the backup using CWM but my phone is now stuck in a bootloop with the Samsung splash screen. Can anybody help me please?
Click to expand...
Click to collapse
you lost your IMEI , that's why i told you to flash CM9 first , to avoid loosing IMEI ,
reflash 2.3.6 firmware via odin , root it , flash CM9 , then flash slim bean rom
Thanks. I've just flashed 2.3.6 again and then applied CWM recovery but it still boot loops. Do you know why I couldn't just restore from the backup I'd created?
How can I flash the CM9 pack with Odin? It's a ZIP folder and wont recognise it. Please help.
Is there any other way around this? I've just installed SB again with the addon pack just so that I could get the CM9 onto my SD card. What's the best way to sort this out and get my IMEI number sorted?
Can anyone help me at all?? I have the IMEI number in the back of the phone if that's any use?
th3rmi1t3 said:
Is there any other way around this? I've just installed SB again with the addon pack just so that I could get the CM9 onto my SD card. What's the best way to sort this out and get my IMEI number sorted?
Click to expand...
Click to collapse
this how to install cm 9
Put it ( zip file ) to your phone's internal sd-card
Reboot to recovery (vol up + home + power)
Wipe data/factory reset
Wipe cache
Advanced > wipe dalvik cache
Install zip from sd-card
Choose zip from sd-card
Select cm-9.0.0-galaxysmtd.zip
Confirm
Wait
Go back
Reboot
the same you way you do with a JB rom
and please push thanks button ,
Thanks for the reply T. So should I do a full wipe (Wipe data/factory reset Wipe cache Advanced > wipe dalvik cache) before installing 2.3.6, then apply the CWM update followed by your instructions above? Will that recover my IMEI because, as you said, it's definitely no longer there.
I've just wiped everything and installed GB 2.3.6 and got the following messages. Does this look ok? Also, after I'd done that, I rooted it with CWM then tried installing the latest stable CM10 but now when I reboot, it shows the CM/Samsung screen as if it was booting then it just goes back to the CWM recovery What do I do now??
Success!
I've just powered up my phone again and suddenly the Cyanogen startup screen appeared! I powered down and put the SIM back in from my backup phone and I'm back on the phone network. I was reading up on lots of other complicated ways of recovering the IMEI and this has been really straight forward. I'm liking the Cyanogen 10.1.2 so far so might stick with that. Thanks so much for your help TT!
So to answer a few of your questions, I know I'm late to the party but for future reference
-The reason why Tox recommended flashing CM9 first is because problems can occur going straight from 2.3.6 to Jelly Bean in terms of your IMEI- your device's "identification". If you lose the IMEI, you lose the ability to connect to your network provider. Flashing CM9 and letting it boot as an intermediate step prevents this from happening. Once you've booted CM9 when you flash and you have reception, you're all goods to flash any JB rom from there.
-Your bootloop from recovering the backup that you made from Slim- I'm guessing it was a backup from 2.3.6- has nothing to do with the IMEI. Phones can boot without the IMEI. Its because the data partitions in 2.3.6 are different to those in Jelly Bean. Hence they're incompatible with each other- you tried to restore a different data partition that what was available on Slim Bean (because it was Jelly Bean).
-Flashing any 2.3.6 rom will restore your IMEI. However regarding the photo you took with the red error messages...
-That's because of the reason I mentioned above, with the data partitions. Because they're different, the phone can't recognise them and so can't boot, hence resulting in a bootloop. Easy way to fix this- there's a file called dbsdata.rfs.tar (its somewhere in these forums, right now I can't find a link). If you get that situation again, just pul the battery and reinsert it, go back into download mode, put dbsdata.rfs.tar in PDA, let it flash. That should put the right data partition on the phone.
Hope that these clarified some of your questions!
Sent from my GT-P7510
Thanks for the tips and clarifying all that for me Soryuu. Much appreciated. Now I've learned a little more, I can have a play around with different ROMS with a bit of confidence. :good: Any suggestions on good things to try out? I think I still need to apply some add-on's for this CM10.1.2 build as I don't have market place, google, FB etc.
th3rmi1t3 said:
Thanks for the tips and clarifying all that for me Soryuu. Much appreciated. Now I've learned a little more, I can have a play around with different ROMS with a bit of confidence. :good: Any suggestions on good things to try out? I think I still need to apply some add-on's for this CM10.1.2 build as I don't have market place, google, FB etc.
Click to expand...
Click to collapse
Don't forget your Gapps ;3 (most roms need them to be flashed seperately)
Good things to try out as in?
Sent from my GT-P7510

Install Stock Firmware (JB 4.1.2) without Odin

Hi everyone, I'm here because i have problems with my phone and i want to fully restore. To do this i would like to install a new ROM, but from what i've seen, to install a ROM is necessary to have the stock JB 4.1.2 on the device, while i have CyanogenMod 11 (4.4.4) running.
This wouldn't be a problem if i could use Odin, but apparently my USB port has something wrong, and i cant connect my phone to any PC, so i cant flash in that way. Luckly i can access to the custom recovery (CWM), so i 'd like to ask if there is a way to flash the stock firmware via CWM.
Instead, If I can install a ROM starting directly from CM11 without restoring stock JB, or if i'm missing something important, let me now, i would appreciate a lot
Thank you in advantage. (Excuse se for any misspelling, I'm not English)
What kind of problems do you have?
If you can access CWM recovery there's no need to install stock in order to flash a new ROM, just be sure to wipe caches and data before installing the new one to avoid related bugs; and you will probably need to update the recovery to TWRP if you want to flash one of the most recent ROMs
It's always recommended to create a backup before everything else.
Peace
Hi, thank you for then anwer Well, it would be a long list of problems ^^ The biggest one though is the fact that if I'm in AeroMode everything works as always, sometimes bugged but nothing exceptional, but in the moment i switch AeroMode off and digit the SIM pin, the phone turns off and then enters in a bootloop(vibrating every 1 minute like before entering the main window, but it remains stuck) that is solvable only pressing for 8/10 secs the POWER button and restarting it. I can't have a phone which is not able to make voice calls :/ Back to the problem, so if i'm not misunderstanding anything, I dont need to reverto to stock and then reflash the new ROM? Because, for example, in the main page of CM13 it's written:
ROM Firmware Required: Stock + CWM compatible with KitKat
and that's the origin of my post... But in case, which wipe should i do? Dalvik + wipe data/factory reset?
OK, the thing is that you need stock + CWM at minimum, it means you can't install it if you are on gingerbread; but if already installed something higher than 4.1 you can go from there.
First create a backup then wipe cache, wipe dalvik, factory reset and install your preferred ROM
Ohhh, that makes sense.... Ok, so i will wipe what you said and flash the new ROM! You saved me a lot of time, thank you so much!

Categories

Resources