Restore /sys/ folder

[kah8br]

I got trigger happy deleting files while trying to remove those annoying virgin boot/shutdown images and sounds, but apparently I deleted the file /sys/power/incoming_call which I'm pretty sure has been causing issues with my incoming calls. I know, I'm a noob. Sorry, but can anyone help me out?

 

[watskyhotsky]

nandroid backup.

if you didnt do a nandroid backup, you really shouldnt have been doing any poking around in the system files to begin with.

go to XDA or AndroidForums where someone posted a stock rom that you can flash over yours to get that folder back.

remember you need to have CWM recovery installed, its super super super easy to do on the triumph

 

[kah8br]

I did a nandroid backup, but that only restores the /system folder. I want a copy of the /sys/power/ folder. Or would someone else's not work on my phone?

 

[watskyhotsky]

i think you can open the .zips on your PC, copy the needed folders/files and put them into the phones SD card, then from the phones file browser, put these files where they really go. the filer explorer needs root and you should have access to write to the required folders to put these back.

next time dont mess with anything

 

[kah8br]

I thought of that, but apparently cwm doesn't back up the /sys folder. I'm thinking because it should never be tampered with anyway. Literally every other folder except the /sys is in the backups I've found. I think even root explorer hides the /sys folder from you altogether so you don't mess it up, but I was using es explorer to explore the root. I've tried my own backups, other backups, but none have been able to restore the /sys folder.

 

[watskyhotsky]

wipe everything, flash a fresh rom, and never touch that folder again

 

[kah8br]

Tried that too and it didn't restore it. I even tried using a custom roms. I'm using miui right now (which I'm really liking), but it didn't restore that file. They all just write to the /system folder. I need the files from the /sys.

 

[watskyhotsky]

im running CM7, fresh flash.

im using file explorer, i found /sys/power but theres no "incoming_call" folder or file.

same thing on MIUI.

these are fresh flashes of a good rom, and i have no issue receiving or sending calls.


you sure this is a rom issue?!?

 

[kah8br]

Well, I was looking alogcat to see what was going on with incoming calls and I saw an exception saying the file was missing; I figured that must be it. But if that's not the case, then I can't figure out for the life of me why my incoming calls take a while to be seen by my phone. Every time someone calls, they get a busy signal until like the fourth or fifth try. I have decent service and had the phone reprogrammed by virgin mobile, all to no avail. Thoughts on what else it could be?

 

[watskyhotsky]

Well, I was looking alogcat to see what was going on with incoming calls and I saw an exception saying the file was missing; I figured that must be it. But if that's not the case, then I can't figure out for the life of me why my incoming calls take a while to be seen by my phone. Every time someone calls, they get a busy signal until like the fourth or fifth try. I have decent service and had the phone reprogrammed by virgin mobile, all to no avail. Thoughts on what else it could be?

go back to a froyo rom and use the activate app again to provision the phone.

or who knows you might be in an area where sprint/VM has spotty coverage.

OR last suggestion its the OTHER persons carrier refusing to connect the two phones.

i get errors sending and receiving texts to ATT users and my cousin is on att and none of us can call each other, does the same thing you mentioned.

may be carrier conflicts in your area.

 

[kah8br]

Well, turns out it's not the phone. I switched my service to one of my old dumb phones and had the same issues. It's a relief, but sucks at the same time haha. The funny thing is VM thought it was an issue with the phone so they sent me out a new triumph. Oh well. Thanks so much for your help!

 

[b_randon14]

You do know that the /sys folder is part of the ramdisk of the kernel. It gets rebuilt at everyboot, therefore rebooting would have solved that. /sys is a folder created in the RAM for storing kernel files at run-time

 

[kah8br]

No, I didn't know this. Now I feel even more foolish! Turns out though the issue was just a local service problem. Perhaps a problem with a local tower. But thanks for the info, good to know that folder it's one less cause for concern.

 

[b_randon14]

Yeah VM has spotty coverage at times, and the 3g will drop out at times!