Database Users

Process System isn't responding

Hi
I'm having issues with my I9505 Galaxy S4. The phone was rooted and after trying a few ROMs (Omega) etc I returned to a NAND backup with was basically rooted stock (via TWRP). Over the weekend strange lock-ups kept happening and I keep getting - Process System isn't responding. When I try and make a call the phone either reboots and hands for a minute and returns that error. This morning I have flashed via ODIN a rooted stock rom then a standard stock ROM - both do not fix the issues, I still have the same errors which is odd.
Can anyone make any suggestions ?
Thanks, Nick

NickBeswick said:
Hi
I'm having issues with my I9505 Galaxy S4. The phone was rooted and after trying a few ROMs (Omega) etc I returned to a NAND backup with was basically rooted stock (via TWRP). Over the weekend strange lock-ups kept happening and I keep getting - Process System isn't responding. When I try and make a call the phone either reboots and hands for a minute and returns that error. This morning I have flashed via ODIN a rooted stock rom then a standard stock ROM - both do not fix the issues, I still have the same errors which is odd.
Can anyone make any suggestions ?
Thanks, Nick
Click to expand...
Click to collapse
bump

NickBeswick said:
bump
Click to expand...
Click to collapse
did you try wiping data and cache??

samersh72 said:
did you try wiping data and cache??
Click to expand...
Click to collapse
Yes many times

NickBeswick said:
Yes many times
Click to expand...
Click to collapse
if you are rooted, flash custom recovery, format system via recovery, then flash a custom rom or stock firmware.

samersh72 said:
if you are rooted, flash custom recovery, format system via recovery, then flash a custom rom or stock firmware.
Click to expand...
Click to collapse
Hi - thanks for the information but again I have already tried this a few times.
Nick

NickBeswick said:
Hi
I'm having issues with my I9505 Galaxy S4. The phone was rooted and after trying a few ROMs (Omega) etc I returned to a NAND backup with was basically rooted stock (via TWRP). Over the weekend strange lock-ups kept happening and I keep getting - Process System isn't responding. When I try and make a call the phone either reboots and hands for a minute and returns that error. This morning I have flashed via ODIN a rooted stock rom then a standard stock ROM - both do not fix the issues, I still have the same errors which is odd.
Can anyone make any suggestions ?
Thanks, Nick
Click to expand...
Click to collapse
Sorry, just saw that you did all these already.
You have to be VERY careful. It is already reported that the wipe in TWRP might screw things up.
So, I recommend you that you install a prerooted stock ROM, and the stock recovery. Then do a factory reset (from the phone!).

[Q] Galaxy s4 Rooted and Custom Rom Problems

I have a Canadian S4 and rooted using the twrp method and then installed the vigin google play edition rom. Everything worked fine at first when I installed it but i was fiddling around after in twrp and thought i should format the internal storage and start completely fresh and now if I install any rom including my original backup the device will boot up into the system fine for the first time but if the device resets after that it just hangs on the galaxy S4 logo and i have to reboot into recovery and flash again. Any ideas on how i could fix this? Thanks!!!

Try this, in twrp go into advanced wipe and wipe dalvik cache, cache, system, data and android secure. Then flash your nandroid.

I don't have a nandroid I have a twrp backup

Jaygrippa said:
I don't have a nandroid I have a twrp backup
Click to expand...
Click to collapse
That is a nandroid.

Dont use TWRP for the S4
From what I have experience and I believe others have as well, if you used TWRP to format where you had to type yes, you are pretty much screwed trying to get things working properly again. Maybe it is certain phones, sd cards, roms, who knows, but after I typed yes in TWRP to format everything, I could flash a rom but couldnt restart and things were buggy. I had to use odin to flash back to stock, re-root and flash the rom again. Now everything is 190% considering my battery life went from 6 hours to 28 with medium usage.
I have always loved TWRP on my other phones, but for the S4, its more frustration and using with caution than its worth.
Another word of caution, use windows to fix your phone. Im on linux and its too much of a pain in the ass to use odin/heimdall to go back to stock for newbs. On windows I went to stock and rooted again in no time.
Good luck!

jd1639 said:
That is a nandroid.
Click to expand...
Click to collapse
After doing that stuff in twrp should I flash right back to my backup of stock touch wiz or straight into the ROM of my choosing? Whenever I would have to reflash I would have to format he internal memory or it wouldn't work

Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?

Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
You might have to. I had the same problem today where if the phone rebooted I would just get a black screen. I ended up using Odin with the stock rom, reinstalling twrp and then restoring my backup. I'm pretty sure it was a rom I flashed that caused the initial problem and only Odin would clear things up.

