My new GT-P5113 with issues - Galaxy Tab 2 General

I’m new to this forum and to the Android world, so please bear with me.
I have just purchased the Samsung Galaxy Tab2 10.1 GT-P5113, and the 1st thing I did was to root the device.
I have since been searching for the perfect ROM in order to get both smoothness/performance and the ability to over clock up to 1400. I have tried a couple of ROM’s and flashing ROM’s became pretty straight forward for me, but I was just not happy with the ones I have tried and the only over clocking one only allowed me overclock up to 1200.
Now I just restored it back to factory settings, but I now have an issue…
The available space on the internal sdcard is less than 500Mb!!!! I followed all the procedures of wipe data/factory reset, wipe cache, wipe dalvik. And still, something is getting stored on the sdcard and I’m not sure what or where that is.
I also have the issue, that I’m not able to update the OS, but that I would guess it’s because, and correct me if I’m wrong.. the devise is Rooted..
So all in all, those are my issues and I would like to get them fixed. Any help would be gladly appreciated.
1- The sdcard space causes me headaches and I don’t know how to resolve it.
2- What ROM would you suggest based on what you read
3- Why can’t I update?

1-Their is option in cwm to format emmc use with extreme caution
2- use aokp or cm10 from www.teamhacksung.org and it has update feature inside it
Sent from my GT-I9300 using xda app-developers app

Related

Wierd Note defects. A wipe is not a true wipe.

