Sick of taking huge sized nandroid backups before applying any tiny tweak/MOD and then undergo the long painful procedure of restoring ??
Through this guide , I will tell you about some really simple yet effective ways to unbrick your soft-bricked phone/get out of boot loops.
Our Unbricking Weapon
Android Commander - http://forum.xda-developers.com/showthread.php?t=628138
About Android Commander - Android Commander is windows application to keep control on your android apps and files from PC.
It detects your device even when it is in a bootloop!
Click to expand...
Click to collapse
TIP : You need a kernel/ROM with root enabled for ADB otherwise the AndroidCommander program will give NO root access ( since it is operated via ADB)
Ok so below are some of the most common reasons of bootloops :
1. Incorrect/Incompatible Build.prop Tweaks - SomeBuild.prop tweaks which you add to your Build.prop file located in /system folder might not be compatible with your device's hardware or firmware and this causes bootloops .
For eg - Over Sized heap limit , changing rendering methods to those which are not supported etc.
Solution - Have a backup of your Build.prop file before adding/removing/changing any build.prop tweak (its doesnt even take 2 minutes ) and if you face a bootloop, simply replace your current build.prop file with your backed up one.
2. A corrupt/incompatible System application / jar file (for eg - a wrong framework-res.apk) - Most of the time when theming or modifying, we might replace a system app with a modified app which might not be made for our device/hardware. This can lead to both bootlooping and/or crashing of the app
Solution - Have a backup of the original apk or download it from anywhere and simply replace( delete the apk and push your downloaded apk ) it via AndroidCommander.
3-An incompatible bootanimation - a bootanimation which either has a wrong desc.txt file with wrong resolution or wrongly sized images can lead to bootlooping
Solution - simply replace the bootanimation.zip file located in /system/media folder with any compatible bootanimation.
4An incorrect/corrupt Dalvik Cache - This can be simply solved by wiping the dalvik cache in recovery. Btw, clearing cache and dalvik cache can solve most of the bootloops which are not caused by incompatible mods/tweaks.
5.An incorrect init.d script and/or a system file like a lib/configuration/property/firmware etc( like efg.cfg file missing )
Solution Delete if its an addition , correct it or simply replace it with an original one
Click to expand...
Click to collapse
Note
There are many other ways to get out of a boot loop like flashing a CWM zip to replace your corrupt file / mounting as USB storage via Recovery but personally i feel that this is the easiest and fastest way to recover from a soft-brick.
These are only a few which i remember, i will post more in the future. As you can see that i didnt go into details of each and every category since there are endless problems and solutions which are obviously very specific. My main motive was to spread this idea since it has really saved me the hassles of restoring a backup for every small tweak i apply. All of the above problems have occurred to my device for once at least. This method has saved me a lot of times , Hope this guide helped you :angel: No more getting scaredof Soft-Bricks :laugh:
Press Thanks:good: if this helped you
But i tried it got some data corruption errors. could not find proper guidance / help on that , after few days sold the device.
Related
Hi
I hope someone can help me.
I am trying to make my own custom rom. I used this way.
- flashed xxJPM
- de odexed all apps and framework
- added stock android lockscreen
- removed some useless system apps
- then changed theme
all this works great. but I had problems with adding some other apps to /system/apps
1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib
But apps like quickpic or the gingerbread keyboard are not working. When I just install them android create a data folder. What do I have to do with those database files in this folder? Can someone show me the right way for installing own system apps?
Then I do a factory data reset in the settings. After this nothing was working. I had no lockscreen. Even all options by pressing the shutdown button except "shutdown" disappeared. Does anyone know why this happened?
I am new to this. So it would be great if you can help me.
cal.mar said:
Hi
I hope someone can help me.
I am trying to make my own custom rom. I used this way.
- flashed xxJPM
- de odexed all apps and framework
- added stock android lockscreen
- removed some useless system apps
- then changed theme
all this works great. but I had problems with adding some other apps to /system/apps
1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib
But apps like quickpic or the gingerbread keyboard are not working. When I just install them android create a data folder. What do I have to do with those database files in this folder? Can someone show me the right way for installing own system apps?
Then I do a factory data reset in the settings. After this nothing was working. I had no lockscreen. Even all options by pressing the shutdown button except "shutdown" disappeared. Does anyone know why this happened?
I am new to this. So it would be great if you can help me.
Click to expand...
Click to collapse
QuickPic/Gingerbread: Nope. Open the .apk and copy the lib files to /system/lib
About the rest. i have no idea since I don't know your internal files.
THIS IS DEVELOPMENT. DO NOT CLOSE.
It helps people with force close problems.
The Dark Lestat said:
QuickPic/Gingerbread: Nope. Open the .apk and copy the lib files to /system/lib
About the rest. i have no idea since I don't know your internal files.
THIS IS DEVELOPMENT. DO NOT CLOSE.
It helps people with force close problems.
Click to expand...
Click to collapse
dude he already added the lib files..so this is an un-usual problem
"1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib"
cal.mar said:
Hi
I hope someone can help me.
I am trying to make my own custom rom. I used this way.
- flashed xxJPM
- de odexed all apps and framework
- added stock android lockscreen
- removed some useless system apps
- then changed theme
all this works great. but I had problems with adding some other apps to /system/apps
1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib
But apps like quickpic or the gingerbread keyboard are not working. When I just install them android create a data folder. What do I have to do with those database files in this folder? Can someone show me the right way for installing own system apps?
Then I do a factory data reset in the settings. After this nothing was working. I had no lockscreen. Even all options by pressing the shutdown button except "shutdown" disappeared. Does anyone know why this happened?
I am new to this. So it would be great if you can help me.
Click to expand...
Click to collapse
After making your own dump your not suppose to factory reset, only after flashing your own dump your ready to factory reset, but if you factory reset while making a dump/removing and adding files, you will soft brick and loose your work..
Did you change the framework and tw framework?
Adding back some framework files via adb might help..
Or you will have to start over again..
I forgot to add that you should check your permissions on the lib file
Sent from my Alpha 17 1.2 GHz ACID Lestatious 2.0 BUILD 1.8 Galaxy 3 FROYO
rudolf895 said:
dude he already added the lib files..so this is an un-usual problem
"1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib"
Click to expand...
Click to collapse
After copying lib files give this command over adb..
chmod 777 /system/lib/filename.so
InDroid 4.0 (Build 6)
cal.mar said:
Hi
I hope someone can help me.
I am trying to make my own custom rom. I used this way.
- flashed xxJPM
- de odexed all apps and framework
- added stock android lockscreen
- removed some useless system apps
- then changed theme
all this works great. but I had problems with adding some other apps to /system/apps
1. I copied the *.apk file to /system/app
2. I extract the lib files into /system/lib
But apps like quickpic or the gingerbread keyboard are not working. When I just install them android create a data folder. What do I have to do with those database files in this folder? Can someone show me the right way for installing own system apps?
Then I do a factory data reset in the settings. After this nothing was working. I had no lockscreen. Even all options by pressing the shutdown button except "shutdown" disappeared. Does anyone know why this happened?
I am new to this. So it would be great if you can help me.
Click to expand...
Click to collapse
As for the lockscreen and power menu, i was having same problem few days back. Searched all over, no solution. In the end I had to start it all over again. I suggest u do the same.
InDroid 4.0 (Build 6)
arunmcops said:
As for the lockscreen and power menu, i was having same problem few days back. Searched all over, no solution. In the end I had to start it all over again. I suggest u do the same.
InDroid 4.0 (Build 6)
Click to expand...
Click to collapse
yeah I think you are right. Thank you all for your help. I'll try it again. And I hope that it will work.
HI ok. I've tryed it again.
But know when I want to flash my new factoryfs.rfs the Download crashed.
I don't know where the problem could be.
Do I have to use this command?
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
Click to expand...
Click to collapse
Can someone explain this command to me?
still third time flashing chrashes.
when Odin is flashing the factoryfs.rfs it stops at a specific level. odin get 99% of CPU and I have to interupped it. What is my fault? DId anyone have same problems? I try it to make like all the tutorials says.
Edit: Odin says before flashing "Big Partition size!" What do I have to do to make it smaller?
Edit: I get this:
# dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
435200+0 records in
435200+0 records out
222822400 bytes transferred in 115.950 secs (1921711 bytes/sec)
Click to expand...
Click to collapse
Found the problem why odin crashes. I copied the factoryfs.rfs file with 7zip into the .tar package but I had to use TotalCommander.
But still I have no lockscreen after flashing and the options in the power menu are not visible.
So here I have noticed issue with using vrtheme on new 4.3 MJ2 and seeking some Linux expert help to solve it.
work around
Simply using vrtheme causing FCs, SO i have changes the destination to see outcome file structure.
-All changes we have applied through vrtheme applied to output file. but icons get changed to android icon.
-Now if you move that output file to other destination using root explorer then also it regenerates original icons and we can use as final apk ready to push to System/app
-Again if we giving same command through recovery, it doesn't works
-Also copying with terminal emulator with cat command, it regenerates original structure. again same command using recovery fails to do it.
May be recovery issue??
here is log cat along with used vrtheme script.
dr.ketan said:
So here I have noticed issue with using vrtheme on new 4.3 MJ2 and seeking some Linux expert help to solve it.
work around
Simply using vrtheme causing FCs, SO i have changes the destination to see outcome file structure.
-All changes we have applied through vrtheme applied to output file. but icons get changed to android icon.
-Now if you move that output file to other destination using root explorer then also it regenerates original icons and we can use as final apk ready to push to System/app
-Again if we giving same command through recovery, it doesn't works
-Also copying with terminal emulator with cat command, it regenerates original structure. again same command using recovery fails to do it.
May be recovery issue??
Click to expand...
Click to collapse
doc, am not a linux expert, but i tried to inject your black aosp vrtheme files into the apk and flash them from cwm, it kills the wifi and have to wipe and reflash the whole rom. so, perhaps you want to put more attention to it.
waiting for your aosp theme and thanks a lot.
Wifi issue will be solved by reflashing recovery
I can show you temporary solution.
Just change path of pushing files to other from System/app then 1. you want get FCc bcoz it is not in system/app
2. Now from where you have defined destination from there move to some pther place with root explorer, now you will be able to see icons, once icons are correct you can pust to system/app.
dr.ketan said:
Wifi issue will be solved by reflashing recovery
I can show you temporary solution.
Just change path of pushing files to other from System/app then 1. you want get FCc bcoz it is not in system/app
2. Now from where you have defined destination from there move to some pther place with root explorer, now you will be able to see icons, once icons are correct you can pust to system/app.
Click to expand...
Click to collapse
sorry doc, but i cannot understand what you mean.
do you mean i should change the flashing path (in the script)? or do you mean i should copy the apks manually into the system/app by root explorer? if you mean the later, i can do, but the first one i don't.
i can see all the icons, just the wifi would not start after i flashed the modified apks through cwm flash. what do you mean by reflashing recovery?
Ok making clear again who want to use vrtheme
1.Change path in vrtheme installertheme.sh from system/app to other (e.g. just system)
2.Now when you flash vrtheme, you won't see any changes in system bcoz all apps will be in system and not in System/app.
3. Manually cut all app with root explorer from system to SDcard
4. Now you can see correct icons of all appl after moving to sdcard.
5.Now move those apk to system/app OR System/framework, where it should be.
6.Enjoy all the changes now in system
7.By this process you will lose wifi and you have to reflash recovery to get it back.
PS : For AOSP for MJ2 I have made it with same method above and uploading, Once uploaded will post to MJ2 thread, you have to simply flash that file. without doing anything above.
dr.ketan said:
Ok making clear again who want to use vrtheme
1.Change path in vrtheme installertheme.sh from system/app to other (e.g. just system)
2.Now when you flash vrtheme, you won't see any changes in system bcoz all apps will be in system and not in System/app.
3. Manually cut all app with root explorer from system to SDcard
4. Now you can see correct icons of all appl after moving to sdcard.
5.Now move those apk to system/app OR System/framework, where it should be.
6.Enjoy all the changes now in system
7.By this process you will lose wifi and you have to reflash recovery to get it back.
PS : For AOSP for MJ2 I have made it with same method above and uploading, Once uploaded will post to MJ2 thread, you have to simply flash that file. without doing anything above.
Click to expand...
Click to collapse
will just wait for your file then. dont want to mess my setup again. spent too much time experimenting with it today. lucky it's saturday in my country...
ok then wait 10 min.
EDIT : AOSP theme for MJ2 ROM Posted to MJ2 thread post#2
Doc.
I just came across thia issue thread discussion.
Surprised to see vrtheme issues.
I think it is worth trying morphing instead of vrtheme.
If it fails, then it is not a recovery issue..m
It might be android 4.3 security files that I noticed in /system...
I will dig in further and check...
Thx for sharing this discussion thread. :thumbup:
wesamothman said:
Doc.
I just came across thia issue thread discussion.
Surprised to see vrtheme issues.
I think it is worth trying morphing instead of vrtheme.
If it fails, then it is not a recovery issue..m
It might be android 4.3 security files that I noticed in /system...
I will dig in further and check...
Thx for sharing this discussion thread. :thumbup:
Click to expand...
Click to collapse
Already fixed that (at least in my MJ2 rom)
vrtheme works perfect on framework-res.apk and secsettings.apk
Hi,
I decided to try to make a modification of an existing ROM which would suit me better right after flashing. Nothing large, only adding some apps and stuff. But Ive got a couple of questions:
1) Ive read some apps cant run from /system partition. Looks like that (at least) one of mine is one of them - it FCs when in /system/apps or /system/priv-apps. Is there any workaround to make this work? I dont want to lose it when doing factory reset (or to flash the ROM again after every factory reset).
2) I wanted to add langunages (http://forum.xda-developers.com/showthread.php?t=2602704) but according to forums those files are odexed. How could I deodex them to make them run on an deodexed ROM?
3) I want to include the faux kernel but Im not sure if simply copying those files into the ROM would do ... in the other cases it went ok but Im not sure about the kernel - Im afraid I could break something.
4) Can I also use the ROM file to store other files? I mean - if I put files into the ROM in /data/media/0/ would it simply appear in my home directory or could this break anything - by which I mean to destroy my existing files?
Thanks for any leads!
michalurban said:
Hi,
I decided to try to make a modification of an existing ROM which would suit me better right after flashing. Nothing large, only adding some apps and stuff. But Ive got a couple of questions:
1) Ive read some apps cant run from /system partition. Looks like that (at least) one of mine is one of them - it FCs when in /system/apps or /system/priv-apps. Is there any workaround to make this work? I dont want to lose it when doing factory reset (or to flash the ROM again after every factory reset).
2) I wanted to add langunages (http://forum.xda-developers.com/showthread.php?t=2602704) but according to forums those files are odexed. How could I deodex them to make them run on an deodexed ROM?
3) I want to include the faux kernel but Im not sure if simply copying those files into the ROM would do ... in the other cases it went ok but Im not sure about the kernel - Im afraid I could break something.
4) Can I also use the ROM file to store other files? I mean - if I put files into the ROM in /data/media/0/ would it simply appear in my home directory or could this break anything - by which I mean to destroy my existing files?
Thanks for any leads!
Click to expand...
Click to collapse
1) What is the app? on system/app they should work fine since kitkat update, i think
2) To deodex i used a kitchen i got out of foro nexus (cant get the link atm) that only worked on linux. If you want to translate things in your rom, i think it can be done without deodexing, im not sure.
3) Copy paste should work fine but if you take a look at faux's meta inf, see what's there, merge it with your rom's meta inf. But it should work with cp
4) You can use the meta inf to link files to storage like your sdcard, yes. However, if you try to put a wallpaper somewhere inside the rom it wont show up
anerik said:
1) What is the app? on system/app they should work fine since kitkat update, i think
2) To deodex i used a kitchen i got out of foro nexus (cant get the link atm) that only worked on linux. If you want to translate things in your rom, i think it can be done without deodexing, im not sure.
3) Copy paste should work fine but if you take a look at faux's meta inf, see what's there, merge it with your rom's meta inf. But it should work with cp
4) You can use the meta inf to link files to storage like your sdcard, yes. However, if you try to put a wallpaper somewhere inside the rom it wont show up
Click to expand...
Click to collapse
Thanks very much for your reply! Now:
1) The app is a game, Traffic Racer. When I flash a ROM where this app has been put in /data/app it runs fine. In /system/app or /system/priv-app it FCs. As you say it should work Ill try to do it again - but I tried it twice in /system/priv-app and once in /system/app already so I dont believe it would work. BTW I use APKs from update.zip created by TiBa if it could be relevant.
2) Linux is not a problem so Ill try to find the link here.
3) Ill try only to copy the files first before messing with meta files.
4) I only want to store some apps config backup files (for Apex launcher and Agenda widget mainly).
michalurban said:
Thanks very much for your reply! Now:
1) The app is a game, Traffic Racer. When I flash a ROM where this app has been put in /data/app it runs fine. In /system/app or /system/priv-app it FCs. As you say it should work Ill try to do it again - but I tried it twice in /system/priv-app and once in /system/app already so I dont believe it would work. BTW I use APKs from update.zip created by TiBa if it could be relevant.
2) Linux is not a problem so Ill try to find the link here.
3) Ill try only to copy the files first before messing with meta files.
4) I only want to store some apps config backup files (for Apex launcher and Agenda widget mainly).
Click to expand...
Click to collapse
Oh, games could cause issues, yes. Better leave it on data app. Messing with meta inf is totally easier than it sounds anyways and could help fixing any possible bugs, you gotta try it. Backup files i dont think they'll work on the rom but you can store them into storage/emulated/legacy which is the storage, though you could do this any other easier way
anerik said:
Oh, games could cause issues, yes. Better leave it on data app. Messing with meta inf is totally easier than it sounds anyways and could help fixing any possible bugs, you gotta try it. Backup files i dont think they'll work on the rom but you can store them into storage/emulated/legacy which is the storage, though you could do this any other easier way
Click to expand...
Click to collapse
Thanks again! Ive got one more question about including the faux kernel. The updater-script is supposed to run this command during the installation in CWM:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
... which I dont know how to implement. If I would only copy all files it would overwrite the original boot.img (Kitkat+ 1.1 original anyway) - which im not sure is the same. So Im not sure if it wont screw something up ...
Or is this extraction the same as copying it? Does the "/dev/block/platform/msm_sdcc.1/by-name/boot" just mean - "its a block device on first SD, partition name boot"?
michalurban said:
Thanks again! Ive got one more question about including the faux kernel. The updater-script is supposed to run this command during the installation in CWM:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
... which I dont know how to implement. If I would only copy all files it would overwrite the original boot.img (Kitkat+ 1.1 original anyway) - which im not sure is the same. So Im not sure if it wont screw something up ...
Or is this extraction the same as copying it? Does the "/dev/block/platform/msm_sdcc.1/by-name/boot" just mean - "its a block device on first SD, partition name boot"?
Click to expand...
Click to collapse
Put faux's boot.img on the rom first, then on updater script go to the line that refers to extracting boot.img (should be like the last one) and replace that with the command on faux's updater script. That means it will extract it in that directory, nothing else. Be sure to copy modules aswell and set the perms
Q&A threads should be created in the Q&A forum... not the Development forum.
Thread moved.
One more question - is there a special way how to pack the ZIP file? Cause I unpacked a ROM, added some apks, packed it but it didnt work (no error, just ended at "opening rom" or what the CWM message is) ... but when I modified existing ZIP it went fine ...
GUIDE: CREATING SMALL FLASHABLE ZIPs TO RESTORE FILES OR SETTINGS WITHOUT HAVING TO DO FULL NANDROID RESTORE
This will enable you to apply MODs without having to do a FULL NANDROID restore to recover if the MOD fails or if you don't like it
This brief guide will teach you how to create a flashable ZIP file that you can use to restore your phone to pre-MOD settings if you want to revert back or if the MOD simply does not work
WITHOUT having to do a full restore of your phone.
It is a very good idea to create these backup flashable ZIPs and keep them safe to recover from mishaps or when creating/testing MODs/themes.
*************************************************************************************************************************************************
As usual: Disclaimer: I am not responsible for any loss of data or functionality on your phone. To be 100% sure, always make a NANDROID backup if you are not 100% certain you can recover.
*************************************************************************************************************************************************
There are many reasons you might want to do this, for example when testing a MOD for another ROM that is similar to yours but not exactly the same (eg: Optimus G3 vs Cloudy G3) or when upgrading your ROM to a new version and wanting to re-apply old MODs.
There are many ways to get into boot loops or fail to boot, the biggest culprit being fonts installations, but include also bootanimations and others.
INSTRUCTIONS:
Part 1: general
1. Install ZIPme app from playstore
2. Find out which files are being modified by the MOD you are trying to apply, this is usually framework-res.apk, LGSystemUI.apk, lge-res.apk, but be aware that some MODs affect a lot of files. See part 2 for more details on how to do this.
3. If you are applying a font, don't worry, the FONTs section (see part 2) should cover all Fonts.
4. If you are applying a bootanimation, don't worry, the bootanimation section (see part 4) should cover all Bootanimations.
5. For every flashable ZIP you create you can test it straight away by booting into recovery and applying the zip file. There is no reason why it should not work.
Part 2: FONTS
1. In ZIPme select the following:
- ADD FOLDER: /system/fonts
- ADD FILE: /system/etc/system_fonts.xml
2. Create the flashable zip in an /sdcard location you can access from recovery
Part 3: MODs that affect framework-res.apk, LGSystemUI.apk or any other app
1. Find out which apks are being modified:
- You should of course read the OP (instructions for the MOD)
- The easiest way to find out modified apks is to download the MOD and open it: the zip file will contain either the apk files themselves or have directories with the names of the apks being modified.
- You can always ask the developer to make sure
2. Once you have a full list of files being affected you can create the flashable zip:
- in ZIPme, simply select "ADD -> File" for every file being affected
- If you have an ODEX ROM (.odex files are present) make sure you pick those too!
- save the flashable zip in an /sdcard location you can access from recovery
Part 4: Bootanimations
1. In ZIPme select the following:
- ADD FILE: /bin/bootnimation
- ADD FILE: /system/media/bootanimation.zip
- ADD FILE: /system/media/shutdownanimation.zip
2. Create the flashable zip in an /sdcard location you can access from recovery
Part 5: Other flashable files you should always keep handy
1. Always keep with you the following files for good measure: they don't take much space but can help recover from problems without having to fully restore from NANDROID backup
- original kernel from your ROM
- flashable bootloader (if you do not know what I am talking about then DON'T do it)
- flashable baseband (if you do not know what I am talking about then DON'T do it)
- flashable recovery image (TWRP, etc)
- "Xposed-Disabler-Recovery.zip": this is created by Xposed when you install it. It is located in the root folder of your sdcard. Copy it and put it somewhere safe.
- SuperSU: keep a flashable latest SuperSU with you to recover root
Any comments, suggestions, feedback are welcome
reserved
bloof said:
Any comments, suggestions, feedback are welcome
Click to expand...
Click to collapse
good work mate, i'm out of Thanks for today.
Just tried, nice and easy to use. Thank u
does it save paired bluetooth and wifi devices?
deleted
Can you use this to make a zip of boot.img and libs? Not finding how to do that. Thanks for any information.
matusala said:
does it save paired bluetooth and wifi devices?
Click to expand...
Click to collapse
Nope. It saves what you tell it to save.
The guide as it is only saves files, was meant for modding restore, not other stuff.
If you try mods a lot and don't like a certain theme or icon set you don't need to do a full nandroid backup and full restore because you changed 3 files in your mod.
countryfolk07 said:
Can you use this to make a zip of boot.img and libs? Not finding how to do that. Thanks for any information.
Click to expand...
Click to collapse
Not with what I wrote.
The app ZIPme can do a lot more than simple file recovery, but I am not an expert at flashable zips so can't comment on more advanced uses like buildprop etc.
I would certainly not write anything about boot images, way too likely to cause someone to screw up their phone....
Pick a flashable boot/libs zip file from somewhere and try to reproduce at your own risk.
It's my first time customizing an android phone, and I have to say, there's a lot to learn. Samsung devices are made to read qmg files when it comes to boot animations, but I'm already making my own boot animations, and I have a lot of questions I hope this post isn't that long.
================================
1- after installing CWM can I UNINSTALL it using odin? Or is there any other way to do it without my computer?
================================
2- I know that you can't UNflash files, so when I flash a zip file (specifically bootanimations4U) what files should I back up? I'd rather back up only the files that will be replaced? Or is there an app to back up files from a certain folder and just bring them back if I want to bing back the normal animations?
================================
3- let's say that my device is rooted, it has CWM installed, and also, has the . zip enabler flashed already and in use. I'm planning to FORMAT my phone in a couple of weeks because I want to use it as if it's rooted with the whole storage available (I don't have storage problems I just want to do that) but my question is...
************************ ==========
-Q3: if my goal is just to delete my data and apps only, can I just use the factory reset from the settings? Do I need to do anything regarding CWM or the zip file I've flashed? Will CWM be deleted? Will I have to flash that .zip reader enabler again? What do I need to do if I needed to reset my phone without any problems?
================================
4- is there a file size limit for the bootanimations.zip files on Samsung files (galaxy s5 android 6.0) and also the audio file size limit?
================================
5- what is the condition in which I have to flash the bootanimation4U . samsungani . zip file and not the other one?