Related
Hello!
I have been searching the forums here about custom roms, and so far, I saw two methods of how to install them.
Method1. update.zip
Method2. Backup/Restore or just advanced restore.
(both in xRecovery)
What's the difference?
If the developer of the rom stated do Method1, can we still do Method2?
Will it affect anything?
Thanks.
You cannot do the other method, it´s not possible, because they are completely different .
Method 2"restore" is like you make a backup trougth xrecovery and restore it. You can do a complete restore (recommended) or only system (your data will be not deleted, but in most cases you will have some problems)
Method 1 update.zip is a kind of script.
Fetz Braun said:
You cannot do the other method, it´s not possible, because they are completely different .
Method 2"restore" is like you make a backup trougth xrecovery and restore it. You can do a complete restore (recommended) or only system (your data will be not deleted, but in most cases you will have some problems)
Method 1 update.zip is a kind of script.
Click to expand...
Click to collapse
Thanks for that!
So you mean, Method1 is like, if you want to upgrade your rom?
Will doing Method1 erase all data?
It depends on a script. There is a file called update-script in every update and custom zip, you can view it in notepad++. If it contains FORMAT command it will wipe any partition that is named after the command. Most ROMs update zips only wipe system, which is a necessity, since you need to put new system in. Some ROMs, like doixanh's one, also wipe cache to get rid of old ROM's stuff. If there is a format data instruction, all your data and apps are gone.
This is a CWM zip which intended purpose is to make creating heimdall one click roms easier.
It will backup partitions using dd and put them in a folder on your internal SD card labeled partition-backup. You can then use these to create heimdall one-click versions of your own rom.
The partitions backed up are as follows:
Captivate Stock based roms:
/system (/dev/block/stl9)
/dbdata (/dev/block/stl10)
/cache (/dev/block/stl11)
kernel (/dev/block/bml7)
modem (/dev/block/bml12)
param.lfs (/dev/block/stl6)
Captivate MIUI/Cyanogenmod based roms:
/system (/dev/block/mtdblock2)
/datadata (/dev/block/mtdblock6)
/cache (/dev/block/mtdblock3)
/radio (/dev/block/mtdblock5)
kernel (/dev/block/mtdblock0)
recovery (/dev/block/mtdblock1)
modem (/dev/block/mtdblock5)
The data partition is not included.
This is not intended to be a backup for your Captivate, although it could be used as one. Again, it's intended for Heimdall rom creation.
For backups, it is preferable to use CWM. I personally, really like the 5.0.2.6 version by mtcarey as it tars up the data rather than dd's the entire partition which saves a lot of space (like the /data partition for example).
DISCLAIMER: I am in no way to be held responsible for what you do to your device. If you use it, whatever the consequences, they are your responsibility.
Now with that being said, this script doesn't do anything destructive but simply copies the partitions to the internal SD card for later use.
Here are the links:
Captivate Stock based - http://db.tt/tPGn42Pi
MIUI/CyanogenMod based - http://db.tt/rwy5WIel
Let me know if you have any issues with the scripts.
My bad...
10 char
b-eock said:
You have to include data on stock ROM's as it will run the check when it installs on reboot... it will fail because of the missing data partition..., so you might wanna put that into the SCRIPT!
Click to expand...
Click to collapse
you will only get the error if you re-partition
b-eock said:
You have to include data on stock ROM's as it will run the check when it installs on reboot... it will fail because of the missing data partition..., so you might wanna put that into the SCRIPT!
Click to expand...
Click to collapse
You don't need /data...
dbdata is the one that gives that error if you re-partition.
Have you given thought to writing a cwm script to backup efs, or adding it to this script?
mrhaley30705 said:
Have you given thought to writing a cwm script to backup efs, or adding it to this script?
Click to expand...
Click to collapse
I could be wrong on this point but as I understand it the IMEI number is contained there so this isn't probably the best idea.
I could add a separate script for it but I will need to confirm that this wouldn't cause issues for people replicating an IMEI number.
I was thinking of using it as a way to backup an efs.
Understood. I'll put one up later today. In the meantime, you can always copy the folder to your sdcard for safe keeping.
backing up of both EFS and Data, would be nice for PERSONAL backups, make a note not to redistribute efs or data in the heimdall one click packages.
any of your passwords/saved information will be in data..... unless you backup data immediately after flashing/pushing apps BUT before android OS setup...
efs is still a DO NOT DISTRIBUTE.
Tried using partition backup and it didn't make the backup file, or i can't find it.
in a folder on your internal SD card labeled partition-backup
Click to expand...
Click to collapse
how long did it take? a while? it should if it did something.
No, just a couple of second.
Edit
Mount system first?
It should take a minute or so to complete. Once done, reboot back into the OS and there should be a folder /sdcard/patition-backup/.
Within this folder you should have multiple images all ending in .rfs. Really they would typically end in .img but I had it save the images using an rfs extention to facilitate things with heimdall as that's what it expects.
What version of Android are you running?
MIUI. 1.11.18 w/Neo 17r18.
TRusselo said:
backing up of both EFS and Data, would be nice for PERSONAL backups, make a note not to redistribute efs or data in the heimdall one click packages.
any of your passwords/saved information will be in data..... unless you backup data immediately after flashing/pushing apps BUT before android OS setup...
efs is still a DO NOT DISTRIBUTE.
Click to expand...
Click to collapse
Agreed. /data has all your personal data and efs has your IMEI. You don't want to distribute either of these. That is primarily why I left them out of the script. Don't forget you can either copy the entire efs folder or just zip it up and save it somewhere off your phone as a backup. If you are just looking to backup the phone, CWM is much more efficient at backing it up, IMO.
mrhaley30705 said:
MIUI. 1.11.18 w/Neo 17r18.
Click to expand...
Click to collapse
Hmmm... I haven't tested it on either MIUI or Cyanogenmod. They may use a different partioning scheme. Can you please copy/paste the response of typing 'mount' from a shell?
( adb shell, then just simply type 'mount' from there )
How's this
Ok, I see the problem. It appears the MIUI and Cyanogenmod use /dev/block/mtdblock* whereas stock Captivate based roms use /dev/block/mmcblk*.
I'll see about making one for your setup.
Thanks for testing this!
No problem.
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
**Removed - wait for JCSullins official release**
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
For those not in the know, it is recommended to update your recovery and essential if you plan to update to cm10. This fixes s file system corruption bug that shows up when expanding the partition in preparation for cm10.
Sent from my HP TouchPad using Tapatalk 2
menthe said:
Hello,
I don't know if you noticed but JCSullins made a new cwm6 based recovery.
If you want to give it a try I've made a cwm flashable update archive,
https://www.dropbox.com/s/hzxb7fswws5l0ss/update-cwm6_tenderloin-20121204.zip
Click to expand...
Click to collapse
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
"Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here."
Click to expand...
Click to collapse
Open terminal
type
su
umount -o remount,rw /boot
then use es file explorer.
chadster1976 said:
Thanks for your installable zip! I had been trying to get things updated and couldn't get the uImage written to the /boot dir on my TP.
Went through adb (reinstalling drivers, connecting,etc.) then tried renaming and copying to /boot through ES File explorer with SU permissions, but it still wouldn't let me write to the /boot folder. I'm not quite sure why - I thought SU permissions allowed me to write to the /boot folder, but I guess not... I'll have to further investigate. I'm still noobish on quite a lot here.
Needless to say, your zip file helped and was finally able to get CWM6 updated on my TP. Thanks button pressed! :good:
Click to expand...
Click to collapse
Rom Toolbox lite will allow you to .
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
I flashed it and now I'm soft bricked. Can't boot into sk8's CWR6, CM10 or anything.
Lesson learned, ask developers before posting there work
Sent from my Galaxy Nexus using xda app-developers app
It likely not the CWM6 that did it but the boot partition full. If you have an extra webos kernel, some moboot themes, TWRP, and then this new larger uImage for CWM you will likely run out of space.
Probably should put that warning here it's pretty important people realize it and/or add a script to remove TWRP, to prevent issues with this zip.
@jcsullins +1 Feedback. Installed your CWM uImage manually. Mounted as mass storage in CWM, copied files, Installed latest CM10 12/05(over older CM10 installed with Acme3), Installed Gapps, Installed Camera Preview 3 patch, Installed WEBCM10, cleared both caches in CWM and noticed no issues during all the processes.
I ACMEU wiped and ACME3'd the whole deal back on w/new recovery. It needed the clean up anyways and I had a NAND from yesterday.
Nice, thanks JC.
Roland Makes oopsy
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Thank you for taking the time to create this great new CWM6. I have been really enjoying the new looks and graphics. I have tested flashing different zips and Roms. I have made and restored Nandroid backups and even restored older CWM5 backups with CWM6. I do this to try and help but sometimes I really step in $#@# trying to help, like with the 4.2gapps.
Sorry about being so anxious to get this out to the public. I have had a lot of complaints about Bricked TouchPads and would like to get the word out about the problem and how to fix/prevent it.
I feel very responsible for the people affected due to me making an install video without knowledge of the corruption issue beforehand.
I wanted to make a video explaining that there was an issue but to fix it they can, Backup, uninstall, reinstall and restore. To prevent future issues I want to included this in my install instructions. They would of course need your New CWM6 to do this and I have been eagerly awaiting this fix.
Sorry about all my stupid mistakes, I get a bit over excited about Tech stuff at times. Please accept my sincerest apologies.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
I'm sorry, but I didn't see your post in Rootzwiki or I would have posted there.
This cwm has worked flawlessly. I haven't had a chance to try all the new features, but the ones I did try worked fine.
Thanks so much for this. The old 5.0.2.6 was starting to show its age. I hope this cwm does away with the sporadic partitioning problems I'd been seeing.
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
New Backup Options
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
webdroidmt said:
In my limited testing to this point, I've not uncovered any issues. I flashed a couple of different roms, gapps and misc zipfiles and all were fine. I also made a nandroid and a subsequent restore which also worked fine.
I like the idea that that the default backup method was tar as opposed to dup, as I am more comfortable with that. Also, was pleasantly surprised to find that USB storage mount was working, I thought that this was "broken" in CWM 6.x. I transferred files back & forth on my PC with no problem.
The only oddity I came across was when trying to view the files in my nandroid backup folder in ES File Explorer, or the stock CM File Manager, the 2 android_secure.vfat.tar files were not visible. Yet they were visible in Root Explorer and of course, when I transferred it over to my PC for safekeeping, they were there.
That's about it for now. Great job as always, JC. Thanks.
Mike T
Click to expand...
Click to collapse
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
RolandDeschain79 said:
I am just trying some of the new backup options. It seems that we have a choice in the backup we make now, the Default is Tar and the 2nd option is Dup. There is also a "free unused backup data" option, since the backups appears to be in several files. I wanted to backup my backups but I am in over my head here and don't know much about the new backup options. Has anyone else had a chance to take a look? I like the spinning ball animation in the Androids stomach while I make and restore my backups:good: I can use my old CWM5 backups but now I don't know what to do about the new ones. Could anyone more experienced help me out please:fingers-crossed:
I was having the same issues trying to view the files from ES File Explorer, and from the PC. I feel like such a noob
Click to expand...
Click to collapse
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
.dup & .tar enlightenment
webdroidmt said:
Hi Roland, hope all is well with you. I am not having a problem viewing my nandroid files on my PC, just from the apps I mentioned within Android.
Anyway, just a quick blurb on the 2 backup methods of .tar & .dup. Tar is what we are used to with the older CWM version, .dup is something new to CWM and fairly similar to the way a windows PC does backups. I'm no expert but in a nutshell, .tar backs up everthing each time you do a nandroid, .dup does incremental backups each time and stores the data in "blob" files which become very large. With the .dup method, because it's only doing incremental, backup time is faster than .tar but with the large "blob" folders of data, it's a PITA to move to your PC for safekeeping.
With all the flashing I do, I'm constantly moving nandroids back & forth, so I prefer .tar at this time. But as usual, YMMV. Take care.
Mike T
Click to expand...
Click to collapse
Thank you very much for the detailed response. I’m feeling good now that I am starting to understand the new recovery. I also really liked having those individual .tar backups:good:, I made one for each version of CM. I wonder how .dup backups will affect the free space on my device. I also backup a lot but I did find that i was able to restore the older CWM5 backups without a problem. I will probably just keep the older CWM5 .tars for CM7, CM9 and do my CM10 backing up with the newer .dup. Time to transfer some backups:victory:
Can we maybe get rid of the link in op? Jc has stated this was only for testing, you shouldn't host a devs work without permission, and maybe for the fact of it will soft brick a TP? Just saying....
Sent from my HTC VLE_U using xda app-developers app
Sorry for possibly misunderstanding but is it recommended to use this yet due to possible corruption issues with older versions of CWM or only intended for testing atm? I've been meaning to ACME uninstall the TP and reinstall CM10 clean again and if this newer version of recovery is recommended for flashing I'll throw it on there while I'm at it
Thx JCSullins! :fingers-crossed:
jcsullins said:
*sigh*
"... At this point I'm just putting out a uImage to allow those who are
comfortable swapping out the uImage to test." (less than 24 hrs ago on rootzwiki)
I was hoping to get some feedback from the "more advanced" users testing this before creating an
installable zip and unleashing it on everyone. So far, virtually no feedback.
Click to expand...
Click to collapse
Hello,
Sorry for that :/
I haven't seen your rootzwiki post and so far I was just willing to help users to install it
easily (seems that was my mistake :x) because after I gave it a try it solved the issues
I was having with the previous CWM one. There is just one thing that disturb me, in
Backup and Restore menu, 'choose backup format' should be rename in something like
"choose default backup format".
That's just my 2cents and besides this all functions work well, thanks for your hard work.
I'll remove the link from the OP post and wait for your public release
Sincerely, menthe.
Has anyone tried the adb sideload yet?
When attempting to sideload I get: * failed to write data 'protocol fault (no status)' *
Any other adb commands I issue are met with "error:closed"
I am stuck here because I don't have a power button to do a hard reset... please someone tell me this function is working and I am just doing something wrong. My TP has a full charge and I don't feel like waiting 8hrs for it to die so it can be reset.
Edit: just took the whole thing apart and pulled the battery
So I was able to do a full adb backup when I was on 4.1.2 before I updated to 4.2.2.. I wanted to do another full adb backup again on 4.2.2 before putting a recovery or custom rom on my device so it would be easy to restore back to my completely stock experience (with root) if I choose. But for some reason after letting it run all the way through (I let it run overnight since it takes so long) the backup is nowhere to be found which leads me to believe it failed somewhere along the way, but no errors are reported. Has anybody had this issue or have any advice on what may be going on? I've tried doing:
Adb backup -all
Adb backup -all C:\Users\Wyth\Desktop
Adb backup -all G:\ (external HDD)
Adb backup -all G:\xtzbackup (in case adb backup had some sort of bug saving to the root of the drive)
If anybody has any help or alternative solutions to creating a full system backup I'd appreciate it! Thanks in advance!
If you are going to supply a path and file name, don't forget the -f switch
dph3055 said:
If you are going to supply a path and file name, don't forget the -f switch
Click to expand...
Click to collapse
Thanks, that was absolutely the issue. I guess I did that the first time around but forgot the second. I ended up making the backup and then unlocking the bootloader. Unfortunately I forgot that it would completely wipe the internal storage rather than just a factory reset, so I lost my titanium backups. Tried to do the adb restore, and every time after the first app it would just reboot the device. After trying it many times I ended up using the adb extractor tool to create a tar from the backup. Apparently however the backup was no good because when extracting the tar after getting to a certain part every time it came up with unexpected end of archive. But I at least got most of the titanium backup folder out. Tried copying that to internal storage and it was permission denied. Copied it to external sd, and then on the tablet transferred it to internal storage. Then every time I restored any of the data, when I rebooted the tablet it would go into bootloops. After many ftf flashes and time wasted copying things back and forth all over the place I finally am basically just resigning to starting over. Boot into CWM and made a backup, and find that it makes the clockwork mod backup folder in data/media rather than the proper place in data/media/0 or even data/media/legacy. The option to backup to external sdcard also doesn't work, as it refuses to mount sdcard or external-sdcard. Needless to say the last 24 hours or so has been massive headaches. Is there a newer version of CWM for the tablet than 6.0.3.2? It seems pretty buggy and hard to believe that it is what everyone has been using as the button combination to reboot to recovery doesn't even work.
Btw, I'm trying to do this on the stock sony 4.2.2 firmware for sgp312.
Using kernel and recovery from here:
http://forum.xda-developers.com/showthread.php?t=2433466
with ftf from here:
http://forum.xda-developers.com/showthread.php?t=2424550
Background
I do not plan on flashing roms, I have a rooted note 3(900t) with knox at 0x0(want to keep it that way). I do not want to backup APKs or personal information.
Desire
I only want to make a backup of all of my critical system files necessary to do a soft reboot. So that in a worst case scenario I never have to worry about not being able to reset my phone.
Reason
I plan on editing files with a root explorer and using Xposed framework.
Hope this is a little more clear, thanks for the help!
7US said:
I have a rooted note 3 with a knox warranty of 0x0. I would like to make a full backup of any system files that could become corrupted so that I may restore them without tripping the knox. I do not care about backing up Apps(Actually prefer to manually install them as I need them), I have all of my APK files manually backed up. Additionally I want to install Xprivacy and Xposed framework but they always warn to do a full backup. I was playing around with ADB as well but that backup seems to be directed at Apps and Contacts which I don't care about. Would it be safe to just install Xposed framework and Xprivacy and rely on the factory reset? Or is there some method I should use of doing a complete system backup. Also how would I restore that backup? (preferably I would like to have a nice backup/recovery method that I know I can always restore from my computer in case somehow one of my system files get deleted) Thank you for your help. I like to edit my system files and I have no problem using the standard phone reset I am more worried about critical failures really just as a failsafe.
Click to expand...
Click to collapse
too long.
if i get right from this longe sentences;
u cannot backup knox counter.
u can make nandroid backup from ur system but knox counter will change its value.
:good:
x102x96x said:
too long.
if i get right from this longe sentences;
u cannot backup knox counter.
u can make nandroid backup from ur system but knox counter will change its value.
:good:
Click to expand...
Click to collapse
I fixed my original post, hope it is more clear for you.
I know I cannot backup my knox counter, which is why I do not plan on installing CWM.
I am new to the Android operating system and read many threads about different methods of backing up and restoring(CWM/Titanium Backup/etc) but they always seem to be centered around backing up APKs+Contacts or backing up Roms for Rom Flashing.
I am trying to understand what I need to backup to be safe to play around with my system files and Xposed and always be able to restore any damage that I may do.
So far I played around with ADB a little bit and saw some tutorials on how to do full backups through ADB but not for the note 3. Thanks for your help! I plan on experimenting and such on my own but first I want to make sure I have necessary backups to not worry about crippling the OS.
Perhaps a question within my question is.. What type of backup do I need? What files need to be preserved for me to be able to do a system reboot to restore the phone? Is it safe for me to be using Xposed without a backup and playing around with system files? Will the soft reboot restore these files? If not what needs to be backed up, that really is my question.
7US said:
I fixed my original post, hope it is more clear for you.
I know I cannot backup my knox counter, which is why I do not plan on installing CWM.
I am new to the Android operating system and read many threads about different methods of backing up and restoring(CWM/Titanium Backup/etc) but they always seem to be centered around backing up APKs+Contacts or backing up Roms for Rom Flashing.
I am trying to understand what I need to backup to be safe to play around with my system files and Xposed and always be able to restore any damage that I may do.
So far I played around with ADB a little bit and saw some tutorials on how to do full backups through ADB but not for the note 3. Thanks for your help! I plan on experimenting and such on my own but first I want to make sure I have necessary backups to not worry about crippling the OS.
Perhaps a question within my question is.. What type of backup do I need? What files need to be preserved for me to be able to do a system reboot to restore the phone? Is it safe for me to be using Xposed without a backup and playing around with system files? Will the soft reboot restore these files? If not what needs to be backed up, that really is my question.
Click to expand...
Click to collapse
instead of making backup of ur system files u can download a firmware of ur region!
if something goes wrong when u try to modifying then flash the stock rom.
however u can easily copy a file to another direction and then paste back to original if issue appears.
for example build.prop and etc.
and for ur firmware as i said u can make nandroid backup (thr s lots of tools in play.store for it that not need custom recovery) (if i say correctly!)
:good:
7US said:
Background
I do not plan on flashing roms, I have a rooted note 3(900t) with knox at 0x0(want to keep it that way). I do not want to backup APKs or personal information.
Desire
I only want to make a backup of all of my critical system files necessary to do a soft reboot. So that in a worst case scenario I never have to worry about not being able to reset my phone.
Click to expand...
Click to collapse
suggestion:
you could use safestrap.
it is based on the twrp custom recovery but it will not trip knox !
read the thread before using it. you have some more benefits using ss, you will see.
backup the system and data partition and you are safe.
please note that this will never backup the content of your internal storage like your music, videos ond so on.
just dont wipe/format your internal storage from recovery or if you feel you need to, copy the whole content to your pc first.
additional things to backup:
you might want to backup your efs and maybe your pit file too.
easy to find info on this forum.
if you want to read more about backing up via adb, directly to the pc then this thread is for you.
i made a backup of the whole memory block one time, just for the worst case...
basicly, you just need the required files, open 2 cygwin windows and copy and paste(right click) the commands from the first 2 codeboxes from the thread into that windows.
hope this helps
A.N.Droid said:
suggestion:
you could use safestrap.
it is based on the twrp custom recovery but it will not trip knox !
read the thread before using it. you have some more benefits using ss, you will see.
backup the system and data partition and you are safe.
please note that this will never backup the content of your internal storage like your music, videos ond so on.
just dont wipe/format your internal storage from recovery or if you feel you need to, copy the whole content to your pc first.
additional things to backup:
you might want to backup your efs and maybe your pit file too.
easy to find info on this forum.
if you want to read more about backing up via adb, directly to the pc then this thread is for you.
i made a backup of the whole memory block one time, just for the worst case...
basicly, you just need the required files, open 2 cygwin windows and copy and paste(right click) the commands from the first 2 codeboxes from the thread into that windows.
hope this helps
Click to expand...
Click to collapse
Very interesting! Reading the 2nd link made me think... could I even recover my files through ADB if I crippled my OS? Don't I need to boot into the device to even get to ADB? Or can I access ADB through the stock boot screen without CWM? Safestrap also looks very tempting. Also do you have a list of the note 3 partitions for me to make ADB backups I have been looking for them on Google and can't find them anywhere the Android file structure is a jungle to me especially how it varies from phone to phone.
7US said:
Very interesting! Reading the 2nd link made me think... could I even recover my files through ADB if I crippled my OS? Don't I need to boot into the device to even get to ADB? Or can I access ADB through the stock boot screen without CWM? Safestrap also looks very tempting. Also do you have a list of the note 3 partitions for me to make ADB backups I have been looking for them on Google and can't find them anywhere the Android file structure is a jungle to me especially how it varies from phone to phone.
Click to expand...
Click to collapse
i´m not sure for the stock recovery but from twrp you can use this adb backup method. i just did it a few days ago.
you must change the path in the commands from /system/xbin to /sbin and no need for su.
it should work from safestrap too but i couldn´t get adb to work, some error message was shown.
for the partitions:
system ,data, efs
and maybe modemst1 and modemst2
theres a full list of partitions and an interesting discussion about this topic on this thread.