Related
Saurik's mempodroid exploit needs offsets of "exit" and "setresuid" functions calls in order to work.
Here's a tool that may find this two offsets while running on your ICS device and give you the mempodroid command line to run for gaining a temporary root shell.
This tool doesn't add any capability to Saurik's exploit.
Please let me know if you have any idea for improvement.
Feel free to use this tool, at your own risks.
1- download and unzip
2- push the two binaries to /data/local/tmp with adb
3- chmod 755
4- run n95-offsets
5- copy / paste the command line given by the tool
If the trick works, you will see the $ prompt change to a # one.
Hope it will help.
Hi,
don't work on HTC One X with 4.0.3.
cheers
starbase64
Already too old
Hi,
Mempodipper / mempodroid exploit uses a serious security hole in Linux kernels 2.6.39 and higher, making some noise in Linux' world. A patch has been given by Linus Torvalds himself late january.
It always take some times to deploy patched kernels but by now, most of them are probably mempodroid-resistants.
Wait for the next...
I just updated my samsung galaxy nexus from 4.0.2 to 4.0.4. Before that, I could root it using the command line provided by saurik:
Galaxy Nexus 4.0.2: 0xd7f4 0xad4b
Click to expand...
Click to collapse
source: https://github.com/saurik/mempodroid
After the update, I did not manage to root it so I came to this topic after some research on xda
Unfortunately, it looks the 4.0.4 update patches this hole on the galaxy nexus (or the n95-offsets tool does not work, which is probably not the case). Here for the record is what is returned by the tool:
[email protected]:/data/local/tmp $ ./n95-offsets
n95-offsets by Nesquick95
Gets requiered offsets for mempodroid exploit
./mempodroid 0xd7cc 0xad27 sh
1|[email protected]:/data/local/tmp $ ./mempodroid 0xd7cc 0xad27 sh
1|[email protected]:/data/local/tmp $
Click to expand...
Click to collapse
No root shell given. Any proof on the vulnerability beeing patched with 4.0.3 or 4.0.4?
No proof but...
Hi,
I've also lost mempodroid rooting capacity when upgrading my Galaxy Nexus from 4.0.2 to 4.0.4.
The tool can be wrong but I mainly think that the hole has been patched. But you're right, no proof of it until now
Nesquick95 said:
Hi,
I've also lost mempodroid rooting capacity when upgrading my Galaxy Nexus from 4.0.2 to 4.0.4.
The tool can be wrong but I mainly think that the hole has been patched. But you're right, no proof of it until now
Click to expand...
Click to collapse
Yes, I think that too. How did you managed to get the 4.0.4 rooted then? Did you unlock the bootloader or did you use another root exploit?
Unlocked
I've rooted 4.0.4 by unlocking the bootloader, flashing ClockworkMod recovery then an update.zip containing only the su binary.
I'd prefered keeping stock booloader locked but there is not so much kernels exploits around here for now and I ain't got time for testing other devices (Acer, Sony,...) specifics exploits on the Gnex...
If you're interested, you can take a look at Dan Rosenberg's works, in addition to all the great things already done here at XDA :
http://vulnfactory.org/blog/
Nesquick95 said:
Saurik's mempodroid exploit needs offsets of "exit" and "setresuid" functions calls in order to work.
Here's a tool that may find this two offsets while running on your ICS device and give you the mempodroid command line to run for gaining a temporary root shell.
This tool doesn't add any capability to Saurik's exploit.
Please let me know if you have any idea for improvement.
Feel free to use this tool, at your own risks.
1- download and unzip
2- push the two binaries to /data/local/tmp with adb
3- chmod 755
4- run n95-offsets
5- copy / paste the command line given by the tool
If the trick works, you will see the $ prompt change to a # one.
Hope it will help.
Click to expand...
Click to collapse
Hi Nesquick. I need to compile this source and mempodroid for a MIPS tablet (4.0.3 ICS and 3.0.8 kernel), since it seems that it cannot be rooted. Can't adb root or su. Do you think that it could be used or you can help generating the binaries for MIPS?
Thanks in advance
Hi,
Hard to say if it will work or not... Your 3.0.8 kernel may be a good candidate as long as it hasn't be mempodroid-patched by the tablet's provider.
I have Google NDK r7 installed, it offers only x86 and ARM support. It seems that MIPS support comes with r8 :
http://developer.android.com/sdk/ndk/index.html
You'll find the perl script used to compile my C programs attached (thanks to the author, Andrew Ross). I think t won't be to hard to adapt it to NDK r8 / MIPS platform...
the offsets of "exit" is wrong
Nesquick95 said:
Saurik's mempodroid exploit needs offsets of "exit" and "setresuid" functions calls in order to work.
Here's a tool that may find this two offsets while running on your ICS device and give you the mempodroid command line to run for gaining a temporary root shell.
This tool doesn't add any capability to Saurik's exploit.
Please let me know if you have any idea for improvement.
Feel free to use this tool, at your own risks.
1- download and unzip
2- push the two binaries to /data/local/tmp with adb
3- chmod 755
4- run n95-offsets
5- copy / paste the command line given by the tool
If the trick works, you will see the $ prompt change to a # one.
Hope it will help.
Click to expand...
Click to collapse
this is ok, great!!!
n95-offsets can work
olive360 said:
Hi, I get the offsets with n95-offsets
the offsets of "exit" is wrong
offsets of "setresuid" is right
my cell offsets is 0xd524 0xab8f
the offsets obtained with n95-offsets is 0x8003 0xab8f
Click to expand...
Click to collapse
sorry, i make a mistake, n95-offsets can work, i have rooted use it.
Thanks!!! It works with my Yifang / Mediacom MD 860 S2 (Generic ICS 4.0.4 tablet on a Cortex A9 platform)
Hi, I've Mediacom 715i (new one with 4.0.4), I've used n95-offsets to find the two offset, then I've executed mempodroid, but it doesn't work. still have '$' prompt. Any Idea?
About Busybox: busybox.net/about.html
More on Busybox: busybox.net
This is just for anyone who wants to try, and especially those without access to a PC.
:
: --------------- BUILD STEPS --------------
:
Things we'll need besides your phone:
- "Android Terminal Emulator" app
- "Complete Linux Installer" app , I also recommend trying "linux deploy" for more advanced usage
- internet/wifi
- latest "busybox" source
1) We need to get Ubuntu or Debian booted for a sufficient build environment (kali linux works well too). I've used them all on Android but I like the better stocked terminal in the Ubuntu images. I used the app "Complete Linux Installer" which is free and works beautifully, very simple and easy. In the app you want to follow the short instructions to download an Ubuntu image, rename it to ubuntu.img, and place it in a folder named ubuntu in /sdcard. Then hit menu in the app and click the terminal screen icon that says "Launch". An Ubuntu terminal will now open in Android Terminal Emulator. Super quick and easy.
2) Let's download some crucial build environment tools.
Code:
apt-get install -y gcc build-essential libncurses5-dev libpam0g-dev libsepol1-dev libselinux1-dev
--EDIT-(30AUG2014)--
For Selinux compatibility and loginutils, we need to also download a few extra packages. Already included in the code above.
3) Now the cool thing about this chroot Ubuntu environment is that we still have access to the sdcard to transfer files between Android environment and the chroot jail. Extract your downloaded busybox source to your Ubuntu home with something like:
Code:
cd
tar -xf /sdcard/Download/busybox*bz2
cd busybox*
4) Now we can build busybox statically. The first thing we do is generate a Makefile by running "make" with a "defconfig" (default configuration file) Usually you will run "./configure" with other programs, but busybox compiles more like a kernel, so it uses a config which has a huge checklist of options.
(After successfully compiling busybox, we can go back and customize the .config; this entails that for each "CONFIG ..." line we see, we can uncomment it and mark it "y" or "n" to configure some option... This can be more easily done from a terminal busybox menu interface with "make menuconfig". You just need to crank font down to 7 or use telnet/ssh)
Skip "make defconfig" if you use a customized ".config" file such as one I've attached.
Code:
make defconfig
If all goes well, we now have a Makefile and are ready to compile:
Code:
make clean && make LDFLAGS=-static
Let "make" crank out the binary for a couple minutes. The extra variable we set after make is to compile statically. When compiling is complete we'll have a few different busybox binaries at the root of the source directory. We use the one named "busybox" since we're not debugging.
5) Now let's copy it to /system/usr/bin to install for test usage.
Code:
cp ./busybox /android/data/media/0
(Open a new terminal tab to get into Android Environment)
mount -o remount,rw /system
mkdir -p /system/usr/bin
cp -f /sdcard/busybox /system/usr/bin
chmod 0555 /system/usr/bin/busybox
/system/usr/bin/busybox --install -s /system/usr/bin
mount -o remount,ro /system
PATH+=:/system/usr/bin
.. and done. Run some scripts and enjoy your static busybox!
:
: Extra steps for SELinux-enabled busybox
:
Here are the extra steps you need to take to compile busybox with SELinux features. Sorry it took so long to get this added to this first post.
First we need to download the source for libselinux and libsepol and compile it. (This is for use with the standard glibc toolchain.)
Code:
cd
apt-get source libselinux libsepol
cd libselinux*
make
cd
cd libsepol*
make
Now that we have those libraries compiled, we can proceed to the busybox compilation.
Code:
cd
cd busybox*
make clean && make LDFLAGS='-static -L ../libselinux*/src -L ../libsepol*/src' CFLAGS='-Os -I ../libselinux*/include -I ../libsepol*/include'
That's pretty much it. It initially seems more complicated than it actually is, but all we're really doing is including the libraries for libselinux and libsepol into the busybox compilation.
edit:
**Commands to run if you have compile errors:
Code:
apt-get build-dep busybox
apt-get install -y build-essential
apt-get -f update
dpkg --configure -a
:
: --------------- DOWNLOADS --------------
:
***** Attached are flash installers for busybox (v1.23.1 stable, non-SELinux, 374 applets included!, ~1.1MB size) or busybox (v1.23.1 stable, SELinux, 386 applets included!, ~1.6MB size) *****
Since it's up-to-date it has some nice extras most people haven't seen like a "-I" option for xargs! Yes, that is correct, busybox xargs has its testicles back.
Code:
e.g.
$ echo Hello | xargs -I{} echo {} world!
> Hello world!
: ---------- UPDATES ----------
-------------------EDIT-2-(30AUG2014)----------------------
Got a Selinux-enabled busybox attached now. This means Selinux flags are integrated into applets like ls, id, ps, etc, and there are now 12 extra Selinux applets to give a total of 386 applets, ~1.6MB in size. The previous one is more portable, but this one can completely replace toolbox and gives you Selinux control for Android 4.4+. Plus it's pure maxed-out awesomeness.
***I've also attached the .config files for each busybox I've compiled, so anybody can remake them (from their phone!) as I've posted. You just need to download and extract the .config file to the root of your busybox source directory and type "make".***
-------------------EDIT-3----------------------
YashdSaraf has made some very useful flash zips to install either the non-selinux- or selinux-enabled busybox 1.23.1 via recovery. Installation replaces the stock busybox in /system/xbin. I've attached the zips he made to the end of this OP.
(**Note: Thought I'd mention that there will be a handful of applets that don't work in "Android" environment such as su(don't worry this isn't linked with the installer) Part of this is because of the way Android's default file structure is an amputated modified version of linux. With almost all of them, slight modifications to environment and file structure can be made to get them to work. This is just normal behaviour of busybox in android. The su and init applets shouldn't be used in Android though. I keep them compiled into the binary anyway for completeness of the build and because they work and are needed for a root.gz initrd or some chroot environments. It also doesn't hurt keeping them compiled in. You just have to remember not to link them when installing busybox.
-------------------EDIT-4-(06SEPT2014)----------------------
:
: How to compile against(using) uclibc for a smaller binary!!
:
Download the attached arm-linux-uclibcgnueabi toolchain package that I pre-compiled. Extract to /data/media:
Code:
cd /data/media
zip='/sdcard/Download/2014-09-06__arm-buildroot-linux-uclibcgnueabi.tar.lz.zip'
unzip -op "$zip" | lzip -d | tar -xf -
Then let's open up the "Complete Linux Installer" or "Linux Deploy" terminal.
To use the toolchain with a busybox build, we just need to specify the parameter CROSS_COMPILE which is a prefix to the compiler tools. So if you extracted the toolchain to /data/media, you will use:
Code:
make clean && make LDFLAGS=-static CROSS_COMPILE=/android/data/media/arm-buildroot-linux-uclibcgnueabi/bin/arm-buildroot-linux-uclibcgnueabi-
When you're done you should have a busybox binary with 374 functions with size around 1.1MB. That's a 20% decrease in size from using the standard glibc toolchain!
**IMPORTANT Notes
- The toolchain can't be used with lollipop since it's not compiled with -fPIC. I'll fix this later. Busybox is fine since it's static, it's just the toolchain I uploaded.
- Selinux-enabled busybox .config errors out when building using the uclibc toolchain; I think this is a lack of support issue. In the "Complete Linux Installer" app you'll need to add the mount "/data/media" in options. This gives you access to it as "/android/data/media", very very useful for extra space needs.
Difference between SELinux and non-SELinux busybox
The SELinux (NSA security enhanced Linux) binary comes with the following extra utilities: chcon, getenforce, getsebool, load_policy, matchpathcon, restorecon, runcon, selinuxenabled, setenforce, setfiles, setsebool, and sestatus. There are also some selinux flags enabled for applets such as "ps" and "ls", e.g. "ps -Z" and "ls -Z" to show the context for processes or files. If you are using Android 4.3 or newer, then you probably want to use the SELinux-enabled busybox since Android 4.3 is when SELinux was introduced to Android. Using the SELinux busybox on older version of Android without SELinux file structure should probably work besides the SELinux applets, but I haven't tested this. The non-SELinux binary can be used on any version of Android. When it comes down to it, the system actually uses "/system/bin/toolbox" SELinux applets for SELinux operations, so unless you specifically want to use busybox's SELinux tools for personal use, the safest option is to go with the non-SELinux busybox. I use Android 4.3.1 and 5.x, so I use busybox's better featured SELinux tools.
Latest updates see post 2
Busybox 1.23.1 (2015-02-06) below
Busybox compilation on Linux
reserved
Great Info here!
But I would be interested to know how well this method works on Samsung Stock devices running AOS 4.2 and above? Any experience?
Awesome info, this thread came up #1 while googling busybox 1.23
I made a flashable zip of the attached binary in the op to clean the old one(if any) and install the new busybox in xbin, just in case if anyone needs it. :good:
Is it work on xperia sp on 4.3 fw yes ?
YashdSaraf said:
Awesome info, this thread came up #1 while googling busybox 1.23
I made a flashable zip of the attached binary in the op to clean the old one(if any) and install the new busybox in xbin, just in case if anyone needs it. :good:
Click to expand...
Click to collapse
Thanx,worx fine with Carbon 4.4.4 on my LG.
GREETZ FROM TEAM-OPTIMA!!!
E:V:A said:
Great Info here!
But I would be interested to know how well this method works on Samsung Stock devices running AOS 4.2 and above? Any experience?
Click to expand...
Click to collapse
Thanks man. I've been compiling tons of stuff with Debian and Ubuntu chroot no problem on top of 4.3.1 Vanir and also 4.4.4 Carbon, both are my daily drivers. "Complete Linux Installer" is pretty fast compared to some other chroot apps like GNUroot (no offense to GNUroot, it works but is way too slow). It runs real-time compared to non-chroot. When compared to my dual-core 2007 Pentium M laptop, it's about 2-3 times as slow which isn't too bad for compiling something like mksh or even busybox which takes up to 5 mins I'd say.
In terms of binary size, compiling natively is better than cross-compiling it seems. I used gcc with no size optimizations here, so 1.37MB is pretty nice compared to some others around 2MB with full configs. With this method and klcc (gcc wrapper) I got mksh compiled to 192KB. I'm currently trying to build a uclibc toolchain on my laptop that will give me a mksh binary under 300KB..
YashdSaraf said:
Awesome info, this thread came up #1 while googling busybox 1.23
I made a flashable zip of the attached binary in the op to clean the old one(if any) and install the new busybox in xbin, just in case if anyone needs it. :good:
Click to expand...
Click to collapse
Cool thanks man! That is really useful, glad to hear from CALIBAN that it works. Could I add this to the OP with credit to you?
Hamidreza2010 said:
Is it work on xperia sp on 4.3 fw yes ?
Click to expand...
Click to collapse
Yes, xperia sp uses armv7 so you should be good to go.
7175 said:
Cool thanks man! That is really useful, glad to hear from CALIBAN that it works. Could I add this to the OP with credit to you?
Click to expand...
Click to collapse
Sure bro go ahead
Edit: Went ahead and made one for selinux enabled busybox :silly: , you can add this one in the op too.
Hey guys I was able to get an entire uClibc toolchain built the other day (using buildroot). I tested it and it makes some nice small binaries with about 20%+ smaller size than the standard glibc. Man that took hours to compile but was well worth it. It really put the stability of Android OS to the test as well. Kitkat absolutely couldn't finish compiling with multiple oom's and oops's, but Vanir 4.3.1 stuck it out real nice. Once I had the huge amount of required buildroot packages downloaded, I was able to compile in TWRP as well with good stability. (I have the "Complete Linux Installer" startup chroot script aliased in my mkshrc so I can pull up an ubuntu terminal without starting the app. )
So I got 3 new attachments to OP:
- arm-linux-uclibc toolchain for anyone who wants to compile stuff with it (host=arm AND target=arm)
- busybox (374 fcns, non-selinux) 1116KB
- lzip binary (in case you need it to unzip the toolchain, which is highly compressed from 64MB to 14MB with lzip's lzma)
**As I mentioned in the updated OP, I wasn't able to get selinux-enabled busybox compiled with uclibc. This may be something unsupported, or there may be a patch fix. I'll check it out. I'll try with musl libc and musl-gcc as well.
I have another approach, I try aboriginal cross compiler toolchain in archLinux it produced small binary, but I can't compile busybox for android. For Linux it work. Maybe need bionic lib?
ndrancs said:
I have another approach, I try aboriginal cross compiler toolchain in archLinux it produced small binary, but I can't compile busybox for android. For Linux it work. Maybe need bionic lib?
Click to expand...
Click to collapse
Sounds interesting. I honestly haven't given this a try yet, but I'm very interested in taking a look at it. At this point I'm pretty much addicted to making the smallest binaries I can and testing out different toolchains. I'll give it a good search on duckduckgo, and if you have any insightful links that would be great.
Edit: Alright cool I found the source for Aboriginal Linux at landley.net/aboriginal and am building on Android now. I'm also trying this on my x86_64 laptop so that I can compare the differences like I have with glibc, uclibc, musl, klibc binary builds in a native environment and a cross-compile environment.
I see from my laptop's build that a busybox was generated, but it was dynamic and has a libc.so.6 dependency. @ndrancs : this might be what you were talking about. Did you try compiling static? Also see if "make allnoconfig && make clean && make LDFLAGS=-static" works for compiling busybox with Aboriginal Linux.
7175 said:
Edit: Alright cool I found the source for Aboriginal Linux at landley.net/aboriginal and am building on Android now. I'm also trying this on my x86_64 laptop so that I can compare the differences like I have with glibc, uclibc, musl, klibc binary builds in a native environment and a cross-compile environment.
I see from my laptop's build that a busybox was generated, but it was dynamic and has a libc.so.6 dependency. @ndrancs : this might be what you were talking about. Did you try compiling static? Also see if "make allnoconfig && make clean && make LDFLAGS=-static" works for compiling busybox with Aboriginal Linux.
Click to expand...
Click to collapse
I preferred to use uclibc I think it easy to setup and produced small binary.. Aboriginal cross-compiler use uclibc as default. Btw I don't use cmd : LDFLAGS=-static instead I set it in .config.. Maybe I try this later..
ndrancs said:
I preferred to use uclibc mk it easy to setup and produced small binary.. Aboriginal cross-compiler use uclibc as default. Btw I don't use cmd : LDFLAGS=-static instead I set it in .config.. Maybe I try this later..
Click to expand...
Click to collapse
Ok yeah I like how aboriginal set up with uclibc, and it has scripts for each build stage, so you can stop at the toolchain. I'll be interested to see their future releases with the musl libc as well.
Also for anyone interested, I figured out how to run dynamic binaries in android:
- make the directories "/lib" and "/lib/arm-linux-gnueabihf"
Code:
mkdir -p /lib/arm-linux-gnueabihf
- copy the linker "ld-linux-armhf.so.3" to "/lib"
- find a specific binary's dependencies: e.g. for dynamic mksh do:
Code:
strings mksh | grep \\.so
- copy the listed libs to "/lib/arm-linux-gnueabihf": e.g. for mksh that would be libc.so.6. The libs/linker you copy over will come from the mounted ubuntu/debian/... image you have mounted like with "Complete Linux Installer".
- adjust your LD_LIBRARY_PATH:
Code:
LD_LIBRARY_PATH=/lib:/lib/arm-linux-gnueabihf:$LD_LIBRARY_PATH
Any plan to update the busybox to current version. Thanks.
@7175 can you update flashable zip to 1.23.0 stable ?
@ndrancs @exodius48 : Thanks for notifying me guys, I needed to get around to updating to 1.23.0 stable. I updated the original post with no-edify installers for busybox 1.23.0 stable. There's a non-SELinux uclibc compiled version and a full 386-applet SELinux glibc compiled version. They're included in this post too for ease.
7175 said:
@ndrancs @exodius48 : Thanks for notifying me guys, I needed to get around to updating to 1.23.0 stable. I updated the original post with no-edify installers for busybox 1.23.0 stable. There's a non-SELinux uclibc compiled version and a full 386-applet SELinux glibc compiled version. They're included in this post too for ease.
Click to expand...
Click to collapse
Great..been waiting for this release.. :good:
Btw, can i use busybox_full_selinux.zip on android 4.2.2 MIUI rom?
exodius48 said:
Great..been waiting for this release.. :good:
Btw, can i use busybox_full_selinux.zip on android 4.2.2 MIUI rom?
Click to expand...
Click to collapse
Yeah that should work just fine. I'm pretty sure any SELinux tools or applet flags should work since 4.2 introduced SELinux to its filesystem. Let me know if there are any issues.
7175 said:
Yeah that should work just fine. I'm pretty sure any SELinux tools or applet flags should work since 4.2 introduced SELinux to its filesystem. Let me know if there are any issues.
Click to expand...
Click to collapse
Great release..busybox_full_selinux.zip working fine so far on MIUI rom V5 android 4.2.2. :victory:
7175 said:
@ndrancs @exodius48 : Thanks for notifying me guys, I needed to get around to updating to 1.23.0 stable. I updated the original post with no-edify installers for busybox 1.23.0 stable. There's a non-SELinux uclibc compiled version and a full 386-applet SELinux glibc compiled version. They're included in this post too for ease.
Click to expand...
Click to collapse
Hey @7175
Great guide. I am able to compile just fine on my device using your guide. However, is there any way to compile the selinux applets support using a Linux PC (or NDK)? I am not able to find a selinux supported toolchain. May be you can help.
Hi all,
I noticed that a new stable release of was released, BusyBox 1.23.2 - so I did download and compiled it in order to replace my old one.
If you want to try it on, I recommend you to put the binary file under the directory /system/xbin/ to keep it apart from the rest of your system files. Make sure that you have enabled the read and the execution permission flag (r-x).
I have included my .config file. Feel free to use and reconfigure it as you like.
The ARM cross compiler I have used is the recommended one on the BusyBox FAQ and you can download it http://landley.net/aboriginal/downloads/binaries/.
Good luck!
Note: I cannot guarantee its functionality on your device, it seems to work on my LG G3 D855.
Hey k02a,
thanks! I was looking for that, and installed it over the custom install feature and works flawless.
But there is one more thing, and maybe you can help me. I am looking for a tar version for android
that supports the --H ustar option like the linux one. To create odin packages within the phone.
I cannot find anything usefull for this. Any Idea? Maybe cross compile?
Cheers
NewBit
Good to hear that the binary worked on your device too!
Regarding the lack of flags and options in BuxyBox, I assume the developers have made a trade-off between functionality and binary size. - and in your case, the need for supporting the -H ustar format (e.g. for making Samsung/Odin images) have obviously not been considered.
Anyway, to get around this problem, I looked at my LG G3:s tar binary and discovered that it obviously supports the ustar format. I have included this file and hopefully you are able to use it as well. I hope this will help you a bit.
Kind regards,
k02a
Code:
[email protected]:/ $ /system/bin/tar --version
/system/bin/tar --version
tar (GNU tar) 1.16
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software. You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
...and this:
Code:
[email protected]:/ $ /system/bin/tar --help
...
Archive format selection:
-H, --format=FORMAT create archive of the given format
FORMAT is one of the following:
gnu GNU tar 1.13.x format
oldgnu GNU format as per tar <= 1.12
pax POSIX 1003.1-2001 (pax) format
posix same as pax
ustar POSIX 1003.1-1988 (ustar) format
...
Here is the MD5 hash sum:
Code:
[email protected]:/ $ busybox md5sum /system/bin/tar
busybox md5sum /system/bin/tar
d19775629f7f966e65bf1de7e2f695cf /system/bin/tar
Some kind of integrity verification in Linux (Slackware 14.1).
Code:
bash-4.3$ file tar; md5sum tar tar.zip
tar: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, stripped
d19775629f7f966e65bf1de7e2f695cf tar
e72aefb1060bc70725a1e2e0d432c9e0 tar.zip
Bamn, it's done! Thank you so much. It works great, this is exactly i was heading for! I own you a favour!
Btw: I have a Samsung Rugby Pro I547C with Android 4.1.2 and CWR.
Cheers
NewBit
I'm just glad to be of some help.
Take care
k02a
k02a said:
Hi all,
I noticed that a new stable release of was released, BusyBox 1.23.2 - so I did download and compiled it in order to replace my old one.
If you want to try it on, I recommend you to put the binary file under the directory /system/xbin/ to keep it apart from the rest of your system files. Make sure that you have enabled the read and the execution permission flag (r-x).
I have included my .config file. Feel free to use and reconfigure it as you like.
The ARM cross compiler I have used is the recommended one on the BusyBox FAQ and you can download it http://landley.net/aboriginal/downloads/binaries/.
Good luck!
Note: I cannot guarantee its functionality on your device, it seems to work on my LG G3 D855.
Click to expand...
Click to collapse
Im on samsung galaxy s4 i9500, i want to update my rom with this, can you provide a flashable zip? Or tell me how to replace this with my currently busybox?
HAYLCION said:
Im on samsung galaxy s4 i9500, i want to update my rom with this, can you provide a flashable zip? Or tell me how to replace this with my currently busybox?
Click to expand...
Click to collapse
I made one and it works for the I547, but on my S3 it wasn able to install over TWRP.
Maybe you can send me a working zip file for your S4 and I will mod it for you with the busybox bins.
Cheers
NewBit
newbit said:
I made one and it works for the I547, but on my S3 it wasn able to install over TWRP.
Maybe you can send me a working zip file for your S4 and I will mod it for you with the busybox bins.
Cheers
NewBit
Click to expand...
Click to collapse
Thnks , sorry what should i send you? You mean a busybox installer pakage?
HAYLCION said:
Thnks , sorry what should i send you? You mean a busybox installer pakage?
Click to expand...
Click to collapse
Nooo, the busybox installer pakage is actucally that what you wanted!?
I ment a working update zip for whatever, but known as runable. So I could just add the code
for install the busybox binary. Anyway, I guess you want root anyway!? So i've just updated
the Chainfire UPDATE-SuperSU-v2.46.zip, which is very universal, with the busybox_1.23.2_k02a version.
It worked on my S3 GT-I9300. So give it shot and me a feedback.
How do you proof if busybox is proper installed?
newbit said:
Nooo, the busybox installer pakage is actucally that what you wanted!?
I ment a working update zip for whatever, but known as runable. So I could just add the code
for install the busybox binary. Anyway, I guess you want root anyway!? So i've just updated
the Chainfire UPDATE-SuperSU-v2.46.zip, which is very universal, with the busybox_1.23.2_k02a version.
It worked on my S3 GT-I9300. So give it shot and me a feedback.
How do you proof if busybox is proper installed?
Click to expand...
Click to collapse
Seems goot , thanks
Great, you already seemed to solve it even before I logged in! :good:
newbit said:
How do you proof if busybox is proper installed?
Click to expand...
Click to collapse
Via Terminal Emulator or on ADB, you can type "busybox" after you got superuser's permissions and check the version.
@k02a Does this busybox support x86 intel device?
@k02a i rooted my lenovo a7000 today. busybox installer shows busybox 1.21.1-jb installed in /sbin. so do i need to install busybox 1.23.2 and where to install? /system/xbin? and if yes then do i need to uninstall older one from /sbin?
670 MB for download... for study...
Code:
AP_R600XXU1AQI8_usr.tar
BL_R600XXU1AQI8_usr.tar
CSC_OXA_R600OXA1AQI8_usr.tar
Download Link for OXA region... contains all CSC for SM-R600:
https://www.file-upload.net/download-12796748/R600XXU1AQI8_OXA.zip.html
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Still missing, maybe somebody can share the LDU XXX Version.
Thanx in advance.
Code:
COMBINATION-FT30_R600XXU1AQI4.tar
COMBINATION-FT30_R600XXU1AQI6.tar
LDU Live Demo Unit XXX
Code:
AP_R600[B][COLOR="Red"]X[/COLOR][/B]XXU1AQI6_usr.tar
BL_R600[COLOR="Red"][B]X[/B][/COLOR]XXU1AQI6_usr.tar
CSC_OXA_R600[B][COLOR="Red"]X[/COLOR][/B]OXA1AQI6_usr.tar
Best Regrds
What is tizen version
What is tizen version
Click to expand...
Click to collapse
In theory something with Tizen 3...
At the moment I am not 100 % sure if:
Code:
3.0.0.0
Maybe more something like this:
Code:
3.0.0.1
Best Regards
SM-R600 Bootloader...
R600XXU1AQI8
Code:
sboot.bin
cm.bin
Please ask before you try something "amazing"... and your Gear is dead...
OWN RISK!
For study... and maybe repair...
Best Regards
Meanhwile I have SM-R600 Firmware for study.. Thanx. :angel:
Next problem.
Old methods not work to unpack...
7zip nor ext4 unpacker work...
So they used something "new"...
Code:
nad_fw.bin
nad_refer.bin
In BL package... this 2 for me unknown files inside...
Maybe with some Google search I can find some usefull info...
Short XDA search...
https://forum.xda-developers.com/sitesearch.php?q=nad_fw.bin
https://forum.xda-developers.com/sitesearch.php?q=nad_refer.bin
Maybe this can lead to compatible Unpacker/Extractor...
Best Regards
For extraction I will try this... as other attempts failed...
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-extract-img-to-dump-t3673863
Will report if success...
Best Regards
Edit 1.
Attempt 1 fail...
SVAImgUnpack.exe ramdisk.img
Code:
SVAImgUnpack - Unpacker img to ext4. Version 2.1 from 30.04.2013
----------------------------------------------------------------
Source file: ramdisk.img (file size = 7.340.304 bytes)
Destination file: ramdisk.ext4.img
Unpacking ...
Header error: source file has wrong format! Program terminated.
Unpacking successfully done!
Press any key ...
Edit 2.
I can mount *.img files in Tizen Studio...
Emulator with Tizen 3 Mobile... as I need SD card feature... otherwise not enough space to mount and tar 1200 MB
Then simple "copy & paste"... with SDB
First I have waste my time with Wearable Image T3... and spent hours to realize that SD card option is not possible here...
No success with any "converter" Tools at the moment...
New idea is to mount in Tizen 3 Emulator... need some time for Copy & Paste...
Later more...
Meanwhile if sombody want take an look:
https://www.file-upload.net/download-12781791/CSC_OXA_R600OXA1AQI8_usr.tar.md5.zip.html
Only CSC + PIT inside...
I am toooo lazy to upload now... and it seems nobody else want R600 Firmware.
Best Regards
Code:
R600XXU1AQJ5
Seems updated to this Version...
Somebody knows the Changelog...
I am not able to find something similar like this...
http://doc.samsungmobile.com/SM-R760/CHC/doc.html
Not for XAR nor for DBT or other Sales Code...
Maybe depend on big or small letters... like here
http://doc.samsungmobile.com/sm-g930f/dbt/doc.html
Or Samsung work like this...
Ehne mehne mu und Du kriegst halt nix...
Best Regards
Oh, magic.
After 5 years of Development from Tizen 3.0 we reach:
Tizen 3.0.0.1
http://doc.samsungmobile.com/SM-R600/CHC/doc.html
Code:
R600XXU1AQJ5
Best Regards
P.S:
I have added Link in first post for Odin package...
Only as hint...
I downloaded COMBINATION-FT30_R600XXU1AQI6.tar.rar from some kind of free site, so 100% is not sure if this is really it. I will be grateful if anyone will check - https://www.dropbox.com/s/z6nvlob4f3ixoft/COMBINATION-FT30_R600XXU1AQI6.tar.rar?dl=0
Code:
COMBINATION-FT30_R600XXU1AQI6.tar.md5
:good:
Thanx for sharing.
I can not try self... as no SM-R600... but first look looks good.
Related to my first mistake with SM-R732... where I have first flashed the Live Demo Unit Firmware...
2 XX in Filename is correct for Retail device
3 XXX means "danger", because for LDU
Also no Rollback Prevention problem at the moment visible...
Code:
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI6
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI8
Both Firmware packages in same Software Revision. :good: :good:
So in theory...
We need only 1 brave tester.
I need some time to extract all files...
To check if Codes etc. maybe same or changed...
Best Regards
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-R600
SM-R600 Source for study available. :good:
Best Regards
I have extracted Combination Firmware in this way...
Still with help of Tizen Studio... Tizen 3 Mobile Emulator...
"Beta" Batch...
Code:
sdb root on
sdb push t3.tar /opt/media/SDCardC
sdb shell cd /opt/media/SDCardC
sdb shell tar -xvf t3.tar
sdb shell mkdir csc
sdb shell mkdir user
sdb shell mkdir ramdisk
sdb shell mkdir ramdisk-recovery
sdb shell mkdir system-data
sdb shell mkdir rootfs
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/csc
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/user
sdb shell mount -t ext4 -o loop,rw ramdisk.img /opt/media/SDCardC/ramdisk
sdb shell mount -t ext4 -o loop,rw ramdisk-recovery.img /opt/media/SDCardC/ramdisk-recovery
sdb shell mount -t ext4 -o loop,rw system-data.img /opt/media/SDCardC/system-data
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/rootfs
tar -cvf r600v1.tar rootfs
tar -cvf r600v2.tar csc
tar -cvf r600v3.tar user
tar -cvf r600v4.tar ramdisk
tar -cvf r600v5.tar ramdisk-recovery
tar -cvf r600v6.tar system-data
rm t3.tar
sdb pull *.tar
Maybe someone find other Tool or method to extract Tizen 3 Firmware...
Best Regards
Woooah, seems I was drunken with my "Beta" Batch file... for extracting *.img
Few really bad "mistakes"...
I made it few times now with line by line...
As my batch not work proper..
Meanhwile SM-R600 got new update:
Code:
R600XXU1AQK4/R600OXA1AQK4
At the moment I can again not find up2date Changelog...
Best Regards
Code:
COMBINATION-FT30_R600XXU1[B]AQL1[/B].tar.md5
Meanwhile new Combination Firmware floating around...
Only as info.
Best Regards
adfree said:
Code:
COMBINATION-FT30_R600XXU1AQI6.tar.md5
:good:
Thanx for sharing.
I can not try self... as no SM-R600... but first look looks good.
Related to my first mistake with SM-R732... where I have first flashed the Live Demo Unit Firmware...
2 XX in Filename is correct for Retail device
3 XXX means "danger", because for LDU
Also no Rollback Prevention problem at the moment visible...
Code:
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI6
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI8
Both Firmware packages in same Software Revision. :good: :good:
So in theory...
We need only 1 brave tester.
I need some time to extract all files...
To check if Codes etc. maybe same or changed...
Best Regards
Click to expand...
Click to collapse
I HAVE the live demo version. Can I Flash regular version of tizen onto live demo unit with any of the zip files in this forum? I'm very familiar with flashing via odin, i just can't tell if any of these will work on my unit?
Thanks for all the work @adfree! I have the Canadian SM-R600 (R600XXU1AQK4) and was wondering if you have had any success yet changing the CSC? I saw you played an active part in accomplishing that on the S3.
I'm by no means proficient in programming, but quite familiar with rooting, sdb, odin, etc. Let me know if I can help.
Cheers!
@detjoe
I have no SM-R600 for own tests...
1 user told me via PM he tried COMBINATION-FT30_R600XXU1AQI6.tar.md5 long time ago.
With no success in changing CSC...
He wrote...
Flashing no problem... Combination Firmware work... Code is same...
But after Reboot old CSC is back...
I have only idea it is maybe related to Product Code...
Maybe security increased... or maybe only no luck.. or maybe error in Combination Firmware...
Meanwhile also CQL1 as Combination Firmware "available":
Code:
[COLOR="Red"]COMBINATION-FT30_R600XXU1AQI4.tar.md5[/COLOR]
[COLOR="Green"][B]COMBINATION-FT30_R600XXU1AQI6.tar.md5[/B][/COLOR]
[COLOR="Red"]COMBINATION-FT30_R600XXU1AQL1.tar.md5[/COLOR]
Green means we have for free download... :good: and tested by 1 user
Red is only on paid sites...
Maybe with other Combination Firmware more luck...
Maybe if somebody is willing to test...
Own risk!
Best Regards
Edit 1.
SDB Tool is for instance here... with tiny Instruction how to connect via WiFi...
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
@mmafighter077
I wrote you PM...
No idea if you allready tried?
Best Regards
Hoping this works....
adfree said:
@mmafighter077
I wrote you PM...
No idea if you allready tried?
Best Regards
Click to expand...
Click to collapse
I'm hoping you guys get this to work.....I have a German version of the watch, but need it to be set for the US. I had the same issues as reported above with it swapping back to the original CSC.
Any update on this for you guys?
Hi Folks - The Info below is "obsolete" as @TheAirBlow found a New Version in the LAP$US Samsung leak ( something I didn't know was a thing ... show's how much attention I've been paying lately lol )
The newer version appears to support newer samsung firmwares which using lz4 files inside the tar's ( according to the license at least )
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux
Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in...
forum.xda-developers.com
[OLD POST BELOW]
Hi Folks
It's been a while since I posted here but I think it might be time for me to get involved again
Anyway I was reading the "Odin Downloader Release Notes.xls" and decided to translate the Korean to English. I was quite surprised to see that there was an Entry noting the release of "Odin V1.0 for Linux" ... WTF a Linux version of Odin. I figured I'd try to track this B**tard down and I've finally found one.
In some random Odin3 v3.12.7 Download I've discovered a binary called odin4 which looks legit. It's a command line tool.
The help looks like this
Code:
Usage : odin4 [args...]
Odin4 downloader. odin4 version 1.0.
-v SHOW VERSION
-w Show License
-b Add Bootloader file
-a Add AP image file
-c Add CP image file
-s Add CSC file
-u Add UMS file
-V Home binary validation check with pit file
-d Set a device path (detect automatically without this option)
-l Show downloadable devices path
IMPORTANT : You must set up your system to detect your device.
create this file: /etc/udev/rules.d/51-android.rules
to add a line to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
(http://developer.android.com/tools/device.html)
And you maybe need to unload a module cdc_acm before downloading.
$sudo rmmod cdc_acm
OR
echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf
Example :
$sudo rmmod cdc_acm
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
Example (Select One Device):
$odin4 -l
PATH_OF_DEVICE_A
PATH_OF_DEVICE_B
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A
and the beginning of the show license has
Code:
odin4 -w
Copyright(C) 2016 Samsung Electronics.Co, Ltd. All rights reserved.
the file output is as follows
Code:
odin4: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=bdec684a47ab0b2109cb60b1bea18e3878750f30, with debug_info, not stripped
Not stripped with debug info.. sounds interesting!
I've attached the Odin rar file I found it in if anyone is interesting in playing with it. I haven't managed to flash anything with it. although I was only attempting to flash a J320FN combination firmware.
Obviously use at your own risk etc etc.. and have fun!
trevd
Additional: I can confirm this works a treat on the Galaxy S6 at least ( SM-G920P ) :good:
[/QUOTE] I was only attempting to flash a J320FN [/QUOTE]
Well isn't that interesting. Is that the J3 series Samsung, that I have the J320, the J327 and the J337-V?
I decided to make an unexpected change to linux, currently on Ubuntu 14. So I have had to find new tools to work with. I'm not even sure this was really ever intended to work, but it does. Perfectly. restored a Galaxy S4 SM-S975L to stock using your linux based binary. Truly impressive.
---------- Post added at 05:09 PM ---------- Previous post was at 04:56 PM ----------
P.S. So far this has done everything the Windows based ODIN does. Just re-rooted with it too
It also works with newest of Samsung phones, flashed Galaxy G975U earlier, must decompress lz4 files and repack tar
kalexander7 said:
It also works with newest of Samsung phones, flashed Galaxy G975U earlier, must decompress lz4 files and repack tar
Click to expand...
Click to collapse
Yeah that's what I was doing with those newer firmwares. I did contemplate writing a bash wrapper to handle the lz4b stuff but never got round to it lol. I'm always hunting for a newer version which might slip out of Samsung by accident at some point.
Hi
Sorry for joining to this thread a few years later. I cannot find the odin4 .rar file that trevd is supposed to have uploaded. Could you pleae help?
Thanks
Would be nice if somebody has a download link for this, thanks.
feddozz said:
Hi
Sorry for joining to this thread a few years later. I cannot find the odin4 .rar file that trevd is supposed to have uploaded. Could you pleae help?
Thanks
Click to expand...
Click to collapse
Synt4x.93 said:
Would be nice if somebody has a download link for this, thanks.
Click to expand...
Click to collapse
Found one! There you go...
https://androidfilehost.com/?fid=674106145207484582
Another: https://androidfilehost.com/?fid=6006931924117939794
trevd said:
Hi Folks
It's been a while since I posted here but I think it might be time for me to get involved again
Anyway I was reading the "Odin Downloader Release Notes.xls" and decided to translate the Korean to English. I was quite surprised to see that there was an Entry noting the release of "Odin V1.0 for Linux" ... WTF a Linux version of Odin. I figured I'd try to track this B**tard down and I've finally found one.
In some random Odin3 v3.12.7 Download I've discovered a binary called odin4 which looks legit. It's a command line tool.
The help looks like this
Code:
Usage : odin4 [args...]
Odin4 downloader. odin4 version 1.0.
-v SHOW VERSION
-w Show License
-b Add Bootloader file
-a Add AP image file
-c Add CP image file
-s Add CSC file
-u Add UMS file
-V Home binary validation check with pit file
-d Set a device path (detect automatically without this option)
-l Show downloadable devices path
IMPORTANT : You must set up your system to detect your device.
create this file: /etc/udev/rules.d/51-android.rules
to add a line to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
(http://developer.android.com/tools/device.html)
And you maybe need to unload a module cdc_acm before downloading.
$sudo rmmod cdc_acm
OR
echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf
Example :
$sudo rmmod cdc_acm
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
Example (Select One Device):
$odin4 -l
PATH_OF_DEVICE_A
PATH_OF_DEVICE_B
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A
and the beginning of the show license has
Code:
odin4 -w
Copyright(C) 2016 Samsung Electronics.Co, Ltd. All rights reserved.
the file output is as follows
Code:
odin4: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=bdec684a47ab0b2109cb60b1bea18e3878750f30, with debug_info, not stripped
Not stripped with debug info.. sounds interesting!
I've attached the Odin rar file I found it in if anyone is interesting in playing with it. I haven't managed to flash anything with it. although I was only attempting to flash a J320FN combination firmware.
Obviously use at your own risk etc etc.. and have fun!
trevd
Click to expand...
Click to collapse
Hi, I realize that the binary you found is non exist in any other Odin download, even from it's official Odin Forum. I've been using Odin version that you've uploaded several times with big success. However, in my phone I can only flash Android 7.0 with this Odin version.
Now that I have a stock ROM for 9.0, this Odin version doesn't work. Even after I decompress lz4 and re-tar it again. After long digging on the internet, many told me that it was because I was using older version of Odin. Yours is 3.12, the latest now is 3.14. They suggested me to use newer version, little did they know I don't have Windows machine. Heimdall is a mess and never work on my Samsung, Jodin doesn't work as well.
I was wondering if you have newer version of Odin ? With binary as well ?
-------------------------------------------------------------------------------------------------------------------------
UPDATE
--------------------------------------------------------------------------------------------------------------------------
After changing ports and cable around 126722 times, I can confirm this Odin STILL WORKS !
I was able to flash a fresh ROM of Android 9 on my Samsung Galaxy S8.
TIPS : Use USB 3.0 cable, but not a fast charging cable. Fast charging cable didn't work on me at all. As for ports, port 3.0 works just fine
Only for flashing a fresh ROM. Rooting doesn't seem to work at all.
sheinbo said:
After changing ports and cables around 126721 times, I failed completely to get JODIN working - now I discover this thread- but I have to admit: I have not idea what exactly to do with odin4 (blame on me). So 2 questions: could anybody tell step by step what do do with that ODIN4 - and: did anybody flash A10 or A11?
Click to expand...
Click to collapse
1. I'm assuming you have a Linux machine ? This will run only in Linux terminal environment (or Mac -- perhaps). You can read the first post from the OP, he explains in detailed of how to use this tool (in example section), I don't think I could explain any better than the OP.
Download Odin4 from this thread, then extract it in a folder along with your extracted ROM. Inside your folder, right click and choose "Open in Terminal". Put your phone in Download mode, try to connect it 126721 times with a cable to your machine and start flashing from terminal with this code :
sudo chmod a+x odin4
./odin4 -b [your BL file] -a [your AP file] -c [your CP file] -s [your CSC file]
Click to expand...
Click to collapse
For better example, take a look at OP's original post. If flashing is succeed, your phone will restart automatically. If not, change the cable 126721 more times.
2. No. Haven't tried with A10 or A11