I'm sorry to say I have no idea but I'm now determined to learn how and I think I'll start with a linux partition.
Anyone care to join me?
I think the Avabox that avaluanchemods posted up included the files to pull out the files from the .img, after that wouldn't it be just like modifying another ROM (with a lot more to mod, of course, to gain root, etc.)?
danaff37 said:
I think the Avabox that avaluanchemods posted up included the files to pull out the files from the .img, after that wouldn't it be just like modifying another ROM (with a lot more to mod, of course, to gain root, etc.)?
Click to expand...
Click to collapse
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
regaw_leinad said:
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
Click to expand...
Click to collapse
Hahaha yeah, getting the images from the ruu is a blast!
u guys want the new sprint ruu turned into a flashable update.zip? isn't that what damages 2.06 basically is? if not i'll do it for you.
I think it's really more that they wanna learn how. Anyone down to throw out some pointers?? I'd be interested to learn too
I was actually just looking into pulling the files from the ruu myself.
extract the exe file. unyaffs the system.img. make an update-script in META-INF/com/google/android/. zip the boot.img META-INF/ folder, and system/ folder and sign it. nothing more to it. lol
zenulator said:
u guys want the new sprint ruu turned into a flashable update.zip? isn't that what damages 2.06 basically is? if not i'll do it for you.
Click to expand...
Click to collapse
well, well howdy stranger! zen you were a great dev on the vogue/android...we need you here my man!
fixxxer2008 said:
well, well howdy stranger! zen you were a great dev on the vogue/android...we need you here my man!
Click to expand...
Click to collapse
this communtiy is a little crazy for my taste. but darchstar answered the question.
http://code.google.com/p/zen-droid/downloads/list
this is a link to the files i use. you must have linux installed to use them as well as pearl which should be installed on most distros. you'll prob have to chmod them executable if you download them.
any questions post them and i'll try to help. i'm glad to see people trying to learn.
regaw_leinad said:
nope, this ruu is different
doesn't work like that.
well, once you have the images you can use yaffs, for the system image, but getting the images from the ruu...
Click to expand...
Click to collapse
thats all you need for a rom. is the /system. just place that in a folder along with the boot.img. andddd archive and sign. you have a rom now.
and if you want to know a secret. lol
if you are in windows, all .exe's are archived as zips. change .exe to .rar/zip and then you can unzip and have everything. very simple.
o and you need an update script which you can create, or take someones from a rom and edit it to fit the RUU. and as always give credit where needed
Avalaunchmods said:
thats all you need for a rom. is the /system. just place that in a folder along with the boot.img. andddd archive and sign. you have a rom now.
and if you want to know a secret. lol
if you are in windows, all .exe's are archived as zips. change .exe to .rar/zip and then you can unzip and have everything. very simple.
o and you need an update script which you can create, or take someones from a rom and edit it to fit the RUU. and as always give credit where needed
Click to expand...
Click to collapse
interesting. so in theory this could be done as easily on windows, no linux partitions?
mountaindont said:
interesting. so in theory this could be done as easily on windows, no linux partitions?
Click to expand...
Click to collapse
i hate linux. lol so yes
Not all exe's work like that. Like this one for example....
not even 7zip can get into it.
danaff37 said:
Not all exe's work like that. Like this one for example....
not even 7zip can get into it.
Click to expand...
Click to collapse
uniextract, google it. you are correct some are a certain type that cant be extracted but 99% of RUU's can.
Ok here is a basic run through for extracting the RUU and making an update.zip
1. Run the RUU in windows or through wine. You don't have to run it completely with your phone plugged in. The install shield will extract the files to a tmp folder. Search through your tmp folders until you find it. Inside should be a rom.zip. Unzip it. Inside it should be system.img data.img boot.img etc...
2.
a: Switch to linux. Use unyaffs to extract the system.img. I usually make a directory called system in the same directory as the system image and cd to it. then issue.
unyaffs ../system.img
this will extract it into the system directory that your in. make your changes. add apps/busybox/su etc..
b: You can also use unyaffs for windows from here: http://code.google.com/p/unyaffs/downloads/list it should do the same thing but I've never used it.
3. If you want apps pre-installed to /data then make a data directory with a apps directory in it and put your extra apps there like wireless tether etc... so now you have a directory with
/system
/data
boot.img
4. Use an update script from another rom as a base and modify it to symlink busybox, set the correct permissions, copy data write boot.img, clear cache etc... read through some other update scripts to get the idea of whats going on it's simple text based stuff. The update script is inside the directory
META-INF/com/google/android.
Once done move the META-INF directory to your working directory. so you should now have
/system
/data
/META-INF
boot.img
Zip up the above directorys/files into something like myrom.zip
5. Sign the zip. You'll need java and a testsign.jar and the android sdk. I've never done it without the sdk. Create a directory called sign inside the tools directory of the android sdk. Move testsign.jar and your myrom.zip to the sign directory. Execute the following command while in the sign directory
java -classpath testsign.jar testsign myrom.zip myrom-signed.zip
6. Copy myrom-signed.zip to the root of your sdcard. reboot recovery. nandroid backup. wipe/factory reset. flash update zip.
Good luck.
zenulator said:
Ok here goes a basic run through for extracting the ruu and making an update.zip
1. Run the ruu in windows or through wine. It will be extracted to a tmp folder. Search through the tmp folders until you find it. Inside should be a rom.zip. Unzip it. Inside it should be system.img data.img boot.img etc...
2. Switch to linux. Use unyaffs to extract the system.img. I usually make a directory called system in the same directory as the system image and cd to it. then issue.
unyaffs ../system.img
this will extract it into the system directory that your in. make your changes. add apps/busybox/su etc..
3. if you want apps pre-installed to /data then make a data directory with a apps directory in it and put your extra apps there like wireless tether etc... so now you have a directory with
/system
/data
boot.img
4. use a update script from another rom as a base and modify it to symlink busybox, set the correct permissions, copy data write boot.img, clear cache etc... read through some other update scripts to get the idea of whats going on it's simple text based stuff. the update script is inside the directory META-INF/com/google/android. once done move it to your working directory. so you should now have
/system
/data
/META-INF
boot.img
Zip up the above directorys/files into something like myrom.zip
5 sign the zip. you need java and a testsign.jar and the android sdk. i've never done it without the sdk. create a directory called sign inside the tools directory of the android sdk. move testsign.jar and your myrom.zip to the sign directory. execute the following command while in the sign directory
java -classpath testsign.jar testsign myrom.zip myrom-signed.zip
6. copy myrom-signed.zip to the root of your sdcard. reboot recovery. nandroid backup. wipe/factory reset. flash update zip.
Good luck.
Click to expand...
Click to collapse
uhh...i think ill leave that one too the pros
zenulator said:
Ok here goes a basic run through for extracting the ruu and making an update.zip
Click to expand...
Click to collapse
Interesting. Sounds easy enough, I'll definitely have a go. Thanks for the tutorial.
pseudoremora said:
Interesting. Sounds easy enough, I'll definitely have a go. Thanks for the tutorial.
Click to expand...
Click to collapse
+5, HOLY CRAP guys, I havent checked the forum in a few hours.
Thank you all so much for the insight.
I'll be back in a week!!
nebenezer said:
+5, HOLY CRAP guys, I havent checked the forum in a few hours.
Thank you all so much for the insight.
I'll be back in a week!!
Click to expand...
Click to collapse
There's an easy fix for your problem... Install the XDA Android App. Seriously, my soul belongs to Android now... and XDA has become my home, I HAVE to know what's going on at all times... it's like a drug, lol.
Related
Basically I just want a stock ROM base with the sprint crap taken out and unrevoked added in with some other app mods.
I've grabbed all the sources for YAFFS2/yaffs2Utils and compiled them using cygwin.
Now when I go to extract the system.img all I get is a fonts folder.
I'm setting up a virtual linux machine to try to mount the image instead, but in the meantime anyone care to assist me?
Do a search for android basic kitchen .53. Made myself a custom rom off the .6 release
Sent from my Evo 4g using Tapatalk
stroths said:
Do a search for android basic kitchen .53. Made myself a custom rom off the .6 release
Sent from my Evo 4g using Tapatalk
Click to expand...
Click to collapse
Awesome!!!
Since you claim it works, I'll take your word for it and say I can't thank you enough!
(even if it doesn't do what I need, it should one step forward nonetheless)
Neotelos_com said:
Awesome!!!
Since you claim it works, I'll take your word for it and say I can't thank you enough!
(even if it doesn't do what I need, it should one step forward nonetheless)
Click to expand...
Click to collapse
It seems to be worthless for EVO, only generates update files...I can't even use it to extract the filesystem from system.img
my experience has been working with rfs and not yaffs2 so far.
i think you'll be needing yaffs2 tools, like unyaffs2, etc.
i googled, android system.img mount. seems like a great place to start:
http://wiki.xda-developers.com/index.php?pagename=Android system.img Customization
let us know what works or doesnt work?
If you are rooted with toast, you can flash the custom roms made with that kitchen. you can add or remove apk files before recompiling to the update zip format. I am typing this from my customized rom I made with that kitchen. The kitchen can root the rom for you, add apps2sd (havent tested that) and add wifi tether. I mainly went this routw as io wanted a rooted .6 rom to use after rooting with the Toast method. I am an Android newbie but managed to do this
Sent from my Evo 4g using Tapatalk
joeykrim said:
i googled, android system.img mount. seems like a great place to start:
http://wiki.xda-developers.com/index.php?pagename=Android system.img Customization
let us know what works or doesnt work?
Click to expand...
Click to collapse
Awesome, I figured I would need linux (why I installed it)
stroths said:
If you are rooted with toast, you can flash the custom roms made with that kitchen. you can add or remove apk files before recompiling to the update zip format.
Click to expand...
Click to collapse
I already said it's useless and I said why, it generates update files...
I need to actually extract/mount the original system, that is precisely what the thread title is about.
From the command line you can create a system dump using the following command
tar -cvf /sdcard/system.tgz /system
assuming both /sdcard and /system are mounted. you may have to use "busybox tar" instead.
You can run it from recovery mode.
To mount the filesystems while in adb shell use
"mount /dev/block/mtdblock4 /system" to mount system
and
"mount /dev/block/mmcblk0p1 /sdcard" to mount sdcard
if needed
As for making an update.zip you can take an existing one and replace the system directory inside it with your own custom one. Rezip it, no need to resign it for the EVO recovery, and flash away. Oh, and you'll have to delete any symlinks from the /system/bin directory inside the zip before flashing.
Hello, I have searched everywhere and cant find the answer to my question. I wanted to replace a file using CWM .zip how in the heck do I do that? Most of all I just wanted to learn how to do it as well...
Thanks,
Chad
Well to begin with you can take an existing zip with the file path you need, delete everything in the folders not touching the META-inf folder at all, those are the install instructions, and put the file you want to flash in the correct folder. I think thats how everyone starts out.
studacris said:
Well to begin with you can take an existing zip with the file path you need, delete everything in the folders not touching the META-inf folder at all, those are the install instructions, and put the file you want to flash in the correct folder. I think thats how everyone starts out.
Click to expand...
Click to collapse
but your update-script has to match what you are flashing via cwm. if you take a rom zip and just pop in a few files in place of the whole rom structures, your flash will fail because your update-script is looking for specific structures.
Oxicottin said:
Hello, I have searched everywhere and cant find the answer to my question. I wanted to replace a file using CWM .zip how in the heck do I do that? Most of all I just wanted to learn how to do it as well...
Thanks,
Chad
Click to expand...
Click to collapse
One way would be to use: Update Zip creator/modifier (Requires Windows)
yeah it would be bad mojo if you used a wipe rom zips META INFO to make an update zip.....
Thanks a million everyone......
Sorry for being late to the party again.. Here goes my attempt at an explanation though:
Essentially, a CWM flashable zip is just a zip file with the file system replicated in it. So for example, if you wanted to add swype, and you know Swype.apk would regularly go in /system/app, then you would create a blank folder called 'system', and another folder inside system called 'app', and put your Swype.apk inside that. (/system/app/Swype.apk)
After that, all that's left is to build an update script. So, from your root directory (where your system folder is), you would make another directory called META-INF, with a folder inside called 'com', another one inside that called 'google', and finally one called 'android' inside that (/META-INF/com/google/android), you put a text file in there called 'update-script' that tells recovery what you want to do (in this case, copy swype over to the corresponding directory on the file system).
http://forum.xda-developers.com/showthread.php?t=641223
^There's a guide for how to make those. You can also pick apart any rom you find in the dev section and check out the update script for reference.
After that, it's just a matter of zipping up all the contents in your root directory, then signing the zip with testsign.jar
modest_mandroid said:
Sorry for being late to the party again.. Here goes my attempt at an explanation though:
Essentially, a CWM flashable zip is just a zip file with the file system replicated in it. So for example, if you wanted to add swype, and you know Swype.apk would regularly go in /system/app, then you would create a blank folder called 'system', and another folder inside system called 'app', and put your Swype.apk inside that. (/system/app/Swype.apk)
After that, all that's left is to build an update script. So, from your root directory (where your system folder is), you would make another directory called META-INF, with a folder inside called 'com', another one inside that called 'google', and finally one called 'android' inside that (/META-INF/com/google/android), you put a text file in there called 'update-script' that tells recovery what you want to do (in this case, copy swype over to the corresponding directory on the file system).
http://forum.xda-developers.com/showthread.php?t=641223
^There's a guide for how to make those. You can also pick apart any rom you find in the dev section and check out the update script for reference.
After that, it's just a matter of zipping up all the contents in your root directory, then signing the zip with testsign.jar
Click to expand...
Click to collapse
Is there a way from the CWM interface to do the same with a backup you create? I noticed backups are not in the same format, they are usually .img, .tar, and an md5 file?
I have googled this alot and have not found any helpful results. I have unziped a rom I like to remove some .apks and add some of the ones I always find myself re-installing. I also have been playing with the build.prop, and the framework. I'm not trying to steal anyones work I just want to have a fresh version of this rom when I go back to it (which I do about once a week). my intent would be to flash, enter my wifi and google passwords, and start using it. I know I can just do a backup and reinstall that, but this has been helpful with my trying to understand how to build a rom and what makes it work. My question being what are the steps to rezip this rom into a flashable update. I have tried dsixda kitchen with no luck, just reziping it, and some other dumb methods. What am I missing here? plz help thank you.
also don't think it matters but this is for a o.g. evo
we got same problem, i edited a working rom for galaxy y (adding and removing some apk) then i was like huh??? what to do next, tried zipping it but doesnt work. hope.someone will reply here.
Sent from my Nokia 3310 running ICS
The problem is the signature verification of the ROM. We sign the ROMS when we create them.
No idea what custom recovery you might use but there should be an option to disable it before you try flashing.
I hope this helps.
No I have cwm and I disabled signature verification, it still starts fine says updating than immediately says its failed
Sent from my PC36100 using XDA App
I also just have it in the folders it unzips in then inside a folder and I just zip that folder is that not right I don't know lol hope someone can help
Sent from my PC36100 using XDA App
That's what's wrong. You can't zip an entire ROM as a folder then zip that folder. Doesn't work that way.
Open a ROM. See how its packed. You'll have a system folder, data, sdcard perhaps. But that's how you package it.
This isn't as easy as you think. You can't just hack stuff up and expect it to work if you don't do it properly.
MattCrystal said:
That's what's wrong. You can't zip an entire ROM as a folder then zip that folder. Doesn't work that way.
Open a ROM. See how its packed. You'll have a system folder, data, sdcard perhaps. But that's how you package it.
This isn't as easy as you think. You can't just hack stuff up and expect it to work if you don't do it properly.
Click to expand...
Click to collapse
No I'm leaving the folders inside the ROM intact. everything is in a folder with all the folders ( data folder, META-INF folder, system folder ect..., and the boot image inside that single folder and then I am ziping all those items in the folder into a zip. I just can't get it to flash it starts then after a second of installation it says aborted.
sknight13602 said:
No I'm leaving the folders inside the ROM intact. everything is in a folder with all the folders ( data folder, META-INF folder, system folder ect..., and the boot image inside that single folder and then I am ziping all those items in the folder into a zip. I just can't get it to flash it starts then after a second of installation it says aborted.
Click to expand...
Click to collapse
Zip up the ROM you want. Take that ROM to the kitchen then build it again. Try that. Sign it and everything. If you want a walk through PM me and ill give you my gtalk address.
sknight13602 said:
No I'm leaving the folders inside the ROM intact. everything is in a folder with all the folders ( data folder, META-INF folder, system folder ect..., and the boot image inside that single folder and then I am ziping all those items in the folder into a zip. I just can't get it to flash it starts then after a second of installation it says aborted.
Click to expand...
Click to collapse
After reading this more I'm still understanding that the data and meta, system folders are in a folder, then that folder is zipped.
This is incorrect way to package it. The data, meta, system etc needs to be zipped all together as one. Not in a folder that is zipped. Make sense? Hope this explains more.
I'll try that I guess Mabry them all being in a folder is the prob I hope thanks man
Sent from my PC36100 using XDA App
Yup. Let me know if you need anymore help and if that works for you.
MattCrystal said:
After reading this more I'm still understanding that the data and meta, system folders are in a folder, then that folder is zipped.
This is incorrect way to package it. The data, meta, system etc needs to be zipped all together as one. Not in a folder that is zipped. Make sense? Hope this explains more.
Click to expand...
Click to collapse
lol so I find this funny but after some research I found that their were some commands in my update script I was leaving in that needed to be removed because I was removing the apk from the rom but it was looking for them and causing errors so after all my headaches it was something simple that'll teach me not to mess with something that aint broke
just tryed to flash it and now after it almost finished flashing I got
"update sdcard/romname/blah blah. failed"(status 6)
does that mean anything to you besides that I messed something up?
I playing with a sense 3.5 rom on a gb 2.3.5 base. Is their an easier rom to play with thats is more user freindly for a newb? mabey takeing the original ruu and tweaking that? I just want to start somewhere and develop my skills.
sknight13602 said:
just tryed to flash it and now after it almost finished flashing I got
"update sdcard/romname/blah blah. failed"(status 6)
does that mean anything to you besides that I messed something up?
I playing with a sense 3.5 rom on a gb 2.3.5 base. Is their an easier rom to play with thats is more user freindly for a newb? mabey takeing the original ruu and tweaking that? I just want to start somewhere and develop my skills.
Click to expand...
Click to collapse
k I got it now thnx for your help MattCrystal
Your welcome. Every phone works a little differently but get used to having problems and fixing them. Part of the struggle. And to me the fun. I love troubleshooting.
i think just open the zip (not unzip it)..
when dialog box open,,you can choose the apk or the others you want to delete..
if you want add somthing to zip,,just open the folder location you want add that,,and than drag n drop the file(s)..
thats it..
than close the dialog box..
winrar will ask you to save the change or not,,choose,,save..
its work for me..
P.S.
use the rom by yourself..
as your personal rom..
if you want to publish it,,ask the permit from the devs..
hey guys i just wanted to ask something. Its possible to install apps via update.zip immediately after flashing ROM rite? I searched XDA and found this: http://forum.xda-developers.com/showthread.php?t=917922
but im not sure how to do it and anyway the meaupload link for that download is down. Btw since all my app data together is more than the data partition of the phone (>200mb), is it possible to make the apps link to my second partition of sd card via update.zip script or something? Hope u guys can help me!!
Does anyone know how to do this? if possible i think it would save a lot of time as when reinstalling via titanium backup. this way would be more hassle-free if possible.
So no one knows how to do this? ok then nvr mind i guess it must be too hard or something....
Why not just use an ext partition and app2ext?
Creating an update.zip is possible, but it's not very convenient. Esp keeping it up-to-date.
Mioze7Ae said:
Why not just use an ext partition and app2ext?
Creating an update.zip is possible, but it's not very convenient. Esp keeping it up-to-date.
Click to expand...
Click to collapse
srry if im asking a really dumb qn but does that mean that if u install apps to ur ext2 via link2sd, u dont have to install them again on new ROM?
App2ext is different from link2sd (but they both use ext partition.
In link2sd you usually create /sd-ext/link2sd folder, reboot and then use the Link2SD app to manually move apps to /sd-ext/link2sd. This is good if you want to mix apps on SD and internal.
In app2ext (which I'm suggesting) you instead create /sd-ext/app folder on sdcard and reboot. All your installed apps will be moved there from internal memory and new apps will be installed there automatically. They will still be there after you factory reset or install a new ROM. (To preserve application data you need something else such as titanium backup)
Ohhhhh. Thx a lot!! Ok I just wanna try a bit of programming that's why I asked how to make update.zip. haha. Anyway Thx!!
Sent from my XT720 using XDA App
androidlover123 said:
Ohhhhh. Thx a lot!! Ok I just wanna try a bit of programming that's why I asked how to make update.zip. haha. Anyway Thx!!
Click to expand...
Click to collapse
You can learn by studying the gapps package used by CM or any other update.zip. The "magic" is inside the META-INF folder. META-INF/com/google/android/updater-script has the installer commands that do things like mount /system and extract files, set permissions etc. The final step is to sign the update. OpenRecovery allows unsigned updates, but you should sign anyway even using testkeys--it forces a sha1 verification of the zip files to detect corruption before the update is applied.
Mioze7Ae said:
You can learn by studying the gapps package used by CM or any other update.zip. The "magic" is inside the META-INF folder. META-INF/com/google/android/updater-script has the installer commands that do things like mount /system and extract files, set permissions etc. The final step is to sign the update. OpenRecovery allows unsigned updates, but you should sign anyway even using testkeys--it forces a sha1 verification of the zip files to detect corruption before the update is applied.
Click to expand...
Click to collapse
oooh i can kinda understand the code in the updater-script. for eg: ui_print to print to screen, package_extract_dir to extract files to the directory in whatever folder u state. but what is the update-binary file?
The update-binary is the program that reads and executes updater-script.
Mioze7Ae said:
The update-binary is the program that reads and executes updater-script.
Click to expand...
Click to collapse
Is that something you must write yourself or something? Or just copy from other update.zips?
I just copy it. It's probably in the AOSP source somewhere but I've never looked.
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Dude once again you're creativity and hard work is paying off. Great job man
Style point for the rip bud!
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
SaschaKH said:
Sounds very helpfull and as markbencze already replyed I gues it's working on the O+O too. Have to try it in the next days.
thx markbencze for sharing.
Click to expand...
Click to collapse
Yes. I tested it on my OPO. It went out for a rip. It will run on any device, and it will find the partitions on most.
Where's the download link dude, i'm not find download link from github ?
itsnie said:
Where's the download link dude, i'm not find download link from github ?
Click to expand...
Click to collapse
On the right side of page near the clone url, there should be a button that says download as zip.
Just realized you have to be in desktop view to see the download as zip button. I will post an additional link a little later.
Just added backup and restore contacts.
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Rukbat said:
N-i-c-e!
Thank you.
I've been working on the same sort of thing, and trying to figure out how to get adb connected to the phone with debugging off, for those people (I won't use the word I'm thinking of) who don't make backups, then break the screen, or bootloop the phone. Your script makes finding the data partition trivial, but I'm still working on the "force debugging on from outside" part.
But munky is going to be part of my phone from now on.
Click to expand...
Click to collapse
Thanks, man. Glad to hear you like it.
mike the inkman said:
***MUNKY-TOOL***
IS AN ONBOARD ANDROID UTILITY
FEATURES
[*]Copy system.img
[*]Copy boot.img
[*]Backup efs
[*]Logcat
[*]Backup and Restore Contacts
[*]Out For A Rip
Munky-tool will locate and copy most partitions without you having to track down paths. This is convenient if you use a ROM kitchen, or just want to make a backup of your system without using custom recovery. Some devices do have weird partition names, and munky-tool will not find them. If this happens to you, run the following command in terminal emulator
Code:
ls /dev/block/platform/*/by-name
Paste the output and your device name in the comments, and I will work your device in if possible.
INSTRUCTIONS
Download zip or clone git
Place extracted munky-tool folder in system partition (must be able to set permissions)
Set permissions of munky-tool script (not the directory) to at least 775 (rwx rwx rw)
Open terminal emulator and key in 'su' for root permissions
cd to the munky-tool directory
Type ./munky-tool to execute the script and start the utility
DOWNLOAD
github
Click to expand...
Click to collapse
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Azlun said:
Good Tool, do you already plan to support restore EFS? which make a full loop of running time change the EFS setting without a PC,
this can help to me to control the modem band preset selections for network testing purpose.
Click to expand...
Click to collapse
It is usually done in bootloader, but I am pretty sure I can make it work. Just need to test it before I release it. I am also going to release this as an apk soon. (Don't know how soon, but I probably won't have time for a few weeks)
An app that we can point new users to that will back up their userdata partition? Fantastic!
Rukbat said:
An app that we can point new users to that will back up their userdata partition? Fantastic!
Click to expand...
Click to collapse
Yeah, I think it will fill a need. I am going to do an APK to do the things from this script, and a corresponding GUI Linux package for APK modding, and maybe do something for Windows as I get time. In the process of moving somewhat unexpectedly, so it is taking longer than I would have liked.