Start Over
Jaygrippa said:
Ya I did the thing where I typed yes... Crap ya its my first time doing all this stuff so you suggest I Re do all of the rooting stuff and then flash my backup I made?
Click to expand...
Click to collapse
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.

ericchaffey said:
Actually its going back to stock, then rerooting. All I did was follow androidrootz guide here:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
After that, motochopper back to get root and followed this guide to install OUDHS recovery:
http://forum.xda-developers.com/showthread.php?t=2291956
This worked for me, at least for now. Hope it can help you out.
Click to expand...
Click to collapse
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Now the only problem is i have to find a Fido ROM

Jaygrippa said:
Hey thanks a bunch ill try that out later. I am at work right now and i can still use my phone on the rom i have just as long as i dont reset it. Ill try all of this out when i get home and see if that works. Thanks for everyones help
Click to expand...
Click to collapse
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.

ericchaffey said:
A couple other notes, to avoid other possible problems, use the original samsung cord when connecting to your computer. Switching USB ports can help if there are transfer or other issues. Its pretty easy and straight forward if everything works out well, but there are so many gawt dayum variables that minor issues can cause problems, though may never manifest.
Hopefully this works and please post some results to help the same in need.
Click to expand...
Click to collapse
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!

Jaygrippa said:
Ya thinks i will, now im just in the process of finding a rom for Fido, they are owned by rogers so im not sure if the rogers rom will work, This android stuff is so stressful its my first android phone so i hope all goes well!
Click to expand...
Click to collapse
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.

jd1639 said:
I get firmware from sammobile.com. You have to register but it's free. You'll download a zip. Use 7-zip to extract the .tar.md5 file from it. Use that in Odin, PDA.
Click to expand...
Click to collapse
ya even they dont have a specific "Fido" firmware...

Anyone know if I can just use the Rogers ROM its pretty much the same company

Jaygrippa said:
Anyone know if I can just use the Rogers ROM its pretty much the same company
Click to expand...
Click to collapse
It'll work. It'll just put their bloatware on and the boot animation will be theirs

Reflashed
Ok so i reflashed to the stock rom using odin and bam it works again, im just wondering what is a good way now too root, and install the same rom i had

This will have everything you need http://forum.xda-developers.com/showthread.php?p=42320391

Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order

Jaygrippa said:
Thanks everyone for your help, I got my phone back up and running stock, then i rooted using CF- Autoroot and installed twrp again. I then reinstalled the rom i wanted to use and everything is in tip top order
Click to expand...
Click to collapse
Glad to here it. Have fun.

Bootloader Loop problem

Hi, my phone acted weird today, been running custom room for over couple months without any problem, but then when i resart my phone today it got to the bootload screen and stuck there ever seen. I can able to go into custom recover and did a full wipe but nothing change, could anyone help me out? I have loki also. Using S4 ATT version.

Try wiping cache in your recovery

i did that, always do that after install a new rom, don't know why my phone is soft bricked now...

akahimaro said:
i did that, always do that after install a new rom, don't know why my phone is soft bricked now...
Click to expand...
Click to collapse
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.

xBeerdroiDx said:
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.
Click to expand...
Click to collapse
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...

Before ODIN'ing back to MDL/MDB...
akahimaro said:
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...
Click to expand...
Click to collapse
What recovery image are you running? You are not the only one that had this problem. I am trying to piece this together.

[[SOLVED]] Process system isn't responding

Hi,
I rooted my phone 2 days ago and installed custom ROM everything went well, except for today my phone start to lag too much, so I decided to flash back the stock ROM that I have downloaded from Sam-mobile using Odin 3.08, but now my device not responding to anything and even I get "Process system isn't responding" in Samsung wizard installation also the sound disappeared and when try lunch any app like camera I get message "camera failed" and keep getting "Process system isn't responding".
[[The Solution]] for Process system isn't responding follow the steps: ((ONLY SM-N9005))
1-Unroot your phone if you are rooted.
2-Factory rest your phone and clear cache. .
3-Flash the Stock rom for your device.(if this fixed the the problem stop here if not continue to step 4)
4-Download this ROM and flash it by Odin 3.04.(this rom somehow managed to restore my EFS files and fixed the problem)
and that's it.

root is bad
bad root it is for you

dancapitan said:
bad root it is for you
Click to expand...
Click to collapse
I don't think so because I used this root http://forum.xda-developers.com/galaxy-note-3#root

Hi, I have the exact same problem and I can't seem to figure out how to fix it either

