NOTE: IF YOU HAVE NO CLUE WHAT THIS IS, THEN LEAVE IT BE
CAUTION: PLEASE READ THE FOLLOWING POSTS ABOUT BACKING UP "USERDATA".
CONFIRMED WORKING!!!
Thanks to then following for their feedback and testing:
open1your1eyes0
con247
scrosler
While playing around with my extra SCH-I535, I came across something very interesting.
I was having a lot of problems getting "full" backups of my larger .img's (ie. data, cache, etc.) I was told to try and mount my system as r/w and adb through my computer instead.
When i would try backing them up in a terminal emulator, I would always get an error about the file being too large...[\B]
I got too confused trying and got way too frustrated.
I found out that I could obtain these .img's just as easily as copy and pasting.
I was able to get the full backup sizes this way also.
Now this method does not have EVERYTHING worked out. If I could get some input and help on this, that would be greatly appreciated.
DIRECTIONS:
1. Take any rooted sgs3 and install ES File Explorer.
2. Setup ES with root (go into settings and click on the "root options" and allow ES to take advantage of root and go up to the "/" directory).
3. Also make sure to change your default home folder to "/" in settings.
4. Now exit out of ES and open it up again. You should be in the root directory (/).
5. Open up the folder marked "dev" (or the "/dev" folder) and locate the "block" folder (or the "/dev/block" folder).
6. Copy the folder named "block" (long-press and select "Copy").
7. Now move to your extSdCard (or you can stay in your internal card if you insist and have a lot of room to spare).
8. Create a folder and name it something you will remember.
9. Paste in that folder and go make yourself a bowl of oatmeal or whatever (you can see the process ongoing in your notification bar).
10. After they are done copying, you will be left with a lot of files (there will be a folder in the folder you created and then a few more folders you will have to open to get to the folder with all the goodies in it)(you'll understand when you see it). Most of them you will find familiar if you ever opened up a stock ODIN tar.md5 before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---
11. Now you have all these files, but none of them have extensions. Transfer this folder to your Linux environment and go ahead and add the proper extensions to these files by renaming them.
Some of them should be .sbn, some should be .img or .ext4. The best thing to do is to download a stock ODIN img and add the file extensions that correspond with them to your copied files.
12. Now you can use the kitchen or any other method that would require these files.
I have only had time to test these files out in the kitchen and create a working folder for them (so I could remove unwanted things and bloat ware, etc.).
I used the system.img.ext4 and another boot.img to create a flashable ROM.
I didnt use the boot.img from the copy I made cause I didn't have time to play around at the moment. But I will be trying later tonight.
It would be cool if anyone else could help me out by testing this and letting me know what was up.
NOTE: I AM NOT RESPONSIBLE FOR ANYTHING YOU DO. PERIOD. BOOM.
IF I MADE YOUR LIFE ANY EASIER, HIT THE THANKS BUTTON
Sent from my SCH-I535 using Tapatalk 2
Interesting...
I will give it a shot tomorrow
Good method but essentially this is the same as this without creating an actual ODIN image: Link to thread
Minor word of caution, the "userdata" partition include all the contents of your /sdcard partition (meaning your internal storage). Basically if you're backing that up you have to have enough space to duplicate the contents of your internal storage your external SD card or the same internal SD card (whichever location you are copying to).
open1your1eyes0 said:
Good method but essentially this is the same as this without creating an actual ODIN image: Link to thread
Minor word of caution, the "userdata" partition include all the contents of your /sdcard partition (meaning your internal storage). Basically if you're backing that up you have to have enough space to duplicate the contents of your internal storage your external SD card or the same internal SD card (whichever location you are copying to).
Click to expand...
Click to collapse
This!
And, backing up userdata while it is being "used" can result in corruption. I wouldn't recommend this backup method for backing up userdata.
Thanks for the feedback brothers.
For the system partition and what not, its a much easier way for me. And it takes some confusion out of getting the errors (too large errors).
Its a bit faster too.
Just wanted to share it with y'all.
Sent from my SCH-I535 using Tapatalk 2
Have you noticed anything odd with the files you get using this method? I was just wondering about backing up partitions while the system is booted normally. To be honest I haven't noticed anything wrong with images that I pull from my device while its booted normally, but I was looking at this thread and the thought popped into my mind that maybe some files might be in use by the system? Probably not except for log files.
Anyway, I could write a script that would do this on your device without having to fiddle around with ES. The only difference would be that I use tar and excludes to get /data without pulling /data/media. I'd really like to get a /data img without having to resort to tar, but I haven't gotten around trying to dd mmcblk0p15 without getting the whole internal sdcard along with it. I have the 32gig SGS3 so its a big issue for me. I had an idea to unmount /mnt/sdcard, but I'd imagine its not as trivial as unmounting the internal sdcard while in recovery and I really don't want to destroy my phone.
Anyway, nice find mate.
Ta,
ALQI
I personally haven't had any problems when backing up my system.img. I always make sure to do a fast reboot and kill any tasks running with ES right before I do it.
I have taken the system.img and used it in the kitchen a few times andnnot had any problems.
This method works for the most part but shouldnt be something to mess around with unless you know what your doing. I am trying to work out a way so that I can get it to match 100% with a regular dump (MD5).
This is really just a kind if a shortcut for people already using ES on a rooted system.
If your already rooted and already have ES File Explorer installed, all you literally have to do is go into the /dev folder and copy the /block folder (or whatever you need from it) to your extSdCard. And then add ".img" or whatever the extension should be to the end of the file.
Just copy, paste and add extension.
I was having issues with the terminal kicking back at me with "file too large" errors when trying to get some of my backups.
I was fiddling around with ES and discovered this.
I was hoping someone might be able to use this. Or that maybe it was a missing piece to someone's puzzle or that someone could do something more with it.
When I discovered I could get a result from just copy and pasting, I thought I might be able to figure out another easy way that backup. In known there is a couple really good ones out there already, but having different options can sometimes benefit different situations, scenarios and whatnot.
If you wanna play around with this, feel free to brother.
:thumbup:
Sent from my SCH-I535 using Tapatalk 2
Related
All issues fixed, new file has been uploaded and the link updated
Ok, I like you, am tired of not having anything at all out there to flash and screw around with. I put this together last night and now that we have a somewhat functional clockwork recovery I wanted to give people something to screw around with.
That said, I'm having a lot of issues getting clockwork to properly flash .zips but fortunately there is a ghetto work around until I can look into fixing the issue.
Framework and apps are all deodexed and zip aligned. This is virgin, you will have to enter all of your information again so keep a titanium or mybackup handy.
I advise against restoring any data from apps that were once .odex. So restore your previous information carefully.
Do a Clockwork backup prior to doing this. If you don't then that is your own problem.
What you need:
1. You should be rooted and have clockwork recovery installed.
2. Download this image
http://www.megaupload.com/?d=CEIZVMHK
3. Extract the folder to your desktop. DO NOT CHANGE THE NAME leave it in the format that it is in.
4. Mount your sd card and open it. You should have a folder clockworkmod > backup >
If you don't then you didn't do a backup. Go back and re read what I wrote from the top and do that first.
5. Open that backup folder and drop in the file you extracted
6. You should see
clockworkmod > backup > 2010-09-15.00.44.56 > with three files cache, data and system .img.
If there is an extra folder from extraction or your directory structure is different it won't work.
7. reboot to clockwork recovery (power off, wait, hold volume down, camera then power until you see it)
8. go to backup and restore
9. restore
10. Select 2010-09-15.00.44.56
The backup will process on your device, once finished hit reboot and you will have a fully deodexed, zip aligned stock rom that you can now customize.
I have done this multiple times without any issues. You can also try a selective backup of just the /system folder and try an retain your /data. This has worked in the past for me, however I did have one incident where it cause a lot of issues and I had to do a full restore to stop the force close.
What do you gain?
Well the rom is a little bit zippier with things optimized a bit and there is a little more RAM available. It is also easier to skin and do other things now that all those pesky .odex files are gone.
If you have a question or issue post it here. Don't send me PM's.
Troubleshooting
1. Can't download from market?
Make sure you are signed into Gtalk.
check your pm and respond
Thanks man. Im speeding home for you. I can't download it from the epic for dome reason. My hero or evo was fine downloading zip files.
Sent from my SPH-D700 using Tapatalk
Sir. Yes Sir!
J/K
Seriously though, noobnl, is there a problem with this? You shortness makes me think there may be some issue.
done12many2 said:
Sir. Yes Sir!
J/K
Seriously though, noobnl, is there a problem with this? You shortness makes me think there may be some issue.
Click to expand...
Click to collapse
nope no problem
I'm out right now so I don't have acess to anything. I'll take a look at my update script and files to make sure its not just a stupid mistake.
Until then this works fine for people looking for something to mess with.
Flashing right now.
I have to files in the "clockworkmod/backup" folder. On is my backup today, which is 2010-09-14.20.23.11 and the other is 2010-09-14.05.12.51 (3 files totalling 254 Mb).
When I attempt to restore the 2010-09-14.05.12.51 folder, I get the following.
Please advise if this is correct.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure you don't have an extra folder. Sometimes depending on how you extract the files you will end up with an extra folder.
Clockworkmod - should have the backup folder among other things
backup folder -should have the 2010-09-14.05.12.51 folder and your other backups
2010-09-14.05.12.51 folder should have cache.img, data.img and system.img
There shouldn't be any extra folders, that will create an issue with the recovery seeing the files.
Aridon, bro. Just flashed. No problems what so ever.
Yeah, all three (cache.img, data.img and system.img) are in there. I have run the restore twice with the extact same results as the pictures I've posted.
Aridon, the phones feels Snappier by FAR. I'm gonna run Quadrant and Linpack.
done12many2 said:
Yeah, all three (cache.img, data.img and system.img) are in there. I have run the restore twice with the extact same results as the pictures I've posted.
Click to expand...
Click to collapse
Did you do the newer version of Clockwork recovery?
http://forum.xda-developers.com/showthread.php?t=782300
Make sure your directory structure is exactly as it needs to be. I have it bold in the first post. Under Step 6.
If so, try downloading it again maybe its corrupt. Make sure you use winrar or 7zip to open it. Windows built in depacker is ****.
Aridon said:
Did you do the newer version of Clockwork recovery?
http://forum.xda-developers.com/showthread.php?t=782300
Make sure your directory structure is exactly as it needs to be. I have it bold in the first post. Under Step 6.
Click to expand...
Click to collapse
I did that exact Clockwork recovery in your link. As far as the directory structure, I know nothing abou that stuff I do know that it did successfully restore my original back up just now, so at least that is working for me. I am more than confident I am not seeing something, but I have no idea what. It seems pretty straight forward.
Aridon, got an 8.113 on first try with Linpack and 965 on Quadrant.
Could having the Andromeda Galaxy Kernel v1.3.0 mess up this process at all?
done12many2 said:
Could having the Andromeda Galaxy Kernel v1.3.0 mess up this process at all?
Click to expand...
Click to collapse
I had it. No problems.
done12many2 said:
I did that exact Clockwork recovery in your link. As far as the directory structure, I know nothing abou that stuff I do know that it did successfully restore my original back up just now, so at least that is working for me. I am more than confident I am not seeing something, but I have no idea what. It seems pretty straight forward.
Click to expand...
Click to collapse
Directory structure is easy: Its a giant file cabinet with folders.
clockworkmod > backup > 2010-09-14.05.12.51 > with three files cache, data and system .img.
Open clockworkmod folder on your sd card:
Open backup
open 2010-09-14.05.12.51
You should see 3 files in there (cache.img, data.img and system.img). You shouldn't have to open anything else to see those files. Even an extra step like opening 2010-09-14.05.12.51 twice will mess up the process.(eg. you open it and see another one there and open it and then see the files, that would mess things up).
You should NOT have to open up any other folders, even if they have the same name, it will screw up the restore. So if you had to open 2010-09-14.05.12.51 (or any of the other folders twice or in a different order) that would be an issue.
done12many2 said:
Could having the Andromeda Galaxy Kernel v1.3.0 mess up this process at all?
Click to expand...
Click to collapse
No. This doesn't make any changes to that portion of the device.
Aridon said:
Directory structure is easy:
clockworkmod > backup > 2010-09-14.05.12.51 > with three files cache, data and system .img.
Open clockworkmod folder on your sd card:
Open backup
open 2010-09-14.05.12.51
You should see 3 files in there (cache.img, data.img and system.img). You shouldn't have to open anything else to see those files. Even an extra step like opening 2010-09-14.05.12.51 twice will mess up the process.
You should NOT have to open up any other folders, even if they have the same name, it will screw up the restore. So if you had to open 2010-09-14.05.12.51 (or any of the other folders twice or in a different order) that would be an issue.
Click to expand...
Click to collapse
Well sir, you are a great fellow! You hit the nail on the head with the structure as I had the three files within a folder named 2010-09-14.05.12.51, which was located within another folder named 2010-09-14.05.12.51.
Thanks for your patience with a new guy. This and my Evo are my first Android phones and guys like you are making the transition great!!
Let me know what the protocol is for giving credit for credit due around this forum!
So custom kernels stay? AWESOME!!!
I made one of these for my MicroSD card 'cause I'm nerdy like that
Thought some of you might like them too.
Only working with Android 2.1 and below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install Instructions:
*flashable zip in post 6
You can change the name you want displayed under your icon by opening autorun.inf in any text editor and changing the 'label=' value.
You may have issues viewing the icon or renaming the drive if you don't unmount then remount after first 'install'.
If you want to install both of these (at separate times, of course) I highly recommend that you rename the 'icon' and 'label' values in autorun.inf as well as the .ico file or you may get a black icon where a white should be or vice versa.
Thanks, looks great!
Good Idea, thank you for sharing.
AyDee said:
Install Instructions:
I tried to make it noob-proof, so bear with me, advanced users
Download one of the attached .zip files
Attach your X10 to the computer and mount the sd card from the pulldown menu on your phone and open to the root
Unzip the contents of your .zip file to the root of your MicroSD (2 files)
Choose to safely remove the MicroSD {ie PHONE CARD (F: )} on your computer then unmount it from the pulldown menu on your phone
Done. The next time you mount the sd to the computer it will have a custom name and icon.
You can change the name you want displayed under your icon by opening autorun.inf in any text editor and changing the 'label=' value.
You may have issues viewing the icon or renaming the drive if you don't unmount then remount after first 'install'.
If you want to install both of these (at separate times, of course) I highly recommend that you rename the 'icon' and 'label' values in autorun.inf as well as the .ico file or you may get a black icon where a white should be or vice versa.
I found the original .png's on the internet and just converted them to icons (less time/work). If anyone has time to make some other icons or has some already made, feel free to post!
Click to expand...
Click to collapse
This is SO not noob friendly
I download the zip file (by default goes to sdcard/downloads)
I attached my phone to my comp and mounted my sdcard, I think....I selected "turn on usb storage" is that mounting my sdcard?
Here's where I get lost, you said "and open to the root"....please clarify.
First problem is I don't have any option that says "mount sdcard" in the pull down menu once you connect the phone to the pc, when I pull down that menu it says "USB Debugging connected" and "USB connected, select to copoy files to/from your computer." When I select that option, the contents of my sdcard automatically pop up in a window on my pc, I can't get to the root of my sdcard on my comp. Opening Root Explorer and trying to access my sdcard results in an error that says "sdcard is not currently mounted" and won't allow access. I then went to settings/storage to see if I could mount my sdcard that way but the option was greyed out, it was as if I didn't even have an sdcard in my phone as none of the other sdcard info was populated either.
I then ejected my device from my pc and turned off usb storage, went back to settings/storage, and my sdcard was recognized and the "unmount sdcard" option was active, making me think that when the phone recognizes my sdcard, that means it's mounted. Also making me think that in your directions you mean "turn on usb storage" not "mount sdcard".
How do you gain root access via PC? The best I could do was see everything stored on the sdcard.
When you unzip the zip, you have a folder that contains the 2 files, are we supposed to copy/paste those files somewhere or can we just put the whole folder where it needs to be?
Please advise
916x10 said:
This is SO not noob friendly
Here's where I get lost, you said "and open to the root"....please clarify.
Click to expand...
Click to collapse
I believe that means the root of the SDcard.
e.g. C:/Computer/sdcard
Shadow Xs said:
I believe that means the root of the SDcard.
e.g. C:/Computer/sdcard
Click to expand...
Click to collapse
This^
I'll make a couple of flashable zips... This was pre-xrecovery!
Seems so long ago, but it was less than a year....
*Edit- Attached
AyDee said:
This^
I'll make a couple of flashable zips... This was pre-xrecovery!
Seems so long ago, but it was less than a year....
*Edit- Attached
Click to expand...
Click to collapse
That wasn't my only question, but the rest is irrelevant now thanks to the flashable zips
Still doesnt work
Sent from my X10i using XDA App
916x10 said:
Still doesnt work
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Does it flash?
You have to turn usb storage on to see it, not just connect via usb.
Sent from my X10i using XDA App
Give it up guys, these icons will not work on GB, since for security reasons Android deletes all autorun.inf files from SD card each time it is mounted. I've tried many options, like making it readonly, system etc., still no luck - file gets deleted.
Wow. I'm an idiot lol.
I never mount my card to PC anymore, I just push things to my card with adb/X10Mod Tool or throw it in Dropbox. Sorry for the runaround.
*Edited 1st post
AyDee said:
Wow. I'm an idiot lol.
I never mount my card to PC anymore, I just push things to my card with adb/X10Mod Tool or throw it in Dropbox. Sorry for the runaround.
*Edited 1st post
Click to expand...
Click to collapse
On GB the autorun file disappers after reconnect...
AyDee said:
Does it flash?
You have to turn usb storage on to see it, not just connect via usb.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Yeah it flashed fine but when I turned on usb storage and checked my sdcard for the files, only the icon file was present. Pretty much confirming the other guys post. Oh well, it was worth a shot.
Its a free Root Explorer without Ads and without network use.
When busybox and root modes are enabled, you can make dumps of your nand partitions and export Kernel and initramfs (Menu/Tools)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://market.android.com/details?id=fr.wdscript.yaffsexplorer
You can report here bug and feature requests...
Example : Dump and Rename The /cdrom partition (p17)
change dump file ext from .raw to .iso and you get your Windows drivers (MotoHelper 2.0.44 Driver 4.9.0 - 27 Jan 2011)
Version 1.9.9.8 attached
Awesome thanks, will def check this out.
useful tool
How can i dump the roofs?
can i restore it after backup?
Thank you.
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Update v1.1 : You can create yaffs images now
Epsylon3 said:
This tool execute this command :
dd if=/dev/block/<partition> of=/sdcard/<partition>.raw ibs=8192 obs=8192 conv=notrunc
So you can do the reverse command (not in the tool because dangerous)
Click to expand...
Click to collapse
Do you know, how to dump and remount the rootfs?
Thank you.
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Epsylon3 said:
in fact, i dont know... rootfs is mounted before android (initrd on some devices)
Click to expand...
Click to collapse
Ok, thank you.
Ok, been using this for a while now; couple suggestions.
1. Copy feature needs to work more like Root Explorer.
---- So when you long-press and copy a file, two buttons popup, Paste and Cancel - Maybe you could even add a third to paste quickly to a favourites folder without leaving working directory ?
2. Be able to change text size of file browser. I have big fingers heh.
3. Have a Mount/Unmount button similar to the Mount R/W in Root Explorer.
--- I find I cant copy anything to anywhere, am I just missing something ?
4. Select multiple files, and copy, delete, zip, move . . . . . to favourites ?
5. Compress files or folders and save zip to a saved favourites without leaving working directory.
6. Load apk icons maybe; easier to find things sometimes.
7. Show favourites picker on program startup. I'm always working in the same directories.
A built in text editor with line numbers would be awesome. Maybe an sqlite editor addon too ?
I like what this looks like so far; I really like that you can see symlinks, the dropdown with recent paths, nandroid dumps of any partitions (nice), and the favorites are cool. Just hoping it can take over for root explorer.
Keep up the great work so far. Will be keeping on eye on this for sure.
Thanks for your report
First, i dont want to copy Root Explorer or all these slow and "3 lines" explorers... So no image/movies preview... This tool is focused on system files exploration
Apk icons maybe but not in my prority (filter by name is nice), line size : not for the moment (maybe a zoom or something later)
The multiselect on click is almost ready (for files), to keep folder navigation
the Mount/Unmount will be in tools menu later (in mounted devices menu) i need to make a new window for that... but that need work (and could make lot of reports from unknown devices, like chinese ones)
Compression.... yea hmm v2.0
Hm. I tried this, but it is a lot slower than Root Explorer. Perhaps this is because it shows a lot more objects, or due to it having a lot of features I do not directly associate with a program to manage files. Still, I can not say that having more competition is a bad thing, so keep up the good work
its because the tool use a terminal process to list folders, and a new one on each refresh... I think i can optimize that if i keep the shell process opened.
but Root enabled, its 5x slower (220ms instead of 40ms)... i think there could be a problem with superuser tool, will try to uninstall it to check...
johnw.xda said:
Do you know, how to dump and remount the rootfs?
Thank you.
Click to expand...
Click to collapse
to remount In fact like others :
Code:
mount -o rw,remount,relatime -t rootfs rootfs /
This feature will be available in some minutes (v1.3.0)
But to dump... you need to skip /proc /tmp and /sys
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Its the next step yaffs extraction...
sorry, not for the moment (but soon)
just made an update v1.3.2 which really enhance exploration speed...
I hope you release it soon
Thanks
I can't Dump Partition. A circular thing shows up then it disapear and no text saying records in+out and that it finished (like in the screenshot). And there is no file on my SD card and yes I have plenty of space.
Tried several of the small 512k partitions and the Boot and Recovery partitions.
I'm running rooted froyo 3.4.2-155, few bloat APK's removed.
this feature uses busybox "dd" applet, try to set another busybox in setting window
you can search for them in other apps, do a search in /data/data/
Namiga said:
Hi.
I´m using your app in a Samsung galaxy S.
I lost one file and I want to recover it from a CWM backup.
Your app lets me read the backup, but I cant save the needed file ...
Is there a possibility to extract it from the backup?
Thanks in advance
Click to expand...
Click to collapse
Done... in v1.5.0 Single file or Folder for the moment... (file/folder context menu)
full extraction will be possible in next version... not linked
I've done tons of research... I just can't seem to get cm7 on my phone. I have rom manager and bootstrap recovery already... but I can't for the life of me get the proper files onto my sd card in the right spot (I have no idea what it means when they say put it to the "root" of the sd card).... and plus, the files I'm downloading such as cm7 itself and gapps don't even appear to be .zip when i download them... isn't that what I want it to be? (I use WinRAR by the way.. not sure if that makes a difference) but ive tried over and over again to extract the files i download onto the sd card (again, no clue where on it but ive tried many different locations) and I never get a cm7 .zip, all i get is some META-INF folder and stuff... so when i put the phone into recovery i dont know what to use!!!! im sooooo confused, please help! my phone is a droid x2 and yes, it is rooted. Thanks!!!
Moved to General Q&A.
Johnnymaaaac said:
I've done tons of research... I just can't seem to get cm7 on my phone. I have rom manager and bootstrap recovery already... but I can't for the life of me get the proper files onto my sd card in the right spot (I have no idea what it means when they say put it to the "root" of the sd card).... and plus, the files I'm downloading such as cm7 itself and gapps don't even appear to be .zip when i download them... isn't that what I want it to be? (I use WinRAR by the way.. not sure if that makes a difference) but ive tried over and over again to extract the files i download onto the sd card (again, no clue where on it but ive tried many different locations) and I never get a cm7 .zip, all i get is some META-INF folder and stuff... so when i put the phone into recovery i dont know what to use!!!! im sooooo confused, please help! my phone is a droid x2 and yes, it is rooted. Thanks!!!
Click to expand...
Click to collapse
I believe when they say put it in the "root of the SD card" it means don't put it in any folder on your SD card. So you know how right when you plug in your card a window pops up to the main directory? Open that and put the files there. Like for instance in this image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you see all the folders and stuff on your removable storage, put the file here in this directory.
You aren't suppose to unzip those files at all (I did the same mistake too when I first started flashing lol). You suppose to leave them in the zip form, put them in the main directory hopefully they should pop up. If all else fails ask the developer personally and what you're doing wrong, and give clear instruction on what you did. Hope this helps
Johnnymaaaac said:
I've done tons of research... I just can't seem to get cm7 on my phone. I have rom manager and bootstrap recovery already... but I can't for the life of me get the proper files onto my sd card in the right spot (I have no idea what it means when they say put it to the "root" of the sd card).... and plus, the files I'm downloading such as cm7 itself and gapps don't even appear to be .zip when i download them... isn't that what I want it to be? (I use WinRAR by the way.. not sure if that makes a difference) but ive tried over and over again to extract the files i download onto the sd card (again, no clue where on it but ive tried many different locations) and I never get a cm7 .zip, all i get is some META-INF folder and stuff... so when i put the phone into recovery i dont know what to use!!!! im sooooo confused, please help! my phone is a droid x2 and yes, it is rooted. Thanks!!!
Click to expand...
Click to collapse
It means to simply place the file on your SD card (not in any folder). They need to be .zip files. If you have a different file extension, just change it to ".zip". Never extract the ROMs when sending them to be flashed. Only do that if you know what you're doing (e.g. removing apps to free up space, etc.).
This guy needs to learn A LOT before flashing a ROM. If he doesn't even know what the root of the SD card is, he has no business in rooting an Android device.
Sent from my MB508 using xda premium
be careful bro!, you might end up bricking your phone!, read more!
bro try to have a clear idea before go for flashing...this l help you to produce some confidence on you.:good::good::good::good::good::good:
1. Paste the zip file of the ROM in the root folder of your SD card
2. Boot into Clockword Mod
3. Select install from zip
4. It should be done in 2 minutes.
If you don't have Clockwork Mod installed, follow a flashboot or fastboot guide. The Cyanogenmod wiki is quite good at this.
Johnnymaaaac said:
the files I'm downloading such as cm7 itself and gapps don't even appear to be .zip when i download them... isn't that what I want it to be?
Click to expand...
Click to collapse
Please link us to these files. Also, link us to the threads you're getting it from.
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, it doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and if I find I have a bad nvflash blob file).
For other's info, I'd originally asked about re-running the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set. In preparation for recreating one, I moved the /sdcard/AndroidRoot folder to another location. I happened to reboot and noticed the AndroidRoot folder and its contents are automatically recreated upon rebooting. So for these files, there's no need to re-run the fastboot command for another set.
I did notice one "issue" viewing the /sdcard/AndroidRoot folder in Windows 7 after the initial reboot. While they display fine via my TF300T's File Manager, it took either disconnecting/reconnecting my usb cable or rebooting one more time for them to display correctly in Windows 7.
I still plan on re-running nvflash to create a new bricksafe.img, factory-config.img, and unlock-token.img set just to be extra safe.
wha2do said:
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and I find I have a bad nvflash blob file).
Can I rerun the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set? While I'm at it, I figure I should be able to rerun nvflash and create a new bricksafe.img, factory-config.img, and unlock-token.img... Is that possible and does it make sense?
Thanks!
Click to expand...
Click to collapse
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
Thanks for the confirmation. I dislike relying on an unverified backup only to find out too late that it's not valid or usable! And out of curiosity, you went through a recovery successfully? It'd be great if you had a link to the thread/post you followed.
I had missed one step after upgrading the jb bootloader (didnt force shutdown after upgrade, just let it load) and were stuck with official jb with no root or recovery, so i tried to use nv flash and messed up even more , post 3 in this thread helped me get the bootloader to work so I cound install TWRP again using fastboot.
I do not recommend testing it "just for fun" but it worked for me. Search for "nvflash restore" if you have any problems.
totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
I'm curious about your sizes matching mine; more specifically my unlock-token.img file size matching yours. Maybe fine if you used your unlock-token.img file when you did your recovery. If didn't use, might want to (if you still can) go back and recreate it and compare with your original...see below why.
Being OCD on backups, I created a new bricksafe.img, factory-config.img, and unlock-token.img and compared the files. I was a bit surprised to see factory-config.img and unlock-token.img were not exact copies of the original set created. Factory-config.img had some bits that varied, but was mostly the same. I'm figuring it's something "internal" as I haven't changed anything on my table between runs and is fine...
But seeing a large size change between the two unlock-token.img files, I went back through my logs, etc. Lo and behold, I had a typo and hadn't changed the partition from 14 to 7! So I had made duplicate backups of the factory-config partition by accident. The actual file size is 8,192 KB and not 5,120 KB.
That could have been a real problem down the road if ever I need to recover (assuming this file is vital to the particular recovery procedure). So if nothing else...the lesson to learn is always double check what you've done to make sure!