How to root MEDION LIFETAB S10333? - General Questions and Answers

Hi!
I have trouble with rooting my MEDION LIFETAB S10333. This tablet runs Android 4.4.2, so I tried to run psneuter exploit but Android shell returned error: "FATAL: Kernel is too old Aborted".
After this I tried to install Magisk via adb and program returned error: "Failure [INSTALL_FAILED_OLDER_SDK]". Then I tried to root this device via towelroot and kingoroot to no effect.
Do you know other ways to root this tablet?
Kernel version: 3.0.36+
Regards!

AFAIK Magisk only is supported on devices running Android 6.0 ( released 2015 ) - API-level 23 - and higher.
You can try to temporarily root your tablet's Android by means of ADB if you have a su binary what is matching Android 4.4 at your hand.
FYI:
Android 4.4 ( released 2013 ) is API-level 19, today ( 2022 ) Android 12 ( released 2021 ) is API-level 31.

xXx yYy said:
AFAIK Magisk only is supported on devices running Android 6.0 ( released 2015 ) - API-level 23 - and higher.
You can try to temporarily root your tablet's Android by means of ADB if you have a su binary what is matching Android 4.4 at your hand.
FYI:
Android 4.4 ( released 2013 ) is API-level 19, today ( 2022 ) Android 12 ( released 2021 ) is API-level 31.
Click to expand...
Click to collapse
I cloned this github repo: https://github.com/jpacg/su-binary, then I tried to compile it but I got this error:
make[1]: Entering directory '/home/tomek/.bin/su-binary'
Android NDK: WARNING: Building static executable but APP_PLATFORM android-21 is not the latest API level android-31. Build may not succeed.
make[1]: Leaving directory '/home/tomek/.bin/su-binary'
make[1]: Entering directory '/home/tomek/.bin/su-binary'
[armeabi-v7a] Executable : su
ld: error: duplicate symbol: setxattr
>>> defined at common.c:113 (jni/su/common.c:113)
>>> ./obj/local/armeabi-v7a/objs/su/su/common.osetxattr)
>>> defined at syscalls-arm.S:1639 (out/soong/.intermediates/bionic/libc/syscalls-arm.S/gen/syscalls-arm.S:1639)
>>> syscalls-arm.o.text+0xE28) in archive /home/tomek/.bin/android_ndk/android-ndk-r23b/toolchains/llvm/prebuilt/linux-x86_64/bin/../sysroot/usr/lib/arm-linux-androideabi/21/libc.a
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [/home/tomek/.bin/android_ndk/android-ndk-r23b/build/core/build-binary.mk:728: obj/local/armeabi-v7a/su] Error 1
make[1]: Leaving directory '/home/tomek/.bin/su-binary'
make: *** [Makefile:5: build] Error 2

Related

[FIRMWARE]ME600GC-N-00.00.34R (chinese backflip)

So, currently the backflip is released in 3 markets:
USA under AT&T as the Backflip MB300
Brazil under Vivo as the Backflip MB300
and
China from motorola as the MB600
MOTOSTORE (chinese)
Currently there is know firmware released for the USA and BRAZIL versions, but it appears I was able to find the firmware for the ME600!!
The file found is ME600GC-N-00.00.34R.zip and contains MotusGC_N_00.00.34R-supermonster-customer.sbf
The original post (chinese) is available at ME600GC-N-00.00.34R - ME600/MB300/Backflip - Android
The direct download for the ZIP containg SBF is http://me600.net/files/ME600GC-N-00.00.34R.zip
I have not had time to do anything with the files, and anybody who uses this file is doing so at their own risk... no complaining to me about ruining your phone.
If you want track my progress at http://twitter.com/moosefist
So i decided to risk (NO brick created) it and tried flashing the file and RSDlite failed with this error:
Code:
23:50:41, March 23, 2010
Line: 563
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP
File: X:test_dev_usbflashcodeflashdllRDLOp.cpp
Device ID: 0
23:50:41, March 23, 2010
Line: 318
ERROR: Phone[0000]: Error jumping to RAM Downloader
File: X:test_dev_usbflashcodeflashdllRDLOp.cpp
Device ID: 0
23:50:41, March 23, 2010
Line: 1182
ERROR: Phone[0000]: Flash failed.
File: X:test_dev_usbflashcodeflashdllPST_FP_FlashThread.cpp
Device ID: 0
23:50:41, March 23, 2010
Line: 587
ERROR: Flash failure: Phone[0000]: Error sending JUMP command Device API Error: 0xE0030040 Address: 0xB00000 Command: JUMP (Error Code: e0030040),
Detailed Error Details: Direction of the Error=2000, Command Value=500000, Code Group Number=No Codegroup
File: X:test_dev_usbflashcodeflashdllFlashHdlr.cpp
Device ID: 0
you may need to put it in recovery mode as described here
androidin.net/bbs/thread-71604-1-1 .html

