in the recovery mode, when you perform a wipe, what exactly does it wipe from the phone?
I was in the process of updating from JF 1.31 to JF 1.41 and one of the themes I had was messing with my phone so I performed a wipe ( alt + W). when I rebooted I was still running JF 1.41 w/o root or any of my information (apps, data, etc). So I would assume everything but the current ROM is wiped? meaning I still have to telnet to get root again?
after upgrading the JF 1.41 I performed a NAND restore...
I had previously moved the caches / apps to my sdcard do I need to do this again? iI am assuming with the NAND restore I am all set, but if I had to performed the wipe w/o the NAND restore I would need to move them again?
and what are the commands to clear the caches? I know it's listed somewhere but I can't seem to find it.
If you installed JF1.4.1 then you have root. Once you root then you don't have to re-root unless you re-flash with the unmodified RC30 image.
I'm not sure about nandroid backup and restore, having never gotten around to using it, but I would think that if you did a nandroid backup of JF1.3.1 then restoring it from JF 1.4.1 would return you to JF 1.3.1 -- that's a complete guess, though.
Wipe formats the /system and /data partitions, so you'll have to re-do all of your cache moves and moving your apps to sd.
well I must have lost root or messed it up somewhere with the NAND restore as when I open up terminal and type in SU I get the following:
error type 3
error: activity class {koushikdutta.superuser/koushikdutta.superuser.superuserrequestactivity} does not exist
....root also does not show up in the SU whitelist app.
I think at this point I am just going to backup my apps/info with mybackup, wipe and start from scratch without NAND for now....eventually creating another NAND after a fresh install.
try reinstalling super user, also you apps should still be on you sdcard, just repush mountd and init files recreate syslinks and reboot, first reboot may seem like its stuck but just wait for it atleast 5min-10min
bornsteinSAE said:
in the recovery mode, when you perform a wipe, what exactly does it wipe from the phone?
Click to expand...
Click to collapse
It formats /data and /cache.
Related
i'm using a htc desire running on cm6.
when there are newer versions of cm and i would like to update to it.
what is the best way of achieving this without having to wipe the data/settings/etc?
if there is no such way, what can i do to backup settings/data/apps so that once i update to a newer cm , i can just restore my stuff?
what about Rom Manager Premium, theres an option to check for rom updates, would Rom Manager update your rom for you?(and keep all settings/data/etc?)
Yup.
it does everyting. buy it. seriously.
vision
seriously?
i use titanium backup and it works fine for me..
another option to back up your apps & system data is the nandroid backup on the recovery menu..
titanium backup requires busybox and for that to work i need to be nand unlocked.(which im not).
i always thought that nandroid backup will backup everythign to a state, so if i were to upgrade roms, and then use restore, wont it just revert me back to the previous state(not updated)?
edwinlee90 said:
titanium backup requires busybox and for that to work i need to be nand unlocked.(which im not).
i always thought that nandroid backup will backup everythign to a state, so if i were to upgrade roms, and then use restore, wont it just revert me back to the previous state(not updated)?
Click to expand...
Click to collapse
You are correct. A nandroid restore will undo your update.
If you're upgrading to a newer release of CM6, you should be able to do it without wiping your data. Wipe dalvik and cache, flash the rom, and reboot. You'll have new featuers but all your old apps and data in tact.
Nandroid backup first for good measure though
oh okay, so wiping dalvik and cache would just wipe all settings(including home screen layout, widget placements, folders etc?)
some tutorials that i've read about updating roms, is that i dont even need to wipe dalvik and cache, anythign bad about that?
edwinlee90 said:
oh okay, so wiping dalvik and cache would just wipe all settings(including home screen layout, widget placements, folders etc?)
some tutorials that i've read about updating roms, is that i dont even need to wipe dalvik and cache, anythign bad about that?
Click to expand...
Click to collapse
Nope, dalvik and cache wouldn't even affect your settings.
The cache is the temporary cache used by the Android operating system, and the Dalvik-cache is the cache used by the Dalvik Virtual Machine. The only thing about wiping them is that the first boot will take longer as they rebuild their indexes and such.
Nine times out of ten, you'll be fine without wiping these. It's just generally considered "better" if you do.
Again, nandroid backup and try it out. If it doesn't work without wiping, restore back and wipe the caches.
The question is :
restoring "USER APP" from a backup made with clockworkmod,is the same thing than restoring from titatanium backup?
I'm talking about user app and not system app, and i know that titanium let you choose what you need.
Thanks!!!
CWM only lets you restore everything in the "Simple" mode (that is, format all main partitions and replace with the backup). If you click on advanced restore you can do the same for a particular partition, such as just /data which would essentially do what you just said.
Now i've not tried doing this via CWM, but i can easily see this leading to problems. I would use NANDROIDs only to do full backups or advanced restore only if you are using the exact same ROM as the backup. Otherwise, probably best to save the trouble and stick with Titanium.
Usually i flash cm9 kang every day,so i assume that restoring from cwm advanced restore should works without problem.
It most likely would work perfectly fine in that case. Though you can probably just wipe everything besides the /data partition to begin with and just flash the new ROM. Why wipe /data just to flash the same /data?
Harbb said:
It most likely would work perfectly fine in that case. Though you can probably just wipe everything besides the /data partition to begin with and just flash the new ROM. Why wipe /data just to flash the same /data?
Click to expand...
Click to collapse
i'M AN IDIOT...YOU'RE RIGHT
But the doubt is inside me and sometime i like to try different rom...how can i open "data.img" from cwm backup?
i would like to see what exactly is inside.
I believe it is a yaffs image file. I've not tried to open it but maybe have a look around for unyaffs. Might be easiest to do it in a linux environment, i think there are some native tools available.
However, it is likely just an exact copy of all the files in the /data partition, you're not missing out on anything root explorer doesn't already show you. This means the dalvik cache is in there too, so it might be best to wipe that separately every flash, especially if you decide to restore data via CWM afterward.
Harbb said:
However, it is likely just an exact copy of all the files in the /data partition, you're not missing out on anything root explorer doesn't already show you. This means the dalvik cache is in there too, so it might be best to wipe that separately every flash, especially if you decide to restore data via CWM afterward.
Click to expand...
Click to collapse
I had a look inside root explorer...i wanna try
I think it's the best way,if something goes wrong i'll still have my nand bkp
i tried and seems everything works fine:
start with cm9kang
-nandroid backup
-wiped all
-installed "codename 1.4.0"
-restored from kwm advanced only data
-wiped dalvik
-installed gapps
some settings have been restored,other no ,and all app works
I'm wondering now if codename is cm9 based rom
+1
albedebbi said:
i tried and seems everything works fine:
start with cm9kang
-nandroid backup
-wiped all
-installed "codename 1.4.0"
-restored from kwm advanced only data
-wiped dalvik
-installed gapps
some settings have been restored,other no ,and all app works
I'm wondering now if codename is cm9 based rom
Click to expand...
Click to collapse
sent from my so icey ns4G
For whatever reason last time my battery died my phone's not properly booting anymore.
I flashed stock rom and kernel, wiped dalvik cache, battery stats cache partition, fixed permissions...
I remember last time I had a bootloop resulting from something I did with build.prop I was able to get a verbose realtime log of the booting over USB, but I don't remember how I did it.
logcat's not found in my sbin, it's in /system/bin, and when I run it from there it stops when trying to boot into main.
I have adb and fastboot.
In recovery (ie, CWM or TWRP), do a full backup (NANDROID) and then:
data/factory reset
format /system
format /boot
Now flash a Stock ROM for your phone again. This should sort out just about any non-hardware issue.
if i restore that backup will i have my /data back? Would restoring put it in the same state of affairs that led to the bootloop?
Is there a way to partially restore a nandroid backup? I'm trying to get app data and such back.
You can restore either the whole partition via cwm or parts of it via app extractor. You can also edit the data partition and restore the edited version.
For 2 days or so I've been having random reboots and today after one I couldn't boot up my phone.Tried wiping dalvik cache and cache, flashing new boot.img and backuping and restoreing.
ROM: ViperS 1.6.3(clean install)
Kernel at that time: SebastianFM 1.5.2
Logcat attached
steelclaw said:
For 2 days or so I've been having random reboots and yoday after oen I couldn't boot up my phone.Tried wiping dalvik cache and cache, flashing new boo.img and backuping and restoreing.
ROM: ViperS 1.6.3(clean install)
Kernel at that time: SebastianFM 1.5.2
Logcat attached
Click to expand...
Click to collapse
Can you please attach a dmesg?
I also tried installing ViperS 1.63 and restoring only the data partition from the backup but again I get stuck at the splash screen.
a quick look at the logs seems like modem initialization has failed
reflash the firmware and see
also ..do a clean flash of vipers rom ..then boot it up ..setup the basic stuff
then go back to recovery and do any other things you want (another kernel, restore data etc etc )
As I said restoring data from the backup to a freshly installed ROM causes bootloops again, therefore I think that the problem is somehow connected to the data partition.
Side note: Just before the phone shut down I turned on my mobile data.Maybe it is indeed a problem with the radio?
HBOOT-1.27.1100
Radio-11.24A.3504.31_M
PS. Anyway I can get my data back from a nandroid backup?
Update:
If I wipe out the data the phone can boot normally.
steelclaw said:
As I said restoring data from the backup to a freshly installed ROM causes bootloops again, therefore I think that the problem is somehow connected to the data partition.
Side note: Just before the phone shut down I turned on my mobile data.Maybe it is indeed a problem with the radio?
HBOOT-1.27.1100
Radio-11.24A.3504.31_M
PS. Anyway I can get my data back from a nandroid backup?
Update:
If I wipe out the data the phone can boot normally.
Click to expand...
Click to collapse
Your data partition had errors. I assume the wipe/format cleaned and corrected the problem.
Yes but is there anyway I can get my data back because I have some really important stuff there.
steelclaw said:
Yes but is there anyway I can get my data back because I have some really important stuff there.
Click to expand...
Click to collapse
It's possible.
You'll need to restore the /data image you have backed up.
Reboot into 4EXT and mount the /data partition.
Make an Adv. Backup of the current /data partition.
Restore the old backup.
Run this.
Code:
e2fsck -f /dev/block/mmcblk0p23
Code:
adb pull /data/ .
The entire /data directory will be pulled from the phone to the folder in which you keep your ADB executable.
From there you can selectively copy files to the phone.
or an easy way to do is from titanium backup app
you can extract data of apps /phone from nandroid backup
Thanks both of you.
Update:
Most of my data is corrupted but luckly the one I needed was still intact
long story short: just to assure myself for everything to go smoothly while installing Lineage OS 14.2 i stupidly decided to tick the 'system' box on factory reset for TWRP along with the standard data, cache and dalvik. now i tried to system restore the backup i have on my sd card and it says error 225 at the end and its stuck on boot!
what have i done wrong? can you no longer restore if you tickbox the 'system' thing; does the backup option not backup literally everything? did my files corrupt? will the 'format data' option (deleting everything on internal storage), then trying to restore fix it? HELP.
phone is a Samsung Galaxy J3 2016 (J320fn) fwiw
idklol123 said:
long story short: just to assure myself for everything to go smoothly while installing Lineage OS 14.2 i stupidly decided to tick the 'system' box on factory reset for TWRP along with the standard data, cache and dalvik. now i tried to system restore the backup i have on my sd card and it says error 225 at the end and its stuck on boot!
what have i done wrong? can you no longer restore if you tickbox the 'system' thing; does the backup option not backup literally everything? did my files corrupt? will the 'format data' option (deleting everything on internal storage), then trying to restore fix it? HELP.
phone is a Samsung Galaxy J3 2016 (J320fn) fwiw
Click to expand...
Click to collapse
If you wiped everything, you can't just restore the system only, the default restore that restored all partitions that were backed up, is what you need.
Or, you can boot into TWRP, then select the wipe option, then select advanced wipes, then select the system, data, cache and dalvik cache partitions then swipe the slider to wipe. After the wipe is finished, flash your LineageOS ROM and gapps.
After flashing the ROM and rebooting the device, if you want to try to restore the backup that you made, boot into TWRP, when retoring a backup, it isn't necessary to do any kind of wipes because it automatically formats the partitions before restoring the backed up data to each partition.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you wiped everything, you can't just restore the system only, the default restore that restored all partitions that were backed up, is what you need.
Or, you can boot into TWRP, then select the wipe option, then select advanced wipes, then select the system, data, cache and dalvik cache partitions then swipe the slider to wipe. After the wipe is finished, flash your LineageOS ROM and gapps.
After flashing the ROM and rebooting the device, if you want to try to restore the backup that you made, boot into TWRP, when retoring a backup, it isn't necessary to do any kind of wipes because it automatically formats the partitions before restoring the backed up data to each partition.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
i solved. it turns out i just didnt have enough memory to extract the system restore into internal storage.
what do you mean though? the only problem im having in the stock OS now is that my phone will randomly stop charging and/or display different battery %'s (one time it said i had 89% for 15 minutes straight without charging it. i rebooted it and then it said it was at 94%), as well as im unable to manually update (says my original OS was modified in a non authorized manner)
is there anything i can do in TWRP in regards to either of these things? maybe re flash stock OS? (how would i go about doing that without losing all my data?)