Yes i know the fastboot trick, but can anyone guide me towards making the nandroid backup files into a update.zip that would work?
I'd like to know too ^^.
Me too.
I've successfully scripted the automated creation of a file structure into which the contents of BOOT.IMG, SYSTEM.IMG, DATA.IMG, CACHE.IMG and SD-EXT.IMG are extracted. The script also creates a valid update-script file under ./META-DATA/....
The only issue I have is that I'm using windows so the .IMG files extracted as a yaffs file system, looses the original file permissions. I need someway to recreate the permissions in the update.zip.
Thats all.
Having a way of converting a nandroid backup to an update.zip means you can very easily cook custom roms from a nandroid backup, and port ROMs across phones using a portable .ZIP format.
Maybe dsixda can help
http://forum.xda-developers.com/showthread.php?t=633246
"OR [cook a rom] from a Nandroid backup (under /sdcard/nandroid) [NOT RECOMMENDED]:
Copy the system.img and boot.img files from the backup folder to your kitchen's original_update folder
NOTE: The Nandroid-backup method of cooking is not the best way to cook, because the kitchen may not account for various advanced options that were cooked outside of this kitchen (these options are in the update-script file which was in the original ROM but is not in the backup. The kitchen needs to re-create this file and 'guess' those options). However, it will support Nandroid backups that already have basic features like root, busybox and /data/app functionality. "
You get nandroid backup images by backing up a ROM which was flashed from an update.zip package. What is then the point of recreating that update.zip package?
giant is right with the klitchen by dsixda you can make an update.zip form nandroid very easy
Guys, we're missing the point.
To clarify:
The "point of recreating the ZIP ROM file" are numerous. For example, to create a ROM where the original ROM isnt available, i.e. to create a portable ROM based on an existing set of images in a phone where the phone and/or its sdcard cannot be removed or where we do not wish to remove the card. Simple. But more importantly, the process is a learning and development activity that I want to undertake, its a personal decision, for which support would be welcome.
Secondly, dsixda issues many caveats around cooking ROMs from nadroid backups. It simply doesnt work - I've tried it - thus his caveat is correct and should be observed. Furthermore, his kitchen creates windows based ZIP files. The process is inherently flawed for creating ROMs for linux because the ZIP files contain a windows file structure which does not contain the appropriate linux based file permissions (linux being the O/S base system on android. The restore operation does not work - in stock form - because one looses the critical file permissions, UID and GID that are required in order for the ROM to function correctly, and in some instances from my experience, to even boot up! His update-script attempts to reinstate the appropriate permissions, UID and GIDs, however, and as dsixda admits, the process is not foolproof and does not cover all eventualities, combinations and scenarios. Thus, the issue of permissions, GID and UID remains outstanding.
For these reasons, in my humble view, the issue of permissions is critical in ensuring a successful ROM flash from [linux based] .IMG files. Once this is resolved, the rest of the process is trivial. Indeed, if this one issue could be resolved, then dsixda's kitchen would mature from a useful toolset, to a truly wonderous one-stop solution.
well i don't know what people have tried and got to work or not, but it can eb done and have been done before, one of my sliderom build was done froma nandroid
soo i guess it's up to how much effort you put into it and use the kitchen as a tool, but not only use it, cause then you fail, if you don't do some manual work, nothing 100% automated will ever be a big succes
I have a solution.
I am coding this up as we speak.
My solution will extract the file permission, UID and GID from the .IMG , for each contained file. My script then runs as part of the update-script (i.e. RUN_PROGRAM restore-protection) subsequent to a ROM flash. Thus, the resultant file structure after a ROM update is exactly the same as that contained within the .IMG files.
EDIT:
coding complete.
will test tomorrow on existing phone + sdcard.
The purpose of this exercise is to 'clone' an existing phone software load, as ROM file, that can then be flashed. My script takes all partition images (system, data, cache, sd-ext and so on), creates a ROM that includes functionality that will - when flashing - restore the exact permissions, GID and UID as written in the backup files (.IMG), thus cloning the phone.
I plan to update the script in future so that APK files can be added or removed, and additional low level features such as kernel pre-empting, scheduling and other features can be added --- I think they call this "a kitchen" in Android speak.??
From your description of what you're doing it sounds like you could end up with the simplest and closest to a one click kitchen that allows users with less knowledge to fully backup / restore / clone their phone (rom, personal settings, data and all). A lot of noobs might like this tool big time
Any progess made on this? I have been trying to create a rom for a nandroid backup. When I go to flash it, I get symlink errors and the flash fails.
dazxda said:
I have a solution.
I am coding this up as we speak.
My solution will extract the file permission, UID and GID from the .IMG , for each contained file. My script then runs as part of the update-script (i.e. RUN_PROGRAM restore-protection) subsequent to a ROM flash. Thus, the resultant file structure after a ROM update is exactly the same as that contained within the .IMG files.
EDIT:
coding complete.
will test tomorrow on existing phone + sdcard.
The purpose of this exercise is to 'clone' an existing phone software load, as ROM file, that can then be flashed. My script takes all partition images (system, data, cache, sd-ext and so on), creates a ROM that includes functionality that will - when flashing - restore the exact permissions, GID and UID as written in the backup files (.IMG), thus cloning the phone.
I plan to update the script in future so that APK files can be added or removed, and additional low level features such as kernel pre-empting, scheduling and other features can be added --- I think they call this "a kitchen" in Android speak.??
Click to expand...
Click to collapse
Do you have a link?
dazxda said:
I have a solution.
I am coding this up as we speak.
My solution will extract the file permission, UID and GID from the .IMG , for each contained file. My script then runs as part of the update-script (i.e. RUN_PROGRAM restore-protection) subsequent to a ROM flash. Thus, the resultant file structure after a ROM update is exactly the same as that contained within the .IMG files.
EDIT:
coding complete.
will test tomorrow on existing phone + sdcard.
The purpose of this exercise is to 'clone' an existing phone software load, as ROM file, that can then be flashed. My script takes all partition images (system, data, cache, sd-ext and so on), creates a ROM that includes functionality that will - when flashing - restore the exact permissions, GID and UID as written in the backup files (.IMG), thus cloning the phone.
I plan to update the script in future so that APK files can be added or removed, and additional low level features such as kernel pre-empting, scheduling and other features can be added --- I think they call this "a kitchen" in Android speak.??
Click to expand...
Click to collapse
Hi, could yo share your script? I'm also working on something similar, and could use a bit of help
OMG this is exactly what I need.. I read all the way to the end and then ARRGGGGGG.. no more responses in months. Have you made this script yet? If no .. does anyone else have instructions on taking a nandroid backup and creating an IMG or ?
My personal reasons.. I have a Craig CMP741E tablet that is stuck in the android logo screen after attempting the factory update.. the one that crashes EVERY1's tablet. And there is no working way that I have found to fix it. No custom roms or factory roms that can be flashed without FIRST having the tablet ON and turn on USB Debugging or already have CWM installed. So I cannot use ADB or any other method I can find to do this.
I have a buddy with the same tablet that is rooted and has GAPPS and everything on it. He gave me a copy of his nandroid backup but now I cannot find anything I can actually do with it. If I can turn it into an Update.zip or IMG I can simply put on SD Card.. restart and cross my fingers.
lilc420 said:
OMG this is exactly what I need.. I read all the way to the end and then ARRGGGGGG.. no more responses in months. Have you made this script yet? If no .. does anyone else have instructions on taking a nandroid backup and creating an IMG or ?
My personal reasons.. I have a Craig CMP741E tablet that is stuck in the android logo screen after attempting the factory update.. the one that crashes EVERY1's tablet. And there is no working way that I have found to fix it. No custom roms or factory roms that can be flashed without FIRST having the tablet ON and turn on USB Debugging or already have CWM installed. So I cannot use ADB or any other method I can find to do this.
I have a buddy with the same tablet that is rooted and has GAPPS and everything on it. He gave me a copy of his nandroid backup but now I cannot find anything I can actually do with it. If I can turn it into an Update.zip or IMG I can simply put on SD Card.. restart and cross my fingers.
Click to expand...
Click to collapse
Can you access the tablet's fastboot mode? Turn the tablet fully off, then hold the Menu button and the Power button. I don't have your tablet, but it's a standard boot mode.
Make sure you have the tablet connected to the PC. You should see it pop up in the Device Manager, or by doing "fastboot devices" from a command prompt.
If you can get there, you may be able to flash a recovery image.
Hi, does anybody knows if there is a response for this post??, i am looking for a method to convert the images files that are included in a rom stock (for using with sp flash tool) to an update.zip file. I have no way to use sp flash tool because my tablet has a hardware problem with microusb port and the only way is flashing a new rom via microSD card with an update.zip..
Maybe the solution is in another thread, please be kind and give me a link or at least give me some suggestions where to look for.
I have been running roto backups for a while now, but have never had the need to restore from one. While looking through the different files that were backed up after I ran the command code, I noticed a file called data.tar.gz. Where is the correct place for selecting this file in Heimdall when doing a restore? For example, do I put it in the recovery slot under other, or does it not matter where I put this file performing a restore?
Also, I found a file called efs.rfs that was backed up and I have the same question for that file.
Thanks in advance for any advice,
caveman999
caveman999 said:
I have been running roto backups for a while now, but have never had the need to restore from one. While looking through the different files that were backed up after I ran the command code, I noticed a file called data.tar.gz. Where is the correct place for selecting this file in Heimdall when doing a restore? For example, do I put it in the recovery slot under other, or does it not matter where I put this file performing a restore?
Also, I found a file called efs.rfs that was backed up and I have the same question for that file.
Thanks in advance for any advice,
caveman999
Click to expand...
Click to collapse
By just taking a look at how data.tar.gz is created it looks as though you could just copy it to your phones sd card and extract it to /data.
Heimdall does support efs.rfs, however it's intentionally not included in the user interface. The efs partition includes a lot of phone specific data, which depending on where you live it might be illegal to tamper with. As a general rule you shouldn't need to flash this file as the phone should retain this information. However, if in the event your efs does become corrupt you can flash the efs partition via the Heimdall command line tool.
Benjamin Dobell said:
By just taking a look at how data.tar.gz is created it looks as though you could just copy it to your phones sd card and extract it to /data.
Heimdall does support efs.rfs, however it's intentionally not included in the user interface. The efs partition includes a lot of phone specific data, which depending on where you live it might be illegal to tamper with. As a general rule you shouldn't need to flash this file as the phone should retain this information. However, if in the event your efs does become corrupt you can flash the efs partition via the Heimdall command line tool.
Click to expand...
Click to collapse
Thanks for the detailed response.
What program would you recommend to extract the data file? Would root explorer be suitable?
Thanks
Sent from my AT&T Galaxy Tab using XDA App
Hi everyone
I've got a few questions about flashing an Android phone. I've tried going through KIES but unfortunately they don't have any updates for the below mentioned model.
I've got an GT-I5800XXXMST (Belgium telecom model) that I want to flash using Odin. I want to use the following image: I5800XWJPE.tar
1. Do I need to remove the sbl.bin, boot.bin and logo.png to play it safe? In that in that case I always retain the ability to flash
2. Do I need to edit the OPS file and remove the above mentioned entries?
3. Which OPS file should/can I use? Are they all the same for the I5800? (apollo_0531.ops)
4. Which version of ODIN do I need to use? I currently have I5800_Odin_Multi_Downloader_v4.252.exe
5. Do I need to backup my EMEI?
6. Simple and plain backup tool for upping my current os?
7. Any tips?
Many thanks all,
Tempert
tempert said:
Hi everyone
I've got a few questions about flashing an Android phone. I've tried going through KIES but unfortunately they don't have any updates for the below mentioned model.
I've got an GT-I5800XXXMST (Belgium telecom model) that I want to flash using Odin. I want to use the following image: I5800XWJPE.tar
1. Do I need to remove the sbl.bin, boot.bin and logo.png to play it safe? In that in that case I always retain the ability to flash
2. Do I need to edit the OPS file and remove the above mentioned entries?
3. Which OPS file should/can I use? Are they all the same for the I5800? (apollo_0531.ops)
4. Which version of ODIN do I need to use? I currently have I5800_Odin_Multi_Downloader_v4.252.exe
5. Do I need to backup my EMEI?
6. Simple and plain backup tool for upping my current os?
7. Any tips?
Many thanks all,
Tempert
Click to expand...
Click to collapse
1) Yes removing boot.bin and sbl.bin would be safe.
2) No need to edit ops or anything.
3) Ops is same for all ROMS(i.e. apollo_0531.ops).
4) The ODIN version that you have mentioned is the correct version. Use that.
5) Yes. Backing up IMEI would be good. For tutorial click here.
6) Use titanium backup to backup apps.
1. yes, but you can download romfiles without those files in the forums
2. no, you just remove them from the tar archive
3. all the same
4. that's the one
5. better be safe, but I haven't had a problem with it
6. Alexgalaxy's backup script
7. read and search the forum
Go for jpn or jpm . Yes you have to remove the files to avoid hardbrick. Dont worry its been done by dharamg3
use this link:
http://forum.xda-developers.com/showthread.php?t=1125387
After downloading from the above thread thread
Just use apollo_0531.ops for flashing using the odin that you have
Yes it is recommended to backup your IMEI
Use this thread for backup and restore of IMEI
http://forum.xda-developers.com/showthread.php?t=888193
The IMEI is stored in a partition called efs
And root your phone before you backup
Many thanks all!!
Verry clear answers
Running 2.2 happily
Yesss!
Any luck with the backup of your original firmware ? Could you share the factoryfs.rfs ?
I have tried to backup my phone with that Alexscript. Although It gave some errors about not finding some directories...
Will the factoryfs.rfs contain personal data?
No, it's your system partition; personal info is stored in the data partition. You have root and your sdcard is big enough for the backup (500MB free should do it) ?
But if you have already flashed another rom, there's obviously no need. I thought about having an original "Orange" rom for when I need to use warranty on my phone.
It's a Mobistar rom. I think I have it but the .tar file was only 200Mb big if I remember correctly. I will try an upload it if I have the time.
Hmm, yeah, I meant Mobistar obviously.
Sounds about right. You can zip it again to save a lot of space.
I currenty running Thor rom 14.2 and i want to return to stock 3.1.
I have a nandroid backup but accidentally i deleted .txt files inside.
Could i restore it or my tablet will brick
anyone??
First of all: Remember xda-developers is quite international so the person with the answer to your question may be asleep or working at the time you post...
Other than that: If you deleted part of your backup that's bad. You may get away with a partial (possibly non-functional) restore, or restore may fail altogether... Both shouldn't brick your tab, but you might have to do a full wipe and configure your rom from scratch; it may well be worth trying a restore, though, as you won't be causing any more damage anyway if your tab doesn't work anymore. Just make another nandroid backup in case you decide things were better before you hit the restore button... As long as you don't accidentally kill your recovery, android devices are incredibly hard to brick.
jimmis1996 said:
I have a nandroid backup but accidentally i deleted .txt files inside.
Could i restore it or my tablet will brick
Click to expand...
Click to collapse
I just checked a number of nandroid backups of mine and the only ".txt" file that I could see was uid.txt in the main backup directory that contained the ".img", ".tar", and ".md5" files.
You could just run another nandroid BU of your current system and copy over the uid.txt file from that one to replace the one that you deleted. The uid.txt file should be the same from one BU to the next.
Jeff.
Thanks
Thanks for your help
So if i create a .txt file with my id number my restore will work?
Is there another way to restore to stock.
jimmis1996 said:
Thanks for your help
So if i create a .txt file with my id number my restore will work?
Is there another way to restore to stock.
Click to expand...
Click to collapse
If you just put a text file with some random information in it, it may not work right.
Here is the procedure that was suggested:
Make a backup of your current settings
make a copy of the text file in that most recent backup
place that copied text file in the backup with the missing text file
try to restore the backup that was missing the text file, which you just copied the text file to
Psichi said:
If you just put a text file with some random information in it, it may not work right.
Here is the procedure that was suggested:
Make a backup of your current settings
make a copy of the text file in that most recent backup
place that copied text file in the backup with the missing text file
try to restore the backup that was missing the text file, which you just copied the text file to
Click to expand...
Click to collapse
I will try it.
I remember when i downgraded to 3.0 from 3.2 i use something called APX mode could this restore my tab to full stock
problem solved
ok backup my rom copy uid file and everything is ok.thanks