Related
Any one out there that can help me understand the last part of Adb.
lol.
I learned how to use Odin and superoneclick.
Now I am on Adb.
I read all I can on Team Whiskeys and XDA website and other googled websites. I installed everything and did the My computer/system properties/advance/Enviroment Variables/Path entries.
I start ADB and then I do in command prompt "adb devices" and whoopie I see my phone.
NOW WHAT?
No body on the instructions or website that I have read goes past that.
How do I push down a Rom to overwrite the system with the new Rom I want to try?
Hope someone out in the Forum has really done this before and will post how they do it.
Need to find someone smart enough to finish the instructions.
Thanks,
CatfishKnight
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
birgertime said:
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
Click to expand...
Click to collapse
Thanks for showing me how to push to my phone. Now do I install it. In recovery mode as a zip? I thought adv installed it and I just rebooted and it was installed.
birgertime said:
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
Click to expand...
Click to collapse
Thanks for showing me how to push to my phone. Now do I install it. In recovery mode as a zip? I thought adb installed it and I just rebooted and it was installed.
It just moves the file to the phone. You have to flash the file yourself if it is a flashable.
You can push a .jpg file if you want, it doesn't matter, it only moves it.
And I think you're getting confused with the 'adb install' command. You can install NON-system APKs by doing that.
Code:
adb install someprogram.apk
birgertime said:
It just moves the file to the phone. You have to flash the file yourself if it is a flashable.
You can push a .jpg file if you want, it doesn't matter, it only moves it.
And I think you're getting confused with the 'adb install' command. You can install NON-system APKs by doing that.
Code:
adb install someprogram.apk
Click to expand...
Click to collapse
I guess I was confused on what ADB could do.
I thought it could push down a Rom and install it onto the phone.
Then I would disconnect it and reboot the phone and I would have the newer rom installed.
I didn't know that it only pushed the ROM onto the sdcard and then I would install the zip from the phone itself.
Finally I got an answer to my question.
LOL.
I have tried on the team whiskey site to and no one answered it. Also all the stuff I read on it really didn't tell me that either.
I really appreciate your answer in helping me understand it.
I am also using Trigger 2.8 like you. But you said you had Trigger2.8.1 saved??
I have only seen Trigger 2.8 today.
^ birgertime is the developer of Trigger. He is already cooking something new in the kitchen.
s15274n said:
^ birgertime is the developer of Trigger. He is already cooking something new in the kitchen.
Click to expand...
Click to collapse
Duhhh... I missed that... LOL. I am brain fried!!! I have installed Odin, SuperOneClick, and ADM. I have be learning all three but was having trouble with understanding what ADB could do. Been reading lots and lots about it all day. Whew. I am tired. Ever instruction got down to connecting and seeing your phone and then it would end there. Finally I got an answer from Birgertime. Thanks.
I have 4 different roms saved to my phone to switch between if I want too. But I love Trigger 2.8 with Overclock v2. Also I am seeing 9 sats out of 11 on my gps. With Overclock v2 and using CPUBoostPro I am right at 2000 with Quadrant.
Hi guys,
Couldn't find the answer to this anywhere but I noticed in the newer releases of busybox there's no 'zip' command anymore. I'm running busybox 1.19 on my Incredible.
I have been using this command to create different bootanimation.zip files from my phone but am wondering if there is an alternative command I can use from within Android. I've tried tar -cvzf but I believe tar archives/compresses the files differently and renaming the extensions to .zip does not work.
Any ideas besides using an actual PC to do what I want to do?
Thanks,
Zebdor
Sent from my Incredible using XDA App
There are apps out there such as AndroZip, that essentially creates zip files.
If you are doing this for an app, there are built in zip classes in Java.
java.util.zip.*;
Edit: Just realized you asked for it to be command line. I will keep looking!
Yeah, I used to use 'zip -0r ...' to zip up a folder but for some reason the busyboxes I've tried downloading don't come with the zip command anymore...
I'm looking through the BusyBox source...
Does it have to be .zip? I mean there are plenty of others to choose from such as tar, gz, bz.
I can't find anything on the website why it is left out.
Best of luck
travmanx said:
I'm looking through the BusyBox source...
Does it have to be .zip? I mean there are plenty of others to choose from such as tar, gz, bz.
I can't find anything on the website why it is left out.
Best of luck
Click to expand...
Click to collapse
I was thinking of using tar and gz but every tutorial I've read says Android requires the bootanimation to be in .zip format uncompressed. I even tried tarballing it as bootanimation.tar but it didn't work...
did anyone ever find an answer to this?
im currently trying to find a portable binary for just zip (or something like busybox that includes zip) because im trying to automate creation of a cwm zip ON an android device during the installation of another cwm zip
iXNyNe said:
did anyone ever find an answer to this?
im currently trying to find a portable binary for just zip (or something like busybox that includes zip) because im trying to automate creation of a cwm zip ON an android device during the installation of another cwm zip
Click to expand...
Click to collapse
This seems to work fine: https://code.google.com/p/zip-for-android/people/[email protected]
I thought I was crazy...
I have surely been missing the zip command too... I just got done downloading and about to reboot into recovery to install...
Zarchiver is a free app in the market that i use to.make boot animation zips and any other kind of zip on my Android device.
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
It's possible. In fact I mentioned this about a month ago to a developer.
I would like to see one that has a couple of options such as flashing recovery and flashing boot.img files.
You can easy push the flash_image binary to /system/bin and set the permission to 755. In fact my CWMFaux kernel does just that. Faux stopped using it because it doesn't always work.
In fact I made it so easy that all you need to do is push the boot.img to /system and reboot. Yet... no one uses it. In fact I suggested to a couple of rom developers to simply add the binary file to /system/bin so that you can at least run the command from terminal but they don't even want to do that. I like being able to update my recovery at anytime by entering "flash_image recovery /sdcard/recovery.img" and then just rebooting to recovery. You can easily do that for kernels too. But I suppose it's so much easier to carry a computer around.
Binary100100 said:
It's possible. In fact I mentioned this about a month ago to a developer.
I would like to see one that has a couple of options such as flashing recovery and flashing boot.img files.
You can easy push the flash_image binary to /system/bin and set the permission to 755. In fact my CWMFaux kernel does just that. Faux stopped using it because it doesn't always work.
In fact I made it so easy that all you need to do is push the boot.img to /system and reboot. Yet... no one uses it. In fact I suggested to a couple of rom developers to simply add the binary file to /system/bin so that you can at least run the command from terminal but they don't even want to do that. I like being able to update my recovery at anytime by entering "flash_image recovery /sdcard/recovery.img" and then just rebooting to recovery. You can easily do that for kernels too. But I suppose it's so much easier to carry a computer around.
Click to expand...
Click to collapse
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
Keep me posted will ya?
I believe that Faux and other developers would have to use the zImage kernel flashing technique to get it to work with his existing app but I'm sure he can simplify it to accept .img files and the .ko files in the /system/lib directory of a zip file. It actually should be very easy. It took me about ten mintues with testing included to create the script for my method. I just can't code for apps else it would be done by now.
DEFINITIONOFREAL said:
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
I contacted pershoot, no answer lol!!!
Joeykrim is willing to support the Amaze, he just needs testers, this would be a great backup incase the new script failed to push the kernel. I'll keep everyone posted with updates
Sent from my HTC Amaze 4G using XDA App
I've been working with joeykrim getting his app setup for our device, it looks like it should work, hopefully, within the next couple of days we can get this working and released
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
I've been working with joeykrim getting his app setup for our device, it looks like it should work, hopefully, within the next couple of days we can get this working and released
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
That would be wonderful!
I'm tired of having to repeat myself.
flash_image boot /sdcard/boot.img
flash_image recovery /sdcard/recovery.img
Binary100100 said:
That would be wonderful!
I'm tired of having to repeat myself.
flash_image boot /sdcard/boot.img
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I just wish the devs would use your script, it would make things so much easier
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
I just wish the devs would use your script, it would make things so much easier
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Binary100100 said:
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Click to expand...
Click to collapse
could a script be written to automatically flash these while installing/flashing the custom rom? This would cut down atleast the step for flashing kernels for a lot of noobs!!
seansk said:
could a script be written to automatically flash these while installing/flashing the custom rom? This would cut down atleast the step for flashing kernels for a lot of noobs!!
Click to expand...
Click to collapse
Actually, yes! I did add it to the init.d script but since xboarder had removed the init.d scripts from his rom it doesn't work anymore. But you sure could. It was basically how I was setting up my CWMFaux kernels. However it didn't seem to work 100% of the time. Couldn't figure out why.
It basically worked like this...
Flashing the CWM custom kernel .zip via recovery.
copies boot.img to /system
copies init.d 06tweaks script to init.d folder.
copies and set permissions for flash_image binary and kernelupdate script to /system/bin directory.
You then boot your phone up which triggers the init.d script which commands the kernelupdate script to initiate. The kernel update script is simply using the flash_image binary command "flash_image boot /system/boot.img" and it automatically updates the kernel. Then the init.d script removes the boot.img file from the /system directory to keep it from flashing upon every boot.
I would like to change it to /sdcard directory but there's the problem that the sdcard doesn't get mounted until the very end. WAY after the system. Which is why I stored it there. The system gets mounted even before the data partition so I couldn't even store the file in data because the script would run even before the data partition could mount. Basically the script is initiated while your still looking at the boot animation. Pretty much when your softkey backlights and led light comes on it flashes the new kernel. It's a pretty neat workaround if I must say but unfortunately nowhere near perfect and not even close to having an s-off workaround.
Now if you don't mind the fact that it won't be initiated upon boot I could make it so that it will flash any file in a perspective folder on the sdcard.
example:
kernelupdate would update the kernel with any *boot*.img file located in a certain directory... say /sdcard/kernel
recoveryupdate would update the recovery with any *recovery*.img file located in a certain directory... say /sdcard/recovery
The problem:
Some people would want to collect their kernels and recoveries and store them in those directories. That would NOT be possible since using the command "flash_image recovery /sdcard/*recovery*.img would flash any img file with the word "recovery" in it. So if there's more than one it would error out and not flash anything because of the conflict. Same principal with the kernel only MOST kernels are simply named "boot.img" where-as almost all recovery files have a unique name since they are all already custom.
Binary100100 said:
Actually, yes! I did add it to the init.d script but since xboarder had removed the init.d scripts from his rom it doesn't work anymore. But you sure could. It was basically how I was setting up my CWMFaux kernels. However it didn't seem to work 100% of the time. Couldn't figure out why.
It basically worked like this...
Flashing the CWM custom kernel .zip via recovery.
copies boot.img to /system
copies init.d 06tweaks script to init.d folder.
copies and set permissions for flash_image binary and kernelupdate script to /system/bin directory.
You then boot your phone up which triggers the init.d script which commands the kernelupdate script to initiate. The kernel update script is simply using the flash_image binary command "flash_image boot /system/boot.img" and it automatically updates the kernel. Then the init.d script removes the boot.img file from the /system directory to keep it from flashing upon every boot.
I would like to change it to /sdcard directory but there's the problem that the sdcard doesn't get mounted until the very end. WAY after the system. Which is why I stored it there. The system gets mounted even before the data partition so I couldn't even store the file in data because the script would run even before the data partition could mount. Basically the script is initiated while your still looking at the boot animation. Pretty much when your softkey backlights and led light comes on it flashes the new kernel. It's a pretty neat workaround if I must say but unfortunately nowhere near perfect and not even close to having an s-off workaround.
Now if you don't mind the fact that it won't be initiated upon boot I could make it so that it will flash any file in a perspective folder on the sdcard.
example:
kernelupdate would update the kernel with any *boot*.img file located in a certain directory... say /sdcard/kernel
recoveryupdate would update the recovery with any *recovery*.img file located in a certain directory... say /sdcard/recovery
The problem:
Some people would want to collect their kernels and recoveries and store them in those directories. That would NOT be possible since using the command "flash_image recovery /sdcard/*recovery*.img would flash any img file with the word "recovery" in it. So if there's more than one it would error out and not flash anything because of the conflict. Same principal with the kernel only MOST kernels are simply named "boot.img" where-as almost all recovery files have a unique name since they are all already custom.
Click to expand...
Click to collapse
quite a dilemma, I wonder if we could add pause to the script until everything is loaded on the first boot then after the pause the script flahes the recovery and more importantly the kernel!!! if this was possible we could keep the files in a separate place on the SD card.
Still nothing like S-off!!! Thanks HTC for being so dev friendly
seansk said:
quite a dilemma, I wonder if we could add pause to the script until everything is loaded on the first boot then after the pause the script flahes the recovery and more importantly the kernel!!! if this was possible we could keep the files in a separate place on the SD card.
Still nothing like S-off!!! Thanks HTC for being so dev friendly
Click to expand...
Click to collapse
I'm sure there's a way to add a delay timer of some sort. I'm just not that savvy. Easiest way would be through an app like Tasker.
DEFINITIONOFREAL said:
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
The short answer is yes!
I've setup the application to support the HTC Amaze 4G, but before I release it publically and officially, I want to have a few testers confirm everything is working properly for them.
Posted all the information in a new thread as this one seems to be covering a few different topics so I didn't want to "hijack".
http://forum.xda-developers.com/showthread.php?p=21574722
Thanks for the request and for reaching out to me DEFINITIONOFREAL.
Binary100100 said:
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Click to expand...
Click to collapse
I think my application, Flash Image GUI, will be the best alternative, but of course I have a biased opinion!
Regarding alternatives, I think a simple sh script which takes an argument would make a nice wrapper. The argument would be location to the image file to flash. The script could either bundle the flash_image binary or take the location of it as another argument.
All depends on how the developers want to create some type of standard. Which is another great reason Flash Image GUI will work well as it contains everything required and doesn't rely on developers providing support in their ROM, only relys on developers following the standards for ROMs and kernel .zip files.
Also, in looking through some of the custom ROMs and kernel .zip files for this device, I notice one of the custom kernels does something similar to the suggestions above, it executes a file located in /system/etc/init.d on every boot which automatically flashes /system/boot.img file.
At first glance I was horrified to see this as this is a *major* security issue. If anybody were to place any type of file in /system/boot.img, either a rogue kernel or just a blank file, the script automatically flashed it on boot w/o any type of file verification or user notification!
Wanted to get that off my chest and discourage the use of *automatic* loading of any type of major file, such as kernel or recovery image, especially without at least file verification or user approval/notification.
I'll try and keep up with the thread and help contribute ideas to alternatives for anybody who wants to develop/implement! Great ideas in the thread and always enjoy reading community collaboration efforts, especially in resolution to manufacturer "adjustments" of standards.
ugh, sorry about the double post (too excited for being too early in the morning). if a moderator wants to combine my last two posts, please do. i dont have access to delete a post.
joeykrim said:
I think my application, Flash Image GUI, will be the best alternative, but of course I have a biased opinion!
Regarding alternatives, I think a simple sh script which takes an argument would make a nice wrapper. The argument would be location to the image file to flash. The script could either bundle the flash_image binary or take the location of it as another argument.
All depends on how the developers want to create some type of standard. Which is another great reason Flash Image GUI will work well as it contains everything required and doesn't rely on developers providing support in their ROM, only relys on developers following the standards for ROMs and kernel .zip files.
Also, in looking through some of the custom ROMs and kernel .zip files for this device, I notice one of the custom kernels does something similar to the suggestions above, it executes a file located in /system/etc/init.d on every boot which automatically flashes /system/boot.img file.
At first glance I was horrified to see this as this is a *major* security issue. If anybody were to place any type of file in /system/boot.img, either a rogue kernel or just a blank file, the script automatically flashed it on boot w/o any type of file verification or user notification!
Wanted to get that off my chest and discourage the use of *automatic* loading of any type of major file, such as kernel or recovery image, especially without at least file verification or user approval/notification.
I'll try and keep up with the thread and help contribute ideas to alternatives for anybody who wants to develop/implement! Great ideas in the thread and always enjoy reading community collaboration efforts, especially in resolution to manufacturer "adjustments" of standards.
ugh, sorry about the double post (too excited for being too early in the morning). if a moderator wants to combine my last two posts, please do. i dont have access to delete a post.
Click to expand...
Click to collapse
I look forward to tryin out your app.
It was basically what this thread was all about in the first place.
The clockwork method that you mentioned is the only workaround that I was able to come up with for custom kernels (like Faux123) because a kernel cannot be flashed through recovery without s-off. Really stupid. So I started thinking "How can we flash a boot.img file from recovery without the typical means?" Then came up with the solution to flash_image the boot.img file automatically IF the file is detected. But how to start a script automatically upon boot? init.d is the only way I could think of. Okay... so where to put the boot? I tried the sdcard but it failed to mount until it was way too late. So... data. Nope... still didn't mount in time. Cache? Well... how many developers will include a cache file into their roms? So the only other option was /system and it seemed convenient since /system mounts BEFORE the script can run (obviously) so that's why it is as it is. I also figured "If someone wants to flash a new kernel all they need to do is push the boot.img to /system and reboot." Must easier than using the EKF method (requiring PC access) and I don't know about you but I'm not around a computer 24/7.
Wanted to share this with fellow amaze users. It's a collection of scripts/binaries that will seamlessly reodex your /system/app and /system/framework folders. This will give you a noticeable increased in overall speed/fluidity, boot times, ram usage... I generally prefer to re-odex anything I use. Major downside to re-odexing is that you can't easily modify the APK. But honestly, it's not that difficult to simply deodex the APK in question, mod/theme it, then reodex it. I find the benefits are well worth it.
The original script was created by tommytomatoe. All credit goes to him for the actual creation of this script. I simply made a windows batch file to ease the setup and execution of said script.
Please PLEASE PLEASE make a NANDROID backup before you run this. I've never had it mess anything up, but who knows... just back up and be safe!..
ZIP is attached below. Unzip into any directory (make sure the files stay together) and run Dexo.bat - You MUST HAVE BUSYBOX, WORKING ADB (Wireless ADB support is built into the batch file), and ROOT!
I originally had a quick batch file made for just myself.. but I changed things around and made it a bit more user friendly and other things.... I've only tested it ONCE on my own device once (the modified one).. so just be warned.. and make a backup first!
The batch file will not close on its own, when it's done the device will reboot on its own. You can simply just close the window.
Hope this helps some people! Good luck.
--------------------
[What is Odex?]
During the build process, Android can be built with the flag “WITH_DEXPREOPT=true”. This means that the dex files are preoptimized in the build environment using a dalvikVM on the host, as opposed to optimized during boot on the device. The dex-preopt process results in two files per apk or jar – the jar/apk file and its accompanying .odex file.
----------------------
[What is so tricky about reodexing?]
Due to the nature of the dalvik VM (according to documentation in AOSP), the VM expects the optimization process to follow the strict BOOTCLASSPATH.
/* There are some fragile aspects around bootclasspath entries, owing
* largely to the VM's history of working on whenever it thought it needed
* instead of strictly doing what it was told. If optimizing bootclasspath
* entries, always do them in the order in which they appear in the path.
*/
So that is the dex-preopt during the build time. All the vendors ship devices with Odex, ie, stock ROMs are odex. What about ROMs that have been deodexed? Or how do you go about editing the smali code from the odex files? Thank goodness for JesusFreke, we have baksmali and smali. Using the two in sequence, one can successfully convert the optimized dalvik executable (odex) and dissemble it into a human readable (sorta) language called “smali”, created by JesusFreke and resembles the Jasmin language. Anyways, carrying on. Using the dexopt-wrapper binary, you can re-odex your ROM after it has been deodexed. This sounds pretty simple but as stated above, the VM expects the optimization to follow the BOOTCLASSPATH. You cannot silly nilly deodex android.policy.jar and then re-odex it. Your device will not boot. You must transfer the original “signature” from the original odex file to the newly created (Hint, dd if=original.odex of=new.odex bs=1 count=20 skip=52 seek=52 conv=notrunc). This can be done on a Linux machine or with the busybox binary.
OK. So what is this tool? I just wanted to give a brief (or not so brief) overview of the process. This tool doesn’t deal with partially odexed ROMs. This tool is for odexing a ROM that is completely DEODEX.
The benefits? Faster boot, smaller imprint on /data/ partition, overall faster feeling. The phone will generally just run a little bit faster, system apps will launch quicker..
The myths? I can’t theme ODEX! WRONG! You can theme odex just fine! Just use baksmali and smali.
This requires BUSYBOX.
This requires ADB.
Again HUGE THANKS to tommytomatoe for the original script and his original efforts.
THIS ZIP FILE IS NOT FLASHED IN RECOVERY! You simply extract it to a folder on your hard drive. Then run Dexo.bat, follow on screen instructions. Make sure to nandroid as well as having phone plugged in VIA USB with debugging enabled, or have wireless ADB ready to go.. batch file supports wireless. Just have to follow prompts and enter IP.
ericdjobs said:
Wanted to share this with fellow amaze users. It's a collection of scripts/binaries that will seamlessly reodex your /system/app and /system/framework folders. This will give you a noticeable increased in overall speed/fluidity, boot times, ram usage... I generally prefer to re-odex anything I use. [/B][/SIZE]
Click to expand...
Click to collapse
Tried this on my ICS ROM and it works fine.
Thanks!
Doesn't work for me :/
Sent from my HTC Ruby using xda app-developers app
avenged_sevenfold27 said:
Doesn't work for me :/
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Oh! It's not supposed to be flashed in recovery!
Sorry if I wasn't clear on that.
It's a script and a batch file. The batch file will make uploading the script, changing permissions, etc etc etc, a lot more intuitive and easier.
You simply need to extract the ZIP anywhere on your harddrive (Have to be using windows for the batch file to work.. if you're running Linux i'm sure you can figure out how to do it manually anyways) Make sure to keep all the files in the same folder.
Then simply execure dexo.bat and follow the prompts. Make sure you have the phone plugged in via USB and USB debugging enabled.. or have Wireless ADB running (batch has built in support for wireless ADB)
You can run it while the phone is on. The phone will reboot itself when the script is finished.
ericdjobs said:
Oh! It's not supposed to be flashed in recovery!
Sorry if I wasn't clear on that.
It's a script and a batch file. The batch file will make uploading the script, changing permissions, etc etc etc, a lot more intuitive and easier.
You simply need to extract the ZIP anywhere on your harddrive (Have to be using windows for the batch file to work.. if you're running Linux i'm sure you can figure out how to do it manually anyways) Make sure to keep all the files in the same folder.
Then simply execure dexo.bat and follow the prompts. Make sure you have the phone plugged in via USB and USB debugging enabled.. or have Wireless ADB running (batch has built in support for wireless ADB)
You can run it while the phone is on. The phone will reboot itself when the script is finished.
Click to expand...
Click to collapse
It goes through all the prompts for me, but then on the final "Press any key to continue" when I press any key, the batch file just closes with nothing being done to my phone.
Guess I should add, I'm using windows xp, and yes, usb debugging is enabled
masondoctorjt said:
It goes through all the prompts for me, but then on the final "Press any key to continue" when I press any key, the batch file just closes with nothing being done to my phone.
Guess I should add, I'm using windows xp, and yes, usb debugging is enabled
Click to expand...
Click to collapse
Hmm strange. I guess I should add instructions to do it manually, just in case something like this happens
Basically just open a command prompt, navigate to wherever you unzipped everything...
adb root
adb remount
(adb connect again here if using wireless)
adb push dexo /system/bin
adb push dexopt-wrapper /system/bin
adb push zip /system/xbin
adb push zipalign /system/xbin
adb shell chmod 755 /system/bin/dexo /system/bin/dexopt-wrapper /system/xbin/zip /system/xbin/zipalign
then the final command
adb shell dexo
let me know where at in this process it's getting snagged if that doesn't work.
ericdjobs said:
Hmm strange. I guess I should add instructions to do it manually, just in case something like this happens
Basically just open a command prompt, navigate to wherever you unzipped everything...
adb root
adb remount
(adb connect again here if using wireless)
adb push dexo /system/bin
adb push dexopt-wrapper /system/bin
adb push zip /system/xbin
adb push zipalign /system/xbin
adb shell chmod 755 /system/bin/dexo /system/bin/dexopt-wrapper /system/xbin/zip /system/xbin/zipalign
then the final command
adb shell dexo
let me know where at in this process it's getting snagged if that doesn't work.
Click to expand...
Click to collapse
Thanks... It might be a couple of days before I have a chance to try this again, but I'll let you know if this way works.
Sent from my HTC_Amaze_4G using xda app-developers app
Just ran the manual instructions since I had the same error noted above and all goes well until after the last adb shell dexo command; I get a message saying everything is installed but I also see this: Please install these binaries to continue: sed cp unzip. What does that mean?
Edit: I went ahead and rebooted anyway and nothing happened, still deodexed.
How can you tell if the custom rom you're on is dedoxed or redoxed? I'm on the ViperA
Sent from my HTC_Amaze_4G using xda app-developers app
kevinrubio1 said:
How can you tell if the custom rom you're on is dedoxed or redoxed? I'm on the ViperA
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Use root explorer or some similar app and go into system/apps and if you see any files right next to the app files that say .odex then you are not deodexed.
Also most custom ROM's state right in the OP if the are deodexed or not.
Sent from my HTC_Amaze_4G using Tapatalk 2
I don't have access to computer so can I run commands through terminal emulator?
Sent from my gt-1900 using xda premium
Doesn't work as of yet...
Followed the instructions
BusyBox Rooted S-off on ViperAmaze 1.7.1 ran the script as Admin and phone restarted after completion of script and stuck on bootscreen.
running fix permission and wiping dalvik+cache just in case if it works will report back EDIT: doesn't work had to recover nandroid
Can anyone dumb this thread down to what deodex/odex means to a person with no dev skills or
What can I do with deodex apks?
Is this a significant boost in speed etc?
Dumb and Dumber (remember the movie?)
blindskater39 said:
Can anyone dumb this thread down to what deodex/odex means to a person with no dev skills or
What can I do with deodex apks?
Is this a significant boost in speed etc?
Click to expand...
Click to collapse
When a Carrier releases a version of software it is ODEXED meaning you have an app like camera.apk, and you have a camera.odex
It's a file that contains the libraries and other things to support the apk.
When you DE-ODEX you build all of the stuff into the apk file so you don't need the .odex files.
it reduces the nuber of files in the rom. Meaning you now only have a camera.apk with no .odex file.
RE-ODEXING the apps and files makes it run faster.
That is taking the files back out of the apk file so you have two files again.
It seems easier to take DE-ODEXED files from one rom and use them in another rom, but you cannot just copy an apk that hasn't been DE-ODEXED into another rom without its' associated odex file.
How's that?! Hope it helps!
Looks like.... IT WORKS on Super Sense 3.2 (coming very soon)! This will speed it up big time!
chevycowboyusa said:
When a Carrier releases a version of software it is ODEXED meaning you have an app like camera.apk, and you have a camera.odex
It's a file that contains the libraries and other things to support the apk.
When you DE-ODEX you build all of the stuff into the apk file so you don't need the .odex files.
it reduces the nuber of files in the rom. Meaning you now only have a camera.apk with no .odex file.
RE-ODEXING the apps and files makes it run faster.
That is taking the files back out of the apk file so you have two files again.
It seems easier to take DE-ODEXED files from one rom and use them in another rom, but you cannot just copy an apk that hasn't been DE-ODEXED into another rom without its' associated odex file.
How's that?! Hope it helps!
Click to expand...
Click to collapse
For the most part its much easier to comprehend, thanks! But why can't you copy a de-odexed apk to another rom if it doesnt which doesnt need the .odex files anymore?
blindskater39 said:
For the most part its much easier to comprehend, thanks! But why can't you copy a de-odexed apk to another rom if it doesnt which doesnt need the .odex files anymore?
Click to expand...
Click to collapse
You can. I'm sorry if I complicated that part..
Sent from my HTC_Amaze_4G using xda app-developers app
this may be a stupid question but will this work on cm11?
dtr145r said:
this may be a stupid question but will this work on cm11?
Click to expand...
Click to collapse
No, CM11 is already deodexed.
SuperAfnan said:
No, CM11 is already deodexed.
Click to expand...
Click to collapse
well yea,
i know that.
thats the point, to 'RE-Odex' it....
Hi all, I have made been using these tools to modify and customize livesuit images to suit my needs, now I have packed all of them for u to get ur workstations to get ur hands dirty with some ROM editing/making. before u jump right in I must say though allwinner devices are not brickable, but still u may get ur warrenty void,get ur data wiped or miss a trip with ur mama or gf, and for all those reasons Ill not be held liable.
Now, my toolset includes the following - A ROM backup utility that backs up ur BOOT,BOOTLOADER,SYSTEM n RECOVERY, this will be ur starting point if u dont have any stock image.
A blank livesuit image with fake bootloader,boot,system n recovery fex files. which u will have to fill in with ur own stock roms, after u take backup. (if u dont have a stock ROM already.)
Linux tools to help u edit script.bin files and image tools to split boot images, pack or unpack system.fex etc.
The image packing/unpacking program.
#### GUIDE ####
Now we have our tools, get started....
To make stock image :
1. Get ur fimware dumped using the backup tool.
2. On a linux pc use the tools in the tools.tar.gz archive to make the dumped system file into a system.fex file by doing the follwing :
Make a directory called system.
Unpack the whole system.tgz file which u got from the dump tool inside it.
run a shell, inside the shell run the make_ext4fs binary and give these arguments [make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex>] u will get a system.fex file as output.
3. Now copy the boot.img bootloader.img recovery.img (rename the .img extension to .fex) and the system.fex u made inside the blank livesuit image and replace the nessecary files. And also replace files in the _iso folders. here ull hav to add .iso at the for filename. its pretty simple, just see how the blank files are kept.
4. Now u can pack the whole directory using the image_repacker program. Fire up runner.bat and put the directory make_stock.img.dump in it. It will generate a stock image of ur tablet. back it up as it will save u from many blunders in future.
Now if u want to modify any other livesuit image what will u do:
Just unpack the tool using the image_repacker program. run the runner.bat file, put the .img file on it(drag n drop) and use the /skip parameter in the options and let it do its work. u will get lots of files. now in a linux machine u can use the simg2img binary to make the system.fex file to a mountable image by using [simg2img <system.fex system.img>]
now mount it...make a directory called system, type these commands in the shell , [sudo mount -o loop system.img system ] this will mount the system.img inside the folder. now to make life simpler type [sudo nautilus] (on ubuntu) n start the file manager with super user access. n navigate to the system folder. now u can change files,delete unwanted stuff etc. after ur done with it pack the system directory using the make_ext4fs binary,type [ make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex> ] u will get ur system.fex file which u can pack in a livesuit image and flash.
Allwinner tools2.rar
http://www.4shared.com/rar/S3cbf46k/Allwinner_tools2.html
Editing bootloader scripts
Well, we have the freedom to try images of diffrent vendors to see what works and what doesnt, but some times the display resolution makes a problem, and theres alot of associated problems too. heres how u can edit the bootloader scripts.
I personally would say u download magicISO, and open the bootloader.fex with it, n copy the script.bin n script0.bin from ur backed up stock bootloader n then flash.
but otherwise u can do this via adb too.
run adb shell
type mkdir sdcard/bootloader
type mount -t vfat dev/block/nanda mnt/sdcard/bootloader
then goto sdcard/bootloader to see if it has actually mounted or not.
then with adb push script0.bin n script.bin to mnt/sdcard/bootloader.
then in adb shell type umount bootloader n then reboot.
If u want to mannually edit the bin files use the tools inside sunxi-tools-static.tar.bz2. the bin2fex will decode the bin n make a readable fex file which u can edit, and then use the fex2bin to make it back to bin. commands are [ bin2fex script.bin script.fex] and same goes for [ fex2bin script.fex script.bin]
SDcard Problems...
U must backup ur sdcard data... and after u flash a custom image if u dont see ur internal sd mounting the use following commands...
[ busybox mkfs.vfat dev/block/nand(x) ] here the x refers to the last nand partition that u can check by typing [cd dev/block] and then type [ls]
then type [vold] and u will see ur internal sd.
p.s I had uploaded the toolset but i dont seem to understand the upload system of xda, each time i close the window of attachments,my file is gone. so Im uploading it in 4shared. wait...ill link it.
I have no credits except that I collected and archived these tools. All these tools are made by their original programmers who have given us enough freedom to ruin our devices. So the credit goes to them.
Happy Hacking!!!!
cybermate123 said:
run a shell, inside the shell run the make_ext4fs binary and give these arguments [make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex>]
Click to expand...
Click to collapse
Shouldn't it be [make_ext4fs -s -l 500M -a system <filename.fex> {location of the system directory}]?
alright, following all instructions, I got a img made for my current setup, I flashed with LiveSuit to test if the img worked to get back to original...now im stuck at the android loading screen...any ideas?
EDIT: I'll just post details on my thread... http://forum.xda-developers.com/showthread.php?p=42373627
OMG!!! Why??? Im running my stock,its working...
EarthBoundX5 said:
alright, following all instructions, I got a img made for my current setup, I flashed with LiveSuit to test if the img worked to get back to original...now im stuck at the android loading screen...any ideas?
Click to expand...
Click to collapse
hey,did u unpack the system.tgz in linux or in windows? Aftr getting the rom backup copy the system.tgz file to linux. Unpack it there. Else ull broke symlinks as windows FAT n NTFS file system can contain symbolic links. U pls calm dwn n do the following, extract the system.tgz,make the system.fex n use the blank image i gave. Use ur own boot n bootloader. Replace files in ISO folder too n pack. N flash it.. It will work. I hav tested alot of roms. If u keep the whole system.tgz intact and dnt change anything ull get a working image. Im using mine. Still u try with a cool head n know each tool well 1st. Thn try again. If u hav a backup dnt wrry,u will b able to build ur image. Tell me if it works or not.ok.
Oops!!! Ya I made a typo on the make_ext4fs part.
EarthBoundX5 said:
Shouldn't it be [make_ext4fs -s -l 500M -a system <filename.fex> {location of the system directory}]?
Click to expand...
Click to collapse
Ya I made a typo on the make_ext4fs part. Yup file name should come first. Then directory containing system files. If all else fails u can upload ur backup (boot,bootloader,system) n ill hav a go at it.
cybermate123 said:
hey,did u unpack the system.tgz in linux or in windows? Aftr getting the rom backup copy the system.tgz file to linux. Unpack it there. Else ull broke symlinks as windows FAT n NTFS file system can contain symbolic links. U pls calm dwn n do the following, extract the system.tgz,make the system.fex n use the blank image i gave. Use ur own boot n bootloader. Replace files in ISO folder too n pack. N flash it.. It will work. I hav tested alot of roms. If u keep the whole system.tgz intact and dnt change anything ull get a working image. Im using mine. Still u try with a cool head n know each tool well 1st. Thn try again. If u hav a backup dnt wrry,u will b able to build ur image. Tell me if it works or not.ok.
Click to expand...
Click to collapse
99% sure I extracted in windows! Didn't even cross my mind about symlinks! I'll make a new img then, but just for archival purposes at this point...
EDIT: Again, I'm gonna continue a bit more, but at my thread, as I don't want yours to get garbaged up with my specific posts that are not 100% on topic to your thread...
EDIT 2: and nvm, I've been up late, and looking at my linux machine...I definitely extracted my system in linux, not windows...but again, doesn't really matter moving forward...
Thanks for providing very nice tool suite. I've just started to find decompile/compile tool for fex file. Fortunately soon your tool was found in XDA and I could start modding bootloader in order to solve hsync area problem on my device!!
Sent from my ATB701A using xda app-developers app
There must be something wrong going on, Ive tested my tools again...
EarthBoundX5 said:
99% sure I extracted in windows! Didn't even cross my mind about symlinks! I'll make a new img then, but just for archival purposes at this point...
EDIT: Again, I'm gonna continue a bit more, but at my thread, as I don't want yours to get garbaged up with my specific posts that are not 100% on topic to your thread...
EDIT 2: and nvm, I've been up late, and looking at my linux machine...I definitely extracted my system in linux, not windows...but again, doesn't really matter moving forward...
Click to expand...
Click to collapse
Im nt able to understand what might have gone wrong. As I hav unpacked ROMs of LY-F1,Eken T01,My stock ROM,an Sanei A90 ROM,Digma ID7 etc. I only got bootloop while making a livesuit image out of a Cyanogen mod build. But that was all about symlinks. I hav a doubt though I tested everything still I say u take a look at the blank livesuit image I provided, If its the problem( mines 7inch tab n that blank img is my base) u dwnload a img file which nearly matches urs n rip it apart,change n push ur things in n pack. Dnt wrry ur tabs nt bricked. And u can post here, it will nt trash my thread. Giv a logcat if u can. Ok.
cybermate123 said:
Im nt able to understand what might have gone wrong. As I hav unpacked ROMs of LY-F1,Eken T01,My stock ROM,an Sanei A90 ROM,Digma ID7 etc. I only got bootloop while making a livesuit image out of a Cyanogen mod build. But that was all about symlinks. I hav a doubt though I tested everything still I say u take a look at the blank livesuit image I provided, If its the problem( mines 7inch tab n that blank img is my base) u dwnload a img file which nearly matches urs n rip it apart,change n push ur things in n pack. Dnt wrry ur tabs nt bricked. And u can post here, it will nt trash my thread. Giv a logcat if u can. Ok.
Click to expand...
Click to collapse
I have already been flashing other images, and I am not concerned about bricking it anymore (now that I understand FEL and LiveSuit). I've already moved passed getting this working and am not working on getting CM10 working with compatibility packs...as I have no idea which to use for my tablet.
EDIT: I mean, should I just make my own compatibility pack? If so, I wouldn't know where to begin with what files out of my old system partition I'd need are...or even if they were jb compatible (coming from ics)
EDIT 2: Its a BRONCHO A710 according to the build.prop if that will help
EDIT 3: Which I've found is a clone of LY-F1, so I'll try messing with installing CM10 with that compatibility pack...although it appears many have had issues with it...which apparently I am having too, as its hanging on booting CM...
EDIT 4: I updated my thread with my absolute current situation and made 3 posts in other threads...
Also, to clarify, I'm not getting booting problems after I flash my created image, I'm getting Android loading problems...it passes the boot screen and enters the 2nd loading screen just fine, but it sits at the 2nd loading screen (3rd different screen visible during boot) forever.
Size of the system partition should never be set as fixed 500 mb, it should be taken from sys_partition.fex or sysconfig.fex (depends of AW chip) * blocksize. Setting wrong size can cause image corruption and partition will be always mounted as read only.
Yup. Sysconfig file should also be set properly.
EarthBoundX5 said:
I have already been flashing other images, and I am not concerned about bricking it anymore (now that I understand FEL and LiveSuit). I've already moved passed getting this working and am not working on getting CM10 working with compatibility packs...as I have no idea which to use for my tablet.
EDIT: I mean, should I just make my own compatibility pack? If so, I wouldn't know where to begin with what files out of my old system partition I'd need are...or even if they were jb compatible (coming from ics)
EDIT 2: Its a BRONCHO A710 according to the build.prop if that will help
EDIT 3: Which I've found is a clone of LY-F1, so I'll try messing with installing CM10 with that compatibility pack...although it appears many have had issues with it...which apparently I am having too, as its hanging on booting CM...
EDIT 4: I updated my thread with my absolute current situation and made 3 posts in other threads...
Also, to clarify, I'm not getting booting problems after I flash my created image, I'm getting Android loading problems...it passes the boot screen and enters the 2nd loading screen just fine, but it sits at the 2nd loading screen (3rd different screen visible during boot) forever.
Click to expand...
Click to collapse
yup sysconfig files should be set properly n u should see logcat. If ur file system is read only it will nt let u run anything n say sh permission denied. If thats the prob thn its error wit livsuit or system img making. As Ive seen sum roms use a bootloader script o make some symlinks n set permissions. I think ur bootloader is also doing same but as ur using the ROM frm ur tablet the flag fr da script is already present so its nt making the changes. Thus in someplace its stuck. A logcat would hav really given clr indications.
why its hard for me to this?
this is the files i get at first satge aka dumping :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's an Allwiner A20 tablet and I just want to have a backup img nothing more.
is there an easier way to do this?
I can install lnux inside vbox and go for step two but
what about " putting .iso files in _iso folder? where are they? I don't have any .iso files in dump folder.
sr i hope u can help please
hi bro i have my dump rom but i need make a .img file to take my own stock rom cause my divice es too strange and i have no way to take my stock rom. my tab is now in some rom but dint work anythink just boot and thats it.
can use my dump to make me a img file to flash with live suit? i realy dont know linux i use windows.
cybermate123 said:
Hi all, I have made been using these tools to modify and customize livesuit images to suit my needs, now I have packed all of them for u to get ur workstations to get ur hands dirty with some ROM editing/making. before u jump right in I must say though allwinner devices are not brickable, but still u may get ur warrenty void,get ur data wiped or miss a trip with ur mama or gf, and for all those reasons Ill not be held liable.
Now, my toolset includes the following - A ROM backup utility that backs up ur BOOT,BOOTLOADER,SYSTEM n RECOVERY, this will be ur starting point if u dont have any stock image.
A blank livesuit image with fake bootloader,boot,system n recovery fex files. which u will have to fill in with ur own stock roms, after u take backup. (if u dont have a stock ROM already.)
Linux tools to help u edit script.bin files and image tools to split boot images, pack or unpack system.fex etc.
The image packing/unpacking program.
#### GUIDE ####
Now we have our tools, get started....
To make stock image :
1. Get ur fimware dumped using the backup tool.
2. On a linux pc use the tools in the tools.tar.gz archive to make the dumped system file into a system.fex file by doing the follwing :
Make a directory called system.
Unpack the whole system.tgz file which u got from the dump tool inside it.
run a shell, inside the shell run the make_ext4fs binary and give these arguments [make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex>] u will get a system.fex file as output.
3. Now copy the boot.img bootloader.img recovery.img (rename the .img extension to .fex) and the system.fex u made inside the blank livesuit image and replace the nessecary files. And also replace files in the _iso folders. here ull hav to add .iso at the for filename. its pretty simple, just see how the blank files are kept.
4. Now u can pack the whole directory using the image_repacker program. Fire up runner.bat and put the directory make_stock.img.dump in it. It will generate a stock image of ur tablet. back it up as it will save u from many blunders in future.
Now if u want to modify any other livesuit image what will u do:
Just unpack the tool using the image_repacker program. run the runner.bat file, put the .img file on it(drag n drop) and use the /skip parameter in the options and let it do its work. u will get lots of files. now in a linux machine u can use the simg2img binary to make the system.fex file to a mountable image by using [simg2img <system.fex system.img>]
now mount it...make a directory called system, type these commands in the shell , [sudo mount -o loop system.img system ] this will mount the system.img inside the folder. now to make life simpler type [sudo nautilus] (on ubuntu) n start the file manager with super user access. n navigate to the system folder. now u can change files,delete unwanted stuff etc. after ur done with it pack the system directory using the make_ext4fs binary,type [ make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex> ] u will get ur system.fex file which u can pack in a livesuit image and flash.
Allwinner tools2.rar
http://www.4shared.com/rar/S3cbf46k/Allwinner_tools2.html
Click to expand...
Click to collapse
ok but can i use it in win7 it very helpfull and i wnna it so
need livesuit image file for ice x treme tab
Hi Bro,
Please share me link of any working JB livesuit Roms for ice extreme tablet ,
my tablet specs here : http://www.icexelectronics.com/shop/ice-xtreme/
Bro , if u have the same tablet with u , plz plz help me by making a livesuit image of yours...
currently , my tablet hangs around the boot logo .... cant get in to recovery either...
Please do help me...
Thanks
Hari
cybermate123 said:
Hi all, I have made been using these tools to modify and customize livesuit images to suit my needs, now I have packed all of them for u to get ur workstations to get ur hands dirty with some ROM editing/making. before u jump right in I must say though allwinner devices are not brickable, but still u may get ur warrenty void,get ur data wiped or miss a trip with ur mama or gf, and for all those reasons Ill not be held liable.
Now, my toolset includes the following - A ROM backup utility that backs up ur BOOT,BOOTLOADER,SYSTEM n RECOVERY, this will be ur starting point if u dont have any stock image.
A blank livesuit image with fake bootloader,boot,system n recovery fex files. which u will have to fill in with ur own stock roms, after u take backup. (if u dont have a stock ROM already.)
Linux tools to help u edit script.bin files and image tools to split boot images, pack or unpack system.fex etc.
The image packing/unpacking program.
#### GUIDE ####
Now we have our tools, get started....
To make stock image :
1. Get ur fimware dumped using the backup tool.
2. On a linux pc use the tools in the tools.tar.gz archive to make the dumped system file into a system.fex file by doing the follwing :
Make a directory called system.
Unpack the whole system.tgz file which u got from the dump tool inside it.
run a shell, inside the shell run the make_ext4fs binary and give these arguments [make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex>] u will get a system.fex file as output.
3. Now copy the boot.img bootloader.img recovery.img (rename the .img extension to .fex) and the system.fex u made inside the blank livesuit image and replace the nessecary files. And also replace files in the _iso folders. here ull hav to add .iso at the for filename. its pretty simple, just see how the blank files are kept.
4. Now u can pack the whole directory using the image_repacker program. Fire up runner.bat and put the directory make_stock.img.dump in it. It will generate a stock image of ur tablet. back it up as it will save u from many blunders in future.
Now if u want to modify any other livesuit image what will u do:
Just unpack the tool using the image_repacker program. run the runner.bat file, put the .img file on it(drag n drop) and use the /skip parameter in the options and let it do its work. u will get lots of files. now in a linux machine u can use the simg2img binary to make the system.fex file to a mountable image by using [simg2img <system.fex system.img>]
now mount it...make a directory called system, type these commands in the shell , [sudo mount -o loop system.img system ] this will mount the system.img inside the folder. now to make life simpler type [sudo nautilus] (on ubuntu) n start the file manager with super user access. n navigate to the system folder. now u can change files,delete unwanted stuff etc. after ur done with it pack the system directory using the make_ext4fs binary,type [ make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex> ] u will get ur system.fex file which u can pack in a livesuit image and flash.
Allwinner tools2.rar
http://www.4shared.com/rar/S3cbf46k/Allwinner_tools2.html
Click to expand...
Click to collapse
Help wit custom ROM AMPE A96
I have an original ROM for my tablet (download here w-w-w.szampe.com/en/support_down.asp?id=1205 or here w-w-w.szampe.com/UploadFile/file/2011-08/0317.rar
Can you help me creating a custom ROM with CMW recovery and a current android OS?
a31 ?
Does this tool also work for allwinner a31?
Thanks in advance.