Database Users

How to make update.zip from boot.img, system.img, data.img (the nandroid backup)

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.

Efs backup -- important !!!!

For those of you that don't think you need to read this - you are wrong! I have flashed 100's of ROM's with no issue until the end of last week.
MODERATORS PLEASE STICKY THIS IN A PLACE WHERE EVERYDAY USERS THAT FLASH ROMS WILL SEE IT
I uneventfully flashed a ROM (not important which one because I don't think it has anything to do with particular ROM) and all went well. I went to bed with a working phone and the somehow a reboot happened and awoke with a phone with no signal. The error was saying that there was no SIM card and / or No Network Available.
I finally used HC-kTool app on the Market (used latest version) to Restore an efs.tar file and my phone started working but I had a generic / fake IMEI number -- 004999010640000
If you have backed up your /EFS folder on the root of your phone then all is well. The easiest way is to use Hellcat's HC-kTool to back up your EFS and save a copy on your sdcard and your PC and that way you will not have to go through my misery.
However if you have not BACKED UP your EFS files then you will have issues like I did
Ok so here is what I can tell based on my experience:
Look for any files or folders on your sdcard that have EFS in the name. You might get lucky and look in the /EFS folder on your phone. If the nv_data.bin file has been corrupted the .nv_data.bin.bak might still be OK. If that is the case you may be able to follow this guide: http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
What won't work is any sort of simple copying nv_data.bin from the sdcard to the /EFS folder using Root Explorer - I spent almost an entire weekend trying this.
If your /EFS folder .bak file has been corrupted then in my case I found a folder on my sdcard named EFS_BACKUP that I assume that Clockworkmod has created during some of my ROM flashes (somebody correct me if I'm wrong because otherwise I have no idea how it got there).
In the EFS_BACKUP folder I have a number of files form different dates (I assume of flashes) labelled efs_xxdate.tar.gz
btw you can use these or any .gz file when using HC_kTool tool simply by renaming the file (long press with Root Explorer) to just a .tar file (delete the .gz). HC_kTool uses a file named efs.tar on the root of the sdcard to restore.
In my case I had to extract one of these files by long pressing in Root Explorer and choicing extract. I then went to the extracted folder on the sdcard (using Root Explorer) and found a folder named efs_xxdate and within that a folder named EFS
... again don't get mislead -- simply copying and pasting that file or any other to the root /EFS folder will not work!!
I noticed that there were multiple files in the extracted/efs_xxdate/efs folder but the dates were different. The nv_data.bin and the nv_dat.bin.md5 files were dated the same as the date of the folder BUT the .nv_data.bak file was dated Dec31, 2010
Here's how I restored that file:
1) I extracted the .tar.gz file as above
2) Went to sdcard\extracted\efsxxdate\efs folder and copied the older dated .nv_data.bak to the root of the sdcard using Root Explorer (long press, copy, then paste)
3) Then renamed the .nv_data.bak file to nv_data.bin on the root of the sdcard
3) Then followed these instructions from line 14 on in this post .. http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
14 = at command prompt [ C:\adbtools\ ], type adb shell
15 = type su
16 = type cp /sdcard/nv_data.bin
17 = type rm -rf /efs/nv_data.bin.md5
18 = type exit & exit
19 = REBOOT YOUR PHONE
I'm not sure why this works but EVERY combination of copying and pasting nv_data.bin , .bak, or entire EFS folders suing Root Explorer does NOT work but this above technique did work for me ! Somehow having the .md5 file recreated is the key ??
I hope this helps someone.
BACKUP YOUR EFS -- Hellcat's HC_kTool seems to work great
Thank the DEVELOPERS

Already been highlighted a few times
http://forum.xda-developers.com/showthread.php?t=1068193&highlight=efs

Can you please clarify....I always keep a weekly copy of clock work mod backed up. Is this not enough? A lille confused about the need for efs backup...
Sent from my SGS2

Thx for this post. Anyway, i got stuck at 17, it says "-rf: not found". What does that mean? Am i unable to mount efs?

Nice post. Not happened to me *yet* but you never know.
Here is the direct link to Hellcats K-tool
Backing mine up now

