I am running the following:
Model Number:SPH-D700
Firmware Version: 2.2.1
Baseband Version: S: D700.0.5S.EC05
Kernel Version:2.6.32.9
Build Number: SRF 1.1.0/TwilightZone 1.1.0
Hardware Version: D700.0.5
I to had the same problem when installing:
"""I got the "$" when I typed in "adb shell" and superuser did show up in the app drawer, so I assumed it took, despite the error I received in cmd."""
However, when I click on an application within the SuperUser app, it gives me the following error: "The application Superuser (process com.noshufou.android.su) has stopped unexpectedly. Please try again." (with a "Forceclose" button)
I also get this error when a incoming call happens and sometimes with text msgs.
"The application Google services Framework(process com.google.process.gapps) has stopped unexpectedly." (With a Forceclose button)
How can I fix these problems? I'm a newbie to all of this, but I'm pretty quick with tech stuff. ... help!
Try reflashing your Kernel by itself through clockwork.
I recently encountered this issue when going to syndicate 1.1.1
For some reason, the Twilight Kernel wasn't flashing properly (or it is not included in the rom itself ) and everything superuser/root related was force closing causing all sorts of issues.
I flashed the Twilight Kernel again, and then in the about page, kernel said Twilight, and now everything works well.
EDIT - Nevermind, it doesn't say Twilight as the Kernel version, but for some reason it worked for me to reflash it.
CW re-flash worked - Contacts?
I did as you said and went into CW and re-flashed the ROM. Everything seems to be running great. However, I'm wondering if importing my contacts is what screwed my ROM up?
Are there any known problems with loading Contacts with custom ROM's?
Specifically Syndicate Frozen ROM?
abqdavid said:
I did as you said and went into CW and re-flashed the ROM. Everything seems to be running great. However, I'm wondering if importing my contacts is what screwed my ROM up?
Are there any known problems with loading Contacts with custom ROM's?
Specifically Syndicate Frozen ROM?
Click to expand...
Click to collapse
I havent read anything through the SRF thread about importing contacts messing anything up.
You may want to post ROM specific problems in their threads so this way the Devs and people that might be experiencing the same problems as you can chime in on
FORCE CLOSE CAME BACK! Dangit!
abqdavid said:
I did as you said and went into CW and re-flashed the ROM. Everything seems to be running great. However, I'm wondering if importing my contacts is what screwed my ROM up?
Are there any known problems with loading Contacts with custom ROM's?
Specifically Syndicate Frozen ROM?
Click to expand...
Click to collapse
After using the phone for a few phone calls the problem came back...
What can I do from here?
Will it screw things up worse if I try the entire process over again? (Root and ROM)
Any help will be greatly appreciated.
David
http://forum.xda-developers.com/showthread.php?t=1091680
I don't know when you downloaded the ROM but the updated the DL link to include the Kernel. I would suggest dling just the Kernel and try flashing that in CWM (Not the ROM, but the KERNEL).
If that doesn't work I would try flashing a different Kernel, either the Genocide or Vision 1.1.
If it still doesn't work then you will have to ask the impaler about it as he know way more than myself about this.
Related
so, i previously had a rooted ROM. one of the stock rooted 2.2 roms that came out a while back. 2.09? and now the new rooted stock roms are out, 2.10? so i tried to install that. used rom manager and installed from SD and everything went well. but now i seem to have a problem with random reboots. haven't quite found a correlation between anything causing reboots yet. is there a way to log what happens to find out what may be causing the reboot?
or should i try flashing a new radio? i really don't see how radio's affect stability (came from winMo where it didn't), but i've seen reports about that here.
i have already tried restoring to my previous rom (via rom manager) and the random reboots are still there.
Well radio is how hardware communicates with software so I would guess it would be that.. in rom manager there is a rom download section.. click on NeoPhyTe and at the bottom there are radios so just flash one of them
Sent from my HTC Desire using XDA App
1. hard reset. is it still doing it?
2. adb logcat. <- this logs what is happening with your phone. but without knowing what is causing it you could be watching your logs for a while
So was a cause found? Reason for asking is because quite a few of us are starting to get the same problem including myself .
Only when i got the phone with the factory 2.2 ota update did it work. I have tried numerous roms to try and find one that gets rid of this issue. I open the camcorder app and it will run fine for 5 seconds, freeze then reboot. Phone was downgraded to 2.1 then rooted with unrevoked3. I have tried CM6, CM6.0.1/2 ans nightlies 94-97, Shadow rom, uncommonsense, jagerrom, virtuous, and a few others. no kernal updates. I never had issues with my moto droid any insight would be appreciated.
I had isues where the camera would freeze up, but no reboot, when i try to start the camera up again, my phone says it cant detect the camera, ruby 1.1.1 unrevoked3 + forever
Don't know if there is a correlation to the two, but they sound similar, did you try ruby 1.1.1?
yes i tried that too. just tried kings kernals too. same no matter what
Which radio are you running? "Phone was downgraded to 2.1" sounds like you might be running one of the 1.00 radios.
2.05 is what it says for baseband
Went to 2.15 seems to have fixed the issues.
I had the same problem with my old ROM and upgraded to Froyo 2.2f and still the phone hangs and restarts after i open the camcorder .... please if anyone knows how to solve the issue tell me ...
fox_fox_2000 said:
I had the same problem with my old ROM and upgraded to Froyo 2.2f and still the phone hangs and restarts after i open the camcorder .... please if anyone knows how to solve the issue tell me ...
Click to expand...
Click to collapse
Update your radio.
im getting FC on com.android.mms so i thought that running "Fix Permissions" in rom manager would fix it but this only results in "An error occurred while attempting to run privileged commands"
the odd thing is that this behavior only shows when i receive a mms, it delivers one mms but then one or two additional empty mms's from a unknown address well that's what it says in the notification bar, arrives stating that it could not retrieve the mms's
i completely wiped 4 times, everything and flashed leedroid latest build last night and that still didnt resolve it.
now im completely stuck
A little more info would help. e.g
what rom are you running.
sense or stock?
Moved to Q&A as not development.
divvet said:
A little more info would help. e.g
what rom are you running.
sense or stock?
Click to expand...
Click to collapse
well i thought i wrote that i was using leedroid but my bad, anyhow im using this one http://forum.xda-developers.com/showthread.php?t=768703
well i did anyway i just flashed in modaco r9 to se if there was any issue with that but it's not. strangely.
I have ReflexTSenseHD 1.6.1 installed on my desire, but the menu "contacts" does not work, or not
passes the message "loading". Does anyone have the same problem?
Is this a very old rom? just wonddering.
Solutions might be to reflash the rom over the top of you existing rom, or try another app like dialer one and see if that works.
The problem is solved, I returned to flash the rom. Apparently all this
working fine.
Thanks.
I'm currently using Cm7. I just rooted it tonight and I'm currently not being able to receive txts. I rooted using Revoked and clockwork recovery.
Did I root wrong? I tried wiping and reflashing different wrongs. I also tried downloading different Messaging apps such as: ChompSms and Handcent, still no luck. Please help
Did you update all radio/WiMAX/PRI/NV?
I'm having the same issue. I was running the latest Calukin rom (which has sense) and all of the sudden it stopped, I uninstalled all my apps, nothing, I flashed to mikfroyo, nothing. Updated my prl and profile, nothing.
I experienced a similar issue switching from one CM7 nightly to another, I forget which I was upgrading from/to. To resolve the issue, I restored the nandroid backup of the last working ROM I had, verified things were working again, and reflashed the latest nightly from there. Good luck, hope this helps...
Brian
brianw7761 said:
I experienced a similar issue switching from one CM7 nightly to another, I forget which I was upgrading from/to. To resolve the issue, I restored the nandroid backup of the last working ROM I had, verified things were working again, and reflashed the latest nightly from there. Good luck, hope this helps...
Brian
Click to expand...
Click to collapse
not to thread hijack, but I was running a sense rom and it happened suddenly
I'm haven the same issue wit my CM7 nightly build 29...any way on fixing that problem
Sent from my PC36100 using XDA App