Related
Hey guys,
Does anybody know what commands the ClockWorkMod recovery uses to generate backup images? Like when you browse to your /mnt/sdcard/Clockworkmod/backups/ directory and see your *.img files, what command is used to generate that file? I know in linux you can use dd and cat (block partition) > *.img and that would generate it, but i want to know the exact command used by ClockWorkMod recovery.
Thanks all for your time!
ANSWER: mkyaffs2image
Bumpy bump bump bump :/
HELOO!?!?!?!?!!??
I take it you're looking to replicate the functionality of the nandroid backup? If so this thread contains a script to do so.
If you want to find out for some other reason, I suggest you examine the script and/or CWM source files.
Bloved said:
I take it you're looking to replicate the functionality of the nandroid backup? If so this thread contains a script to do so.
If you want to find out for some other reason, I suggest you examine the script and/or CWM source files.
Click to expand...
Click to collapse
THANK YOU VERY MUCH FOUND MY ANSER
mkyaffs2image is the command used to generate an image file from your partitions thanks! no i can make my app
Hi all, researcher and enthusiast,
I own a complete backup of all partition of the LG P990 with stock ICS, made it with nvflash with a command like this,
Code:
nvflash -r -read <-partition number-> my_partition.img
for all the partition listed in the partition table.
I guess that in someone of that raw image file, (outputted by nvflash), is located the entry system partition, (PartitionId=23 for the LG P990 ICS partition layout).
It's easy for every linux user to mount the raw image file, simply with 'mount' utility.
Browsing them we can find as already hypothesized the entrie android system partition!
If I copying in it the 'su' executable compiled for my platform, it could work?
Yes. Simple as that. Just be careful with permissions.
There's a topic I made on the ancient v28g time with stock v28g rooted system, on dev section. There you'll find useful info.
Do not say "thanks"; just press it under here.
louiscypherbr said:
Yes. Simple as that. Just be careful with permissions.
There's a topic I made on the ancient v28g time with stock v28g rooted system, on dev section. There you'll find useful info.
Do not say "thanks"; just press it under here.
Click to expand...
Click to collapse
Thanks! I'll have a close look to your work now, for others that consider this stuff interesting, louiscypherbr's work is here:
http://forum.xda-developers.com/showthread.php?t=2010671
Nice job!
louiscypherbr said:
Yes. Simple as that. Just be careful with permissions.
Click to expand...
Click to collapse
Ok louis, but the partition23 image file after adding su binary or other things is bigger than the previous that we had read with nvflash, right?
If I flash back it with
--bl fastboot.bin --download 23 image.img
how can this work..?
In the part table is write that have been reserved 536.870.912 bytes for the partiton 23, but we want flash an img file bigger than that size (because we added some stuff), this not causes problem?
And what do you mean for careful?
The extracted file is a dd partition image, meaning it's extracted byte by byte. So it includes the empty space, which you can see with "df" command after mounting it.
You can add files that fit in that position and it will be ok when flashed.
Do not say "thanks"; just press it under here.
Stupid thing! You're right!
And, what you mean for careful with perm?
The su binary should be have the setuid bit set in addition to the obvious x, is this enough?
Have you compiled su by yourself...?
louiscypherbr said:
There's a topic I made on the ancient v28g time with stock v28g rooted system, on dev section. There you'll find useful info.
Click to expand...
Click to collapse
Where have you found the executable of su packed in your v28g louis...???
Hey, sorry for being far from this.
What I was talking about permissions is that you should keep su permissions/owner. I did this just copying the su from a rooted Rom zip to /system/xbin and pasting inside your loop mounted /system with file manager (I'm kde fan, so I used dolphin, the kde graphical file manager, but you can use any other as well).
Sent from my LG-P990 using xda app-developers app
Hello,
I installed last week this version of android on my G9, all was fine until today when my tablet ran out of battery, I plugged it and start it again as I always do in that case. Except that today android didn't start and I got the multiboot screen which you can see in attached files. I tried both options but my tablet always restart on that screen.
When my tablet is plugged into my computer it is not recognized so I can't put a new ROM of android and make a new installation, I tried to use ADB to debug it but there are no device detected ...
Does someone have a solution to my problem ?
Thanks in advance for your answers.
Olorin59.
PS: sorry if there are language mistakes in what I wrote but i'm French so English is not my birth language.
You have 2 options right now. You can either just install stock ROM, or if you have Linux in you computer you can use sde to mount data partition to your PC and moving the ROM again in there.
Installing stock ROM is easier and faster, so I recommend doing that. You remember how it goes? Download latest firmware from achos' site an use firmware update option located in sde.
Sent from my GT-I9100 using xda app-developers app
I think I already tried that : download the aos file from the official site of archos, go in recovery mode, chose upgrade firmware and copy the aos file to the drive which appears on my computer then chose ok ???
If it is that I tried and I got an error message "update failled : 221".
So if it is that could you explain me more how to do it with linux, i'm not sure I understood everything.
olorin59 said:
I think I already tried that : download the aos file from the official site of archos, go in recovery mode, chose upgrade firmware and copy the aos file to the drive which appears on my computer then chose ok ???
If it is that I tried and I got an error message "update failled : 221".
So if it is that could you explain me more how to do it with linux, i'm not sure I understood everything.
Click to expand...
Click to collapse
Okay.
That 221 sounds weird.
After booting in to Linux (livecd is sufficient, I recommend Ubuntu or variant of it), open the sde in archos and navigate to data mount option. I can't remember what it is called, but should be something like mount data partition. Then plug your tablet to PC running Linux, and the PC should find the tablet.
You should now be able to browse data on /data partition of the tablet, but writing there requires you to use superuser.
Check the path to data partition. If I remember correctly, it will be something like /media/(device name)/ but I'm not sure.
Navigate to archos.etx4.update file and use this command to move it:
sudo mv archos.ext4.update path-to-data/media/archos.ext4
If /media/path-to-data/media won't work, try using /media/path-to-data/local
Sent from my GT-I9100 using xda app-developers app
I don't have mount data partition but I do have "export data partition" and "export hard disk (H models only)" in the developer edition menu, is it what you are talking about ?
olorin59 said:
I don't have mount data partition but I do have "export data partition" and "export hard disk (H models only)" in the developer edition menu, is it what you are talking about ?
Click to expand...
Click to collapse
Yeah, that is the one: export data partition
Sent from my GT-I9100 using xda app-developers app
When I plugged my tablet, ubuntu told that I do not have the authorisation to see the content of the drive ...
Can't I do the same with windows ?
olorin59 said:
When I plugged my tablet, ubuntu told that I do not have the authorisation to see the content of the drive ...
Can't I do the same with windows ?
Click to expand...
Click to collapse
HMM.. That sounds weird, as I do not have that problem. Can you try other Linux? I think backtrack allows you to login as root, so you are able to do anything...
The filesystem of data partition is ext4 I guess... Or ext3. Windows can not read ext filesystem, so you can't use windows.
Sent from my GT-I9100 using xda app-developers app
Ok I'll try an other version of linux, backtrack is downloading as i'm writing this. I'll get back to you soon.
Hi julle131, I'm currently using backtrack which as you told allows me without problems to access the data on the tablet.
I'm a little bit lost about what's next to do.
The tablet appears as a drive called "data" in which there a is folder called media as you said, inside it there are a lot of folders for various apps I had installed. If I understood correctly the goal is to find the archos.ext4 file but I can't find it ...
Can I download the archos.ext4 file and put it again on the memory of my tablet to re-install it ?
olorin59 said:
Can I download the archos.ext4 file and put it again on the memory of my tablet to re-install it ?
Click to expand...
Click to collapse
Yes you can.
Hopefylly after downloading archos.ext4, your tablet will hopefully work normally again :thumbup:
Sent from my GT-I9100 using xda app-developers app
So, I copied archos.ext4 to in the media folder of the tablet then in recovery mode, I flashed kernel and initramfs but after that my tablet don't reboot, it don't have the multi boot menu or anything and when I press the start button nothing happens I can only access the recovery menu. Do you have any idea ?
olorin59 said:
So, I copied archos.ext4 to in the media folder of the tablet then in recovery mode, I flashed kernel and initramfs but after that my tablet don't reboot, it don't have the multi boot menu or anything and when I press the start button nothing happens I can only access the recovery menu. Do you have any idea ?
Click to expand...
Click to collapse
The initramfs you flashed probably does not have multiboot menu. Keep the zImage from the rom you downloaded and get initramfs from this link:
http://forum.xda-developers.com/showthread.php?t=1578438
when you download the zip, only extract the initramfs.
Then install zImage from the original rom and initramfs from the multiboot menu thread. That should bring the multiboot menu back, and hopefully you can see the new archos.ext4 in there.
I just tried : Kernel (zImage) not found !
olorin59 said:
I just tried : Kernel (zImage) not found !
Click to expand...
Click to collapse
What i meant was to take the zImage from the rom you downloaded and initramfs from my link, and install them both.
Make a new folder to the desktop, and extract initramfs from the link i gave you in earlier post.
Now you have a new folder with initramfs inside it. Then put the zImage from the rom you downloaded to the folder.
Now you should have a folder which has initramfs AND zImage, right? Then just install them to the tablet. This way you get the multiboot and the new kernel.
It's what I did.
I chose flash kernel and Initramfs in the recovery menu and I paste inside the ramdisk the initramfs from your link and the zImage from my ROM.
I tried both version of the initramfs from the link you gave me.
Any idea, please ?
I'm still stuck on the multi boot menu ...
Can someone help me please ?
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
looking for the same
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
me too looking for the same thing ..how to extract from or decompile .backup file which we get thru recovery.
hi loverboyritesh :: i and you are in same position.. but some advaaanced users are here that we are telling rumors and lies.. dont worry bro.. even i'm trying to get solution.. will tel you after geeing one.. Still no one can tell me hoe to extract .BACKUP file..
same
i am looking for how to reinstall .backup myself so i can have my original rom install.
but i have notice my .backup is 700+mb while custom rom is 200+mb
do you know how to?
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
same here. dunno how to open and extract the files from a .backup file. hoping you know already
siiingkeeet said:
same here. dunno how to open and extract the files from a .backup file. hoping you know already
Click to expand...
Click to collapse
Nope.. Still i'm having that file but no one knew
reena0307 said:
Nope.. Still i'm having that file but no one knew
Click to expand...
Click to collapse
been searching for 5 days now :<
not a single answer found on google and forums
cant even post a new thread yet. just joined
hope someone will drop by this thread
still no solution?
got same problem here
Got a bootloop issue with an ASUS MeMo Pad 7 HD and I've booted in recovery <3e> to make a backup.
I've got a userdata_YYYYMMDD_HHMMSS.backup. I tried opening it with a bunch of tools like unyaffs, abe (Android backup extractor), going live on the file using linux tools (open as 7zip, zip, rar, tar, tar.gz, gz, bz2 , mount as iso, ext4 and so on....)
Still no luck :-/
Only clue is that the file seems compressed. During the backup under recovery, it told me 3600MB to backup and the file userdata_xxxxxxxx_xxxxxx.backup show only 2.61GB
I did this backup 3 time to ensure there were no corruption during the write process from the pad and did again the same "tests" to open the file...Not better.
If any dev' have any clue of the file format, I'd be glad to help
It doesn't seem to be a valid unix img file. Tried mounting it to no avail. When it's restored by the recovery it also extracts the individual files because i fails on one in my case and stops the entire restore... I tried unzipping it, changed extension to ,jar, .tar, .zip, etc., none of them are recognised...amazing for a standard android feature to find so little info about it
Any solution?
I called Alcatel's technical service today and they told me that you can use the backup file only from the phone. Mine gives me the following error when I try to restore it: Error Magic header
If anyone knows how to unpack the backup file I would be more than grateful.
It's a 512 byte header in front of a "tar.gz"
hexdump -C userdata_xxxxxxxx_yyyyyy.backup | less​showed the magical zip header "1f8b0800 00000000" at offset 0x200
So, skipping 512 bytes, the rest can be gunzip | tar
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv​
Sir ektoric what d u mean on ur post?
Sorry cant understand it..
Can u please d a step by step procedure? Please...pls...plss
Thanks in advance...
Steps?
@ektoric sir im a noob in this... Can u show a step by step procedure?
@killen00 sorry, I assume you have a linux machine (or have access to one). The command is actually all there is to it.
Code:
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
If you don't have a linux machine available, might I suggest one of the many distros of your choice, most of which have LiveCDs which you can run without installing.
script for gunzip method
maybe on xda it is common sense, but for me it was necessary to know, that these stock android recovery extracted files can be restored with nandroid custom recovery, if you simply repack them into tar archive.
i put this two command lines in a dirty shell script (extract + repack as tar).
thanks to ektoric figuring out his gunzip method!
edit: notamamasboy's mount method added (but not tested yet). if script not works come back few days later, download again and check version, maybe it has changed meanwhile.
with this you're able to transfer data of non-rooted phone to (rooted) similar one.
this is useful in case touchscreen is broken, you haven't custom recovery installed, usb-debugging is disabled and connecting usb-otg-mouse doesn't work.
tested on my Archos 50 b Oxygen (Mediatek MT6582).
it works for me, feel free to improve, port to busybox and publish. no support. use at own risk.
edit: bckp2cwm.sh is deprecated it is FOR JELLY BEAN ONLY (no selinux support)
a newer (selinux) version bckp2win.sh for TWRP you can find here:
http://forum.xda-developers.com/showthread.php?t=3775129
How did you go about determining the magic number found at 0x200? My hexdump output does not have that magic number (1f 8b) in any instance. Leads me to believe my backup is not a tar file. Any suggestions then?
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
ektoric said:
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
Click to expand...
Click to collapse
Even more peculiarly, two backups were created a .backup and a .backup2, I wonder if combining with cat I can get somewhere...
So I was trying to package a rom and let the kitchen create the meta-inf folder along with the updater-script but the problem is that it's not using the specified mount points.
My phone isn't supported in the kitchen so I had to make a file in the edify_defs folder for my phone. I did all the right steps, I renamed the file to that of the ro.produc.device, used the template and made the necessary edits using notepad ++, and checked the file for any incorrect syntax yet after all that, the kitchen isn't using the mount points I put but instead uses the default value "mount("MTD", "system", "/system")".
Any help?
bump
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
iZLeeP said:
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
Click to expand...
Click to collapse
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
black_fire21 said:
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
Click to expand...
Click to collapse
What's your device and android version? Much better if you could post on your device's specific thread.
It's a local phone called starmobile quest, running jellybean. Sadly, there is absolutely no support for the device not even from the manufacturers. There are no developers either. The only thing we have is root and cwm.