[Q] process com.android.phone has stopped problem - Legend Android Development

Hello everyone !
I've rooted my SFR Legend, and since i've flashed the 3st rom, i've randomly this message "The process com.android.phone has stopped unexpectedly" and i need to enter my PIN, at this time i've never wiped, and i decided to wipe data/cache/dalvik-cache, flash radio and flash rom and the problem disappeared. But since i installed another rom (now i redo these steps in the same order every flash , wipe, flash radio and flash rom) the problem came back. I think Froyo must solve this problem and i've wait, now froyo is here and i've already the problem. I've tried to format SD and flash, i've tried to unroot but CID incorrect. I've wiped a time with clockworld mod and another time with r4-legend-root.
I need help please i don't find any solution
Edit: SOLVED , Andromax cause the problem

no answers? i didn't found any solutions

since you have the phone rooted, why don't you just install whitesnakedk's Froyo modified Vodafone ROM? I got tired of waiting for HTC to release one so I went ahead and used his and i feel like I just took it in to the shop and got it souped up, I love it! Everything feels like it's working better. So give that a try and see if the phone app keeps failing.

I think is a problem due to the radio update (included in 2.03), i think many files enter in conflicts between residues (if any) of the original radio and the new version. But wipe doesn't fix this

Related

[Q] Please help me :(

I tried to upgrade to the new 2.2 froyo and all it gave me was the JM2, I had JM1 so I did it. Then the phone started to turn itself on and off again, so I did a factory reset from the recovery menu. Now nothing works and everything pops up with force close. I can't do anything but get back to the 3br. Please, I'm sure I'm getting freaked out for no reason but it's 4am here and I've been working on it for hours trying and looking for something.
did u have a lagfix installed on your phone before u started flashing to 2.1.1 ?
Very similar issue here - used regedit hack to get 2.2 - all I got was the JM2, phone was working fine, but I did factory reset hoping to clear all the old data, after this all I get is "Sorry!, The application TwLauncher (process com.sec.android.app/twlauncher) has stopped unexpectedly. Please try again"
I did have lag fix, but unnistaled it before upgrading to 2.2
How this could be solved ?
install via odin. Kies is a P.O.S
Got the same problem.
Installed Froyo using Kies and the registry hack. After rebooting I checked my Android Version: 2.1 Update 1. So I followed the instructions to do a factory reset. Now all I can do is boot the phone and type in my pin-code. Then there are lots and lots of popups telling me a process has stopped working ...
Can anyone help? Is odin really the only way to regain access to my phone?
Factory reset, clean cash, wipe internal sd-card
I already wiped the cache and also did a factory reset twice. When entering recovery mode I receive the error: "multisc: can not acces to /system/csc/DBT/system/"
How to wipe the internal sd card then?
I have the same problem! Have a brand new Vodafone handset (no lag fix etc.), ran the regedit patch and whilst I didn't get 2.2, I stayed on 2.1 update1 but unbranded. Was delighted to get rid of bloatware but after a factory reset, the same problem!
Using my registry settings, I flashed back to Vodafone firmware but the problem still remains
OK wiped and then even formatted the internal sd-card - did this from windows explorer whilst connected via usb.
I then did a wipe/factory reset, wiped the cache and then reboot.
Still the same problem!
I eventually got it to work
I flashed via Odin, the JPK firmware and that was stable enough to get some sleep. In the morning, I flashed JPM and then rooted and lag fixed. I took the lag fix and even the root off of it before trying to upgrade on Kies so I have no idea how that happened. I'm thinking that flashing with the new ROM is the only way to get it un-bricked after that but it's good anyway because now it has FroYo with root and lag fix even though I was originally trying to keep updates to official channels so to speak (guess I found out just how unsafe the official way is vs. the unofficial way).
Me too! Thanks for the advice, I ended up doing the same!
Only difference is I updated to JPM firmware as shown on this forum - works perfectly Likewise I would have preferred not to have to do the unofficial way - guess my warrranty is now void?
Out of interest, I found it hard to figure the difference between JPK and JPM but I seemed to conclude that JPM is a slightly more recent and technically the 'final' of Froyo?
Flashed via Odin and it started to work, finnaly.
Good question regarding formware versions - it is interesting for me also !

Strange Captivate issue

OK.. First of all I want you to know that I'm not a n00b and that 99% of the cases I know what I'm doing with my phone but this is a weird one
Problem no.1: The simcard keeps on "disconnecting", resulting in disconnection from the network. Since the first seconds I start the phone it does this. Sometimes it doesnt even accept my PIN as being incorrect, but in the notification bar the SIM+! icon disappears for a moment. This is after I screwed a ROM and returned to stock using the OCD JF6.
Problem no.2: It wont master clear! No matter what I do, it wont do it. I tried since the first second when ODIN detects the phone. I tried it when it fully loads the ROM, it just wont go.
Background: Before, I had installed Froyo JPA i9000 ROM with Reoriented kernel 2.1.2 (voodoo lagfix+color,bln). Everything was soooooo fast on that ROM (with around 100 apps installed) but I wanted to theme it. So I tried to deodex it using xUltimate. I followed the (logical) instructions found in a post here and it didnt want to boot anymore... well, it did but in a FCs symphony.
I did what I believed is right and I returned to stock but I forgot to pull out the SIM card... then these problems appeared.
Gimme a hint what could I do. I'm asking first here because a working PDA without a SIM is .. acceptable but a totally bricked one is worse so before I take any steps further I need your opinion.
Thanks a lot.
No one?
Sent from my SAMSUNG-SGH-I897 using XDA App
icezar1 said:
OK.. First of all I want you to know that I'm not a n00b and that 99% of the cases I know what I'm doing with my phone but this is a weird one
Problem no.1: The simcard keeps on "disconnecting", resulting in disconnection from the network. Since the first seconds I start the phone it does this. Sometimes it doesnt even accept my PIN as being incorrect, but in the notification bar the SIM+! icon disappears for a moment. This is after I screwed a ROM and returned to stock using the OCD JF6.
Problem no.2: It wont master clear! No matter what I do, it wont do it. I tried since the first second when ODIN detects the phone. I tried it when it fully loads the ROM, it just wont go.
Background: Before, I had installed Froyo JPA i9000 ROM with Reoriented kernel 2.1.2 (voodoo lagfix+color,bln). Everything was soooooo fast on that ROM (with around 100 apps installed) but I wanted to theme it. So I tried to deodex it using xUltimate. I followed the (logical) instructions found in a post here and it didnt want to boot anymore... well, it did but in a FCs symphony.
I did what I believed is right and I returned to stock but I forgot to pull out the SIM card... then these problems appeared.
Gimme a hint what could I do. I'm asking first here because a working PDA without a SIM is .. acceptable but a totally bricked one is worse so before I take any steps further I need your opinion.
Thanks a lot.
Click to expand...
Click to collapse
Problem 1: can probably be fixed by reflashing stock with the SIM card *not* in the slot (that's about my only guess, never seen that).
Problem 2: master clear must be done with the phone turned on *NOT* download mode. the phone must be fully booted with adb debugging enabled in settings.
xUlimate: it's a poorly written application and it's success ratio is probably about 50/50, another tool to look into is auto-deodexer. Also, both the framework AND the system apps need to be deodexed to have everything play nicely (gtg taught me this one)
id experiment. from what i gather you were able to flash jf6 but it was a bad flash. does it still have download mode? maybe try to flash again and then try to master clear? maybe try to flash another rom, then try to flash back to stock?
this doesn't sound like anything anyone has seen before so your best bet is to just try something.
Thanks a lot for the replies guys!
The master clear was tried from all phone statuses (booting; finished booting; after the phone operated for a while) except download and recovery (i know is not suppose to be done from there).
I did reflash to stock without the SIM, same issue.
I will try flashing again some other rom. I'll try more and ill post the result here
Sent from my SAMSUNG-SGH-I897 using XDA App
OK, so, it seems that for some reason, after stock restore there were still remaining of XEE CSC in the phone..
I loaded the JPA back and now is all fine.
I am having the same issue, unable to clear with CWM or odin, or within the OS in either the stock rom or axura 4 or 5...
Can you please elaborate on your solution?
CSC looks familar to me, thats an ODIN file right? If so, what part of the phone would that be (kernal, modem, OS)?
What do you mean by load JPA? Odin package or CWM? WHole rom or specific parts.
thanks...this has got me stumped
Well, my issue is that I cannot use 2.1 anymore (any 2.1, tried stock Captivate and JM8 from i9000), I don't understand what is wrong but my first bet is that the /efs partition got changed in some way when I loaded JPA i9000 ROM.
Froyo works fine, any ROM I load give me full functionality but on 2.1 the SIM gets disconnected all the time and after a while the phone reboots by itself. Just to make it clear, I never had the usual Captivate reboot issue, it started when this SIM problem appeared.
Note: my product codes are fine, in both nv_data.bin and nv_data.bak the product code is finishing in ATT and my IMEI is available in both 2.1 and 2.2 and is correct, so no IMEI corruption here.
Could someone give me a hint?? Would flashing to stock with phone EFS clear help?

[Q] My N1 always hangs

hi
I have got a Nexus ,just after i got it i unlocked and root it after it changed the Rom .
now it hangs most time for example when i plug the charger sometime it hangs and a big X with an open lock appears and i have no way else to remove the battery.
and some time when i use the GPS and navigation it restarts.
i have tried many Roms and Radios but even when i want to go to recovery it hangs too ,and sometimes no.
i tried to switch to ERD79 (fastboot commands)but i found out that when i finish it,still the radio Ver. is 4.06.00.12_7 .
when i change the Rom or radio it restarts and restarts and some time hangs again.
so please help me to solve this problem
thanks
Did you wipe the data?
yeah ,
every time i wiped data .
what's your version of Hboot and recovery?
HBOOT-0.35.0017
recovery Build RA-nexus-V1.8.0.1
really need help ,i can not use the phone .
it sounds like a hardware problem, but could you try a new ROM see if the problem is still there?
well ,last night i tried cyanogen 6.1 with radio 5.12.00.08 but still have problems.
how can i become sure about the hardware problem ?
is there any test or something like this ??
few days ago one of my friends told me to try RUU.
actually i don't know what is RUU and where i can find it.
i have searched for it and found some for desire but not for nexus.

[Q] Please Help. 3 Day old SGS behaving very strangely

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.

[Q] Trouble getting stable ROM

Hi,
I need to repair a M7 T-mobile for a friend of mine.
It had sort of killed itself. It didn't want to start up again. So I though wel than just reflash te ROM and it schould be ok.\
The steps I took
unlock bootloader
flash custom recovry (TWRP)
use sideload to flash rom, internal sd was unreachable
rom flashed it booted up
everything looked good, running stable on the latest sense 6 maximus HD rom
tried to instert sim if that would work (there is probalby my mistake, use Vodafone SIM)
eversince phone reboots after a minute or so, tried reflashing, full system wipe, everything I could think of
Does anyone have any suggestions how I could fix the reboot problem??
I personaly think it is in the radio wich can't communicate properly with the ROM.

Categories

Resources