Develop Bugs

[Guide] preparation guide to running Ubuntu/debian on desire z

Ok , I know there is thread about debian running fine on desire z but the tutorial there is highly unfriendly and there are some other stuff you need to do to your desire z. This is my first guide. The reason for posting in dev thread is because chroot and loop requires specific kernel support to power Ubuntu.
Just to explain certain terms here...
Kernel - the interface for android to access hardware. Note that andorid is stripped down version of ubuntu and it does not have loopdevice support
Loopdevice - Imagine virtual disk mount program such as Daemon tools. This requires specifically supported kernels such
Following tutorial will void your warrenty (root and s off) but you can change to warrenty friendly state of course XD Check out xda wiki for more info( study to know what you are doing there.)
There are plenty of guides to get su and busybox( allows android system to be able to utilise more advanced commands) so check out comprehensive guides for g2 and desirez in this wiki below is my version
-------------------------------------------------------------------------
If your phone is stock, do a lot of research before doing root and s off. cyanogenmod has good guide on wiki for you to s off and get permanet root. Just for you to know, s off is to disable security for us to flash new kernel with loopback support and root is well... needed for most of hacks in XDA XD
*note for noobs: this is tested with desire z but G2 should not have problems. just be careful of which device's gfree you are using to s off.
ENGINEERING HBOOT IS NOT REQUIRED FOR THIS AND IS NOT RECOMMENDED FOR YOU TO DO SO AS IT MAY BRICK YOUR PHONE YOU SHOULD NOT HAVE PROBLEMS FLASHING CUSTOM ROM/KERNEL WITHOUT IT (guides are confusing if custom roms require flashing hboot)
Preparation:
1. busybox (install titanium backup and under problems? you can install busybox in a easy way)
2. Recommended: Clockwork recovery(rom manager in market)
3.Root and S off
4.Optional : remove or move sd card installed apps to internal memory or else LOOPDEVICE may be occupied and you may not be able to mount ubuntu. Do this if you encounter error (caused by app2 sd) please note that recent builds in xda mount loop device as 255 to avoid this problem.
You might want to use adb if necessary
5. android terminal from market
6. 2gb free space in sdcard (certain builds use 4gb as storage image, which is limit for fat32 system)
---------Kernel preparation ---------------------------------
Flashing necessary kernel
1. Download suitable kernel with loop device support. I am using cyanogen -> virtuous-kernel-cyanogen kernel from ://files.virtuousrom.com/vision/kernels/
(add http infront) on Stock HTC Sense Rom
2. To flash this, from rom manager, boot into clockworkmod recovery and select zip file to flash. Nandroid backup is recommended beforehand
-------------------------------------------------------------------
Now your phone has loopback support to chroot into UBUNTU or DEBIAN
Well, this method is not native ubuntu but it works fine.
You can now follow any guide on XDA like G1,nexus 1etc on running linux in android. I recommend nexus 1 hacks .com for ubuntu setup or thread "Debian for Desire" for debian setup (note debian seems to have problem with vnc) there are a lot of newbie frendly guides to do this without partitioning your sd card.
What can you do with them? You can use full android terminal , use vim , open office, gcc or eclipse etc ... makes your HTC Vision true small computer with keyboard . Enjoy
Possible solution to errors you encounter while following chroot tutorial for other android devices:
-----------------trouble shoot--------------------------------
Errors:
/device/loop is busy etc.... chroot: cannot execute /bin/bash etc... shutting down ubnutu etc....
Solution: 1. Get loopback support by flashing above kernel i mentioned
if not 2. TYPE SU BEFORE YOU RUN BOOTSCRIPT ON ANDROID TERMINAL
or if they say the bootscript is not found then type sh ./*your boot script name*
if not 3. move sd apps to phone as i mentioned eariler
Other errors could be from not installing busybox.
Note that in some cases, busybox is included inside the custom rom so you dont need to install it.
Post names of kernels with ability to run ubuntu for others to know.I did not test all of them.
This is my first guide on xda and i hope this helped xda in constructive way...
Post script: I will try my best to maintain quality of the posts to be up to xda standard. Thank you for constructive feedbacks...

quick problem i noticed
I'm running post ota de-odexed and I installed virtuous-kernel_vision_advanced-v1.0.9.zip in attempts to get loopdevice but now my phone doesn't react to an touch... hahaha it's no biggie I can't fix, just wanted to state out a weird outcome I have never seen before
But hey! Your prep guide is much appreciated!
EDIT: All of the 1.0.9 kernels seem to break my touch :/

you need virtuous-cyanogen 1.3 not standard vituous kennel. it is under cyanogen. Since it is developed for cyanogen, it should be fine for wide range of roms including sense roms but yes, it is buggy. I am looking for better kennel now....

squarememory said:
Ok , I know there is thread about debian running fine on desire z but the tutorial there is highly unfriendly and there are some other stuff you need to do to your desire z. This is my first guide. The reason for posting in dev thread is because chroot and loop requires specific kennel support to power Ubuntu. Well, do not attempt this unless you can use computer well XD
Following tutorial will void your warrenty (root and s off) but you can change to warrenty friendly state of course XD Check out xda wiki for more info( study to know what you are doing there.)
-------------------------------------------------------------------------
If your phone is stock, do a lot of research before doing root and s off. cyanogenmod has good guide on wiki for you to s off and get permanet root. Just for you to know, s off is to disable security for us to flash new kennel with loopback support and root is well... needed for most of hacks in XDA XD
*note for noobs: this is tested with desire z but G2 should not have problems. just be careful of which device's gfree you are using to s off.
ENGINEERING HBOOT IS NOT REQUIRED FOR THIS AND IS NOT RECOMMENDED FOR YOU TO DO SO AS IT MAY BRICK YOUR PHONE YOU SHOULD NOT HAVE PROBLEMS FLASHING CUSTOM ROM/KENNEL WITHOUT IT (guides are confusing if custom roms require flashing hboot)
----------------------------------------------------------------
Preparation:
1. busybox (install titanium backup and under problems? you can install busybox in a easy way)
2. Recommended: Clockwork recovery(rom manager in market)
3.Root and S off
4.Optional : remove or move sd card installed apps to internal memory or else LOOPDEVICE may be occupied and you may not be able to mount ubuntu. Do this if you encounter error (caused by app2 sd)...
adb if you want to type things in cmd
5. android terminal from market
6. 2gb free space in sdcard
---------Kernel preparation (may not be needed in some custom roms)---------------------------------
Flashing necessary kernel
1. Download suitable kernel with loop device support. I am using cyanogen -> virtuous-kennel-cyanogen kennel from ://files.virtuousrom.com/vision/kernels/
(add http infront) on Stock HTC Sense Rom
2. To flash this, from rom manager, boot into clockworkmod recovery and select zip file to flash. Nandroid backup is recommended beforehand
-------------------------------------------------------------------
Now your phone has loopback support to chroot into UBUNTU or DEBIAN
You can now follow any guide on XDA like G1,nexus 1etc on running linux in android. I recommend nexus 1 hacks .com for ubuntu setup or thread "Debian for Desire" for debian setup (note debian seems to have problem with vnc)
What can you do with them? You can use full android terminal , use vim , open office, gcc or eclipse etc ... makes your HTC Vision true small computer with keyboard . Enjoy
Possible solution to errors you encounter while following chroot tutorial for other android devices:
-----------------trouble shoot--------------------------------
Errors:
/device/loop is busy etc.... chroot: cannot execute /bin/bash etc... shutting down ubnutu etc....
Solution: 1. Get loopback support by flashing above kennel i mentioned
if not 2. TYPE SU BEFORE YOU RUN BOOTSCRIPT ON ANDROID TERMINAL
or if they say the bootscript is not found then type sh ./*your boot script name*
if not 3. move sd apps to phone as i mentioned eariler
Other errors could be from not installing busybox.
Note that in some cases, busybox is included inside the custom rom so you dont need to install it.
Post names of kennels with ability to run ubuntu for others to know.I did not test all of them.
This is my first guide on xda and i hope this helped xda in constructive way...
Click to expand...
Click to collapse
it's KERNEL! not KENNEL!

teh5abiking said:
it's KERNEL! not KENNEL!
Click to expand...
Click to collapse
Really dude? That was the only time he mispelled it and you the spelling police make a lousey post as if he mispelled it everytime...get a life
Sent from my HTC Vision using XDA Premium App

Well thanks for spelling correction. English is not my primary language

Spastic909 said:
Really dude? That was the only time he mispelled it and you the spelling police make a lousey post as if he mispelled it everytime...get a life
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Tell it spastic tell it!

xsteven77x said:
Tell it spastic tell it!
Click to expand...
Click to collapse
I thought you were insulting him XD

I have installed ubuntu without a hitch, but how do i fix the incorrect key bindings?

im thinking of using the technique that uses vnc to access ubuntu on my desire z. i am running 2.3.3 (cyanogenmod-7.1.0) on it. now forgive me for asking this its nearly 1am and im exhausted so my brain is not working right. which version of the kernel am i best getting for this? im a novice at it all but i do want to make sure i do it properly and dont brick my phone.

traumatism said:
im thinking of using the technique that uses vnc to access ubuntu on my desire z. i am running 2.3.3 (cyanogenmod-7.0.0) on it. now forgive me for asking this its nearly 1am and im exhausted so my brain is not working right. which version of the kernel am i best getting for this? im a novice at it all but i do want to make sure i do it properly and dont brick my phone.
Click to expand...
Click to collapse
This is a thread about installing ubuntu on the phone, not accessing it from the phone.

tsubus said:
This is a thread about installing ubuntu on the phone, not accessing it from the phone.
Click to expand...
Click to collapse
*facepalms* yes i know that. i will be installing it along side android and using vnc to access it locally. its a method i wish to use but i need the kernel for installing ubuntu and want to know which one. i shoulda made it more clear really.

ive just tried flashing the latest kernel for cyanogen with 7.1 but it freezes at the HTC screen on boot. any assistance will be apreciated

[Q] Can't start vncserver in Debian chroot

well, this is something that has been giving me a headache for a good couple months now. For starters, I can't seem to mount a Debian image on my G2, so I went and loaded it onto my sdcard on a ext2 partition using the debootstrap second option using Kubuntu.
Anyway, after mounting <code>/dev/block/vold:179:34</code> to <code>/data/local/mnt</code> and chrooting to /bin/bash I am at the terminal. What I can't do, however, is get xserver-xorg working, or any program that depends on it, which for some reason includes tightvncserver. I get an error about broken packages every time.
I've tried downloading and installing each package manually, but i still can't get tightvncserver running
I THINK I need to compile a display driver in order to get x11 working from a sdcard, but that's a little beyond me since I cant seem to find the right kernel for mah phone.
If anyone has any advice I'd love to hear it.
BTW Im using Cyanogenmod 6 (7 now) on my phone, both with pershoot's OC and stock toxygen.
Thanks!

[Q] Trouble uninstalling debian kit

I installed debian squeeze lately with debian kit.
However, I have a 2GB sdcard, and it uses it for storage, and I ran out of space, and decided to delete some files that I don't need. So, I deleted debian.img as it was over 500M, but now I can't uninstall it.
Whenever I run
Code:
deb u
or similar to uninstall debian on my device, it gives me the following error:
Code:
/storage/sdcard0/debian.img not found. You may re-insert your SD-Card and/or unplug USB
What could I do, as if I try to reinstall it, it says
Code:
You currently have a Debian file system mounted. Start 'deb u' to unmount first.
and
Code:
deb u
gives
Code:
/storage/sdcard0/debian.img not found. You may re-insert your SD-Card and/or unplug USB

Hey know exactly what ya are going though.
First off if the debian.img has been deleted, then deb u isn't going to help as its trying to unmount something that is gone.
Instead reboot your device and either rerun the install with the
/sdcard/download/debian-kit*
or run
/data/local/deb/uninstall
to uninstall the package from the devices' internal memory and start from scratch
or run
/data/local/deb/mk-debian -h
from where you are currently to make a brand new img on your sdcard.
Mainly read the readme that came with debian kit or wait a few days as I'm currently writing a guide that should clear up most of the issues that I've seen.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

Hey its been awile and didn't hear anything back from you so I hope you got it solved.
If not the draft to my debian kit guide is in my signature. Feel free to question and coment. I'll be posting up on the forems here once I get back to my computer so that I can keep the formatting and stuff clean.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
link to guide for Debian Kit I'm working on for you.
https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=sharing

It works well thanks

abiolaxpac said:
It works well thanks
Click to expand...
Click to collapse
Good and welcome
I've stayed busy making new content and scripts for adding more features, link update in signature sums it up, if you've got any requests feel free to post them. I've a few things to wrap up and some new projects to start/finish; Android to Android rooting, Android to Android 3g/4g communications, cloud services, and adaptive 3D sound playback.
Sent from either my SPH-D700 or myTouch3Gs
Debian Kit/QEMU Linux Install guide for all android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Now have working Installers for ARM Java 7 JDK + Maptools + jMonkey

[Q] HTC 1 Mini WILL NOT INSTALL BUSYBOX

HTC One Mini - AT&T
Tried installing Busybox from GooglePlay .apk, FAILED.
Now what?
I'm guessing I have root, not sure how to be completely sure.
Unlocked fastboot, flashed recovery w/ orange, installed SU from .zip
Gave BB SU permission.
FAILED.
Now what? I need BB. Tried looking for flashable .zip to flash from orange, but can't find any DL's.
S = ON :/
I have no idea where to begin fixing this issue...

On a side note...
Still can't find flashable .zip BB version.
Tried using Jrummy BB installer w/ root, still crashes.
Someone help before I manually brick this POS... i.e. throw it at a brick wall....

I just did a search on Google it said you need an app called busy box installer from the playstore
Sent from my GT-P3113 using xda app-developers app

.APK Method/Apps DO NOT WORK.
djerk said:
I just did a search on Google it said you need an app called busy box installer from the playstore
Click to expand...
Click to collapse
They do not work. Both of these:
google*com/store/apps/details?id=stericson.busybox[/url]
google*com/store/apps/details?id=com.jrummy.busybox.installer[/url]
(Official GooglePlay Online Store)
...either crash/reboot during "Advanced/smart" install, or fail using "Normal" install.
I need to to turn "S" off to enable write to nand possibly?
Tried both /xbin/ and /bin/ install directory through .apk
Also tried both Advanced & Normal install on both apps...
OP Specifically says .apk method = FAIL....
Next answer please, lol

Also....
I also verified root, it's there. Both .apk's (Apps) had SU privelage.
Even restarted the apps to make sure they had SU right from the beginning of their loading.
So to summarize:
AT&T HTC One mini
- fastboot : UNLOCKED
- recovery flashed : recovery-clockwork-touch-6.0.3.6-m4.img
- gained root : ClockWorkMod loaded "root.zip" (.zip courtesy root-wiki)
- DL'ed BusyBox .apk's : TWO FAILURES.
- And here I am....
Android version : 4.2.2
HTC Sense Ver : 5.0
Software number : 1.24.502.3
HTC SDK API level : 5.41
Kernel version:
- 3.4.10-10-gae2031e
[email protected] #1
SMP PREEMPT
Baseband version : 1.19.40d.00.14_10.20.40.4408L
Build number : 1.24.502.3 CL224405 release-keys
Browser version : Webkit/534.30

Moderator please move post
Move post to "AT&T HTC One Q&A"
Plz & TY:angel:

I just installed busy box with no issues on my Verizon htc one running 4.3 maybe you have the wrong version for 4.22
Sent from my GT-P3113 using xda app-developers app

Which ver?
djerk said:
I just installed busy box with no issues on my Verizon htc one running 4.3 maybe you have the wrong version for 4.22
Click to expand...
Click to collapse
Which version of Busy did you use?
1.20.2
1.20.1
1.20
1.19
or earlier?

screens
Here's my screens

I installed version 1.22.1
Sent from my GT-P3113 using xda app-developers app

This needs to be in proper section. This is the HTC One Verizon section. Not mini.
http://forum.xda-developers.com/htc-one-mini
Typed on a HTCone via rumrunners

I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip

cmlusco said:
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
Click to expand...
Click to collapse
DL'ed your .zip, but i'm waiting to figure out if my Mini has this "ext4" formating.
I don't know how to check if it does, and I don't want to flash something w/o knowing more.
I know ext4 is the newest? linux file structure, but I'm not sure if my Mini is formatted to it....
Anybody know how to check this?
The Mini when hooked up to a PC is recognizable as an external storage device,
so doesn't that mean its FAT or NTFS if windows can recognize it? Right?
Windows won't automatically recognize ext4 w/o installing something right?
If you have to alter or change your phone to ext4, then mine is not. I have never formatted my phone.
How can I check if this is safe for my phone?
I plan on using ClockworkMod to install this through the GUI.
What exactly is this "recovery-flashable-busybox"?
Does it get flashed over top of my recovery partition?
If so, does that mean I will lose my clockworkmod recovery?
Somehow with no idea what I was doing, I managed to unlock fastboot, and get SU.
Now I'm thinking I have no real idea of how this all works......
I would feel more comfortable installing BusyBox using an .APK because I'm a n00b
at this with an expensive toy that i don't want to break.... Like I mentioned before, would
turning S "off", would that allow me to use an .APK to install BusyBox? Or did my two .APK
installations I attempted before fail bc my internal "emulated" SD card is not formatted to
"ext3/4"? I'm lost now...
I guess in summary I need to know WHY I can't install busybox via GooglePlay .APK's,
and is this .zip safe for me to use, and if it is, how would I even use it?

It seems like the more answers I get, the more complications and questions I have...
How would I message or get help from somebody "high up" on this forum, somebody that knows all the in and outs?
I'm not gunna lie, I need a "babysitter" for this....
All I want to do is install Busybox, and after that I'm good, I don't need to play around with the "sensitive internals" of my phone.
I don't want any special roms, or anything else special. I just want SU privelages, and busybox installed.
Soooo.... how do I find a babysitter lol....
cmlusco said:
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
Click to expand...
Click to collapse
Also, I forgot to ask, did you mean can my phone "READ" ext3/4, or did you mean is my device "FORMATTED" to ext3/4
Neither of which do I know how to check or verify, but it would at least tell me what to do next i guess....

I think I'm may be on to something... The Util's known as "BusyBox", are a bunch of basic/necessary/commonly.used Linux commands wrapped up in a package, correct? So if they are Linux commands, then they probably have to be written to a Linux formatted partition? Correct? And if they are Linux commands, on a Linux partition, then that means my phone must be able to "speak" Linux? Correct?
So essentially I need to create an ext3/4 partition, and then write/install BusyBox to that partition?
Is my assumption correct?
Now another assumption is that the .APK's I want to use, which require these Linux commands, act as an interpreter to translate these Linux commands for my phone? Essentially, my phone does not need to speak Linux bc the .APK's know how to use the Linux commands "automatically" or "within themselves" so to speak?

lgally80 said:
I think I'm may be on to something... The Util's known as "BusyBox", are a bunch of basic/necessary/commonly.used Linux commands wrapped up in a package, correct? So if they are Linux commands, then they probably have to be written to a Linux formatted partition? Correct? And if they are Linux commands, on a Linux partition, then that means my phone must be able to "speak" Linux? Correct?
So essentially I need to create an ext3/4 partition, and then write/install BusyBox to that partition?
Is my assumption correct?
Now another assumption is that the .APK's I want to use, which require these Linux commands, act as an interpreter to translate these Linux commands for my phone? Essentially, my phone does not need to speak Linux bc the .APK's know how to use the Linux commands "automatically" or "within themselves" so to speak?
Click to expand...
Click to collapse
All you need to do is flash it thru recovery. If your phones partitions are not formated ext4, the install will fail before anything is ever changed.
To find out how there fornated type mount into a terminal emulator, or at an adb shell. Look for lines with /system and /cache. In those same lines it will say ext4, ext3, etc. If there not ext4 tell me, and i will edit the flashable with the correct partitions.
All this zip does is install the busybox binary file to /system/xbin, and then make the appropirate symlinks.
Yes i reccomend getting s-off. The reason the apk wont work is because your s-on and have a secured boot.img
Busybox is a bunch of linux commands rolled into one. Your phone is already linux, but busybox puts all these commands in one place, and adds some additiinal commands not native to the phone.

Your partitions are most likely ext4 as the regular one is. Are you sure you have an unsecured boot img installed. Pretty sure busy box won't work without one. If you are not s off flashing a rom will not change the boot img. You will have to extract the image and flash via fastboot manually.
Typed on a HTCone via rumrunners

Sounds good, hopefully w this info I can move on, stuck at the laundrmat w my b**** gf, so ill post results in or about 2 hours. Thnx in adv.:good:

Hello guys, I've been trying to install BusyBox myself too today, but without success.
The flashable via Recovery Mode linked file is dead.
Could somebody please re-upload the file ?
Thanks!

htc_one_mini_m4 said:
Hello guys, I've been trying to install BusyBox myself too today, but without success.
The flashable via Recovery Mode linked file is dead.
Could somebody please re-upload the file ?
Thanks!
Click to expand...
Click to collapse
http://vzw1files.dyndns.org/BUSYBOX/busybox_recovery_flashable.zip

[Q]Looking for some guidence (zips & updater-binaries)

Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}

Dude360 said:
Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}
Click to expand...
Click to collapse
What is it you are flashing exactly? And which recovery are you using? Could be a problem with the recovery you use

I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.

Dude360 said:
I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.
Click to expand...
Click to collapse
TWRP will not work with older update-binary. Could you upload an example zip which does not flash ?

This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!

Dude360 said:
This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!
Click to expand...
Click to collapse
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.

aWFSuser said:
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
Click to expand...
Click to collapse
That error would make sense then, reverting to an older binary.
From memory, Ive used these binaries myself on:
Desire
CWM 5x, 6x
EXT4 Recovery All versions
Desire HD:
CWM 5x, 6x
EXT4 Recovery All versions
Nexus 4:
CWM 5x (I think it was)
TWRP 2.x to latest
Nexus 7:
TWRP 2.x to latest
Samsung S2
Aman Ra I think its called
Transformer 101
CWM 5x (I think)
Nook Simple Touch:
CWM 5x
OUYA:
CWM 5x
Tesco HUDL
CWM 5x
Several Cheap Chinese Tabs with CWM 5x
And as far as I know they've been used on the rest of the ROMCleaner devices as well, but have no idea about the recoveries as I was on hiatus for some of them.
Sensation
Incredible S
One X
One S
EVO 4G LTE
HTC One (m7)
HTC One (m8)
GNex
TF201
Galaxy S3
Galaxy Note II
Galaxy S4
I remember we did a LOT of testing with updater binaries to find one that was compatible with as many devices as possible but at the time none of us had access to a WFS hence why we were never able to check with them.
We we quite surprised that this one worked with everything we tested and tbh I cant even remember where it came from and Its still running on everything we throw at it!
aWFSuser said:
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.
Click to expand...
Click to collapse
I was using PA at the time, same error with CM11 though.
At the end of the day, the binary can be worked around. The romcleaner binary not working is (child status 4 error) cant!
Im beginning to think its definitely a recovery incompatibility, maybe the way it has to be compiled to run on ARM6 or maybe just particular to the WFS.
The romcleaner binary hasnt changed either and is running on the above devices as well.