Database Info

[KERNEL][32B]cm-kernel 2.6.29-bfs with BFS-302

I built a cm-kernel from Cyanogen's git repository for you to use. For now it is just a boot.img and wlan.ko, but I am going to make an update.zip for you as soon as I have time
Thanks to: cyanogen, rikupw, bcrook and Radix
This boot.img is only tested on CyanogenMod 4.1.11.1 and might work with older versions. But not on non-CyanogenMod roms!
I've also made some instructions for you to use if you want to build your own kernel: http://ostebaronen.dk/?p=210
{
"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"
}
Get the two files here:
BFS-300:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/wlan.ko
BFS-302:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/wlan.ko
To put it on your phone do as follows.
Code:
adb shell mount -o rw,remount /system
adb push wlan.ko /system/lib/modules
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
ignore no space left error.
flash_image boot /sdcard/boot.img
ignore read all-zero errors.
DISCLAIMER: I take no responsibility of bricking your phone, remember always to do nandroid backups! I will try to answer questions you ask here, off-topic questions will be ignored.

Lemme know if you need any help making a kernel update.zip. I would be happy to help out.

Oste
Thanks again! worked 100% well for me

i thing this kernel work for 32b

Very nice information. How about a guide for the pre build?

eViL D: said:
Very nice information. How about a guide for the pre build?
Click to expand...
Click to collapse
What do you mean, for making the boot.img?

I've found out compcache doesn't work, going to look at it.

Or wait, module works fine if I load it myself. So compcache can be enabled with.
Code:
modprobe ramzswap
/system/bin/rzscontrol /dev/block/ramzswap0 --init
swapon /dev/block/ramzswap0
Strange though, because the a2sd script should do this for us...

I know why compcache isn't working for you
Kernel versions and modules are intrinsicly linked by 'uname -r'
Cyanogen's kernel uses 2.6.29-cm41 and you've changed the name with yours to be different - so it's not going to load the modules automagically.
Those modules are slightly hidden from view too - they're in modules.sqf which is a squash4 volume that is mounted on boot.
Good job on documenting the git commands to track cyanogen's builds tho - this is what I need!

cat: write error: No space left on device
????

kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
i get the same thing

i skipped cat zero
and it hangs at the mytouch screen:
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
on dwangs 1.6 rom, never had a2sd to begin with

OK, going to rebuild it for you with the correct uname. Lets see if that solves the modules problems, after that I will look at putting it inside a update.zip. bcrook gave me some guidance so it should be fairly easy

Updated kernel recompiled with the correct uname!

kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
This is because cat continues filling the device with zeroes until the device is full. So you are ought to get the error No worries. Though this command is not necessary, but good to do since you are sure that nothing is left on it.

OK, for some reason no matter what I do on my phone it will not activate compcache automatically. I tried wiping and installing stock cm4.1.11.1 it didn't work there aswell. So I am sure it is not the kernels fault.
Could someone please confirm compcache is working for them?

will i still have the same a2sd hang on the mytouch screen now?

kchau said:
will i still have the same a2sd hang on the mytouch screen now?
Click to expand...
Click to collapse
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!

So what is the difference between the BFS in this kernel & the BFS is cm4.1.11.1? Is this one faster?
Edit: You just stated compcache is working if the sdcard is partitioned... so if we are already partitioned, we shouldn't have any problems, correct? Or do we have to reformat?

Cheesebaron said:
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!
Click to expand...
Click to collapse
when im on dwangs rom, it hangs at the mytouch screen, and adb logcat has this message
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
i dont think dwang's rom is a rom with a2sd, and i dont have it partitioned in my sd either.
however, when im on 4.0.4, and still dont have a partitioned sdcard, everything works fine

[HACK]LCD Density Changer That Doesn't Mess With Market

Hello All. Its me again. This time I bring you a long awaited solution. I'm sure you can remember changing your LCD density and then going to install an app which has always worked only to find that the market says its incompatible with your device. Well wait no more, This little hack will make you able to set any density and not be limited in the market.
EDIT: NOW A FLASHABLE ZIP
Process:
Download the zip and flash in recovery. (MOUNT SYSTEM FIRST)
Code:
/system/bin/density (YOUR DESIRED DENSITY)
reboot
Thats it. With every boot, the init.d script spawns the marketdensity script and it waits 45 seconds for boot to complete... Then it swaps the build.props so the market sees the correct one.
Have fun changing your density and not being limited.
Wanna help pay my bills???? Consider Donating
http://goo.gl/qQVRs
atc3030