Dahdoul said:
Hi,
I have rooted my phone 2 days ago and installed custom rom everything went well except for today my phone start to lag too much,so i decided to flash back the stock rom that i have downloaded from sam mobile using odin 3.08 but now my device not responding to anything even i get not responding message in samsung wizard installation and sound disappeared and when try open any app like camera get message camera failed and keep getting process system isn't responding.
i do not know what to do,please help me.
thank you.
Click to expand...
Click to collapse
Oh man, I though I was the only one having this problem. I really don't now how to fix it at all, I've tried flashing stock ROM and I still get the same problem. If anyone can help, I'd be so grateful.

This sounds a lot like the issue I've been having (see details in the thread I posted here).
Any insight would be very welcome.

Yup bad root (it can and does happen the odd time!), clear cache etc in download mode, then reflash the new Stock ROM, then wipe cache etc again in download mode. See if that helps.
Similar issue I had previously after I originally rooted was apps kept closing and saying stopped working. When I wiped the ROM and updated via KIES to MJ7 with wiping cache etc, it seems to have done the trick.
EDIT: Also try ODIN 3.07 rather than 3.08

radicalisto said:
Yup bad root (it can and does happen the odd time!), clear cache etc in download mode, then reflash the new Stock ROM, then wipe cache etc again in download mode. See if that helps.
Similar issue I had previously after I originally rooted was apps kept closing and saying stopped working. When I wiped the ROM and updated via KIES to MJ7 with wiping cache etc, it seems to have done the trick.
EDIT: Also try ODIN 3.07 rather than 3.08
Click to expand...
Click to collapse
I have already done everything you mentioned by clearing cache,wipe system,clear data,flash new stock rom but nothing fix the issue

Dahdoul said:
I have already done everything you mentioned by clearing cache,wipe system,clear data,flash new stock rom but nothing fix the issue
Click to expand...
Click to collapse
Yep, I've done the same and nothing helps either

Maybe just return it, play stupid with the phone shop staff, probably won't notice the flashing anyway.

radicalisto said:
Maybe just return it, play stupid with the phone shop staff, probably won't notice the flashing anyway.
Click to expand...
Click to collapse
LOL i will:cyclops:

radicalisto said:
Yup bad root (it can and does happen the odd time!), clear cache etc in download mode, then reflash the new Stock ROM, then wipe cache etc again in download mode. See if that helps.
Similar issue I had previously after I originally rooted was apps kept closing and saying stopped working. When I wiped the ROM and updated via KIES to MJ7 with wiping cache etc, it seems to have done the trick.
EDIT: Also try ODIN 3.07 rather than 3.08
Click to expand...
Click to collapse
Unfortunately I've tried all of this too (except using Kies, it won't recognise my phone though I'd never tried it before now) to no avail.
I might try a warranty swap, but I'm concerned because the system status shows custom and I'm unsure there's any way to reset it. I suppose my only chance is to try for an on-the-spot swap for a new phone, because if it gets sent back to Samsung I expect they'd reject it due to the system status.
Still can't understand why the issue persists beyond reflashing the stock rom...

sexbot3000 said:
Unfortunately I've tried all of this too (except using Kies, it won't recognise my phone though I'd never tried it before now) to no avail.
I might try a warranty swap, but I'm concerned because the system status shows custom and I'm unsure there's any way to reset it. I suppose my only chance is to try for an on-the-spot swap for a new phone, because if it gets sent back to Samsung I expect they'd reject it due to the system status.
Still can't understand why the issue persists beyond reflashing the stock rom...
Click to expand...
Click to collapse
I don't understand why the issue persists after flashing stock either but I doubt it is hardware fault. I hope someone knows how to fix this

Solution
Guys finally i found the solution for Process system isn't responding follow the steps:
1-Unroot your phone if you are rooted
2-Factory rest your phone.
3-Flash the Stock rom for your device.
4-Download this ROM and flash it by Odin 3.04.
and that's it.:laugh:

Dahdoul said:
Guys finally i found the solution for Process system isn't responding follow the steps:
1-Unroot your phone if you are rooted
2-Factory rest you phone.
3-Flash the Stock rom for your device.
4-Download this ROM and flash it by Odin 3.04.
and that's it.:laugh:
Click to expand...
Click to collapse
Hi, the link for "downloading this" doesn't work, I don't suppose you could re-post it please?

luke05dee said:
Hi, the link for "downloading this" doesn't work, I don't suppose you could re-post it please?
Click to expand...
Click to collapse
Already updated http://forum.xda-developers.com/showthread.php?t=2461929

Dahdoul said:
Already updated http://forum.xda-developers.com/showthread.php?t=2461929
Click to expand...
Click to collapse
Thank you so much, just trying this now although which rom out of the one's in that thread did you use please? Just to confirm this fixed all your problems including the "failed camera"