[Q] I bricked my XOOM

I tried to update my XOOM through FASTBOOT to ICS! i think i've done something wrong and i bricked it.
i Tried to flash it through RSD lite 5.0 and i keep getting error.
i copied the error log and it goes as:
"
19:03:03, February 14, 2012
Line: 2203
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
19:03:03, February 14, 2012
Line: 1045
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 2203
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 1045
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 546
ERROR: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
"
HELP PLZ !!!
omarykm said:
I tried to update my XOOM through FASTBOOT to ICS! i think i've done something wrong and i bricked it.
i Tried to flash it through RSD lite 5.0 and i keep getting error.
i copied the error log and it goes as:
"
19:03:03, February 14, 2012
Line: 2203
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
19:03:03, February 14, 2012
Line: 1045
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 2203
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 1045
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
19:03:05, February 14, 2012
Line: 546
ERROR: Unable to retrieve initialization values from INI file.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
"
HELP PLZ !!!
Click to expand...
Click to collapse
Please use one of the several good rooting guides available right here.
You can try this, but it's not the only one.
http://forum.xda-developers.com/showthread.php?t=1249798
RSD Lite really just doesn't work with the Xoom...we have our own, good tools.
Get familiar with them and use them, please.
okantomi said:
Please use one of the several good rooting guides available right here.
You can try this, but it's not the only one.
http://forum.xda-developers.com/showthread.php?t=1249798
RSD Lite really just doesn't work with the Xoom...we have our own, good tools.
Get familiar with them and use them, please.
Click to expand...
Click to collapse
ok i falshed the recovery img of Tiamat and i cant get the xoom to power on!!
I am new to this, sorry for bothering with silly questions!
now i can boot to recovery android (Tiamat) and fastboot. but i need something i can flash a SBF file to the XOOM ..
Go to Development, look for the EOS ICS Rom for your device, put it and the GApps 10.5 version on your micro sdcard, and flash the rom, and then the GApps file immediately after (follow the instructions in the thread) and enjoy.

[Q] conflict between android and linux "chroot' kernel

Hi its me again
I try to install my wireless key "based chipset RTL8187" under backtrack "chroot", but without success, believe in me, I had to go and solve a lot of problems in the "chroot" although I'm almost nil in linux, but now I'm stuck with this problem for several days, following a lot of tutorials here and elsewhere, I show you a few lines of command to develop;
[email protected]:~# modprobe rtl8187
FATAL: Could not load /lib/modules/3.1.10-10.6.1.15.3/modules.dep: No such file or directory
Click to expand...
Click to collapse
trying to install the driver
ifconfig wlan0 down
rmmod r8187 rtl8187 2>/dev/null
wget http://dl.aircrack-ng.org/drivers/rtl8187_linux_26.1010.zip
unzip rtl8187_linux_26.1010.zip
cd rtl8187_linux_26.1010.0622.2006/
wget http://patches.aircrack-ng.org/rtl8187_2.6.27.patch
wget http://patches.aircrack-ng.org/rtl8187_2.6.32.patch
tar xzf drv.tar.gz
tar xzf stack.tar.gz
patch -Np1 -i rtl8187_2.6.27.patch
patch -Np1 -i rtl8187_2.6.32.patch
make
make install
make -C /lib/modules/3.1.10-10.6.1.15.3/build M=/sdcard/BT5/rtl8187L_linux_1041.0209.2012/rtl8187 CC=gcc modules
make[1]: Entering directory `/lib/modules/3.1.10-10.6.1.15.3/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/3.1.10-10.6.1.15.3/build'
make: *** [modules] Error 2
make -C /lib/modules/3.1.10-10.6.1.15.3/build M=/sdcard/BT5/rtl8187L_linux_1041.0209.2012/rtl8187 CC=gcc modules
make[1]: Entering directory `/lib/modules/3.1.10-10.6.1.15.3/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/3.1.10-10.6.1.15.3/build'
make: *** [modules] Error 2
Click to expand...
Click to collapse
when I search for Linux realise
[email protected]:~# uname -a
Linux localhost 3.1.10-10.6.1.15.3 #1 SMP PREEMPT Wed May 1 13:26:11 CEST 2013 armv7l GNU/Linux
Click to expand...
Click to collapse
when I search for Linux headers
[email protected]:~# dpkg -l |grep header
ii foremost 1.5.7-bt0 A console program to recover files based on their headers, footers, and internal data structures.
ii libpcap0.8-dev 1.0.0-6 development library and header files for libpcap0.8
ii libssl-dev 0.9.8k-7ubuntu8.6 SSL development libraries, header files and documentation
ii linux-headers-2.6.31-607-imx51 2.6.31-607.13 Linux kernel headers for version 2.6.31 on I.MX51-based systems
ii linux-headers-2.6.32-204 2.6.32-204.16 Header files related to linux-mvl-dove kernel version 2.6.32
ii linux-headers-2.6.32-204-dove 2.6.32-204.16 Linux kernel headers for version 2.6.32 on dove-based systems
ii linux-headers-2.6.33-500 2.6.33-500.6 Header files related to linux-ti-omap kernel version 2.6.33
ii linux-headers-2.6.33-500-omap 2.6.33-500.6 Linux kernel headers for version 2.6.33 on OMAP3-based systems
ii linux-headers-dove 2.6.32.204.7 Generic Linux kernel headers
ii linux-headers-imx51 2.6.31.607.8 Linux kernel headers for imx51 machines
ii linux-headers-omap 2.6.33.500.2 Linux kernel headers -- omap
Click to expand...
Click to collapse
but there is no linux-headers-3.1.10-10.6.1.15.3
Also i installed module-assistant_0.11.6_all.deb and ran this command:
[email protected]:~# su -c 'm-a update && m-a prepare'
Updated infos about 42 packages
Getting source for kernel version: 3.1.10-10.6.1.15.3
apt-get install linux-headers-3.1.10-10.6.1.15.3
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package linux-headers-3.1.10-10.6.1.15.3
apt-get install build-essential
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
Click to expand...
Click to collapse
but no luck
I know that 3.1.10-10.6.1.15.3 kernel comes from the android Os, so it doesn't exist in the image of backtrack,
what can I do please !! and is there any way to get it work under Android instead of internal wifi ....thanks
what a deception