Edited OP with new zip. Now flashable.

It didn't take when I flashed it. I'm using twrp recovery. does this support edify?
I could just put those files in there place with root explorer, right? What permissions do they need?
EDIT: I just realized I forgot to mount system. Will try again

Yes you can do root explorer. Idk the perms they need through that but if you use chmod in terminal, the perms are 775
Sent from my DROID2 GLOBAL using Tapatalk

It worked this time mounting system like I should have, lol.
But where do I enter the density? In place of the $1?

No. You run the script in terminal
Sent from my DROID2 GLOBAL using Tapatalk

I'm surprised more people aren't taking an interest in this. I understood this was a problem
Sent from my DROID2 GLOBAL using Tapatalk

atc3030 said:
I'm surprised more people aren't taking an interest in this. I understood this was a problem
Sent from my DROID2 GLOBAL using Tapatalk
Click to expand...
Click to collapse
I'm interested This has been a thorn in my side for a while now...
Gonna try this out
m.

No Joy.
Out of the box, the density script wasn't running, failing on the mount command.
I made a few changes to get it to run:
Code:
#!/system/bin/sh
echo "Setting Density to $1"
# mount only runs as root, so execute 'su' before 'mount'
su
# mount was failing without specifying the device
mount -o remount,rw /dev/block/mmcblk0p24 /system
sed "s/^ro\.sf\.lcd_density=.*/ro.sf.lcd_density=$1/" /system/build.prop > /system/.build.prop.hack
# not sure if this next mount is needed, but it makes sense to me to remount as ro once we've made the changes
mount -o remount,ro /dev/block/mmcblk0p24 /system
exit
After those changes, I was finally able to run density, and it does everything its supposed to, ie it creates /system/.build.prop.hack and the density is set to what I want there.
However, when I reboot, the changes are not applied. I'm guessing that the 98density init.d script is not being called.
I'm running a Telus SGH-T989 with Juggernaut 4.1 ROM.
Any thoughts on how to get this last piece to fall into place?
Clever idea btw, we really need something like this
m.

It works for me. I will work on it when I get home
Sent from my DROID2 GLOBAL using Tapatalk

I wanna try this out when I get home. awesome awesome awesome
Question: the 98density file in init.d is it suppose to be 755? cause all the other files in init.d are like so
I'm getting an sed:command not found. To fix it I had to write:
Busybox sed etc ....
this also needs needs SU
--EDIT-- just noticed a user above me had similar tweaks I wrote below (now striked out).
BTW for the mounting.. I think it will have to depend on your device..I got mine to mount by
mount -o rw,remount /dev/block/mmcblk0p24 /system
which I believe is different per device. I'll try the script again by changing that part of the code
After all the changes and no error. after reboot nothing changed.
very excited though

I am going to work on the scripts when I get home. They are on that computer.
Sent from my DROID2 GLOBAL using Tapatalk

emmdub said:
No Joy.
Out of the box, the density script wasn't running, failing on the mount command.
I made a few changes to get it to run:
Code:
#!/system/bin/sh
echo "Setting Density to $1"
# mount only runs as root, so execute 'su' before 'mount'
su
# mount was failing without specifying the device
mount -o remount,rw /dev/block/mmcblk0p24 /system
sed "s/^ro\.sf\.lcd_density=.*/ro.sf.lcd_density=$1/" /system/build.prop > /system/.build.prop.hack
# not sure if this next mount is needed, but it makes sense to me to remount as ro once we've made the changes
mount -o remount,ro /dev/block/mmcblk0p24 /system
exit
After those changes, I was finally able to run density, and it does everything its supposed to, ie it creates /system/.build.prop.hack and the density is set to what I want there.
However, when I reboot, the changes are not applied. I'm guessing that the 98density init.d script is not being called.
I'm running a Telus SGH-T989 with Juggernaut 4.1 ROM.
Any thoughts on how to get this last piece to fall into place?
Clever idea btw, we really need something like this
m.
Click to expand...
Click to collapse
Not all devices use the same memory block as your devices. therefore, the way you are mounting system will not work. I am working on fixing this now