There are many stories here on XDA Note about wierd problems. They appear and disappear without much sense how.
On Nexus One, if you do a wipe and install a ROM on 5 different phones with different use then each will be identical after wipe/install.
Galaxy Note seems to be different. How do you do a true wipe so 5 phones with same hardware but wierdly defective firmware will be the same after?
The Note is awesome but these wierd problems really let it down for many of us.
Wifi overheat, GPS wakelocks, USB charging failing, hot screen, etc. When a problem comes but then just goes away you know it was never a hardware problem. It was a software problem. The software at the very bottom is the firmware. Its probably the culprit of wierdness.
Can we "true wipe" and get a defective unit into the as new condition that was intended?
Sent from my GT-N7000 using xda premium
What?
GALAXY NOTE
^^^+1 to WHAT???..lol
I think the OP wants to know on how to properly wipe a galaxy note as based on his observation some users fix issues by performing a wipe before installing a firmware while others can never get to fix it with just 1 wipe.
@OP
I know what you mean but I mostly blame the custom firmware used especially when I got back to full stock and I dont see the same rubbish issue. When I perform a wipe I always do it 3 times. Thats out of habit from the Galaxy S and Galaxy S2 days.
I may not have wrote clearly
There are a lot of threads about a lot of different types of problems which a lot of different people have also had. Problems like overheating coming from the wifi. Problems with wakelocks coming from the GPS. And many others.
For some people the phone is fine, and then a problem comes from no where. They wipe and wipe and it doesn't go away after wiping and flashing many different roms. Then one time for no known reason flashing something does make the problem go away. but why not earlier?
Personally I had the same problem when I flashed CM9 alpha. Upon booting it came up with some kind of error that it couldn't open wssyncmlps. I wiped and flashed another ROM but the error didn't go away. Flashed a couple more different ROMs and still the error. Eventually I did a recovery and that got rid of the error.
I would have thought a factory wipe would fix that. But it didn't. That proved a factory wipe DIDN'T REALLY wipe everything.
My housemate just got back from the Android DevCon today in Melbourne. Maybe I should have got him to ask one of the Google engineers about it LOL
I may not have wrote clearly
There are a lot of threads about a lot of different types of problems which a lot of different people have also had. Problems like overheating coming from the wifi. Problems with wakelocks coming from the GPS. And many other common and uncommon problems.
For some people the phone is fine, and then a problem comes from no where. They wipe and wipe and it doesn't go away after wiping and flashing many different roms. Then one time for no known reason flashing something does make the problem go away. but why not earlier?
Personally I had the same problem when I flashed CM9 alpha. Upon booting it came up with some kind of error that it couldn't open wssyncmlps. I wiped and flashed another ROM but the error didn't go away. Flashed a couple more different ROMs and still the error. Eventually I did a recovery and that got rid of the error.
I would have thought a factory wipe would fix that. But it didn't. That proved a factory wipe DIDN'T REALLY wipe everything. Maybe its a fault with the recovery software? Maybe this new RedPill recovery software that Angelom has put into Abyss 3.5 will help? I wonder. I'm flashing Rocket V21 now to see what happens...
My housemate just got back from the Android DevCon today in Melbourne. Maybe I should have got him to ask one of the Google engineers about it LOL
PurpleMelbourne said:
I may not have wrote clearly
There are a lot of threads about a lot of different types of problems which a lot of different people have also had. Problems like overheating coming from the wifi. Problems with wakelocks coming from the GPS. And many other common and uncommon problems.
For some people the phone is fine, and then a problem comes from no where. They wipe and wipe and it doesn't go away after wiping and flashing many different roms. Then one time for no known reason flashing something does make the problem go away. but why not earlier?
Personally I had the same problem when I flashed CM9 alpha. Upon booting it came up with some kind of error that it couldn't open wssyncmlps. I wiped and flashed another ROM but the error didn't go away. Flashed a couple more different ROMs and still the error. Eventually I did a recovery and that got rid of the error.
I would have thought a factory wipe would fix that. But it didn't. That proved a factory wipe DIDN'T REALLY wipe everything. Maybe its a fault with the recovery software? Maybe this new RedPill recovery software that Angelom has put into Abyss 3.5 will help? I wonder. I'm flashing Rocket V21 now to see what happens...
My housemate just got back from the Android DevCon today in Melbourne. Maybe I should have got him to ask one of the Google engineers about it LOL
Click to expand...
Click to collapse
Erase = removing the entry that leads to that data on the storage medium.
The data are there till the get overwrite by something. Even you format/wipe/clear you may get the data on your next install/reboot when the OS scans your medium.
Sent from my GT-N7000 using Tapatalk
Maybe under CWM you need to format system then format data would help ?
What!!!??!!!!!
Braxos said:
Erase = removing the entry that leads to that data on the storage medium.
The data are there till the get overwrite by something. Even you format/wipe/clear you may get the data on your next install/reboot when the OS scans your medium.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
so a format command in android is equal to a quick format in windows only removing the file index? where did you get this info?
Sent from my GT-N7000 using xda premium
If you want to erase all personal information or personal usage history on a desktop or laptop then you need specialist software which overwrites everything.
So it is unreasonable to be disappointed if the Note does not do it and I suspect no other Palmtop does it either.
As far as weird defects goes, Samsung only guarantees the Note will work providing it has only ever used the official ROM for the region.
Gaugerer said:
If you want to erase all personal information or personal usage history on a desktop or laptop then you need specialist software which overwrites everything.
Click to expand...
Click to collapse
your talking about recovering lost files that's not the issue for instance a laptop never accidentally sees deleted files as not deleted
Gaugerer said:
So it is unreasonable to be disappointed if the Note does not do it and I suspect no other Palmtop does it either.
Click to expand...
Click to collapse
you mean a Phone right? ;-)
Gaugerer said:
As far as weird defects goes, Samsung only guarantees the Note will work providing it has only ever used the official ROM for the region.
Click to expand...
Click to collapse
but THIS place is mostly about custom stuff i guess that's why its posted her and not emailed to Samsung support
/Jeriz
jeriz said:
you mean a Phone right? ;-)
Click to expand...
Click to collapse
No I mean a Palmtop running a phone app amongst many others
but THIS place is mostly about custom stuff i guess that's why its posted her and not emailed to Samsung support
Click to expand...
Click to collapse
Click to expand...
Click to collapse
THIS place is the sub-forum for general chat and is NOT mostly about custom stuff.
/Jeriz[/QUOTE]
Gaugerer said:
THIS place is the sub-forum for general chat and is NOT mostly about custom stuff.
Click to expand...
Click to collapse
got me there
/Jeriz
but does anyone know if a cwm wipe actually does format or just deletes?
/Jeriz
jeriz said:
got me there
/Jeriz
Click to expand...
Click to collapse
What a gracious light-hearted response and much appreciated
Well im not actually an ass im just posing as one to blend in
/Jeriz
I think wiping the phone is a very common problem/conundrum for users.
I am in the process of wiping and installing rocketrom 21, and I find that not everything specific to me has been wiped -after a "factory data reset", and a CWM "wipe data/factory reset" and a "wipe cache partition". E.g. right now I'm going into the sd card, using cwm, and finding a long list of folders from apps that I've long since uninstalled. These "wipe/reset" options don't seem to touch them.
Can somebody who knows how these things really work shed some light on... what specifically wipes what?
One last thing, optional: If I find an option to wipe every single partition on the device, how do I then get a ROM on there afterwards? Do I put it in download mode and plug it into my computer and use ODIN? Again only an expert would know.
maybe it is a defective unit....
trumpetboy101 said:
I am in the process of wiping and installing rocketrom 21, and I find that not everything specific to me has been wiped -after a "factory data reset", and a CWM "wipe data/factory reset" and a "wipe cache partition". E.g. right now I'm going into the sd card, using cwm, and finding a long list of folders from apps that I've long since uninstalled. These "wipe/reset" options don't seem to touch them.
Click to expand...
Click to collapse
The internal SD is never wiped as part of a factory reset or wipe - this is by design, as it is considered to be 100% user data, just as if it were a real user replaceable SD card.
In order to clear the internal SD, you can reformat from the storage menu, or flash another ROM via Odin with a PIT file.
Regards,
Dave
Sent from my Transformer Prime TF201 using Tapatalk