[Q] [Q&A]problems when build android-5.1.1_r2

Hello, everyone,
I'm using Ubuntu14.0.4 virtualbox virtual machine, the memory size is set as 2G. I set two more virtual disks(/disk_2nd for source code download, /disk_3rd for build output and the directory is android_out).
Java version is openjdk7 as required by android official website.
Git was rebuilt for openssl because of gnutls_handshake error during downloading source code.
I had met the problem caused by small swap so that I already set a new 8G swap partion(not swapfile).
Now I meet two problems during build the android-5.1.1_r2. I searched from web but can't find answer(looks someone met same problem but no answer). If someone can help, it will be very great. Thank you very much.
--------------------------------------------------------------------------------------------------------
1.
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: /disk_3rd/android_out/androidsource/host/linux-x86/obj32/SHARED_LIBRARIES/libjavacore_intermediates/luni/src/main/native/android_system_OsConstants.o: file is empty
libcore/luni/src/main/native/Register.cpp:36: error: undefined reference to 'register_android_system_OsConstants(_JNIEnv*)'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
2.
target Strip: libwebviewchromium (/disk_3rd/android_out/androidsource/target/product/generic/obj/lib/libwebviewchromium.so)
prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/arm-linux-androideabi-strip:/disk_3rd/android_out/androidsource/target/product/generic/symbols/system/lib/libwebviewchromium.so: File format not recognized
make: *** [/disk_3rd/android_out/androidsource/target/product/generic/obj/lib/libwebviewchromium.so] error 1
make: *** Waiting for unfinished work .....( It could be not exact the same words because I translate it from Chinese)

|Tutorial| How to build and install the new NetHunter|Marshmallow 6.0.1|

