It all started when I tried to update busybox and it told me that multiple versions were present. I reflashed KH3 (which brought me back to basic busybox) and the problem still persists. I can download FINE over 3G. Never had this problem before.
Factory reset the only solution? I've read online that it works, but I'd like to avoid it.
I've decided to go for the hard reset, but I'm worried that I won't clean everything that's necessary.
I think busybox may be installed in /sbin which is outside of /system. I was planning on flashing the leaked KH3 (NON FRANKENSTEIN), but doesn't that only wipe /system?
How can I restore the absolute root of my device to stock? By that I mean the parent "directory" (if you can call it that) of /system.
Thanks!
So I wiped absolutely everything, have basic busybox installed, and I'm still getting the issue. Sometimes I can get an app to install, but more often than not the download fails to start on wifi.
No one else experiences this? Anyone have any idea why this might be happening? I'm so frustrated!
I also think that the wipes may not have worked properly because somehow PowerAMP remembered my settings and Tasker didn't revert to the default notification icon. I can't figure out how this is possible if /system and /data were wiped.
Does flashing a stock ROM not wipe all of /system?
Sent from my GT-I9100 using xda premium
Clean wipe via CWM recovery mounts and storage format system data and sd card .
jje
Aside from SD card and USB storage, doesn't all of that happen when flashing stock ROM?
Sent from my GT-I9100 using xda premium
Hello? Someone confirm please.
Sent from my GT-I9100 using xda premium
Related
Hello guys,
I confused about fix permission option on cwm, what actually it does. And when we should use this fix permission? On what case we need to use it?
2 - how to total hard reset SGS2, completely back as it still virgin ( not include odin binary counter). This should use cwm to use 'format' option. But anyone can help with the steps guide? Or any other hard reset method recommended?
Edit: im sorry guys, im not sure if im posting on the correct section. I cant see '(Q)' mark on my topic.
Thanks
Sent from my GT-I9100 using xda premium
neobirdrio said:
2 - how to total hard reset SGS2, completely back as it still virgin ( not include odin binary counter). This should use cwm to use 'format' option. But anyone can help with the steps guide? Or any other hard reset method recommended?
Click to expand...
Click to collapse
If by virgin you refer to set the phone as the way it was as you purchase it, you should do two things:
1) Erase all user data (you can do that from CWM). Format /data /system and /sdcard
2) Install a stock ROM (via Odin).
If you also want to reset the binary counter, you need the USB Jig to do that.
AzureusPT said:
If by virgin you refer to set the phone as the way it was as you purchase it, you should do two things:
1) Erase all user data (you can do that from CWM). Format /data /system and /sdcard
2) Install a stock ROM (via Odin).
If you also want to reset the binary counter, you need the USB Jig to do that.
Click to expand...
Click to collapse
I see, when im done with all those format steps in cwm, thats mean my phone dont have any OS inside? So that mean i cannot reboot the phone rite?
The next step after format the whole things then shut down the phone and get into download mode and flash stock firmware with odin? Correct me if im wrong.
Sent from my GT-I9100 using xda premium
Yes, that is correct.
Formating /data, /system and /sdcard set the phone empty and without any ROM, so it won't do a full boot. You can power down the phone and power it up in download mode. Then from there you flash your Stock ROM from Odin and you're good to go.
Permissions are explained here:
http://www.legend.ws/blog/tips-tricks/linux-file-permissions-explained/
Since Android is based on the Linux kernel, the same basic file permissions scenarios apply as those outlined above.
In simple terms, when permissions get messed up, you may lose the ability to access or edit files over which you normally should have control, or you may gain control over files which normally you shouldn't, which can cause random problems, like Force Close, etc. in Android.
Repairing the permissions is a housekeeping measure, to keep things neat and tidy. Sometimes, after a repair, you'll have to redo some settings, etc.
AzureusPT said:
Yes, that is correct.
Formating /data, /system and /sdcard set the phone empty and without any ROM, so it won't do a full boot. You can power down the phone and power it up in download mode. Then from there you flash your Stock ROM from Odin and you're good to go.
Click to expand...
Click to collapse
Your description made me very clear, i highly appreciated for your efforts. Thanks so much.
Sent from my GT-I9100 using xda premium
donalgodon said:
Permissions are explained here:
http://www.legend.ws/blog/tips-tricks/linux-file-permissions-explained/
Since Android is based on the Linux kernel, the same basic file permissions scenarios apply as those outlined above.
In simple terms, when permissions get messed up, you may lose the ability to access or edit files over which you normally should have control, or you may gain control over files which normally you shouldn't, which can cause random problems, like Force Close, etc. in Android.
Repairing the permissions is a housekeeping measure, to keep things neat and tidy. Sometimes, after a repair, you'll have to redo some settings, etc.
Click to expand...
Click to collapse
I see, well, let say i just flashed a new rom, and i get fc on some apps. And some app not working properly, in this situation, fix permission can solve the problem? What change we would get after fix the permission, i mean if it can harm the system?
Sent from my GT-I9100 using xda premium
the phone must to be rooted?
delete
I am experiencing the same issues. I assume you have this problem with ICS roms, because that's where I get those problems. I am currently running WEUI and half my apps are not at all working. I have also flashed back to stock, tried ICS Slim and MIUI v4, but no luck. I am also getting issues, while listening to music, where the song will keep on playing, but the app will ask me if I want to FC or wait. This has only happened recently. I really do not feel like going back to 2.2 or 2.3. Any help is greatly appreciated
Have you guys tried fixing the permissions?
That usually fixes most force close problems.
Xenoism said:
Have you guys tried fixing the permissions?
That usually fixes most force close problems.
Click to expand...
Click to collapse
Tried it, but no luck. Only option now is to flash a different ics rom, and see if that works. If all else fails I can always go back to bionix.
2 questions:
1 Can you see your internalSD with a file explorer?
2 Did you try wiping /cache and /dalvik-cache and rebooting?
I find a good wipe cure many things wrong (with my phone too )
Woodrube said:
2 questions:
1 Can you see your internalSD with a file explorer?
2 Did you try wiping /cache and /dalvik-cache and rebooting?
I find a good wipe cure many things wrong (with my phone too )
Click to expand...
Click to collapse
1. Yes
2. Yes, usually before I flash a different rom/reflash rom to try and fix this I wipe data and wipe cache patition and dalvik cache.
OK. The first question was to make sure you still had access to your internal and not sole sort of veiled encryption error.
Let me think about somethings and ill get back to you. I am wondering if it wouldn't be a bad idea to format /data and /system to make sure that you don't have any ghosts lurking. If you do, make sure you back up SDs contents to PC just in case.
Woodrube said:
OK. The first question was to make sure you still had access to your internal and not sole sort of veiled encryption error.
Let me think about somethings and ill get back to you. I am wondering if it wouldn't be a bad idea to format /data and /system to make sure that you don't have any ghosts lurking. If you do, make sure you back up SDs contents to PC just in case.
Click to expand...
Click to collapse
All those apps are still force closing on 2.2. Could it be, because I'm restoring them from titanium backup?
I'll try to backup SD onto my Computer and then format sd. It's probably some ghost file that is causing my phone to have errors. It probably is a file that has to do with MIUI since I flashed that as it happened.
Btw thanks for trying to help
Edit: I formatted sd card, put all the files back onto sd card, restored apps with tiatnium backup, but still no luck. I even factory reset,wiped cache and dalvik cache after formatting sd, but still no luck.
Thanks everyone for trying to help. I figued out the problem. Titanium backup was causing all those apps to have issues. I uninstalled all user apps via tb and download them from the market. I am getting no force close what so ever, with dl apps from market.
Usually when that happens from TB, it is from restoring system files (they show in red in the TB list of apps).
I use it to restore user apps + data every time I flash a new ROM, but I never use it to restore system apps, and I don't have any problems with it.
Since you've already restored from the market, you could try running TB and deleting it's backup data and then running a new batch backup of user apps (and no system apps) to have the freshest copy of your apps from a working system. That should allow you to restore in the future, hopefully without issue.
Sent from my SGH-T959 using xda premium
This could be a problem with using TB. TB gives you the option of restoring apps+data. If you're coming from a 2.2 rom to 4.0, you don't want to keep the data from a 2.2 rom. What you can do is restore apps without the data. That should solve your problem.
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
TeamRainless said:
So I wanted to change my keyboard... In fact I *did* change my keyboard.
At first whenever I wanted to use the keyboard (for notepad for example) it would say something like "Unable to reach" but after a while the keyboard just started working.
Then I switched on wifi and everything started crashing with the usual "Unfortunately (insert every task) has stopped working".
I know I can probably solve this by doing a factory wipe... but I also know that there MUST be a better way to solve this problem.
I have adb installed. I have Siyah kernel.
I can access the whole damned phone from my laptop in or out of recovery mode. I just don't know where to look to fix the problem.
A possible clue:
I tried flashing Keyboard-Blau.zip when my keyboard wasn't working. But CWM aborted the flash with an unknown error.
This is very similar to what happened the last time I had this problem. The only thing in the zip anyway was AXT9IME.apk in the system/app folder.
Any ideas would be appreciated.
P.S. I have also wiped cache and davlak cache AND attempted to install a rom. All permissions in system/app seem fine.
Could it be that system is mounted as r/w somehow?
EDIT2: Just now when I tried to to wipe dalvik (sp) cache it said something about:
"Unknown volume for path sd-ext"
Just a note.
Also I have erased /system then installed the rom again and it's still acting up.
Click to expand...
Click to collapse
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What rom are you on? Did you do a full wipe when you flashed it?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Wanamlite. Latest version. And I sure did...
TeamRainless said:
Wanamlite. Latest version. And I sure did...
Click to expand...
Click to collapse
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard did you choose? One from the play store?
Edit : have you tried to flash the rom over what you have now, with no wipe?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
TeamRainless said:
Yes I tried it.
And somebody had uploaded the stock, touchwiz keyboard. So I copyed it over and set the permissions correctly.
Click to expand...
Click to collapse
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
kilometers4 said:
Hmm.. The only thing I can think of is wiping cache, dalvik one more time EDIT: and try to fix permissions from cwmr. If that doesn't work I would make a nandroid backup and flash your rom with a full wipe again to see if that fixes it. At least you can restore the backup if it doesn't
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
TeamRainless said:
Yeah I know a full wipe will fix it. I've already done that and screwed it up again a few more times for testing purposes.
My point is that there SHOULD be a way to fix it without a full wipe.
I mean if you've got root access, CWM recovery, AND you can actually boot the phone and access adb at the home screen... Then it should be possible to fix the problem.
It's a shame android dosnt return an error telling you WHY something is crashing. Then it would be a cinch.
Click to expand...
Click to collapse
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
kilometers4 said:
What keyboard are you trying?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
TeamRainless said:
This one: http://forum.xda-developers.com/showthread.php?t=1483428
...from post #2. Then I tried the zip in post 3 and four. (If you'd like to replicate the error just backup your /data then you can do whatever the hell you want and just restore /data and you'll have everything.) Then I tried flashing the zip from post 3 or 4... which didn't work. Followed the directions for changing permissions on the keyboard.
I hadn't realized you could backup everything from CWM Recovery. And hadn't even considered that just restoring /data would work without screwing everything up again... but work it did! Wish I had realized that a couple of weeks ago... but I didn't really want that data anyway.
Basically I just want the touchwiz keyboard because the standard android one is too small for my hands.
But I can't quite figure out how changing two files... and even changing them back later... could crash the whole damned OS beyond repair.
Click to expand...
Click to collapse
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
kilometers4 said:
It might be a bad zip/apk file
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
It absolutely was. But what did it do and how could I fix it?
Story:
First a factory reset from the phone.
I have wiped all, battery stats, user files, caches and Dalvik cache, all you can wipe from Clockwork.
Then I formated everything that you can format in Clockwork.
After this I flashed original firmware (unbranded version though) from Odin.
I got rid of the problems I had except one.
Every time I reboot the phone warns that I lost connection for roaming, until I start internet.
Only I have roaming disabled in settings.
Also there was STILL files left in the phone, the folder and files accepted via bluetooth on internal sd card.
I don't know if there's anything else left but these files showed up in Gallery.
How can this be after I reset, wiped and formatted everything? Makes no sense to me.
I really have no idea what to do.
Cant find anything similar in threads to find sollutions from.
And it seems to be pointless to wipe and reformat yet another time.
Any tips at all to get me started would be really great!
You have to manually delete everything. Clockwork does not delete storage files.
Sent from my GT-I9300 using Tapatalk 2
have u tried flashing the latest modem ?
Sent from my GT-I9300 using xda premium
joshnichols189 said:
You have to manually delete everything. Clockwork does not delete storage files.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I know, I meant the system reset, wipe and formats.
But even in CW there is options to format system amongst other tings, that should have done it I think?
vegeta1 said:
have u tried flashing the latest modem ?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hmm.. no I haven't.
Samsung support thinks the 3G chip is broken? I don't know about that?
Ok, so here it is: tried CM11 and decided it was a little too buggy for me. Went into recovery and did a factory reset a couple times and also SYSTEM, CACHE, and DALVIK. From there i restored my Odex Blue backup w/o incident.
However, i noticed that Swiftkey suddenly said it couldnt d/l the language pack. Tried uninstalling and reinstalling. Nothing. Google searched the problem and read numerous posts. Cant figure it out.
I then wanted to test another app that needs to download data. My weather/clock app has the same problem. Wont d/l any new skins. My alternate app market same issue... D/L will start but will never get past 0%.
This is clearly relates to resoring TW after flashing CM11. There must be a step i missed or something.
What would happen if i went into TWRP and chose to FORMAT DATA (clears internal data) and then attempted to restore my Odexed blue backup? I have the feeling that we are bot supposed to wipe internal data but i have no idea how to sort out this problem
Sent from my SM-N900P using XDA Premium 4 mobile app
SantinoInc said:
Ok, so here it is: tried CM11 and decided it was a little too buggy for me. Went into recovery and did a factory reset a couple times and also SYSTEM, CACHE, and DALVIK. From there i restored my Odex Blue backup w/o incident.
However, i noticed that Swiftkey suddenly said it couldnt d/l the language pack. Tried uninstalling and reinstalling. Nothing. Google searched the problem and read numerous posts. Cant figure it out.
I then wanted to test another app that needs to download data. My weather/clock app has the same problem. Wont d/l any new skins. My alternate app market same issue... D/L will start but will never get past 0%.
This is clearly relates to resoring TW after flashing CM11. There must be a step i missed or something.
What would happen if i went into TWRP and chose to FORMAT DATA (clears internal data) and then attempted to restore my Odexed blue backup? I have the feeling that we are bot supposed to wipe internal data but i have no idea how to sort out this problem
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's the symlinks that point to your internal storage that b need to be restored. You can use ADB command lines to reconnect those, or take a more drastic measure that will get you to where you want.
I'll paste the options of which I'm aware momentarily...
--------Begin guidance from @freeza, posted over the weekend in his stock rooted MJ4 thread---------
" please try these commands in adb or terminal emulator... make a backup of your internal storage just to be safe.
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
PS: I'd run these in recovery... "
--------End comments from freeza------
--------Begin alternative method, provided to me by a forum member uncomfortable with ADB and reporting it working-----
"What I did was just wipe everything and started from scratch and everything seems to be normal again..."
---------End comments if not using ADB----
My guess is the latter method was a wipe of everything from within TWRP.
I hope this helps.
Good luck.
Sent from my SM-N900P using Xparent BlueTapatalk 2
GDI, i knew i shouldnt of flashed CM11. I knew something stupid like this would happen! Im ADB illiterate so please break it down for me a bit.
Thanks for the reply Mic!
Sent from my SM-N900P using XDA Premium 4 mobile app
SantinoInc said:
GDI, i knew i shouldnt of flashed CM11. I knew something stupid like this would happen! Im ADB illiterate so please break it down for me a bit.
Thanks for the reply Mic!
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
See above. You can do it without ADB and still be up-and-running, though it's a bit more work on the backend.
If going the command line route, you'd have your phone in recovery, be running the latest version of Android SDK and Eclipse, and running from the subdirectory of where the Android SDK is installed labeled "platform tools." You'll need to run them from a command prompt within Windows, and be at that directory from within the command window.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Mic, if i choose the format data option in TWRP will i be able to restore nandroid on my external sd card? Im afraid once i wipe internal sd card TWRP will not function properly and i wont have a chance to restore a backup from external sd card
Sent from my SM-N900P using XDA Premium 4 mobile app
SantinoInc said:
Mic, if i choose the format data option in TWRP will i be able to restore nandroid on my external sd card? Im afraid once i wipe internal sd card TWRP will not function properly and i wont have a chance to restore a backup from external sd card
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm sorry bro, I haven't done either, though I suspect it's one of the wipe options from within TWRP. If you copy a TWRP backup to your external storage, you will likely be able to put it back after the wipe. Nothing is ever gone if you reset the pointers to your storage.
Let me try to get you some assistance; I believe @Goddly can provide guidance.
OK, here's your update (not from Goddly), you should restore nothing from a prior backup from a previous TouchWiz rom if you have gone from CM11 to TW4.3. I believe it's square one for ya (either Odin or Mobile Odin tar file flash). Just advice from two whom would know.
Or...if you did flash the Skunk Ape1 rom, reinstalled TWRP and re-rooted, you should be able to flash a new TouchWiz rom and could try to restore a prior backup. I don't see why that wouldn't work. I still think starting over is your best call.
Edit: Here are the steps that make the most sense to me if you don't use ADB and are having issues with a TW 4.3 ROM after flashing an AOSP 4.4.2 build:
1. Flash Full Stock (no root or recovery) ROM of MJ4, tar file flashed from Mobile Odin or Odin (tar can be found here)
2. Inject root using Chainfire method using tar.md5 file here,
3. Install TWRP 2.6.3.7, tar.md5 file here, IMG file here,
4. Flash your heart out
Sent from my gimped and overpriced iMac mini, because the dude that owns the place thinks that they are just a terrific value, and still are shiny...
Man, you are thorough! Thanks so much for your time once again! I used skunks file in traditional Odin. When that was done I did a Factory Reset. Then I went back to Odin to flash TWRP recovery. Finally, I restored my good ole SS Odexed. Definitely not worth the hassle IMO. You really can't beat a stock based rom IMO.
Sent from my SM-N900P using XDA Premium 4 mobile app
I had the same problem so what I did was transfer all my important files to my sdcard since I'm rocking a 64 GB card then I wiped everything but my sdcard and finally reinstalled TW.
Sent from my SM-N900P using XDA Premium HD app