what is the secret of stability

What is the secret of stability folks? i was a veteran at making mistakes when flashing roms...(i failed day 1 of owning my DSstreak5...sat seemingly dead for a week before i got things going)
Anyway my post is looking for some post detailing what works. And that means those veterans that appear to be able to go further than 48hrs without a hitch. Is it about how much gets wiped i constantly wipe dv and perform both resets. and still boot to problems.
I have mastered Baseband changes and such one of my crucial first issues (currently 366bb via dsc flashme3).
but as of late I am having problems getting reliable operation out of the box on a few roms..dsc and longhorn.
Dsc has been fairly usable...My bread and butter or must have apps are lastfm and somafm.. i must have these functional but ity appears these may be causing issues...they freeze and fc off and on.
Longhorn seems to want to throw process errors right from the start...with 2.9.1 it constantly froze at boot...(is it truely 366 compatible)
anyway thats my rant for now please post your views and tips...while i attempt to try lxdroid...wish me luck!!!
ps does loading/transferring files in ubuntu linux vs windows make any difference in the stability of files or the sd?
ellisna said:
What is the secret of stability folks? i was a veteran at making mistakes when flashing roms...(i failed day 1 of owning my DSstreak5...sat seemingly dead for a week before i got things going)
Anyway my post is looking for some post detailing what works. And that means those veterans that appear to be able to go further than 48hrs without a hitch. Is it about how much gets wiped i constantly wipe dv and perform both resets. and still boot to problems.
I have mastered Baseband changes and such one of my crucial first issues (currently 366bb via dsc flashme3).
but as of late I am having problems getting reliable operation out of the box on a few roms..dsc and longhorn.
Dsc has been fairly usable...My bread and butter or must have apps are lastfm and somafm.. i must have these functional but ity appears these may be causing issues...they freeze and fc off and on.
Longhorn seems to want to throw process errors right from the start...with 2.9.1 it constantly froze at boot...(is it truely 366 compatible)
anyway thats my rant for now please post your views and tips...while i attempt to try lxdroid...wish me luck!!!
ps does loading/transferring files in ubuntu linux vs windows make any difference in the stability of files or the sd?
Click to expand...
Click to collapse
You may wanna try an app called SD maid... it looks for unused directories and files and THOROUGHLY will clean up your system
Are you doing factory resets from both StreakMod and Dell recoveries?
When you flash ROM you should flash ROM and do a factory reset... then boot back into recovery, wipe cache and dalvik, flash ROM again, then fix permissions from recovery before booting
Also... every once in a while I like to completely wipe my SD card with diskpart using the clean all command and then let the Streak format it. Once booted and SD formatted, I mount in recovery and copy files back to the SD using the robocopy commands from Windows
I can honestly say that apart from the occasional wifi freeze or hangup I have zero problems with apps on my Streak
Mind you I don't install apps just for the sake of having it or because it was cheap on sale... I run what I need to get done what I need.... I don't use task killers but I do use Autorun Manager to prevent apps from starting and Autokiller Memory Optimizer to help out with memory
Nor do I ever have apps installed to my SD cars
Hope some of that helps
Sent from my CM9 TouchPad using TapaTalk 2
cdzo72 said:
You may wanna try an app called SD maid... it looks for unused directories and files and THOROUGHLY will clean up your system
Are you doing factory resets from both StreakMod and Dell recoveries?
When you flash ROM you should flash ROM and do a factory reset... then boot back into recovery, wipe cache and dalvik, flash ROM again, then fix permissions from recovery before booting
Also... every once in a while I like to completely wipe my SD card with diskpart using the clean all command and then let the Streak format it. Once booted and SD formatted, I mount in recovery and copy files back to the SD using the robocopy commands from Windows
I can honestly say that apart from the occasional wifi freeze or hangup I have zero problems with apps on my Streak
Mind you I don't install apps just for the sake of having it or because it was cheap on sale... I run what I need to get done what I need.... I don't use task killers but I do use Autorun Manager to prevent apps from starting and Autokiller Memory Optimizer to help out with memory
Nor do I ever have apps installed to my SD cars
Hope some of that helps
Sent from my CM9 TouchPad using TapaTalk 2
Click to expand...
Click to collapse
I am going to start easing up on the moving to sd ...things do become a little iffy when i move programs over
Wiping the sd card deserves a fresh look...I do recall once long ago wiping or swaping the sd and getting better results initially.
Maybe some mild corruption is occuring during some file transfers?
I wonder if anyone has noticed more or less issues transfering via the usp vs pulling the sd completely and using a sd adapter/slot?
cdzo72 said:
You may wanna try an app called SD maid... it looks for unused directories and files and THOROUGHLY will clean up your system
Are you doing factory resets from both StreakMod and Dell recoveries?
When you flash ROM you should flash ROM and do a factory reset... then boot back into recovery, wipe cache and dalvik, flash ROM again, then fix permissions from recovery before booting
Click to expand...
Click to collapse
The streakmod data/factory reset followed by the dell reset is a true staple in my flashing diet...
i have on occassion tried the double flash as well...but just to clarify you are recommending :
1...access Recovery .....streakmod(my recovery of habit) or clockworkmod(not sure of use on the streak5 havent used since gingerstreak)
2...flash ROM "X"
3...do a factory reset........ "dell" or "streakmod" or "both" (i have done a reboot rather than any resets between the second flash)
4...access Recovery
5...wipe cache
6...wipe dalvik cache
7...flash ROM "X" again
8...fix permissions
9...reboot
I will try to add the double flash more as a matter of design than troubleshoot option in future

