I've nandroid backup of my stock rom. and i want to make cwm flashable zip using kitchen. What file should I copy in the working folder of kitchen?
I only copied system and boot.img file. Should i copy anything else?
These are the files
boot.img
cache.ext4
data.ext4
nandroid.md5
recovery.txt
system.ext4
uboot.img
Click to expand...
Click to collapse
mrtaim3 said:
I've nandroid backup of my stock rom. and i want to make cwm flashable zip using kitchen. What file should I copy in the working folder of kitchen?
I only copied system and boot.img file. Should i copy anything else?
These are the files
Click to expand...
Click to collapse
The steps can vary somewhat depending on the device. I'm assuming it's some sort of a Chinese device, most likely a tablet, with the uboot file... What's wrong with just having the nandroid? It's not like you can't share that with others if you're needing to.
es0tericcha0s said:
The steps can vary somewhat depending on the device. I'm assuming it's some sort of a Chinese device, most likely a tablet, with the uboot file... What's wrong with just having the nandroid? It's not like you can't share that with others if you're needing to.
Click to expand...
Click to collapse
Its not about sharing. I've just bricket my phone. But i had a nandroid backup. I restored it but nothing happened. So i made a cwm flashable zip using kitchen and included only system.ext4 file and boot.img file. and i stuck at boot loop. I think i'm doing something wrong. i just wanted to ask if uboot.img is essential for cwm flashable zip?
mrtaim3 said:
Its not about sharing. I've just bricket my phone. But i had a nandroid backup. I restored it but nothing happened. So i made a cwm flashable zip using kitchen and included only system.ext4 file and boot.img file. and i stuck at boot loop. I think i'm doing something wrong. i just wanted to ask if uboot.img is essential for cwm flashable zip?
Click to expand...
Click to collapse
Well, if a nandroid didn't work, then not likely that making a flashable CWM zip with the same files would make any difference. You might just need to flash the stock firmware and start over.
Related
I have a couple questions about CWM and backups:
Is there a difference between flashing update.zip and installing a zip from the sdcard in CWM?
Also, let's say I make a change to boot.img and system.img and something goes wrong. Instead of flashing the backups of those two images from my computer to my phone using fastboot, can I just place them both in a zip file and install it from CWM? Would I need to include any other files?
How come a nandroid backup makes a system.ext4.tar and not a system.img? How do I turn that into a system.img?
How come I need unyaffs to read cache, data, and system.img files? I thought the filesystem was ext4 and not YAFFS?
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
marko! said:
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
So I found some links about the update-script and I'll be reading those shortly, but after skimming them I didn't see any mention of the binary. Is the binary an executable version of the same script or something else? Any links?
So what your saying is I could just skip the update.zip stuff, extract the images from the zip, and use advanced restore to flash each image? Obviously more work but it's good to know if these two processes are equivalent.
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
And also the last question about ext4 and YAFFS is still there. Thanks.
Most of those I'm really not sure. The update binary is the same for every zip. Just grab it from a rom or theme
I would go with the cwm zips. Way easier once you get them working.
sent from my Atrix via XDA premium
gsingh2011 said:
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
Click to expand...
Click to collapse
I was just looking at this too. My old recoveries from before atrix4.1 was released were all .img files and the post atrix4.1 backups are .ext3.tar (except for boot.img and recovery.img). I'm on a stock deodexed GB ROM, so I don't have any ext4 partitions. I think he changed this with the newest update so CWM can recognize the ext type and mount them appropriately.
This post should hopefully clarify a bit more than I can. I'm relatively new to all this so I'm still learning different aspects of modding. I'm guessing you have some ext4's because you're running one of the newer custom ROM's?
I have CM 10.1.3 installed on my i9100 and I flashed the ZIP file from the thread at the bottom of this post through CWM Recovery. Now, my phone is stuck at the boot screen.
I would realllly hate to reinstall my ROM and all apps, so I'd just like to fix the problem. The ZIP makes changes to the 'SurfaceFlinger' library. Could I reflash a ZIP of the original library? Any idea how I could get the file?
surfaceflinger-fix.zip
http://forum.xda-developers.com/galaxy-nexus/development/fix-lag-fix-cm10-based-roms-cm10-t1875490
SOLUTION:
The only file that surfaceflinger-fix.zip affects is libsurfaceflinger.so. So, I tried extracting this file from a copy of the CM 10.1 zip file. libsurfaceflinger.so is located in system/lib. I then created a flashable ZIP using this guide:
http://forum.xda-developers.com/showthread.php?t=2163974
I flashed the ZIP after pushing it via 'ADB push sample.zip /sdcard'. I installed the ZIP via CWM Recovery. Clear caches, reboot. STILL DIDN"T WORK.
So then I took a look a look in the META-INF folder of surfaceflinger-fix.zip and noticed some additional files that I did not have in my custom 'sample.zip'. So, I just took the libsurfaceflinger.so file that I extracted from CM 10.1 and put this file in surfaceflinger-fix.zip, replacing the original one in the ZIP file. Pushed this ZIP via ADB, everything works.
Had you taken a backup prior to flashing the zip it would've been five minutes work fixing your problem, I'm sure there's a lesson for all of us there.
ghostofcain said:
Had you taken a backup prior to flashing the zip it would've been five minutes work fixing your problem, I'm sure there's a lesson for all of us there.
Click to expand...
Click to collapse
This was definitely easier and this is a better fix than using a backup, but I absolutely agree with you.
I've nandroid backup of my stock rom. and i want to make cwm flashable zip using kitchen. What file should I copy in the working folder of kitchen?
I only copied system and boot.img file. Should i copy anything else?
These are the files
boot.img
cache.ext4
data.ext4
nandroid.md5
recovery.txt
system.ext4
uboot.img
Click to expand...
Click to collapse
After a failed online nandroid backup recovery I just shake my head.... not again. Don't want to flash stock rom, root, custom recovery flash path again!
So, I really like to create a flashable rom from my old backup. I just lack the meta-inf.
All these make flashable threads say get the meta-inf folder from any rom. I don't think that it is THAT easy.
(I tried a Meta-inf from a custom rom
http://forum.xda-developers.com/galaxy-s5/development/rom-noble-rom-t3403867/page19#post69117710
, but during zipping I get an error that it could not create something....)
Where can I get a working meta-inf file for Samsung S5 G901F, that I do not need to alter or just works?
Thanks you very much.
Hey,
Today I used a ROM to flash my mobile (Samsung J5 2016 edition, model: J510FN) and I just used the perfect ROM, and it fits perfectly. But when I try to turn on WiFi it goes back swipe to off automatically when I swipe it to on.
I used this rom (version v1.1 because v2 and v3 were gone and bad): https://forum.xda-developers.com/galaxy-j5/development/rom-light-stock-rom-v1-t3467865
Someone knows what to do? I'm a beginner, so please explain it good. I have everything btw like Odin, TWRP, latest SuperSU, etc.
Please help.
Thanks
From your stock rom Copy the folder named Permissions from /system/etc and paste it at the same location in your new downloaded rom.
DONOT delete the existing folder , just replace the files.
Good Luck Cheers
akash14darshan said:
From your stock rom Copy the folder named Permissions from /system/etc and paste it at the same location in your new downloaded rom.
DONOT delete the existing folder , just replace the files.
Good Luck Cheers
Click to expand...
Click to collapse
But its a md5 file (my stock rom), how do I do it then?
Zarlen said:
But its a md5 file (my stock rom), how do I do it then?
Click to expand...
Click to collapse
You mean an img file , right?
If you have twrp or cwm backup of your stock rom , you can extract it from that file(ext4.system.tar.a) , if you dont have a twrp/cwm backup , you can try to flash stock rom from that img file and then copy necessary files into sdcard and then re flash your new rom and paste the existing files.
Good luck/
akash14darshan said:
You mean an img file , right?
If you have twrp or cwm backup of your stock rom , you can extract it from that file(ext4.system.tar.a) , if you dont have a twrp/cwm backup , you can try to flash stock rom from that img file and then copy necessary files into sdcard and then re flash your new rom and paste the existing files.
Good luck/
Click to expand...
Click to collapse
No, its an md5 file. Inside the md5 file (when I open it with winrar) it only shows hidedcache files etc and also boot.img
I need to have go to the patch (system/etc/permissions
Zarlen said:
No, its an md5 file. Inside the md5 file (when I open it with winrar) it only shows hidedcache files etc and also boot.img
I need to have go to the patch (system/etc/permissions
Click to expand...
Click to collapse
Then you might need to flash your stock rom first and then copy the necessary files.
I have an Mediatek device , steps to troubleshoot are same , but I have a zip of my stock rom created to access stock files when ever i need them.
I would advise you to do the same for future troubleshooting..
Good Luck mate
akash14darshan said:
Then you might need to flash your stock rom first and then copy the necessary files.
I have an Mediatek device , steps to troubleshoot are same , but I have a zip of my stock rom created to access stock files when ever i need them.
I would advise you to do the same for future troubleshooting..
Good Luck mate
Click to expand...
Click to collapse
And what are the nessecary files? Only the permissions folder or more?
Zarlen said:
And what are the nessecary files? Only the permissions folder or more?
Click to expand...
Click to collapse
Permission folder worked for me , but i would insist you to copy the entire /system partition as backup once you have flashed the stock rom just in case.
If permission folder doesnt work , then try replacing files starting with wlan from /system/lib/modules from stock to port
Do only when permissions folder doesnt work.