Related
I flashed my phone to JF 1.5 and in the process some how managed to screw up my sd card and lost all my apps. i did do a nandroid backup of jf 1.41 so i ahve those img files. I tried to restore to that to recover everything but it wont boot past the g1 logo. I tried downgrading firmware to 1.43 (couldnt find 1.41) and using the same restore for nandroid and still wouldnt boot. I also tried jsut applying the user data img to see if i could jsut grab that and it fialed on both firmware revisions 1.5 , 1.43.
In the end im stuck with a backup i cant use, the only thing i need off of it is the apps. I read that you can use the emulator to mount it but i couldnt figure that out. I also looked at yaffs extractor from the google code site but i wasnt quite sure how to compile/run it.
Anyone have a simple solution or a complex one i can follow to getting my apps out?
did you follow this?
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
darkrangr said:
I also looked at yaffs extractor from the google code site but i wasnt quite sure how to compile/run it.
Click to expand...
Click to collapse
You go into the source directory, type "gcc -o unyaffs unyaffs.c", then you (create and) go to some directory where you want to extract the contents ("mkdir ~/extract") "cd ~/extract", and finally you extract the image "/path/to/unyaffs /path/to/data.img".
I tried the standard nandroid restore and it failed.
Trying the yaffs thing now and i got an error.
I placed the yaffs files all in a folder on the sdcard and put the img in that folder as well.
I open the terminal on the phone and did cd /sdcard/nan nan being the directory i made
I then tried to run that command "gcc -o unyaffs unyaffs.c" and i get gcc not found. what did i do wrong?
Unless your backup was corrupted, flashing the backup should have been fine.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
You said it failed - what error did it give? Did it say it couldn't find the command? Be sure you're running these commands on your PC with your G1 connected via USB, the correct drivers are loaded, and you have the fastboot program.
As for using unyaffs - I don't think you understand what you have to do to use it. You have to compile it on your PC...all you get is the source code. I haven't looked on the google code site, but I would imagine there isn't a version for windows.
EDIT: After reading your original post for a second time, I have to ask: if you screwed up your SD card and lost all of your apps, does that mean you were using Apps2SD? That's a bit of an important detail to leave out, if so. Unless I'm mistaken (and someone correct me if I'm wrong), your apps wouldn't be in the backup anyway, you're wasting your time. If your backup is just restoring the symlinks to the SD card and the SD card is screwed up, then no wonder it's hanging at boot. You'd need to wipe your SD card and start from scratch. I'd recommend doing that either way - would you rather have to redownload a few apps or continue having a bricked phone for days?
it didnt fail on the restore with fastboot, it loaded up everything fine and then when i rebooted it just sat on the boot screens forever and never loaded.
I am feeling nice so darkrangr if you want to PM your image files I will unyaffs it on my ubuntu box for you.
TemporalShadows said:
EDIT: After reading your original post for a second time, I have to ask: if you screwed up your SD card and lost all of your apps, does that mean you were using Apps2SD? That's a bit of an important detail to leave out, if so. Unless I'm mistaken (and someone correct me if I'm wrong), your apps wouldn't be in the backup anyway, you're wasting your time. If your backup is just restoring the symlinks to the SD card and the SD card is screwed up, then no wonder it's hanging at boot. You'd need to wipe your SD card and start from scratch. I'd recommend doing that either way - would you rather have to redownload a few apps or continue having a bricked phone for days?
Click to expand...
Click to collapse
no, my apps were installed normally. I am running curent jf firmwar enow while i try to get my stuff back, but some of the apps i had are no longer available or have converted to pay apps, plus i forgot a lot of apps i had.
http://forum.xda-developers.com/showthread.php?t=497034
In the other tools archive on this post you can find the unyaffs tool fully compiled. Just move your image to the same folder, drag and drop it on the unyaffs.exe and watch the files appear.
How about YOU DIDN'T INSTALL GCC!!!
darkrangr said:
I tried the standard nandroid restore and it failed.
Trying the yaffs thing now and i got an error.
I placed the yaffs files all in a folder on the sdcard and put the img in that folder as well.
I open the terminal on the phone and did cd /sdcard/nan nan being the directory i made
I then tried to run that command "gcc -o unyaffs unyaffs.c" and i get gcc not found. what did i do wrong?
Click to expand...
Click to collapse
Hello .
Posting a tutorial on how to create a dump out of your stock rom, in case you delete some apps or modify some settings.
ALRIGHT LETS START:
STEP ONE:
Alright, so you want to make a backup of your phone software, but dont know what to do. Its simple, download the package the Android SDK from google and copy it to C:\ drive. Once you have download it, make sure you have Java installed in your system or else it will not work. After everything is done, open the program and install these two packages:
1. Android SDK Tools, revision 6
2. USB Driver package, revision3 ([COLOR="Red"IMP: Its important that the USB driver installed shows up as Composite Android Debug Device, else it wont work. ][/COLOR]
What Android SDK ?? Read about it here: [url]http://developer.android.com/sdk/index.html[/url]
Why Android SDK ? Because: it has the [COLOR="red"]android debug shell[/COLOR] which you require before communicating with your android phone. So download it ! From here:
STEP TWO:
Download Busybox from here : http://rapidshare.com/files/407238531/busybox What is Busybox ?? Read about it here: http://www.busybox.net/
MD5 Signature: C5B76280434EEF49310AD8F1810B10B2
STEP THREE:
One you have downloaded busybox, copy it to the C:\ drive of your computer and then follow the next step. The next step is to open the Command Prompt ( type cmd in the Run prompt ) if using Vista right click on "Run as Administrator".
Assuming you are the root of C:\
Type: C:\cd android-sdk-windows
-> then
Type: C:\android-sdk-windows\ cd tools
-> if you have android debug shell and USB drivers properly installed
Type: adb devices
Now your device will show up as a binary number .. Success ! if it doesn't show up you need to install the drivers again or something else is wrong.
STEP FOUR:
Now once your device shows up, we will need to download the busybox from the computer to the phone. Since we can write anything in the /data/local portion of the android system we will copy the busybox file to the android device.
Type: adb push busybox /data/local/busybox
Once it has been copied to your device issue this command.
Type: adb shell This coomand is issued to go to your mobile's terminal where you can issue commands internally to the phone.
--> then
Type: cd /sdcard This command is given inorder to go to the sdcard ( i.e the internal storage of your phone )
--> then
Type: chmod 755 /data/local/busybox This command is issued to set user -rwxrwxr-x permissions to the file.
--> then
Finally, issue this command.
Type: /data/local/busybox tar cvf Samsung.tar /system This command is given to copy and tar the system folder where all the stock applications and programs are and to create a dump of that system folder.
STEP FIVE:
Job Done !!
The Samsung.tar file can be copied to the computer now. Have fun.
this is perfect, as i want to create a dump of my original ROM
A dump is simply a backup of your original ROM right?
thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!
OrionTC said:
thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!
Click to expand...
Click to collapse
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.
is there a way for us to backup the firmware?? (not just stock apps)
tids2k said:
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.
Click to expand...
Click to collapse
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?
droidwi said:
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?
Click to expand...
Click to collapse
Correct. We most likely won't be able to actually perform a complete backup until Nandroid works on the handset.
Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.
supercurio said:
Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.
Click to expand...
Click to collapse
im working on creating a stock rom ... may be some happy results and happy faces. who knows . keep sticked !
uploading dump again .. please wait.
So, Can i just select this dump in Odin and it will recover to stock firmware. Quite confused here.
The file size is 275 megs , so is it only for apps? Have you flashed with this dump. Nice work so far. THanks.
Edit: Just realised the dump option in Odin is for dumping my rom , not loading one.
So stuck with this until Samsung update. Huh!
Is this the same procedure as making a backup /efs?
I've been searching the forum for hours and this is the only thing I could find that looked anything like it.
This won't work
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.
Plinn said:
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.
Click to expand...
Click to collapse
+1.. The thread is misleading.. This doesn't accomplish anything! You really think people in the "Android Development" section don't know about tar?
Did anyone already managed to get the built-in dump function from Odin working?
With Odin v1.3 there was the possibility to decide whether to dump AP RAM or AP NAND (followed by an ID).
With Odin v1.52 you can't choose this anymore. It will only dump AP NAND.
But my first attempts were unfortunately not very promising
The recently posted rooting method for the KFHD has been great for owners to get started on modifying the device to suit their own tastes. However, I've been a little concerned about everybody jumping in without a safety net in place. There are numerous ways that this device can get bricked. Not to put all of you into a panic, but just getting an eventual OTA update from Amazon might put some of these rooted KFHDs in jeopardy. With no custom recovery on the horizon, I think it's important to have some backup/restore plan to get these devices booting again.
Overview
This backup plan involves making raw data clones of all critical storage partitions required to boot the device. These backup archives can then be stored somewhere off the device. In case of some critical failure that prevents the device from booting normally, these archives can be used to get the device booting normally again. The restore procedure requires the use of fastboot to write the backup archives back to their proper partitions. The use of fastboot requires a working bootloader, so the device will need to boot to the bootloader's bootlogo at a minimum. If the device has a broken bootloader, this guide will not be helpful. There's currently no working procedure for repairing a broken bootloader on the 2nd generation Kindle Fire devices.
To be clear, this guide is not a backup/restore plan for your data. This is strictly for backing up the system software while in a bootable state and recovering it if some modification bricks the device. This procedure has been tested on a KFHD with system software version 7.1.1. Although I have not tested it, I'm nearly certain it will work just fine on version 7.1.5. If the KF2 has the same partition layout as the KFHD, there's no reason why it shouldn't work for that device as well. Check the post on KFHD partitions for details.
Warning: Everything below is inherently dangerous and can potentially brick your device if they are not executed properly. I have tested various aspects to the best of my ability, but you assume all responsibility for performing any of these steps.
Backup
Attached is a small shell script written to do the following…
Make a "kindlebackups" directory in /sdcard (if necessary) and make it user read/writeable.
Create gzipped backup archives of partitions 1 through 11. This includes all partitions except /cache and /data.
Make all archive files user read/writeable.
The entire backup (stock) takes up approximately 550 MB, so be sure to have at least that much available in /sdcard. Root privileges are required for the script to run properly. The best time to use this script is after step two of the published rooting procedure. That's after the second reboot of the process when the device boots up in emulation mode and allows root access for the first time. At this point, the system partition is completely stock and has not been exposed to any modifications. Even if you are past this point, the backups will still be useful for any bootable state that allows root privileges.
Download the script, unzip and place it into your current working directory where you still have access to adb, then run the following adb commands to copy the script to the Kindle Fire and prepare it to be executed...
Code:
adb push backup.sh /data/local/backup.sh
adb shell chmod 777 /data/local/backup.sh
If the device is in the process of being rooted and it has just finished rebooting for the second time...
Code:
adb shell /data/local/backup.sh
If the device has already been rooted and the su binary is available on the system...
Code:
adb shell su -c "/data/local/backup.sh"
The entire process should take approximately 5 minutes. Once the script has completed the backup, access the Kindle Fire's storage area from your computer, then copy the contents of the "kindlebackups" folder to it. The "kindlebackups" folder may be deleted after transferring to your computer.
Restore
To begin the restore procedure, the device must be put into fastboot mode. My factory cable did the job for me, so I have not explored the possibility of changing bootmodes. I developed this guide on a borrowed KFHD and I do not intend to risk the device more than necessary. Unless someone comes forward with a procedure to change bootmodes into and out of fastboot mode, I'm going to say that a factory cable is required for the time being. Besides, based on my experience with the original Kindle Fire, a broken system almost always means there is no way to change the bootmode through it. Since this procedure will very likely be used on a device that cannot boot completely or otherwise has a bad system, a factory cable will probably be the only way into fastboot mode. If you plan to root or modify your system software, invest in a factory cable.
Use the factory cable (with the device turned off, plug into the device, then the computer) to get to fastboot mode. If successful, a "fastboot" logo will take the place of the original "kindle fire" logo.
Decompress the gzipped archive to be flashed… Linux users have gunzip, Mac OS X users also have gunzip and a built-in GUI utility, and Windows users can use 7-zip. The archive must be decompressed before flashing. Skipping this step will brick your device.
Flash the image file(s) back to the device. In most cases, the device will just have to get a working system partition flashed back to it, but the others are available if they are needed. To flash the system partition...
Code:
fastboot -i 0x1949 flash system system.img
- Optionally erase the cache and/or userdata partitions if the contents of either interfere with the operation of the system software. The system will rebuild them on reboot…
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
Once the process is complete, long-press the power button (~20 seconds) until it powers down, unplug the factory cable, and power the device back up.
Good luck.
Thanks kinfauns. I appreciate everything you did for the original kindle fire. This should help a lot of people.
Sent from my Kindle Fire
My kindles /system directory is already screwed. Do you have a system.img file I can use?
Sent from my Galaxy Nexus using xda app-developers app
When i boot my kindle fire hd to fastboot (by factory cable) and connect it to pc, pc can't recognize kindle, it don't have driver for it.
Could anybody post his clean backup here? Screwed my kindle, want go back to stock. Backup is only way.
Copying kindlebackup folder
Thanks for the script - the backup procedure was smooth -
I couldnt find the kindlebackups folder while browsing through my PC and for others like me who wonder how to take these out of your KFHD, here is a simple way - I used a program called Wondershare MObilego (Manage SDcard option under more tools) Backing up was a cakewalk.
I have no affiliation to this tool maker - Just sharing a way that helped a n00b like me. (First rooting experience)
Thanks for the efforts!
BTW, will a backup from a clean device work for other devices instead of the same one which the backup was created from? Just wondering if people who have already fiddled around their root devices can get a fresh start.
vuhai6 said:
When i boot my kindle fire hd to fastboot (by factory cable) and connect it to pc, pc can't recognize kindle, it don't have driver for it.
Click to expand...
Click to collapse
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
for device driver information. Again, written for the original KF, but the process for installing device drivers is the same. Only the PID is slightly different and that should get edited in the INF before installation.
ceebu said:
Thanks for the script - the backup procedure was smooth -
I couldnt find the kindlebackups folder while browsing through my PC and for others like me who wonder how to take these out of your KFHD, here is a simple way - I used a program called Wondershare MObilego (Manage SDcard option under more tools) Backing up was a cakewalk.
I have no affiliation to this tool maker - Just sharing a way that helped a n00b like me. (First rooting experience)
Click to expand...
Click to collapse
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
dreamcryer said:
Thanks for the efforts!
BTW, will a backup from a clean device work for other devices instead of the same one which the backup was created from? Just wondering if people who have already fiddled around their root devices can get a fresh start.
Click to expand...
Click to collapse
I have not tested this and don't have a way to do so. I have some concerns about it, but I'm sure someone desperate enough will jump in and try it out. I know it's too late for some, but my suggestion is for everybody to make a backup if you can and not rely on someone else to give you archives after the fact. It's better to have your own backups.
Not recognized
My kindle is also not recognized when plugged in
kinfauns said:
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
vuhai6 said:
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
Click to expand...
Click to collapse
I know that the vendor id is correct.
Sent from my Kindle Fire
kinfauns said:
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
Click to expand...
Click to collapse
I was only able to see the contents of /sdcard using windows...
Sent from my GT-I9100 using xda app-developers app
cesdev89 said:
My kindle is also not recognized when plugged in
Click to expand...
Click to collapse
Then you're first going to have problems getting root privileges. You need to get adb working before you attempt any part of rooting or backing up with this procedure.
vuhai6 said:
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
Click to expand...
Click to collapse
This is the correct "product" reported by the KFHD. This and the product ID (0007) are the only differences between the KFHD and the original when it comes to installing the device drivers on Windows.
ceebu said:
I was only able to see the contents of /sdcard using windows...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
/data/media and /sdcard are essentially the same thing (see the second post in this thread for an explanation of why this is the case). You should have seen kindlebackups in that directory.
kinfauns said:
You should have seen kindlebackups in that directory.
Click to expand...
Click to collapse
For some reason I didn't see it there, on hindsight I guess I panicked a bit (n00b) and fell back to the solution I already had.. (been using mobilego to manage my sgs2)..
Sent from my GT-I9100 using xda premium
kinfauns said:
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
for device driver information. Again, written for the original KF, but the process for installing device drivers is the same. Only the PID is slightly different and that should get edited in the INF before installation.
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
I have not tested this and don't have a way to do so. I have some concerns about it, but I'm sure someone desperate enough will jump in and try it out. I know it's too late for some, but my suggestion is for everybody to make a backup if you can and not rely on someone else to give you archives after the fact. It's better to have your own backups.
Click to expand...
Click to collapse
I'm ready to try
Didn't show at first
Kindlebackups showed up in root browser right away, but didn't show on PC until I rebooted KF2. So now should
I decompress and put in folder containing ADB?
Yuretz said:
Could anybody post his clean backup here? Screwed my kindle, want go back to stock. Backup is only way.
Click to expand...
Click to collapse
I got the same situation, could anyone kindly help to provide a backup?
Same here ... just need the system image ... Please
I'd appreciate it if everybody would refrain from making this a "beg for a system image" thread.
strat6 said:
Kindlebackups showed up in root browser right away, but didn't show on PC until I rebooted KF2. So now should
I decompress and put in folder containing ADB?
Click to expand...
Click to collapse
You can put the the images wherever you want, but you'll need to specify the path to the file. For example, if you are using Windows and put the kindlebackups directory on C:, you just need to modify the command to...
Code:
fastboot -i 0x1949 flash system C:\kindlebackups\system.img
Thank you for posting how to do this. It opens a lot of doors with at least a little security.
I made a backup earlier without a problem, then went ahead and made myself a factory cable(easy to do and worked great- old asus usb cable, 1k resistor, soldering iron, shrink tape and voila!). I feel much better about doing any mods to this device now knowing I can just flash my backup.
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.
I'm a complete beginner when it comes to rooting, flashing and so on. I've been using my Nexus 4 since the day it came out, and have always had it completely stock, never even rooted it or anything. I'm normally not too bad at stuff like this, but I've been googling how to do all of this and been reading some guides on here, and I'm just getting more and more confused.
My goal is to go from Stock Android 5.1.1 to the newest Cyanogenmod nightly, and to keep all my data. Now, how do i go about this?
I'm already stuck at the first step (or at least I think, that's the first step): Creating a backup of my current Stock phone. Apparently I need to create a NANDROID backup first, but I can't do it with a locked bootloader? And if i unlock the bootloader, my data will be wiped? This alone seems completely illogical to me, because how am I going to backup my device then? Is there no simple step by step guide for Nexus devices, that includes EVERYTHING, from backup to the final flashing of the ROM?
This is a good guide http://forum.xda-developers.com/showthread.php?t=2018179
I've seen it and it doesn't answer my question. How do I unlock the bootloader to create a backup, without wiping my device?
jb91 said:
I've seen it and it doesn't answer my question. How do I unlock the bootloader to create a backup, without wiping my device?
Click to expand...
Click to collapse
You can't unlock the bootloader without wiping the device. The only backup you will be able to make without an unlocked bootloader is copying your sdcard to your pc and use an app like helium to backup your apps and data. Just remember to copy that backup to your pc as well, otherwise it will be wiped.
theminikiller said:
You can't unlock the bootloader without wiping the device. The only backup you will be able to make without an unlocked bootloader is copying your sdcard to your pc and use an app like helium to backup your apps and data. Just remember to copy that backup to your pc as well, otherwise it will be wiped.
Click to expand...
Click to collapse
Thanks. Do you know this "Nexus Root Toolkit" program? I was able to create a backup file containing all apps with it, as well as extract a file with my contacts data from my Nexus 4. I'm guessing this should also include my SMS / WhatsApp messages and so on?
jb91 said:
Thanks. Do you know this "Nexus Root Toolkit" program? I was able to create a backup file containing all apps with it, as well as extract a file with my contacts data from my Nexus 4. I'm guessing this should also include my SMS / WhatsApp messages and so on?
Click to expand...
Click to collapse
Unfortunately I don't know much about that. You could skim through some of the thread or search to find out if someone else has asked that question and if not ask it there. That would probably be the easiest way to find out.
This is extremely confusing, I have no idea how people can say it is simple to put a custom ROM on a Nexus device. I am absolutely lost trying to back up everything. Is a NANDROID backup just a full backup of the phone? Am I not completely screwed if I can't create this? I have some random app files, extracted from a Root Toolkit, and a contacts file. I don't think that's enough to save my device in case anything goes wrong during flashing?
One of the sticky threads here mentions this right at the beginning:
Before you do anything EVER, you'll always have to backup your stuff, even if you don't feel like it, or your dog died (in which case I'm truly sorry), but, no matter what you're about to do, always have a recent backup sitting around.
There are many ways and things you can and will probably have to backup.
1. Backup your entire phone, by creating a Nandroid Backup.
As you saw in the 'Custom Recovery" picture above, you have a "Backup and Restore" option.
Click to expand...
Click to collapse
But it doesn't make any sense. "Before I do anything", I can't even create the NANDROID backup to begin with, because the bootloader is not unlocked by default, and unlocking it will wipe everything on the device. So I don't get how the first step to put a ROM on a phone is to create a NANDROID backup, because from my understanding, it is not possible to do. Also, my Nexus 4 did not come with a "custom recovery" installed and I have no idea how to put this on there (do i do this before or after the NANDROID backup?). I'm really starting to wonder how anyone actually understands these guides.
jb91 said:
This is extremely confusing, I have no idea how people can say it is simple to put a custom ROM on a Nexus device. I am absolutely lost trying to back up everything. Is a NANDROID backup just a full backup of the phone? Am I not completely screwed if I can't create this? I have some random app files, extracted from a Root Toolkit, and a contacts file. I don't think that's enough to save my device in case anything goes wrong during flashing?
One of the sticky threads here mentions this right at the beginning:
But it doesn't make any sense. "Before I do anything", I can't even create the NANDROID backup to begin with, because the bootloader is not unlocked by default, and unlocking it will wipe everything on the device. So I don't get how the first step to put a ROM on a phone is to create a NANDROID backup, because from my understanding, it is not possible to do. Also, my Nexus 4 did not come with a "custom recovery" installed and I have no idea how to put this on there (do i do this before or after the NANDROID backup?). I'm really starting to wonder how anyone actually understands these guides.
Click to expand...
Click to collapse
Following the link to the guide, I see this:
*****
Unlocking the Bootloader:
***NOTE***
This will perform a factory reset on your device. You will lose all applications. Even the data on your SD Card! I'd recommend making a Backup to your computer BEFORE performing this. There is a method for backing your data up, detailed HERE.
For the time being, there is a method available that will allow you to unlock your device (and root it) without losing your data.
For instructions, click HERE. Please note: this is a hack and isn't the "conventional" and "accepted" way of unlocking your bootloader on a nexus device. The wipe requirement is there for your safety, really, and I'm certain this will be patched in the upcoming releases.
*****
But you can always use adb directly from your pc to backup your entire device. How? adb --help
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
greg17477 said:
But you can always use adb directly from your pc to backup your entire device. How? adb --help
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any installed apk expansion
(aka .obb) files associated with each application; the default
is noobb.)
(-shared|-noshared enable/disable backup of the device's
shared storage / SD card contents; the default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem would
ordinarily cause them to be omitted.)
Click to expand...
Click to collapse
Is ADB this "Android Studio" that I had to install in the first step of this guide (Android SDK)? If so, I opened it but I have no clue how to get anywhere where i could enter code like this. This is what it looks like: http://i.imgur.com/zhujSKR.png
jb91 said:
Is ADB this "Android Studio" that I had to install in the first step of this guide (Android SDK)? If so, I opened it but I have no clue how to get anywhere where i could enter code like this. This is what it looks like: http://i.imgur.com/zhujSKR.png
Click to expand...
Click to collapse
Sorry, i can not help you , if you do not know the basic of basics Lots to read up for you.
cheers
Well ok, lets try it another way: i don't understand how to create a full backup, but i did backup some single apps to my PC using Nexus Root Toolkit (they're .ab files), for which i want to keep my data. I also manually backed up my mp3s and pictures / videos. Would i be fine just starting with the actual process (unlocking bootloader, install custom recovery and so on)?
After all, i should have the possibility to revert anything back for these apps at least, and the official Nexus 4 Stock Android files are available at Google. So, there's no real risk, even without a FULL backup of everything, correct?