jcrompton said:
However if you have not BACKED UP your EFS files then you will have issues like I did
Click to expand...
Click to collapse
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..

s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?

s2d4 said:
someone move it to general please..
Click to expand...
Click to collapse
Sorted
Used K-Tool since the method mentioned via terminal never worked..

stylez said:
Sorted
Used K-Tool since the method mentioned via terminal never worked..
Click to expand...
Click to collapse
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...

s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
I did not have a new efs image file
All the files I had had been corrupted
I spent four days PMing all the big wigs re this. It's not as simple as you think unless you familiarize yourself with EFS backup BEFORE you need it!
Clockwork mod and nandroid backups do not alter the efs folder when a backup is restored! It must be backed up separately
Sent from my GT-I9100 using xda premium

vnvman said:
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
Click to expand...
Click to collapse
I did not have an image file either. Look above at my post where I describe how to do it from step number 1 forward
I didn't use the tool to fix it
I just suggested getting the tool and learning how to use it
Sent from my GT-I9100 using xda premium

jcrompton said:
I didn't use the tool to fix it
Click to expand...
Click to collapse
Just to make the whole thread clear, is your IMEI now the original IMEI or the default U1 IMEI of 0049...?

Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.

vnvman said:
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
Click to expand...
Click to collapse
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)

jcrompton said:
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
Click to expand...
Click to collapse
Thanks, i'll try that right away.

vnvman said:
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
Click to expand...
Click to collapse
kTool does both, raw .IMG dump and filebased .tar.gz backup.

Does K-Tool work with CF-Root kernel?

HellcatDroid said:
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Click to expand...
Click to collapse
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me

nfribeiro said:
Does K-Tool work with CF-Root kernel?
Click to expand...
Click to collapse
Yes, should work fine.
Should you find any missbehavings or issues though, please let me know and they shall be fixed
vnvman said:
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
Click to expand...
Click to collapse
lol xD
Well, but not necessarily stupid, the first few versions indeed only made the raw .IMG dump and the button still only says "backup to /sdcard/efs.img" (yeah, I should really change that text )
But since some 1.2x build it makes the .tar as well and when you hit the restore button it asks if you want to restore the .IMG or the .tar

Haha yeah right, i never hit restore because i didn't have an img dumped to the sd so i thought i had nothing to restore there

[NEED HELP] I Need all image files from pinkscreen (Base B526)

Sir, I Need a Internal Image files(From PINK SCREEN) If you have rom used base B526, please upload it sir, i very need that all files,bcoz with old amss from b526 my X5 can be boot normally, can be shutdown normally. Now i'm using OLD (if it corrects, i see in the thread it's image files from B160, i think that's not compatible with B526 Image) before i do update from external sd card, it was a word "Unpacking blablabla" but after changing the amss and the other, it's looks like this http://www.7ayak.com/up/uploads/13425105111.jpg
so please help me sir, without all of you, my x5 can't be turned on like a normal x5, just reboot, reboot, and reboot every 1-3 minutes

Check my mega drive (signature), you should be able to find them.
Sent from my U8800

