I'm going to flash Nebula ROM when the next beta is released, but I was wondering if it matters how I backed up efs? As in, does it matter if I just copy it using file explorer and then package it as an uncompressed TAR, or do I need to extract efs.rfs using adb commands? I'm new to flashing ROMs so I don't know what the difference is if there is one.
Is one way easier? From what I gather, .rfs has to be flashed but .tar only has to be extracted into the correct folder.
Related
Hey guys, just 2 quick questions about nandroid.
Is it possible to either bypass the MD5 checksum right at the start of every nandroid restore? OR, is it possible to generate your own one somehow?
The reason I ask is, I wanna try and replace the backed up files made by nandroid such as "boot.img", "system.img", "cache.img", "recovery.img" etc with the ones that I have extracted from a stock rom.
The stock rom I have can only be flashed through USB connected to PC, by using "SP Flash Tool". However, I have 2 problems using it. The first is that it doesn't work properly for me. I can only flash the "system.img" file but not the other .img files. It seems I need a USB-to-UART cable to flash ALL the .img files, which I don't have and I don't plan on wasting my money buying it either. Besides, I find flashing on a PC a lot more risky than from memory card.
The 2nd problem I have is that I often have problems getting my phone detected by "SP Flash Tool". I tried using Windows 7 and XP and it's hard to get a connection properly. It's most likely because the phone i'm using a chinese clone, called "STAR A1000". It's cheap and crap, so I'm not surprised that I can't establish a stable connection to my PC. I only got lucky like once or twice but haven't been able to flash from my PC ever since.
So anyway, the stock rom I have contains all the .img files. I wanna try and replace those files with the files generated by nandroid, but of course there's the problem with the MD5 checksum file that will check if the file matches or not. So I need a way to bypass the MD5 checksum completely or force nandroid to perform a restore regardless of the conditions. Either that, or I need a way to generate a MD5 checksum for the .img files from the stock rom, and use that for my nandroid backup.
My last question is, I also have custom roms that are made to be flashed on the memory card. Of course, they contain the "boot.img" file, and so I wanna try and replace that with my own working "boot.img" file. I want to know if this will work when I try to flash it in the recovery, or will it fail and brick my phone?
Hey Guys,
I'm in need of some really n00b friendly advice.
When you flash a new ROM (i.e. CM9) in CWM the tutorials tell you to flash the file named Update.zip. My problem is that I can't seem to find one in the zip file I downloaded for my xperia mini.
I downloaded FXP131, and found the zip file to contain a boot.img, which will be the kernel. And 2 other folders named META-INF and System.
I know how to flash the kernel and expect it was just left in there for easy transportation.
But where in the world is 'update.zip'?
Am I meant to unpackage the kernel then re-zip the META-INF and System folder and then call that 'Update.zip'?
I've flashed roms for some of my other devices before, but they've always used flashtool or samsungs flashtool.
Please help me guys, I don't like sounding this inexperienced
update.zip
I'm wondering if the ROM I am trying to flash needs to be renamed as update.zip in order to work. It is krook's v.6 of JB for the Lenovo K1 tablet. Since the download site has to distinguish between wifi and 3G versions, as well as nvflash versions there are a number of different filenames, however does it need to be renamed after putting it on my SD card?
Generally speaking "update.zip" is used as a generic name. For example the update.zip I just flashed is actually named "rascarlo_maguro_ota_2012-11-01.zip". When you flash a custom ROM in a custom recovery you should be able to browse & flash whichever file you need.
The FXP131.zip file that contains the boot.img and 2 other folders named META-INF and System is the "update.zip"
solved
My problem was an incomplete download. I compared file sizes, and checked md5sums and determined the correct ROM and it is now in the middle of finishing the upgrade/optimization process.
Thx
Ive done a backup on my phone and created a flashable zip (update.zip)
Now im playing around with dsixda's kitchen and trying to extract the system.tar, however it fails most likely due to fact the the system.tar is empty
the files in the archive are as follows
Meta-inf -- <folder>
boot.img -- <8192KB>
image-edify -- <1KB>
system.ext4.tar -- <0KB>
system.ext4.tar.a -- <976,563KB>
system.ext4.tar.b -- <68,151KB>
By the looks of things it has split the system.ext4.tar because its over a gig
How can i compile this into one file or one image so that the kitchen can read it, I'm on a windows 7 PC but i can run linux in a vbox if necessary.
Thanks
Try using the zip file in your input folder.
dsixda's kitchen should be able to extract from it
mikep99 said:
Try using the zip file in your input folder.
dsixda's kitchen should be able to extract from it
Click to expand...
Click to collapse
Already tried, it comes back saying its deleting the part a and part b files and then says the system.ext4.tar isnt a valid archive.
Is it a stock rom?
If so, download the firmware from sammobile and put the tar.md5 file into your input folder (after removing the .md5 suffix).
Thats worked for me in the past....
It is stock, but i have removed the bloatware, installed a few mods, i was hoping to use this particular one really as a base. Ive already played around with fully stock and i kind of broke the whole thing
I'm not too sure then unless theres some tool you can find to merge the 3 tar files into 1...
Never had to do it so I'm unable to suggest anything I'm afraid.
I have been doing a lot of restoring, it would be nice to just be able to push the flash rather than geting an os installed, installing a recovery and then recovering.
I saw something for another samsung device and it involved dd'ing files and then putting them into a tar. but i suspect the /dev/xxxxxx files would be a different name on the GT10.1?
Thanks
Rob
I've tried opening a tar file before, in it was all .img files eg. system.img, boot.img and so on. So my guess is you have to create the .img files, tar them up and flash via Odin.
Sent from my GT-P7500 using XDA Premium HD app
eushaun99 said:
I've tried opening a tar file before, in it was all .img files eg. system.img, boot.img and so on. So my guess is you have to create the .img files, tar them up and flash via Odin.
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
Right, but they are dumps of the /dev/system|recovery|... file systems from using dd to get a binary image, they are not the files like in a zip. which is why, if my reading is correct, zips actually get processed (extracted and moved) and the files in the odin.tar are binary dumps and they just get splatted back out into the file system like a Norton Gost restore. The trick is knowing which /dev/xxxx/ systems to pickup. I found a link right before leaving for work that seems to suggest if I get rooted and busybody on, I should be able to run an fdsik -l and get a list of the partitions.
I just got the stupid tablet back to stock ICS 4.04 this morning after running updates last night, so I hope to have some time play today.
Guys can I convert efs folder to an img or tar file. Because I've flashed a custom rom without backing up my efs in a img or tar file.
Does anyone knows how to convert it guys?
Makes no difference what format the backup is, as long as you make one before you flash.
You mean. I can convert it to a flashable zip and flash it on recovery.?
You can do what ever you like, provided the efs wasn't corrupt before you made the backup.