Hi guys.
Hope you all had a good Christmas , today i have a tutorial for you.
I will show you how to build the new version of NetHunter and install it to your device(must be a supported device,,see the list below)
-Nexus 4 (mako)
-Nexus 5 (hammerhead)
-Nexus 6 (shamu)
-Nexus 7 2012 (nakasi) and 2013 (razor)
-Nexus 9 (volantis)
-Nexus 10 (mantaray)
-One Plus One (bacon)
For my build setup i have Kali Linux installed in vmware, you could use virtualbox also.
If you have it installed on your pc,,more power to you.
So the requirements are:
-Have Kali Linux in a vm or installed on your pc(you could do the same thing on ubuntu,,but for the sake of it i use kali)
-A rooted supported android device(for marshmallow you should root your device with supersu 2.64 , as of the day i write this tutorial it's the latest)
Please note: this tutorial will not show you how to install linux neither how to root your android device.
I tested on a nexus 5 (my phone) and i have the latest marshmallow 6.0.1 on it and device is rooted.
It's not very complicated, if you ever built android roms or aosp from source it's a lot easier, the Nethunter guys made a script that pretty much
does it all by itself.
First thing , we will make a folder to work in, name it the way you want , i will just call it nethunter:
mkdir ~/nethunter
Then change directory into the folder you created:
cd ~/nethunter
Once inside the folder type:
Code:
git clone https://github.com/offensive-security/gcc-arm-linux-gnueabihf-4.7
After that we are going to clone the repo of the new installer branch like so:
Code:
git clone https://github.com/offensive-security/kali-nethunter.git -b newinstaller-fj
What we just done will created a folder named AnyKernel2 so we are going to change directory into it:
cd ~/nethunter/kali-nethunter/AnyKernel2
Then we are ready to build:
python build.py -d hammerhead -m (the -d means the device you are building for in my case it's a nexus 5 codename hammerhead,,and the -m means
marshmallow)
Once it's done,,you will have a zip file into the AnyKernel2 folder, and this is what you are going to flash in recovery to install NetHunter to your device.
The new installer is using aroma so you will be able to choose what to install.
On the first page or so you will be asked to install a version of SuperSu older than the one i provided you , untick this boxs, you don't want this to install and replace the version of SuperSu you curently have(2.64 ++)
When aroma will install it's probable that it will stuck at 40% for a couple of minutes, don't worry, let it do his things,,but if you are stuck there for more than
lets say 10 minutes just force shudown your device by holding the power button down and reboot,,Kali NetHunter should have been installed correctly anyway.
Make sure that once you boot with your new KaliNethunter go into the Kali app and update the chroot.
Also inside the Kali app "Check app update" from time to time since when there is a new thing added/fixed in Github it's just a matter of updating the app to get the update,,as easy as that.
That's about it, if you have any question feel free to ask.
**Big thanks to Binkybear and Jmingov who provided me usefull info**
Nethunter - chroot fails to install Nexus 5 - Cm13 nightly
jonathanxx1 said:
Hi guys.
Hope you all had a good Christmas , today i have a tutorial for you.
I will show you how to build the new version of NetHunter and install it to your device(must be a supported device,,see the list below)
-Nexus 4 (mako)
-Nexus 5 (hammerhead)
-Nexus 6 (shamu)
-Nexus 7 2012 (nakasi) and 2013 (razor)
-Nexus 9 (volantis)
-Nexus 10 (mantaray)
-One Plus One (bacon)
For my build setup i have Kali Linux installed in vmware, you could use virtualbox also.
If you have it installed on your pc,,more power to you.
So the requirements are:
-Have Kali Linux in a vm or installed on your pc(you could do the same thing on ubuntu,,but for the sake of it i use kali)
-A rooted supported android device(for marshmallow you should root your device with supersu 2.64 , as of the day i write this tutorial it's the latest)
Please note: this tutorial will not show you how to install linux neither how to root your android device.
I tested on a nexus 5 (my phone) and i have the latest marshmallow 6.0.1 on it and device is rooted.
It's not very complicated, if you ever built android roms or aosp from source it's a lot easier, the Nethunter guys made a script that pretty much
does it all by itself.
First thing , we will make a folder to work in, name it the way you want , i will just call it nethunter:
mkdir ~/nethunter
Then change directory into the folder you created:
cd ~/nethunter
Once inside the folder type:
Code:
git clone https://github.com/offensive-security/gcc-arm-linux-gnueabihf-4.7
After that we are going to clone the repo of the new installer branch like so:
Code:
git clone https://github.com/offensive-security/kali-nethunter.git -b newinstaller-fj
What we just done will created a folder named AnyKernel2 so we are going to change directory into it:
cd ~/nethunter/kali-nethunter/AnyKernel2
Then we are ready to build:
python build.py -d hammerhead -m (the -d means the device you are building for in my case it's a nexus 5 codename hammerhead,,and the -m means
marshmallow)
Once it's done,,you will have a zip file into the AnyKernel2 folder, and this is what you are going to flash in recovery to install NetHunter to your device.
The new installer is using aroma so you will be able to choose what to install.
On the first page or so you will be asked to install a version of SuperSu older than the one i provided you , untick this boxs, you don't want this to install and replace the version of SuperSu you curently have(2.64 ++)
When aroma will install it's probable that it will stuck at 40% for a couple of minutes, don't worry, let it do his things,,but if you are stuck there for more than
lets say 10 minutes just force shudown your device by holding the power button down and reboot,,Kali NetHunter should have been installed correctly anyway.
Make sure that once you boot with your new KaliNethunter go into the Kali app and update the chroot.
Also inside the Kali app "Check app update" from time to time since when there is a new thing added/fixed in Github it's just a matter of updating the app to get the update,,as easy as that.
That's about it, if you have any question feel free to ask.
**Big thanks to Binkybear and Jmingov who provided me usefull info**
Click to expand...
Click to collapse
I have followed the above instructions and was able to build and install nethunter.
- However, nethunter does not detect the wlan0 (screenshot attached)
- Installing chroot fails (download method)
- With very little that I know, I thought this must be the selinux in enforcing mode.
- Therefore I tried it again in permissive mode and still couldnt make progress.
Logs from catlog indicating the failure installing chroot
01-03 01:04:40.232 D/su (24412): Finishing su operation for app [uid:10146, pkgName: com.offsec.nethunter]
01-03 01:04:40.235 D/su (24410): sending code
01-03 01:04:40.235 D/su (24410): child exited
01-03 01:04:40.237 I/SuControllerImpl( 976): Got change
01-03 01:04:40.237 D/su (24408): client exited 0
01-03 01:04:40.377 E/Shell Error 6803): tar: seek failure: Value too large for defined data type
01-03 01:04:40.446 D/CreateChroot( 6803): Error:
01-03 01:04:40.446 D/CreateChroot( 6803): java.lang.RuntimeException: java.lang.RuntimeException
01-03 01:04:40.446 D/CreateChroot( 6803): at com.offsec.nethunter.utils.ShellExecuter.RunAsRootWithException(ShellExecuter.java:101)
01-03 01:04:40.446 D/CreateChroot( 6803): at com.offsec.nethunter.ChrootManagerFragment$UnziptarTask.doInBackground(ChrootManagerFragment.java:716)
01-03 01:04:40.446 D/CreateChroot( 6803): at com.offsec.nethunter.ChrootManagerFragment$UnziptarTask.doInBackground(ChrootManagerFragment.java:677)
01-03 01:04:40.446 D/CreateChroot( 6803): at android.os.AsyncTask$2.call(AsyncTask.java:295)
01-03 01:04:40.446 D/CreateChroot( 6803): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
01-03 01:04:40.446 D/CreateChroot( 6803): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
01-03 01:04:40.446 D/CreateChroot( 6803): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
01-03 01:04:40.446 D/CreateChroot( 6803): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
01-03 01:04:40.446 D/CreateChroot( 6803): at java.lang.Thread.run(Thread.java:818)
01-03 01:04:40.446 D/CreateChroot( 6803): Caused by: java.lang.RuntimeException
01-03 01:04:40.446 D/CreateChroot( 6803): at com.offsec.nethunter.utils.ShellExecuter.RunAsRootWithException(ShellExecuter.java:93)
01-03 01:04:40.446 D/CreateChroot( 6803): ... 8 more
Logs from install NH
3 Jan 2016 00:44:59 - New instalation log file: /storage/emulated/0/nh_install_20160103_124456.log
3 Jan 2016 00:45:06 - Starting download. Standby&
3 Jan 2016 00:54:02 - Chroot download completed: Total 620.0 MB.
3 Jan 2016 00:54:02 - Original SHA: 45AF3ED319E520B85693EDB2058A82B942F875A0C7F4729DD3E3EAE6F110C7D106A7423639A58C53247BE3E95BF977B2107877FDB0A77B6F7B06286E73E75151
3 Jan 2016 00:54:29 - Checking file integrity... MATCH
3 Jan 2016 00:54:29 - New SHA: 45AF3ED319E520B85693EDB2058A82B942F875A0C7F4729DD3E3EAE6F110C7D106A7423639A58C53247BE3E95BF977B2107877FDB0A77B6F7B06286E73E75151
3 Jan 2016 00:54:31 - Unzipping and untarring....
3 Jan 2016 00:54:31 - Uncompressing the Chroot& (~10 min)
3 Jan 2016 01:01:52 - Deploying the Chroot& (~510 min)
3 Jan 2016 01:04:40 - Error: java.lang.RuntimeException: java.lang.RuntimeException
3 Jan 2016 01:04:40 - CreateChroot >> Error: java.lang.RuntimeException: java.lang.RuntimeException
3 Jan 2016 01:15:19 - New instalation log file: /storage/emulated/0/nh_install_20160103_124456.log
Any help is appreciated.
Thanks,
[email protected]
From where do I to start for customise it for Galaxy S5 ?
I'm new in Rom cooking
---------- Post added at 06:59 PM ---------- Previous post was at 06:47 PM ----------
Hi friend
Would you please help me to start on customising nethunter for Galaxy S5
I'm new in Rom customisation..
Really confused..I don't know where to start

Categories

Resources