Blefish said:
Check my mega drive (signature), you should be able to find them.
Sent from my U8800
Click to expand...
Click to collapse
Ya sir i have download it before. But it didn't work sir, changing the amss and other files still got reboot automatically (in 1-5 mins my X5 will get autoreboot)
I have do partition before about 1GB SD and 1.4GB APP, but i need to install a stock rom, never get completed, always get at 1/2 and failed (no words says 'update blablalba'
When i install a stock partition, never successfull. hmm, after i click emmc unlock boot for my friend l7 , my phone turns like that sir . vie my thread before for details . i have go to huawei centre, but they ask me to pay Rp.2.000.000 for changing the engine inside (WTF! I Have buy it only Rp.1.600.000) :crying:
i see my x5 partition via minitool partition wizard , see that picture sir, are my X5 internal partition was bad or it's okay ?

Blefish said:
Check my mega drive (signature), you should be able to find them.
Sent from my U8800
Click to expand...
Click to collapse
Just need to know something Blefish. In your mega drive, under Cust Partition, there are two files: hw-cust_data.zip and elisa-cust_data.zip. What are these files for?
I think they are both for custom partitioning the data, and none of them return you to stock partition. I think what the OP has done is accidentally flash one of them, and then flash the second one as well. Which has caused his partitions to be messed up.
But, please kindly confirm what these files are for?
Thanks.

Blefish, i've downloaded B526 Image files from your mega, but i think its not correct amss.mbn for B526, it size same as i downloaded before (23,5mb) before i replacing the amss, my amss original size upper than 23mb and my phone never get reboot automatically

rqmok said:
Just need to know something Blefish. In your mega drive, under Cust Partition, there are two files: hw-cust_data.zip and elisa-cust_data.zip. What are these files for?
I think they are both for custom partitioning the data, and none of them return you to stock partition. I think what the OP has done is accidentally flash one of them, and then flash the second one as well. Which has caused his partitions to be messed up.
But, please kindly confirm what these files are for?
Thanks.
Click to expand...
Click to collapse
Sir, i think my phone always get auto reboot its not causing by the partition. first time i got the problem in my other thread is my x5 working like normal but my x5 can;t detect a simcard, and now it can (i'm not fixing it, just maybe it has fixed by itself ) . but my stupid i do change the amss.mbn , before i got amss.mbn size is more than 23,5mb sir
So, the problem may causing my phone auto reboot is need to change the correct amss from the base B526
If someone can't upload the amss, i need to unpack update.app based on B526 and find the amss.mbn . but i don't know how to

rqmok said:
Just need to know something Blefish. In your mega drive, under Cust Partition, there are two files: hw-cust_data.zip and elisa-cust_data.zip. What are these files for?
I think they are both for custom partitioning the data, and none of them return you to stock partition. I think what the OP has done is accidentally flash one of them, and then flash the second one as well. Which has caused his partitions to be messed up.
But, please kindly confirm what these files are for?
Thanks.
Click to expand...
Click to collapse
Under cust/image, there is also cust_data folder. This is not really used in the 2.3 I believe, but it contains some carrier specific bits to Android. Not really necessary though.
VickySullivan said:
Blefish, i've downloaded B526 Image files from your mega, but i think its not correct amss.mbn for B526, it size same as i downloaded before (23,5mb) before i replacing the amss, my amss original size upper than 23mb and my phone never get reboot automatically
Click to expand...
Click to collapse
The B528, B526 all use the B522 amss if I am not mistaken, so there is no difference.

Blefish said:
Under cust/image, there is also cust_data folder. This is not really used in the 2.3 I believe, but it contains some carrier specific bits to Android. Not really necessary though.
The B528, B526 all use the B522 amss if I am not mistaken, so there is no difference.
Click to expand...
Click to collapse
Maybe
*Update
Now i repartitioning the system again with minitool partition wizard
- Ext 3 (system ) : 220mB
- Ext 3 (app) : 700mB+
- U8800-MMC (SD Internal) : 1.9gB
But when i trying to install stock rom, it always fails
I have more fun with my x5 since my x5 goes like a crazy phone
*It's same as before, gets auto reboot.
*I Have changed the Date and Time, but after my phone auto reboot IT'S DATE BACK AGAIN TO JAUNARY 1980 and TIME BACK TO THE 07:00 AGAIN , WHEN I NOT CHANGE IT, THE TIME WILL WORK ONLY ON 07:00 AND UO, Whats wrong with my phone sir>?
Always restart and restart. did u know what is the problem sir ?>

[q] help-how to remove galaxy s3 theme

hello
i i flashed the s3 theme from here
http://forum.xda-developers.com/showthread.php?p=49203319#post49203319
but i dont know how to remove it please help me
#panicked

easiest way to is restore your nandroid backup you made before you flash the mod
What I hear you cry - I have no nandroid backup!!
Well now you are going to have to do things the hard way
unzip the mod
look at all the files in the mod
now unzip your rom zip
replace all the files in the mod with the ones from your rom zip
rezip the mod
flash it in cwm with system mounted

marcussmith2626 said:
easiest way to is restore your nandroid backup you made before you flash the mod
What I hear you cry - I have no nandroid backup!!
Well now you are going to have to do things the hard way
unzip the mod
look at all the files in the mod
now unzip your rom zip
replace all the files in the mod with the ones from your rom zip
rezip the mod
flash it in cwm with system mounted
Click to expand...
Click to collapse
@marcussmith2626: Dude, its only hard for noobs.
@abhishekr700: I can't help you when you choose to be a noob. You can follow marcussmith2626 if you want to restore your backup files.
If you don't need to restore or if you have not created a backup, then download stock ROM for your phone and flash it with odin.
There are lots of tutorials to flash it with odin. So don't ask me how to do so.
Press thanks if I helped you.

marcussmith2626 said:
easiest way to is restore your nandroid backup you made before you flash the mod
What I hear you cry - I have no nandroid backup!!
Well now you are going to have to do things the hard way
unzip the mod
look at all the files in the mod
now unzip your rom zip
replace all the files in the mod with the ones from your rom zip
rezip the mod
flash it in cwm with system mounted
Click to expand...
Click to collapse
thanx both of u
i restored only the system from my nandroid backup and solved my problem
but there is a problem with status bar it has fc issues now

marcussmith2626 said:
easiest way to is restore your nandroid backup you made before you flash the mod
What I hear you cry - I have no nandroid backup!!
Well now you are going to have to do things the hard way
unzip the mod
look at all the files in the mod
now unzip your rom zip
replace all the files in the mod with the ones from your rom zip
rezip the mod
flash it in cwm with system mounted
Click to expand...
Click to collapse
thanx both of u
i restored only the system from my nandroid backup and solved my problem
but there is a problem with status bar it has fc issues now

you can try this:
look in the theme for which files it have and then choose this files but from your current romzip or themezip what you used before you flashed the theme and replace it with the ones you didnt need on your phone,when you didnt have some files than its your fail,because a NANDROID BACKUP is allways recomned before doing changes in anyway

Recommend
Only odex version of the stock rom produce these kind of force close problems.
Try to flash deodexed stock rom. It will solve all the force close issues.
But the only problem is that it occupies more memory.
You can even extend your internal storage either by partitioning the sd-card or by swapping method.
Feel free to PM me if the problem doesn't get solved.
Press thanks if I have helped you.

abhishekr700 said:
hello
i i flashed the s3 theme from here
http://forum.xda-developers.com/showthread.php?p=49203319#post49203319
but i dont know how to remove it please help me
#panicked
Click to expand...
Click to collapse
Wipe cache and dalvik cache then flash ROM again, it worked with me before
Sent from my GT-S5360 using Tapatalk 2

[Q] Help me! I need a file for all the hardware keys

I was trying to disable the hardware buttons, the one next to the home button, and use on screen buttons. But when I edited the file the first time the back button was disabled which is what I wanted but not the other button (menu?). So I tried again and when es file explorer saved it, it saved it as a empty text document. So what I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout. Im sorry if this is in the wrong place im just kinda scared about what could happen, like not being able to power back on. Thank you!

xada162 said:
I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout.
Click to expand...
Click to collapse
You should start making backups. Everyone runs into problems eventually and if you had a backup you could revert to a 100% stable system with only a few clicks.
The file that you can want can be found in the full, stock firmware image. Just download the full firmware and use winrar to extract what you need.
.

Just dirty flash the rom you have (without a wipe).

fffft said:
You should start making backups. Everyone runs into problems eventually and if you had a backup you could revert to a 100% stable system with only a few clicks.
The file that you can want can be found in the full, stock firmware image. Just download the full firmware and use winrar to extract what you need.
.
Click to expand...
Click to collapse
So I have backups of my phone with twrp but I'm lost as to what I need to look for/where that file is going to be

xada162 said:
So I have backups of my phone with twrp but I'm lost as to what I need to look for/where that file is going to be
Click to expand...
Click to collapse
I thought you knew exactly what file you accidentally corrupted. In your original post you said
xada162 said:
I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout.
Click to expand...
Click to collapse
So on that basis, you could extract the cited file from the TWRP system image. Or temporarily restore it and copy that file. Or for that matter simply restore the entire /system partition. The latter would cover you even if you weren't positive which system files were corrupted.
So boot to TWRP, wipe your system cache, then restore the system partition from a known good backup and call it day.
.