Great idea but the hacked market works great.
Sent from my Incredible 2 using Tapatalk

Yeah, my setting wasn't applied after I ran it either but im not sure if it's the same problem as emmdub. I do see that it creates the .buildprop hack file. But i'm not sure why the setting isn't sticking.

I noticed that even with the hacked market sometimes I have to clear data/ cache because sometimes it kind of reverts itself.
Sent from my Incredible 2 using Tapatalk

I would like this to work, but I don't think this solution is permanent for a few reasons:
1. The market does not read the build.prop file directly. It uses the prop values that are stored in memory, and retrieved by the DisplayMetrics class. That is why after changing your density you have to reboot to get the market to recognize your new density.
2. The market does not use your device density to check compatibility. The check is server side. The market sends your density to their servers along with other info about your device when you accept their terms and services (and sometimes periodically, but not every time you use it). It registers your device info with your deviceID, and determines compatibility that way. Its how the website market knows which devices you have and if they are compatible.
Note that I am not an expert, but I have written an app to change lcd density, as well as decompiled the market and studied it a bit, so i am pretty knowledgeable in the subject.

disconnecktie said:
I noticed that even with the hacked market sometimes I have to clear data/ cache because sometimes it kind of reverts itself.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
got a link for the hacked market?
edit: i got it, thanks
http://forum.xda-developers.com/showpost.php?p=20623581&postcount=10

http://forum.xda-developers.com/showthread.php?t=1434037
Here ya go. Just copy the original vending apk from data app to somewhere safe take the new market put in the data/app folder and rename it to vending and change the permissions to
{
"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"
}

Did not think of that. I'm going too look into the memory thing right now.
Sent from my DROID2 GLOBAL using Tapatalk

[BINARY] GNU Nano editor v2.2.6 for Android

