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
I am totally new to flashing. I just backed up my IMEI (created a rfs file using Terminal Emulator and just copied of the efs folder to my sdcard).
My question is that suppose I happen to lose my IMEI on flashing, can I recover it by simply copying the contents of the backed up efs folder to the original folder using root explorer?
yeah, its as simple as that
manish19 said:
I am totally new to flashing. I just backed up my IMEI (created a rfs file using Terminal Emulator and just copied of the efs folder to my sdcard).
My question is that suppose I happen to lose my IMEI on flashing, can I recover it by simply copying the contents of the backed up efs folder to the original folder using root explorer?
Click to expand...
Click to collapse
U can also flash it with Odin even without rooting.
devc0ol said:
U can also flash it with Odin even without rooting.
Click to expand...
Click to collapse
Thanks but I am not sure how I would do that. I went through the IMEI backup and restore thread. So is this what I have to do?
1. Select the .ops file.
2. In the efs section, add the file and not select the one package option.
3. Connect my phone in download mode
4. Flash
Is this method correct?
manish19 said:
Thanks but I am not sure how I would do that. I went through the IMEI backup and restore thread. So is this what I have to do?
1. Select the .ops file.
2. In the efs section, add the file and not select the one package option.
3. Connect my phone in download mode
4. Flash
Is this method correct?
Click to expand...
Click to collapse
Yup thats the way the say it to do.
But i think u have to change the efs folder into a .tar file to flash it.
DO IT AT UR OWN RISK!
manish19 said:
Thanks but I am not sure how I would do that. I went through the IMEI backup and restore thread. So is this what I have to do?
1. Select the .ops file.
2. In the efs section, add the file and not select the one package option.
3. Connect my phone in download mode
4. Flash
Is this method correct?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=888193
Have a look at this Thread also..
Gives the basics of different ways of mounting the efs partion.
Its safe to use the ADB method i guess.
But flashing with efs.tar file should work.
Can someone skilled please explain in detail how to create a non-wipe version of a given stock rom?
I know that the data.img has to be removed from the according .tar.md5 file (see picture), in order to do that you have to open the file with a zip program (remove the .md5 or open it with "open with").
The problem is, after removing the data.img the .tar.md5 file want flash proper with odin. I guess this is due to a wrong md5 sum which was not changed during this process, and therefore is no longer valid!
I remember that I read once that you have to use a specific packer for that (winrar for example is not able to do this), but I cant find this source again!
Can someone please illuminate us in regard to that?
Thank you very much in advance!
ps.:
I posted this in development section because I think this is more development related as Q/A! If this violates the forum rules any mod should feel free to move this thread into Q/A...
You don't have to keep the .md5 extension to flash via odin, and thus skip the md5 checksum check.
But I don't know if it will flash properly after you removed the data.img
I have never tried that. Maybe you still have to modify a script or something...
I thought of using Mobile Odin and not selecting the Code.tar.md5 through the open file dialog, but rather selecting every part to flash individually and NOT selecting anything for data.
Too scared to try...
thanks latoc!
can someone with experience confirm that is it enough to remove the data file from the tar, repack it and don't add .md5?
I tried the mobile odin method and it wiped my phone even though nothing was selected in the data part.
There must be a script somewhere that tells the phone to wipe...
I made a backup before so no problem for me
Sent from my GT-N7000 using XDA App
Use peazip, it can create working tar images that can be flashed. Winrar corrupts tar. Some say 7z also does a good job. I haven't tried it as I was happy with peazip. You can even use gzip. Hope it helps.
You can even extract all the contents, remove add files, then use paezip or gzip to make a tar. Works perfectly. MD5 is not a necessity. If you want, you can create a MD5 hash for the new tar that you have created. Google it. Its easy.
ragin said:
Use peazip, it can create working tar images that can be flashed. Winrar corrupts tar. Some say 7z also does a good job. I haven't tried it as I was happy with peazip. You can even use gzip. Hope it helps.
You can even extract all the contents, remove add files, then use paezip or gzip to make a tar. Works perfectly. MD5 is not a necessity. If you want, you can create a MD5 hash for the new tar that you have created. Google it. Its easy.
Click to expand...
Click to collapse
thanks for the answer!
peazip uses 7zip via console, so its the same!
anyway, the tar from peazip wont flash! odin (1.83 and 1.85) stops with an error (could not write) with the boot.bin (from my modified tar), after that the phone wont boot and give the message: firmware update failed, use kies recovery mode blabla
only way to get it back to life without kies is to flash a proper boot.bin (sbl.tar), which is the software boot loader.
did you experience anything like that before?
No one with an idea?
There must be enough people with this knowledge around here...
Sent from my GT-N7000 using xda premium
I didn't try it myself but someone else post this link to this thread in the SGSII forums about what you're asking about, I want to try when I get home and get the latest LA3 firmware but here it is:
http://forum.xda-developers.com/showthread.php?t=1132724
matius44 said:
I didn't try it myself but someone else post this link to this thread in the SGSII forums about what you're asking about, I want to try when I get home and get the latest LA3 firmware but here it is:
http://forum.xda-developers.com/showthread.php?t=1132724
Click to expand...
Click to collapse
And this supercomplicated procedure achieves what exactly?
A non-wiping rom update?
I think he just wanted to delete the data image, repack and flash with odin.
Just needed the correct packer. Right?
legion1911 said:
And this supercomplicated procedure achieves what exactly?
A non-wiping rom update?
I think he just wanted to delete the data image, repack and flash with odin.
Just needed the correct packer. Right?
Click to expand...
Click to collapse
right, it should be enough to delete the data.img!
it looks like the problem is the packer, although i'm in contact with intratech (who is a xda-mod who did this a few times @sgs2 forums, besides he's really great in what he is doing!) and he meant that there could also be a wipe instruction inside the cache.img!
when i know more i will post it here!
TML1504 said:
right, it should be enough to delete the data.img!
it looks like the problem is the packer, although i'm in contact with intratech (who is a xda-mod who did this a few times @sgs2 forums, besides he's really great in what he is doing!) and he meant that there could also be a wipe instruction inside the cache.img!
when i know more i will post it here!
Click to expand...
Click to collapse
Great! Will be waiting for you're simpler procedure as I found that way hard myself!
Sent from my GT-N7000
TML1504 said:
thanks for the answer!
peazip uses 7zip via console, so its the same!
anyway, the tar from peazip wont flash! odin (1.83 and 1.85) stops with an error (could not write) with the boot.bin (from my modified tar), after that the phone wont boot and give the message: firmware update failed, use kies recovery mode blabla
only way to get it back to life without kies is to flash a proper boot.bin (sbl.tar), which is the software boot loader.
did you experience anything like that before?
Click to expand...
Click to collapse
I think you can safely remove boot.bin from the tar file. You should verify this before trying.
PS : If the bootloaders havent changed, why do you want to flash them? They are already there.
That packer could be used to easily install anything.
So if you find that packer, please let us know.
ragin said:
I think you can safely remove boot.bin from the tar file. You should verify this before trying.
PS : If the bootloaders havent changed, why do you want to flash them? They are already there.
Click to expand...
Click to collapse
it would be ok to remove the boot.bin as well, but then the flash would fail on the next (first) file odin tries to flash!
in case of not deleting boot.bin, this would be the first and therefore damage the boot partition, a reboot is not possible. that's the reason i hat to reflash sbl.bin!
the reason for this is again the packer, if the .tar would be ok, so would be the flash procedure!
intratech suggests to use linux and the following command to create a odin flashable tar:
Code:
tar -c boot.bin cache.img factoryfs.img hidden.img modem.bin param.lfs Sbl.bin zImage >> [Name of the desired file].tar
i will look far a tar executable for win32 and report!
done!!!
found a working packer: tar for win32
this was a little bit tricky, because the download from http://gnuwin32.sourceforge.net/packages/gtar.htm did not work, i always get the error message "The procedure entry point libiconv_close could not ..."
searching in google about that i discovered the following:
in the download from sourceforge is an old dll, the "libiconv-2.dll" which causes this error! you have to download a newer version from diffutils 2.8.7-1, which can be found here!
then, simple rename the inside libiconv2.dll to libiconv-2.dll and overwrite the one in the \bin dir from the C:\Program Files\GnuWin32\bin!
then add "C:\Program Files\GnuWin32\bin" to the path variables of your system, then you can use the tar command from the whole shell!
lol, until now this was all to get the tar program running! all people running linux won't need this steps, as tar should be fully functional for them!
then simple extract the rom files with whatever packer you like, you should see a file named "CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5" or whatever your original rom is. remove the .md5 and extract again, then you should end up with some more files:
boot.bin
cache.img
data.img
factoryfs.img
hidden.img
param.lfs
sbl.bin
zimage
now, tar the files you want to flash into one file with the shell command from intratech, for example:
tar -c boot.bin factoryfs.img hidden.img param.lfs sbl.bin >> filename.tar
you can also add whatever kernel you wish, add a zimage then!
DO NOT ADD CACHE.IMG, AS IT CONTAINS THE WIPE COMMAND!!!
now flash this file (and perhaps the proper modem.tar.md5) with odin as PDA (modem as phone) and you are done!
upgraded with this method from KL7 to LA3 without wipe and without any problems. once you have tar for win32 up and running it's really simple!
big thanks to intratech for aiding me about the cache.img and the tar syntax!!
ps.: i don't care about the yellow triangle nor the flash counter, as it is very easy to reset: use the sbl.bin from the sgs2, flash it, remove battery, use usb-jig, remove battery, flash sbl.bin from note, remove battery, done! no triangle, counter at 0
TML1504 said:
done!!!
found a working packer: tar for win32
this was a little bit tricky, because the download from http://gnuwin32.sourceforge.net/packages/gtar.htm did not work, i always get the error message "The procedure entry point libiconv_close could not ..."
searching in google about that i discovered the following:
in the download from sourceforge is an old dll, the "libiconv-2.dll" which causes this error! you have to download a newer version from diffutils 2.8.7-1, which can be found here!
then, simple rename the inside libiconv2.dll to libiconv-2.dll and overwrite the one in the \bin dir from the C:\Program Files\GnuWin32\bin!
then add "C:\Program Files\GnuWin32\bin" to the path variables of your system, then you can use the tar command from the whole shell!
lol, until now this was all to get the tar program running! all people running linux won't need this steps, as tar should be fully functional for them!
then simple extract the rom files with whatever packer you like, you should see a file named "CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5" or whatever your original rom is. remove the .md5 and extract again, then you should end up with some more files:
boot.bin
cache.img
data.img
factoryfs.img
hidden.img
param.lfs
sbl.bin
zimage
now, tar the files you want to flash into one file with the shell command from intratech, for example:
tar -c boot.bin factoryfs.img hidden.img param.lfs sbl.bin >> filename.tar
you can also add whatever kernel you wish, add a zimage then!
DO NOT ADD CACHE.IMG, AS IT CONTAINS THE WIPE COMMAND!!!
now flash this file (and perhaps the proper modem.tar.md5) with odin as PDA (modem as phone) and you are done!
upgraded with this method from KL7 to LA3 without wipe and without any problems. once you have tar for win32 up and running it's really simple!
big thanks to intratech for aiding me about the cache.img and the tar syntax!!
ps.: i don't care about the yellow triangle nor the flash counter, as it is very easy to reset: use the sbl.bin from the sgs2, flash it, remove battery, use usb-jig, remove battery, flash sbl.bin from note, remove battery, done! no triangle, counter at 0
Click to expand...
Click to collapse
Bravo, Wiener, Bravo!
Btw I found another way and just did it.
I used dsixda kitchen to deodex, root, zipalign and make a non-wipe version and it was easy!
Thought I might share it with you guys
Sent from my GT-N7000
thx for the info, but i personally dislike most deodexed roms!
besides it could cause unknown troubles (remember tha smali baksmali issue) it generally runs less smooth! the reason? simply speaking odexed is optimized (the o in odex), deodex trades this optimizations for the advantage of being simpler to skin, modify etc.
this means deodexed may be acceptable for people who want to skin and modify a lot, therefore almost all custom roms are deodexed. it makes it simpler for the cook!
you as an enduser would almost always prefer odexed roms. also lots of quality mods are available for odexed too...
just my opinion, and i used to use custom roms a lot!
Sent from my GT-N7000 using xda premium
Ok I just upgraded from KKA to LA3 without wiping using nothing but the stock files and mobile odin:
Launch mobile odin, and fill each line one by one, selecting the correct firmware file, except data and cache.
Select ever root if you didn't select a rooted kernel, and flash that baby! !!
Sent from my GT-N7000 using XDA App
Latoc said:
Ok I just upgraded from KKA to LA3 without wiping using nothing but the stock files and mobile odin:
Launch mobile odin, and fill each line one by one, selecting the correct firmware file, except data and cache.
Select ever root if you didn't select a rooted kernel, and flash that baby! !!
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
also thx, for me this didn't work from KL7 to LA1, got bootloops! but generally fine if this was only my fault, and the odin method works fine!
I have absolutely no background knowledge of anything in a smartphone so bear with me. My device is rooted though.
Ok you know how Samsung Galaxy S4 came with all those stock apps? I want to be able to delete all of them.
With some simple google searches I found this link:
http://forum.xda-developers.com/showthread.php?t=2307355
I attempted some of these steps but I have absolutely, not even the slightest how to complete those steps that person has outlined.
Here are the steps:
Download the zip file "TrulyClean_v1.6_MEDIUM_SBROWSER" extract it.
1. Use the default script or edit the script after your taste. (see "hidden "tutorial above!)
2. Copy recovery.zip to phone.
3a. For best experience - do a full wipe, install a custom rom and then flash TrulyClean.zip.
3b. Script only removes apps in /system, so you have to uninstall any updated apps manually.
4. Flash in recovery (I use PhilZ Touch) & run script after every time you flash a new rom.
5. Enjoy and tell me what you think!
So I downloaded the zip file and extracted it, there were two files into: META-INF and busybox.
Ok so I put them in a folder on the desktop called recovery.
On step 2 I zip the folder I created, so now it's called recovery.zip
On step 3 I don't know anything beyond that, are there step by step tutorials with pictures that illustrate these steps?
michaelli1991 said:
Ok you know how Samsung Galaxy S4 came with all those stock apps? I want to be able to delete all of them.
Click to expand...
Click to collapse
Hello,
This is ROMCleaner - http://forum.xda-developers.com/showthread.php?t=2348256
It is a simple zip which you flash in recovery and also comes with a ROMCleaner_user.txt which you serves as the list of apps you want to delete.
Very easy to edit and use.
Also,
http://forum.xda-developers.com/showthread.php?t=2507931
This is a great ready-to-flash script you can try if you are a little unsure of editing your own custom list.
michaelli1991 said:
I have absolutely no background knowledge of anything in a smartphone so bear with me. My device is rooted though.
Ok you know how Samsung Galaxy S4 came with all those stock apps? I want to be able to delete all of them.
With some simple google searches I found this link:
http://forum.xda-developers.com/showthread.php?t=2307355
I attempted some of these steps but I have absolutely, not even the slightest how to complete those steps that person has outlined.
Here are the steps:
Download the zip file "TrulyClean_v1.6_MEDIUM_SBROWSER" extract it.
1. Use the default script or edit the script after your taste. (see "hidden "tutorial above!)
2. Copy recovery.zip to phone.
3a. For best experience - do a full wipe, install a custom rom and then flash TrulyClean.zip.
3b. Script only removes apps in /system, so you have to uninstall any updated apps manually.
4. Flash in recovery (I use PhilZ Touch) & run script after every time you flash a new rom.
5. Enjoy and tell me what you think!
So I downloaded the zip file and extracted it, there were two files into: META-INF and busybox.
Ok so I put them in a folder on the desktop called recovery.
On step 2 I zip the folder I created, so now it's called recovery.zip
On step 3 I don't know anything beyond that, are there step by step tutorials with pictures that illustrate these steps?
Click to expand...
Click to collapse
Hi.
U do not need to extract the two files.
U only do this if u want to remove any system apps u don't want to remove in the update script.
Just copy the zip file in yr sdcard and flash in recovery.
That's it.
Cheers.
Wait, if your rooted. Why not just buy (yes buy, it's worth it) Titanium Backup or Rom Manager Pro and freeze, backup, and uninstall the apps you want removed. And then you have a good end user friendly GUI to work with.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I had 50pc japan version of s5(sc-04f), installed rom 'G900F.STOCK.FOR.SCL23.FULL.MINHQUAN'. The downside of this rom is that its pre-rooted. I managed to unroot it by goin in supersu & click 'full-unroot'. But i had multiple devices to flash, so is there a way for me to re-pack this firmware again after i unroot it? So that i could flash it to my other devices without root.
wee2000 said:
I had 50pc japan version of s5(sc-04f), installed rom 'G900F.STOCK.FOR.SCL23.FULL.MINHQUAN'. The downside of this rom is that its pre-rooted. I managed to unroot it by goin in supersu & click 'full-unroot'. But i had multiple devices to flash, so is there a way for me to re-pack this firmware again after i unroot it? So that i could flash it to my other devices without root.
Click to expand...
Click to collapse
Your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
ok done, thx 4 the info
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
wee2000 said:
just in case if i missed the reply there, hope someone could reply me here?
when i extract the ZIP file, i got
METE-INF folder
boot.img
system.img
Click to expand...
Click to collapse
Should we search for this firmware or you can provide a link to its thread?
the link is here : https://choimobile.vn/threads/6-0-1-scl23-stock-rom-g900f-full-port-v3-by-huaminhquan93.37412/
wee2000 said:
the link is here : https://choimobile.vn/threads/6-0-1-scl23-stock-rom-g900f-full-port-v3-by-huaminhquan93.37412/
Click to expand...
Click to collapse
Generally, if it's 6.0.1 and rooted systemlessly, you need to replace boot.img with a stock one and remove SuperSU app from system.img.
This ROM intended to be flashed from TWRP, so it's an ext4 image.
You can mount it to a linux system on your PC and remove anything you want.
I havent done anything like this before. Could u give me some links or guides? My PC is running Windows 10.
wee2000 said:
I havent done anything like this before. Could u give me some links or guides? My PC is running Windows 10.
Click to expand...
Click to collapse
Ok, here' a simpler way:
1. Make changes on one phone.
2. Make a TWRP backup of boot and system partitions.
3. Restore this backup on other phones. They must have TWRP installed, a 6.0.1 bootloader and modem.
You'll have to rename backup's folder path and to wipe cache/data/system before restore.
can i use winrar to extract & compile the rom, without linux? So that i will have a much faster flashing process for all other units..
wee2000 said:
can i use winrar to extract & compile the rom, without linux? So that i will have a much faster flashing process for all other units..
Click to expand...
Click to collapse
Ok, I've managed to download that ROM at last.
The things look even simpler.
To prepare an "unrooted" ROM:
1. Download the zip form this post and unpack updater-script somewhere.
2. Make a copy of V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip, open it with Windows Explorer and replace V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip\META-INF\com\google\android\updater-script with the file you've unpacked from the attachment.
3. Try to flash ans see if it's what you need.
thx so much, already passed all units to the buyer. ill try that on next batch restock, may iknow if there's a way to get the service menu shortcode *#0*# to work again? This rom doesn't has the service menu.
bbsc said:
Ok, I've managed to download that ROM at last.
The things look even simpler.
To prepare an "unrooted" ROM:
1. Download the zip form this post and unpack updater-script somewhere.
2. Make a copy of V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip, open it with Windows Explorer and replace V3.G900F.STOCK.FOR.SCL23.FULL.MINHQUAN.zip\META-INF\com\google\android\updater-script with the file you've unpacked from the attachment.
3. Try to flash ans see if it's what you need.
Click to expand...
Click to collapse
I've replaced the updater-script in the zip file, but supersu is still there