[Q] Have I been flashing correctly?

Hey guys!
This is my first post on the Nexus 7 forum so if this is the incorrect place to ask such a question, please tell me!
Basically, I wanted to make sure that I'm flashing my roms correctly. Specifically, I've been on a flashing binge and installed Smooth Rom, Paranoid Android and Liquid Smooth all after one another in the same sitting. My flashing process, using clockwork mod, begins by wiping all of my data and cache -> Rewiping the cache (this probably isn't needed) -> Flashing the Rom -> and lastly flashing gapps. I'd be very thankful if someone could tell me if this is a clean flash.
Also, I've noticed from other users on the boards for these roms that they're getting much higher benchmarks. For example, Smooth Rom with the Motley Kernel, one user mentioned that he got around 4800 on the quadrant benchmark which is much higher than what I've gotten even by fully overclocking. That's one of the reasons I wanted to make sure I was flashing correctly. Incidentally, I also seem to create a new set of folders on the Nexus 7 after flashing each Rom. For example, I have on my internal storage the usual set of folders (Alarm, Android, DCIM, etc...) but then I also have folders named legacy and 0. Within 0, there is a whole new set of Alarm, Android, DCIM, Downloads, etc... And within that subset of folders is another 0 folder with more of the same folders. So you get the picture. That doesn't seem right to me since eventually I'll have an outrageous amount of folders, haha.
So yeah! If anyone could tell me whether I flashed correctly and maybe why I seem to have those problems, I'd very much appreciate it!
Also, I'd like to note that coming from the HTC Vivid forums, it's a breath of fresh air to see such a dedicated and organized forum! Thank you!
darkwolfx24678 said:
Hey guys!
This is my first post on the Nexus 7 forum so if this is the incorrect place to ask such a question, please tell me!
Basically, I wanted to make sure that I'm flashing my roms correctly. Specifically, I've been on a flashing binge and installed Smooth Rom, Paranoid Android and Liquid Smooth all after one another in the same sitting. My flashing process, using clockwork mod, begins by wiping all of my data and cache -> Rewiping the cache (this probably isn't needed) -> Flashing the Rom -> and lastly flashing gapps. I'd be very thankful if someone could tell me if this is a clean flash.
Also, I've noticed from other users on the boards for these roms that they're getting much higher benchmarks. For example, Smooth Rom with the Motley Kernel, one user mentioned that he got around 4800 on the quadrant benchmark which is much higher than what I've gotten even by fully overclocking. That's one of the reasons I wanted to make sure I was flashing correctly. Incidentally, I also seem to create a new set of folders on the Nexus 7 after flashing each Rom. For example, I have on my internal storage the usual set of folders (Alarm, Android, DCIM, etc...) but then I also have folders named legacy and 0. Within 0, there is a whole new set of Alarm, Android, DCIM, Downloads, etc... And within that subset of folders is another 0 folder with more of the same folders. So you get the picture. That doesn't seem right to me since eventually I'll have an outrageous amount of folders, haha.
So yeah! If anyone could tell me whether I flashed correctly and maybe why I seem to have those problems, I'd very much appreciate it!
Also, I'd like to note that coming from the HTC Vivid forums, it's a breath of fresh air to see such a dedicated and organized forum! Thank you!
Click to expand...
Click to collapse
if your roms are flashing, then youre flashing correctly. generally you want to wipe data only if going from one rom to a different rom. but if only updating the same rom, just flash your rom without wiping anything. no need to wipe dalvik as it gets wiped when you flash the rom.
what recovery are you using? i thonk its only cwm recovery that keeps adding a 0 folder every time, no such issue with twrp recovery.
benchmarks, its about how you set up your device, and how you actually benchmark. you should benchmark at highest cpu/highest cpu, as to not allow your device to scale. if you allow your device to scale, you dont actually know what cpu speed is being benchmarked. btw, 4800 on a quadrant is low. anyways, benchmarks shouldnt matter to you(to a developer they might matter though), what should matter is how it feels and runs for you.
I follow that same routine, but have only been successful in one flash, and after trying to go to P.A., now I can't get any to boot correctly. I have maybe 4 ROMs to try from, but all day, only the one worked. LiquidJB , I think. I really wanted PA though, cause thats whats on my phone.
Sent from my PG8600 using xda app-developers app
ShifterX2 said:
I follow that same routine, but have only been successful in one flash, and after trying to go to P.A., now I can't get any to boot correctly. I have maybe 4 ROMs to try from, but all day, only the one worked. LiquidJB , I think. I really wanted PA though, cause thats whats on my phone.
Sent from my PG8600 using xda app-developers app
Click to expand...
Click to collapse
did you wipe data before flashing the new rom?
Yes. I always wipe cache and dalvik, before flashing, and I flash the rom then gapps using twrp. At this point, I'm stuck at the Google screen with one, and PA says setup stopped when I load it.
Sent from my PG8600 using xda app-developers app
Man I had at least a half dozen good responses to this topic - but my better judgement stopped me.
ShifterX2 said:
Yes. I always wipe cache and dalvik, before flashing, and I flash the rom then gapps using twrp. At this point, I'm stuck at the Google screen with one, and PA says setup stopped when I load it.
Sent from my PG8600 using xda app-developers app
Click to expand...
Click to collapse
not cache and dalvik, did you wipe data(factory reset)?
simms22 said:
not cache and dalvik, did you wipe data(factory reset)?
Click to expand...
Click to collapse
Yes. Factory reset. Unfortunately, I've now wiped the sd card (internal) so I'm trying to flash AP using a zip on my laptop with Nexus Root Toolkit v.1.5.5, but now that I tried, iss that the rom I managed to boot still has an error that the setup program stopped, and the error keeps coming up, keeping me from entering debugging mode... guess i have to do a flash stock + unroot and start fresh....
Sent from my PG8600 using xda app-developers app
ShifterX2 said:
Yes. Factory reset. Unfortunately, I've now wiped the sd card (internal) so I'm trying to flash AP using a zip on my laptop with Nexus Root Toolkit v.1.5.5, but now that I tried, iss that the rom I managed to boot still has an error that the setup program stopped, and the error keeps coming up, keeping me from entering debugging mode... guess i have to do a flash stock + unroot and start fresh....
Sent from my PG8600 using xda app-developers app
Click to expand...
Click to collapse
you redownloaded it? maybe you have a corrupt download. try a different rom insteadcif stock, unroot, reroot.
simms22 said:
you redownloaded it? maybe you have a corrupt download. try a different rom insteadcif stock, unroot, reroot.
Click to expand...
Click to collapse
Well, mean, I had downloaded something like 5 Roms. Might it be that rooting changed my boot version or something? Not sure what the boot version changes with the N7, on my phone it's pretty important.
Sent from my PG8600 using xda app-developers app
So, is there any fix for this strange folders "legacy" ans "0"?
Hey!
Sorry for not responding sooner. University applications can be so time consuming. Thanks a lot Simms22! You've been a great help. Since then, I've cared less about benchmarks and more on the fact that the Nexus is freakishly fast with SmoothRom.
I haven't fixed the legacy problem but I'm assuming (and I could definitely be wrong with this) I could just delete the extra folders seeing as they technically don't have anything inside of them and afterwards just switch to TWRP. Shouldn't be that difficult.

[Q] Wipe internal memory TWRP 2.5

I could be wrong, but it seems that older versions of TWRP had the "wipe internal memory" option but it's not listed in TWRP 2.5's wipe advanced options. I have heard that wiping "data" essentially wipes internal storage, but I am certain that even after wiping, rebooting into recovery and wiping again, stiff is still on the sdcard0. Amazon mp3's for instance. Not a big deal, but if it's not wiping the amazon mp3's what else may it be missing on the wipe?
My specific issue is that I have heard that the bluetooth issue is fixed on many of the 4.2.2 roms now (aokp apparently included in this, although according to the guy bringing us aokp it always had "no issues that he knows of" since it's release), however after flashing the latest aokp, I am still experiencing random lockups and reboots while attempting to use bluetooth. In fact, 2 versions ago, the bluetooth seemingly locked up far less than it is with the latest aokp I've flashed. So I want to make sure everything is wiped (if that's necessary), before doing a fresh install of aokp in hopes of experiencing the bluetooth without issue.
I know you're not a big fan of me, but I also missed this with the upgrade of TWRP. I've been using the "format data" option every time I flash a new ROM. I wipe caches, wipe system, format data, and reboot recovery and let it install SU prior to reboot. If you do this, make sure you move all the data you want to keep to external, pics, backups, etc.
Off topic, I promise you I'll clean up my act.
Sent from my Droid Razr M using xda app-developers app
RikRong said:
I know you're not a big fan of me, but I also missed this with the upgrade of TWRP. I've been using the "format data" option every time I flash a new ROM. I wipe caches, wipe system, format data, and reboot recovery and let it install SU prior to reboot. If you do this, make sure you move all the data you want to keep to external, pics, backups, etc.
Off topic, I promise you I'll clean up my act.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
Thank you sir, I will give this a shot and let you know how it goes. Hopefully this will do the trick. You are a changed man, RikRong!
Sent from my Droid Razr M using xda app-developers app

[Q] Different backups, superusers, and flashing kernels

Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Any information you guys can offer would be great. Thank you so much for your time !
Downloaded7 said:
Hi all,
I have learned a lot about Android customization in the last week since my Nexus 4 finally arrived at my door, and I have become reasonably comfortable with the processes of flashing ROMs/kernels, and backing up my phone to make sure I have something stable to return to if something happens to go wrong. However, I am still dealing with a few points of confusion that I was hoping someone could clarify for me:
1. I have CWM installed on my phone and I can use it to backup/restore images of my phone for safety. However, I have heard about other methods like Nandroid, Carbon/Helium, and Titanium Backup while browsing the forums, and have tried them only to become confused as to how they are different from using CWM backup. Could someone please explain this to me and clarify which is the best for keeping a backup of my phone stored on my computer?
A backup in CWM is the same as a nandroid backup. It basically take a "snapshot" of your ROM and restore it exactly as it was when backing up.
Titanium Backup is an app that backup your apps and app's data. It's recommend you only restore user's apps and data. Let Google restore any system app's data.
2. I have noticed that when I "wipe date/factory reset" in CWM, not everything on my phone is wiped. There are still plenty of files left over from previous ROM installs when I browse my phone with Android File Transfer, and obviously the .zip files you need to flash new ROM's/kernels are left too. What exactly is deleted when do a CWM factory reset?
Wiping data/factory reset only wipe the data. Wiping system will wipe your ROM (system partition) Of course you don't want to wipe all the files such as the ROM you're going to flash.
There's an option to format internal sd, that will wipe EVERYTHING so unless you know how to ADB push files or sideload a ROM, DO NOT touch that.
3. Is it necessary to wipe everything when installing a custom kernel? I have CyanogenMod 10.2 installed because it is quick and relatively bloat-free, but allows for enough customization that I can make the my phone feel the way I want it to. I want to give Matr1x/Hells-core a try, but I am tired of factory reseting everything when install a new kernel. Can I get away with just wiping Cache/Dalvik and flashing the new kernels? If not, what is the best way to avoid losing app data between ROM and kernel flashes?
No, just flash kernel. Some recommend wipe cache and dalvik cache after kernel flash before reboot.
4. What is the difference between the default Android superuser, CWM superuser, and SuperSU? They all seem like the same thing and it makes me nervous installing different ones.
Different app that does the same thing. Usually go with what is recommend by the ROM's dev. I ususally just leave what's included with the ROM.
Any information you guys can offer would be great. Thank you so much for your time !
Click to expand...
Click to collapse
Hope that answer some of your questions. I'm sure I left out some stuffs so hopefully someone else can add to it.:good:

Categories

Resources