I have managed to successfully cross-compile GNU Nano editor 2.2.6 to run on Android and decided to share it here.
Please note that you need to set up terminfo (if your ROM doesn't have it already), by running:
Code:
export TERMINFO=/system/etc/terminfo
export TERM=linux
Unfortunately, it doesn't fully work through adb shell due to the fact that [enter]-key can't be used (this is a bug of adb shell).
It works flawlessly over ssh, although.
{
"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"
}
EDIT: Fully working version is here.

You will need this patch to fix the enter key:
https://github.com/Evervolv/android...b568f0b417c1fe3fe8597c600bdbcda4837013f.patch

Great! Thanks for the information. :good:
As soon as I have time for that I will apply the patch and release a new binary.

bgcngm said:
Great! Thanks for the information. :good:
As soon as I have time for that I will apply the patch and release a new binary.
Click to expand...
Click to collapse
You are welcome.
I guess you will like this patch too:
http://www.faircode.eu/freexperia/update/terminfo.patch
(I have composed it for CM9, but I guess you known how to modify it, when needed)
Edit: use git apply instead of patch

how do i install this in my phone?

ARM cross-compiling how-to
Assuming a toolchain is already present on the build environment, here are the instructions on how to cross-compile Nano 2.2.6 for ARM devices:
Set the path to C compiler:
Code:
export CC=~/toolchain/bin/arm-none-linux-gnueabi-gcc
After you have unpacked the sources change to the source directory:
Code:
cd nano-2.2.6
Now configure the source:
Code:
./configure --host=arm-none-linux-gnueabi
To compile the sources (statically) type this:
Code:
make LDFLAGS=--static

Here is the fully working version of Nano 2.2.6 for Android (without the [enter]-key bug). Enjoy. :victory:

Great job!
I went ahead and packaged this in a flashable zip for people, it also adds a script to /sbin so you can (temporarily) use nano from the recovery console in AROMA Filemanager during that recovery session.
http://forum.xda-developers.com/showpost.php?p=47402916&postcount=133

Good idea! Thank you.

@bgcngm Any way to fix the output when used through AROMA Filemanager's Terminal Console? Scrolling borks things.
Mention me back when you get the chance.

bgcngm said:
I have managed to successfully cross-compile GNU Nano editor 2.2.6 to run on Android and decided to share it here.
Please note that you need to set up terminfo (if your ROM doesn't have it already), by running:
Code:
export TERMINFO=/system/etc/terminfo
export TERM=linux
Unfortunately, it doesn't fully work through adb shell due to the fact that [enter]-key can't be used (this is a bug of adb shell).
It works flawlessly over ssh, although.
EDIT: Fully working version is here.
Click to expand...
Click to collapse
How do I exit Nano in the android Terminal emulator
Edit: I found out hacker's keyboard's ctrl key helps with this problem

If anyone has this issue, let me help out:
In Windows, running nano and vim through ADB returns weird characters on the terminal, and you need ansicon.
Or better use ConEmu.

That's right. It is documented on the internet, that Ansicon is a requirement for Windows if you use command prompt. As you say, better go with a good terminal emulator.

@bgcngm will u update it to v2.4.2 plz?

Just tried to install through CWM on Cyanogenmod 10.1 Unofficial for Samsung Infuse, and got "installation aborted." Any idea what my problem might be?

The .zip that is available is not to be installed from recovery and that's why you are not able to do it.

osm0sis said:
@bgcngm Any way to fix the output when used through AROMA Filemanager's Terminal Console? Scrolling borks things.
Click to expand...
Click to collapse
bgcngm said:
The .zip that is available is not to be installed from recovery and that's why you are not able to do it.
Click to expand...
Click to collapse
Fixed both of these issues and compiled nano 2.5.0.
http://forum.xda-developers.com/showthread.php?p=64247691#post64247691

If you are a termux user and want to install a nano or vi or any other binaries of termux in Andriod su mode. Here is the link to Termux superuser.
Give it a star if it was helpful !!!

bgcngm said:
ARM cross-compiling how-to
Assuming a toolchain is already present on the build environment, here are the instructions on how to cross-compile Nano 2.2.6 for ARM devices:
Set the path to C compiler:
Code:
export CC=~/toolchain/bin/arm-none-linux-gnueabi-gcc
After you have unpacked the sources change to the source directory:
Code:
cd nano-2.2.6
Now configure the source:
Code:
./configure --host=arm-none-linux-gnueabi
To compile the sources (statically) type this:
Code:
make LDFLAGS=--static
Click to expand...
Click to collapse
How to do this on termux? @bgcngm I got the latest 6.4 tarball.

[SCRIPT] █║ Axis (SDS) ¯`•._ Axis Shell

{
"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"
}
Code:
_ __ __ _____
/ \\ \ / // /
/ \\ \ / // ___/
/ \\ \/ //___ /
/__/\__//__/\__\\____/
Code:
/*
* This is a custom script designed to run on the US version
* of the Samsung Galaxy S3. Other phones are currently not
* supported. Follow the instructions carefully and do not cry
* to me about damaged devices. You are choosing to use the
* script and therefore accept the responsibilities
* of modifying your device.
*/
This script was originally written for use on the AxisM ROM, but I have modified it so that it works on all ROMs - both TouchWiz and AOSP. However, due to the robust error-checking in the script, only the US versions of the Samsung Galaxy SIII are supported. While the script does work perfectly well on the US SGS3, it may not fully work on all ROMs. This is partly due to some ROMs having an extreme amount of mods in the framework that inadvertently break the integrity of the files. Note that app integrity is not always a bad thing, it just means that apps and scripts that require framework integrity simply will not work. Currently there is no way to fix the integrity of a file by use of a script, so if you have a broken app, there is nothing I can do at this point. The next step would be for you to contact the developer of your ROM and have them correctly modify the apps and jar files to ensure capability.
NOTE: AxisM users, do not flash this script. The one included in the ROM has more features that are ROM specific. This script is just for anyone else to use on any other ROM.
The available choices in this script are as follows (this list will be updated with every release):
Clean cache (RAM boost)
Enable zRAM
Clean SQlite database files
Zipalign applications
Fix permissions
Odex
A quick note about zRAM
zRAM is a Linux kernel module that basically allows for real-time compression of memory objects that are in RAM/memory. This essentially makes it possible for the RAM to hold more apps in memory which may potentially == greater performance. Unfortunately, no known kernel on the US SGS3 currently supports zRAM, but when one pops up, this script will be available to initialize and optimize the feature.​
STEPS TO INSTALL
Download one of the attached Axis_Shell packages and move it to your SD card
Boot into recovery
Flash the Axis_Shell package
Reboot
STEPS TO USE
You can use this script either from within your phone or via ADB Shell. To use the script from your phone you must have a terminal emulator app in which you will type the following lines one by one:
Code:
su
axis
If using ADB Shell just type:
Code:
adb shell
axis
Thanks
Tommytomatoe
CyanogenMod

Let me know what else you would like to see in future releases.

Hero said:
Let me know what else you would like to see in future releases.
Click to expand...
Click to collapse
Excellente Chris, Thanks for this!

is this inculdeed in your rom or do i have to flash this

Hero said:
NOTE: AxisM users, do not flash this script. The one included in the ROM has more features that are ROM specific. This script is just for anyone else to use on any other ROM.
Click to expand...
Click to collapse
phoenixaldana01 said:
is this inculdeed in your rom or do i have to flash this
Click to expand...
Click to collapse
It's in the first post.

I know tried to delete post but didn't let me
Sent from my SCH-I535 using xda app-developers app

Failed install for me on stock rooted, tried to manually move everything over and set permissions...still no go. Says I'm missing grep and cut. Any thoughts?

B3L13V3 said:
Failed install for me on stock rooted, tried to manually move everything over and set permissions...still no go. Says I'm missing grep and cut. Any thoughts?
Click to expand...
Click to collapse
same issue here on MOAR w/ CWM touch

B3L13V3 said:
Failed install for me on stock rooted, tried to manually move everything over and set permissions...still no go. Says I'm missing grep and cut. Any thoughts?
Click to expand...
Click to collapse
Fails to flash the zip. I am using TWRP 2.5.0.0.
Sent from my SCH-I535 using Tapatalk 2

Sorry guys, I just uploaded a new version to the OP. I tested it and it works
Just a note, I did remove odex for the time being because I discovered an error within the script. It will be re-added when I work out the kinks.

Hero said:
Sorry guys, I just uploaded a new version to the OP. I tested it and it works
Just a note, I did remove odex for the time being because I discovered an error within the script. It will be re-added when I work out the kinks.
Click to expand...
Click to collapse
Damn that's exactly what I wanted lol oh well guess it's time to flash axis 19

I don't know if this is a bug in the script but when I'm done using the script and want to go back to the terminal (using terminal emulator app btw) I type "e" for exit like it says but it doesn't exit the script and go back to the terminal, it just starts the script over.
Sent from my SCH-I535 using xda app-developers app

[UTIL][WIN]I Don't Want You! || Get rid of unwanted mods || No data loss || No backup

Hi guys,
Have you ever installed a mod without making a backup before? Did the mod break your system or was not working the way you expected? The only way to recover the system to the previous state was to restore an old backup and loose all new data.
Thanks to my mod, this won't happen again! I present to you "I Don't Want You!".
It means NO NEED TO ALWAYS MAKE BACKUP BEFORE INSTALLING A MOD!
How it works?
It creates update.zip containing apps changed by mod in comparison to stock system and deleting files added by the mod to our system.
What it does?
-creates update.zip
-signs the zip
-Additionally: pulls /system from the device (using adb) (you need to do that once before installing mods instead of unpacking system manually form FTF/.zip file)
Requirements:
-Windows
-.NET Framework 4.5 or higher
-files installed/changed by mod (the content of mod's .zip file without META-INF)
-Recovery installed on your Android device
-Rooted android device
-Java
Compatibility:
Every device and every Android build!
It does not fully support mods with AROMA Installer
Currently It works only with mods influencing /system.
Screenshots:
{
"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"
}
DOWNLOAD
[MIRROR]
Be aware that I am a real beginner in programming and some bugs may occur, so I would be very thankful if you could tell me how my work could be improved and what to fix
Please leave a feedback below!
Do not mirror my files! Ask for permission before posting my work anywhere!​

CHANGELOG:
2.1(25.06.2015)
-fixed bug "zip not found"
2.0 (17.06.2015)
-now the update-binary will be taken from mod's zip file so the mod should be compatible with EVERY device
-added ability to extract the mod's zip file so you don't have to extract it by yourself
-no need to write the path now! just drag and drop the folder or file to the program's window!
1.6 (31.12.2014)
-fixed bug when there were no files to delete
-fixed permission
-should be signed now
1.5 (27.12.2014)
-FIXED CRASH DURING CLEANING UP
1.4 (27.12.2014)
-no need to give path to pulled system!
-fixed little bug when there are no files changed by the mod
1.3
-fixed icon
-fixed temp folder bug
BUGS:
-icon bugs
-some users experience ADB bugs if someone could help me with this one, I will be really grateful​

Maciek602 said:
[place for changelog&bugs]
Click to expand...
Click to collapse
This looks handy. Thanks for sharing. Hopefully I'll be able to test it in the next few days after switching roms.

Looks really handy...been looking for this

Too soon to ask for, but I will stick around for a Linux version to come out
Cheers till then.
Happy Holidays

Saatvik Shukla said:
Too soon to ask for, but I will stick around for a Linux version to come out
Cheers till then.
Happy Holidays
Click to expand...
Click to collapse
Would you like a port of it?

Can the update.zip be flashed with stock recovery?
(Probably not, but I don't have my PC around to check )
Sent from my D620r [Stock 4.4.2]

Vagelis1608 said:
Can the update.zip be flashed with stock recovery?
(Probably not, but I don't have my PC around to check )
Sent from my D620r [Stock 4.4.2]
Click to expand...
Click to collapse
Update.zip made by my tool should work on all recoverys using edify language. Please provide me an example of flashable zip for your recovery and I will check.
If It comes to porting the tool for linux, I need help in that matter as far as I am not using Linux and I haven't made any program for that system yet. Of course I will provide source code. Please contact me via PM. However you can try opening the tool with Wine. The ADB wont work but you can copy your /system manually and provide path to it in program.

Maciek602 said:
Update.zip made by my tool should work on all recoverys using edify language. Please provide me an example of flashable zip for your recovery and I will check.
Click to expand...
Click to collapse
Update.zip (attached) : http://forum.xda-developers.com/showthread.php?p=52214999
Sent from my D620r [Stock 4.4.2]

This doesn't also back up the modem/radio, does it?

Such a nice tool .....
Sent from my Moto G using XDA Free mobile app

Great job man!
Would you mind to put up kind of a noob tutorial with a brief description/explanation of what each option would exactly do?
...dont need to explain what the option "EXIT" will do though! Lol

RMarques said:
Great job man!
Would you mind to put up kind of a noob tutorial with a brief description/explanation of what each option would exactly do?
...dont need to explain what the option "EXIT" will do though! Lol
Click to expand...
Click to collapse
+1

Crashed
Looks like it copied /system but then failed at the last minute

Like jshare, crashed in last minute!

crashes during cleaning up process.....maybe add code to kill ADB and restart it before cleaning

@Vagelis1608
It should work
@ChazzMatt
Of course it doesn't! Currently it works only with /system mods.
@RMarques
The only options you need is:
1. For pulling system from your phone
2. To make update.zip (all other options are included in this one)
@jshare @Limac @Manvindar
Yeah, I forgot to add line for killing "adb" process in latest version, because I slightly rearranged whole code. I will upload fixed version in 10 min
UPDATE
I have uploaded fixed version!

Maciek602 said:
@Vagelis1608
It should work
@ChazzMatt
Of course it doesn't! Currently it works only with /system mods.
@RMarques
The only options you need is:
1. For pulling system from your phone
2. To make update.zip (all other options are included in this one)
@jshare @Limac @Manvindar
Yeah, I forgot to add line for killing "adb" process in latest version, because I slightly rearranged whole code. I will upload fixed version in 10 min
UPDATE
I have uploaded fixed version!
Click to expand...
Click to collapse
Backing up modem would be a neat feature.

There is a message saying "This app cannot be executed on your PC".
Im running Windows 8.1 64bits

Do you have .Net framework 4.5?