luke05dee said:
Thank you so much, just trying this now although which rom out of the one's in that thread did you use please? Just to confirm this fixed all your problems including the "failed camera"
Click to expand...
Click to collapse
I installed the first rom under SM-N9005 Official Stock ROM's for Odin (KNOX 0x1).and yes it fixes camera failed and the issues i had before like it never happened.oh BTW i downloaded the preRooted if you don't wanna mess with knox just download the stock rom.:laugh:

Dahdoul said:
I installed the first rom under SM-N9005 Official Stock ROM's for Odin (KNOX 0x1).and yes it fixes camera failed and the issues i had before like it never happened.oh BTW i downloaded the preRooted if you don't wanna mess with knox just download the stock rom.:laugh:
Click to expand...
Click to collapse
OMG thank you so much, I mean thank you so inanely much this worked. I've been so upset all week thinking my note was dead and you have fixed it. Oh man thank you, thank you, thank you!

luke05dee said:
OMG thank you so much, I mean thank you so inanely much this worked. I've been so upset all week thinking my note was dead and you have fixed it. Oh man thank you, thank you, thank you!
Click to expand...
Click to collapse
No problem, am so happy for you :highfive:

Freezing and other issues. Please help.

Running an Australian N9005.
I was running Temaseks unofficial CM11 build just fine. Got bored and wanted to go back to a more Samsung styled phone.
Decided to flash X-Note. As I'd used it before CM11. It worked fine then.
Attempted to flash X-Note but it wouldn't boot, stuck at initial screen with the Kernel warnings at the top of the screen. Was told it was because I hadn't got the new 4.4 bootloader.
I was told to follow the instructions here: http://forum.xda-developers.com/showpost.php?p=46223545&postcount=2
Which I did.
Using these download links and instructions: http://forum.xda-developers.com/showthread.php?p=49931269
That fixed the boot issue. I suppose I'm not on the 4.4 bootloader.
However when I booted up the stock Polish ROM, the initial Samsung Setup Wizard would crash at the end of the setup and force me back to the start of the setup. Tried ignoring it and just flashing the custom recovery and then XNote. Same issue, the setup wizard in XNote crashes as well.
Someone then told me I should try repartitioning the device using a PIT. I don't know what that is, but it was suggested.
Using this ROM: https://mega.co.nz/#!QVwlVDgJ!QyAxmDMcsIA-56cX_28Ua2aPZLcJATVvdM07LOs0V10
And this PIT: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Completes successfully.
Same issue............... That being a third separate ROM (official? at that)....
Samsung Setup Wizard crashes...
I even tried flashing XNote and removing the setup wizard just to get past it. That fixes it for about 10 minutes or so. After about 10 minutes of use the phone freezes and I have to hold the power button to force it to restart. If I leave the phone off, it still freezes, as soon as I try to unlock it it freezes and need to force restart.
I really don't know what to do now... Any help guys? I'm trying my best here...
Please, if you need any more information, please ask.

Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?

Do you have reactivation lock enabled?
Sent from my fingers to your face using my Samsung Galaxy Note 3!

hey_joe said:
Might not help, but have you wiped your phone clean using custom recovery ( data,cache, dalvik, internal sd ) before flashing xnote or factory reset on recovery when on stock?
Click to expand...
Click to collapse
Yes.
nicholaschum said:
Do you have reactivation lock enabled?
Click to expand...
Click to collapse
No.

This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.

radicalisto said:
This has puzzled me, not sure why it's still acting up especially after re-partitioning and flatlining everything.
Click to expand...
Click to collapse
Yes indeed. I'm very confused...

So... I don't want to get ahead of myself, but my phone seems to have sorted itself out...
I decided to just send it back to the carrier to get it replaced. So I decided to just flash the official Firmware again. (I accidentally left repartition ticked)
Once it started I thought... Oh ****... But I was sending it back anyway so who cares. (the carrier said they will just swap it for me if they can see it not working)
So I let it finish and turn it on to see what happens, run through the setup to make sure it still crashes at the same spot so I can show them... and it doesn't crash... wtf?
So I flash the custom recovery and XNote... And it seems to be working now. Now freezing, no nothing... I... I don't know...

Crazy, least it appears somewhat sorted lol

radicalisto said:
Crazy, least it appears somewhat sorted lol
Click to expand...
Click to collapse
So far, yeah... I think I got the runt of the litter or something... Haha

Reynbow said:
So far, yeah... I think I got the runt of the litter or something... Haha
Click to expand...
Click to collapse
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)

radicalisto said:
Just out of curiosity, as I see you have an AU model, did you buy it from Kogan? -- Reason I ask is that they used HK firmware on some models and HK models have issues flashing normal firmware (similar to the issue you had)
Click to expand...
Click to collapse
Not from Kogan, no. From Optus. Pretty standard.