Related
Hi all,
I've just got my hands on the source code for the Buzz kernel and thought it would be a good starting point to build it from source without any changes.
I've got my cross-compile environment nicely set up, however, when building, I am halting at:
make[1]: *** No rule to make target `arch/arm/mach-msm/board-bee.o', needed by `arch/arm/mach-msm/built-in.o'. Stop.
This seems to be due to a problem in the Makefile:
Code:
# MSM7225 boards
obj-$(CONFIG_MACH_BUZZ) += board-buzz.o board-buzz-panel.o board-buzz-keypad.o board-buzz-microp.o
obj-$(CONFIG_MACH_BUZZ) += board-buzz-rfkill.o board-buzz-mmc.o board-buzz-wifi.o
obj-$(CONFIG_HTC_OFFMODE_CHARGING) += htc_offmode_charging.o
obj-$(CONFIG_MACH_BEE) += board-bee.o board-bee-panel.o board-bee-keypad.o board-bee-microp.o
obj-$(CONFIG_MACH_BEE) += board-bee-rfkill.o board-bee-mmc.o board-bee-wifi.o
obj-$(CONFIG_MACH_BUZZC) += board-buzzc.o board-buzzc-panel.o board-buzzc-keypad.o board-buzzc-microp.o
obj-$(CONFIG_MACH_BUZZC) += board-buzzc-rfkill.o board-buzzc-mmc.o board-buzzc-wifi.o
obj-$(CONFIG_MACH_PARADISE) += board-paradise.o board-paradise-panel.o board-paradise-keypad.o
obj-$(CONFIG_MACH_PARADISE) += board-paradise-rfkill.o board-paradise-wifi.o
obj-$(CONFIG_MACH_PARADISE) += board-paradise-mmc.o board-paradise-microp.o
obj-$(CONFIG_MACH_BAHAMAS) += board-bahamas.o board-click-panel.o board-bahamas-keypad.o
obj-$(CONFIG_MACH_BAHAMAS) += board-bahamas-mmc.o board-bahamas-rfkill.o
QUESTION 1: board-bee, board-bahamas and board-paradise are not included suffixes for the various boards in the kernel distribution; is the recommended course of action to remove these from the Makefile (as I am intending this kernel purely for Buzz)?
Doing so allows me to complete the build process.
The next step I am taking is to pack this into a boot.img file following the steps at: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
I'm using:
Code:
~/eclair/out/host/linux-x86/bin/mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel ./boot.img-kernel --ramdisk boot.img-ramdisk.cpio.gz -o boot-new.img
where ./boot-img-kernel is the zImage file at arch/arm/boot/
The ramdisk is exactly as I extracted from the device originally.
Finally, in recovery mode (clockworkmod) I executed:
Code:
# cat /dev/zero > /dev/mtd/mtd2
# flash_image boot /sdcard/boot-new.img
# reboot
However, on reboot the device never comes up and, obviously, I can therefore get no meaningful info from adb.
Booting the kernel in an emulator results in:
Command:
Code:
~/android-sdk-linux_86/tools/emulator -kernel ~/Desktop/buzz-2.6.29-534e5f81/arch/arm/boot/zImage -avd 2.1 -show-kernel -verbose -logcat *:v
Output:
Code:
emulator: found SDK root at /home/martin/android-sdk-linux_86
emulator: root virtual device file at /home/martin/.android/avd/2.1.ini
emulator: virtual device content at /home/martin/.android/avd/2.1.avd
emulator: virtual device config file: /home/martin/.android/avd/2.1.avd/config.ini
emulator: locking user data image at /home/martin/.android/avd/2.1.avd/userdata-qemu.img
emulator: locking cache image at /home/martin/.android/avd/2.1.avd/cache.img
emulator: locking SD Card image at /home/martin/.android/avd/2.1.avd/sdcard.img
emulator: found skin 'HVGA' in directory: /home/martin/android-sdk-linux_86/platforms/android-7/skins
emulator: autoconfig: -skin HVGA
emulator: autoconfig: -skindir /home/martin/android-sdk-linux_86/platforms/android-7/skins
emulator: keyset loaded from: /home/martin/.android/default.keyset
emulator: trying to load skin file '/home/martin/android-sdk-linux_86/platforms/android-7/skins/HVGA/layout'
emulator: skin network speed: 'full'
emulator: skin network delay: 'none'
emulator: registered 'boot-properties' qemud service
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'qemu.sf.lcd_density' = '160'
emulator: Adding boot property: 'dalvik.vm.heapsize' = '16m'
emulator: argv[00] = "/home/martin/android-sdk-linux_86/tools/emulator"
emulator: argv[01] = "-kernel"
emulator: argv[02] = "/home/martin/Desktop/buzz-2.6.29-534e5f81/arch/arm/boot/zImage"
emulator: argv[03] = "-initrd"
emulator: argv[04] = "/home/martin/android-sdk-linux_86/platforms/android-7/images//ramdisk.img"
emulator: argv[05] = "-nand"
emulator: argv[06] = "system,size=0x4a00000,initfile=/home/martin/android-sdk-linux_86/platforms/android-7/images//system.img"
emulator: argv[07] = "-nand"
emulator: argv[08] = "userdata,size=0x4200000,file=/home/martin/.android/avd/2.1.avd/userdata-qemu.img"
emulator: argv[09] = "-nand"
emulator: argv[10] = "cache,size=0x4200000,file=/home/martin/.android/avd/2.1.avd/cache.img"
emulator: argv[11] = "-hda"
emulator: argv[12] = "/home/martin/.android/avd/2.1.avd/sdcard.img"
emulator: argv[13] = "-serial"
emulator: argv[14] = "android-kmsg"
emulator: argv[15] = "-serial"
emulator: argv[16] = "stdio"
emulator: argv[17] = "-serial"
emulator: argv[18] = "android-qemud"
emulator: argv[19] = "-append"
emulator: argv[20] = "qemu=1 console=ttyS0 androidboot.console=ttyS1 android.checkjni=1 androidboot.logcat=*:v android.qemud=ttyS2 android.ndns=2"
emulator: argv[21] = "-m"
emulator: argv[22] = "96"
emulator: argv[23] = "-clock"
emulator: argv[24] = "unix"
emulator: mapping 'system' NAND image to /tmp/android/emulator-lc0c1q
emulator: rounding devsize up to a full eraseunit, now 4a1f000
emulator: using 'esd' audio input backend
emulator: using 'esd' audio output backend
emulator: Trace file name is not set
emulator: control console listening on port 5554, ADB on port 5555
emulator: sent '0012host:emulator:5555' to ADB server
emulator: ping program: /home/martin/android-sdk-linux_86/tools/ddms
emulator: ping command: /home/martin/android-sdk-linux_86/tools/ddms ping emulator 6.0
It then hangs at this point.
QUESTION 2: What am I doing wrong? Could this be related to the removed lines above? (seems unlikely as Buzz should be the only configuration being used)
I've attached a zip file that contains the compiled kernel and boot.img files if anybody found a minute or two to look.
Many thanks in advance and best wishes,
Martin
Can you post your .config? I'll take a look. I don't have a device to test with, but I don't mind testing the compiling part.
Hi,
Many thanks for the offer; I have since got this working.
It seemed to be due to the wrong offset when packing for the Wildfire (the correct offset I have now posted in the dev forum there).
It is fine to remove the non-included board- references
Best
Martin
MartinEve said:
Hi,
Many thanks for the offer; I have since got this working.
It seemed to be due to the wrong offset when packing for the Wildfire (the correct offset I have now posted in the dev forum there).
It is fine to remove the non-included board- references
Best
Martin
Click to expand...
Click to collapse
Cool beans. In the mean time, I took a few minutes and worked out one of the scripts needed to add the buzz to Android Builder.
ab_get_Buzz.29
clear
if [ ! -d $KITCHEN_ROOT/source/kernels/buzz/2.6.29/ ]
then
mkdir -p $KITCHEN_ROOT/source/kernels/buzz/2.6.29
cd $KITCHEN_ROOT/source/kernels/buzz/2.6.29
echo "Downloading Buzz 2.6.29 kernel source code"
wget http://member.america.htc.com/download/RomCode/Source_and_Binaries/buzz-2.6.29-534e5f81.tar.gz
tar xvzf buzz-2.6.29-534e5f81.tar.gz
cp -r buzz-2.6.29-534e5f81/* $KITCHEN_ROOT/source/kernels/buzz/2.6.29/
rm -r buzz-2.6.29-534e5f81/
rm buzz-2.6.29-534e5f81.t*
fi
Hi,
I need to get the default gateway of a device on my application. I am coding in native application in android. Here is my current code to get the default gateway.
Code:
static int get_default_gateway(char *def_gateway, int buf_size)
{
FILE* pipe;
char buffer[128];
char result[2049];
char cmd[] = "netstat -r | grep ^default | awk '{print $2}'";
pipe = popen(cmd, "r");
if (!pipe) return 1;
memset(result, 0, sizeof(result));
while(!feof(pipe)) {
memset(buffer, 0, sizeof(buffer));
if(fgets(buffer, 128, pipe) != NULL)
{
strcat(result, buffer);
}
}
pclose(pipe);
memset(def_gateway, 0, buf_size);
strncpy (def_gateway, result, buf_size );
return 0;
}
It works on my LG p500 but on some devices it doesn't return anything.
My question is this. Does popen() works on android? I read somewhere that it is not included in bionic.
And is there any other method to get the default gateway? I need it to be written in C and not java.
Thank you
I think I found the problem. Maybe grep and awk is not working on their phone. Its working on my phone since I created links to awk and grep to busybox.
Can someone confirm this if awk and grep is not working on a stock rom without creating links to busybox?
Thanks
On a stock ROM there is no busybox too. There is toolbox instead and it does not support much commands. When I first ran a shell on Android, was unpleasantly surprised when I didn't find some things like 'find' and 'grep' on a "Linux-based OS".
Here is complete list of the links to the toolbox on the Android 2.2 emulator: cat chmod chown cmp date dd df dmesg getevent getprop hd id ifconfig iftop insmod ioctl ionice kill ln log ls lsmod mkdir mount mv nandread netstat newfs_msdos notify printenv ps reboot renice rm rmdir rmmod route schedtop sendevent setconsole setprop sleep smd start stop sync top umount vmstat watchprops wipe. On my HTC Wildfire (with a stock Android 2.2.1) there is almost the same. The only difference is: reboot on HTC is a separate binary and there is additional link to toolbox here - strange chownto command.
praetorian droid said:
On a stock ROM there is no busybox too. There is toolbox instead and it does not support much commands. When I first ran a shell on Android, was unpleasantly surprised when I didn't find some things like 'find' and 'grep' on a "Linux-based OS".
Here is complete list of the links to the toolbox on the Android 2.2 emulator: cat chmod chown cmp date dd df dmesg getevent getprop hd id ifconfig iftop insmod ioctl ionice kill ln log ls lsmod mkdir mount mv nandread netstat newfs_msdos notify printenv ps reboot renice rm rmdir rmmod route schedtop sendevent setconsole setprop sleep smd start stop sync top umount vmstat watchprops wipe. On my HTC Wildfire (with a stock Android 2.2.1) there is almost the same. The only difference is: reboot on HTC is a separate binary and there is additional link to toolbox here - strange chownto command.
Click to expand...
Click to collapse
Thanks for posting the complete list of commands
Listed commands are only those that implemented by 'toolbox'. There are also some more: for example sh, gzip, ping and others. You can see them all by doing
Code:
ls /sbin /system/bin /system/xbin
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Well I have been searching and this is such a simple task which is causing me so many problems...
Summary:
I'm trying to execute a ADB push to a SDCARD via a c# app on windows.
using..
var process = Process.Start("CMD.exe", "/c adb push " + textBox1.Text + "/sdcard/" );
Now I'm pretty sure everything before + "/sdcard/" ); is sound.
I manually used ADB to type adb push C:\Users\QC\Desktop\bootanimation.zip /sdcard/
this WORKED.
But for some reason I do not know is that, when i run it via c# it will use ADB but flow through adb functions. normally meaning its not a correct command .
ANY IDEAS AT ALL?
BUMP
Maybe it's because it has to be
Code:
Process.Start("CMD.exe", "/c adb push " + textBox1.Text + " /sdcard/"
//notice the space before /sdcard/
If not,
Try:
Code:
ProcessStartInfo startInfo = new ProcessStartInfo();
startInfo.FileName = "cmd.exe";
startInfo.Arguments = "adb push " + textBox1.Text + " /sdcard/"
Process.Start(startInfo)
tried both already.. still get the same error or problem.. very strange.
try something like this for debugging:
Code:
string string = "adb push " + textBox1.Text + " /sdcard/";
textBox1.Text = string;
and check the string yourself
Edit: Have you also tried launching adb directly ? not through cmd
Attention
XM Infinity System Is Now Only Compatible With SHV-E160 And SGH-I717 Models. Do Not Use This On Another Devices Except For T-Mobile Note And GT-N7000.
Notice
After Learning A Big Lecture From Our XDA Forum Moderator Mark Manning, I've Been Decided To Use My Own Knowledge For Projects In XDA. This Time I Will Not Use Other Private Techniques From Others.
Introduction
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XM Infinity Is A Unix System C Program Or ELF Designed To Work For Almost Android Devices. It Has To Tunes Up Your Device Upto Beyond Without Using Tuning Apps Which Is Not Helpful Nor Helps Others.
General Notes For Devs And User
Dear Devs And Users,
If Your Willing To Add This To Your Developments Like ROMs, KERNELs, MODs, And ETC. You're Allowed Even Without Asking My Permission But Still Recommended To Ask My Permission Related For This And Dont Forget To Insert Proper Credits.
If This Project Kills Your Device or ETC, Dont Blame Me For It. You Must Use This At Your Own Risk
Sincerely Yours,
RenzkiPH
Click to expand...
Click to collapse
Credits
zeppelinrox - For Awesome V6 SC And Codes That I've Used Before
pikachu01 - For Kernel Tweaks Taken From His ThunderBolt!
Exit_Only - For Ass Kicking OKJ™
Yoda @ unix And linux Forums- For A Big Help For C Coding
LENAROX - For So Many Help In The Past
idcrisis/fivefour - For CrossBreeder
Buda1996 - SPL TEAM
jai554 - SPL TEAM
Linus Yang - For BusyBox v1.21.1 That I've Use In My Projects Before
And All Devs At XDA And Other Forums
Screenshots
Advantages Of XM
-Better Android Device Performance & ETC
-No Need Of Use Of Init.D(optional)
-No Bootloops Or Softbrick
Disadvantages Of XM
-Not Automatically Executed At Boot Without Init.D
-May Brick Your Android Device If Wrong Usage Occurs
-Inform Me
Requirements
-An Android Device Which Is Rooted, Have BusyBox, Custom Recovery/Kernel/ROM, Init.d Support And Running 4.0.x And Above.
-Terminal Emulator App For Play Store
-Recovery Backup(TWRP or CWM Based)
Features
-Tunes Up Your Android's Performance and ETC Upto Beyond
-Clears DNS Cache To Help Internet Connection Speed
Instructions
-- To Install --
1. Download XMD_v*.*.*_****.zip From Link Below
2. Reboot To Recovery Then Backup Your Current ROM
3. Install It Using Your Custom Recovery
4. After Installation, Reboot
5. Open Terminal Emulator App Then Type The Following Commands
Code:
su
xmd
6. Follow The Help On xmd Command
7. All Done
-- To Uninstall --
1. Open Terminal Emulator App Then Type The Following Commands
Code:
su
rm -rf /system/xbin/xmd
2. Reboot
Click to expand...
Click to collapse
I Hope You've Follow The Instructions Properly
Take Note That I Will Not Respond On PM. Related On Instructions For This Project.
Download Link
XM Infinity System v1.1.0 - Latest i717
XM Infinity System v1.0.1 i717 Beta - Older
XM Infinity System v1.0.0 Beta - Oldest
Changelog
Version 1.1.0 Beta 2014/03/22
Code:
-Added Config
-Added Boot Script
-Added New Options On XMD Program
-Improvements And Fixes
-Rewritten From Scratch
Version 1.0.1 Beta 2014/04/17
Code:
-Fixed Issue When Renicing Processes And ETC
-Improvements On Header Files
Version 1.0 Beta 2014/04/14
Code:
-Initial Release For SGH-I717 And SHV-E160(Note LTE)
Click to expand...
Click to collapse
List Of Compatible MODs
-Odexer Tool By @MatrixDJ96
-SwapItOn By @defiant07
List Of Recommended Apps
-CPU Tuner
-Greenify By @oasisfeng
-Clean Master Or SDmaid
-Battery Doctor
-Holo Launcher
Thanks To All Devs Of Apps From Above.
If You Like This Project, Consider To Press Thanks And Rate A ★★★★★. Thats It And Thank You For Using This Project.
Reserved For A Useful Content
Sent from my SHV-E160L using Tapatalk
More Luv for this age old device....thank a ton!!
:good:
Just installed it to my T-Mobile note and boy it smoothed my recent install of the new PAC man ROM with oc. I was having weird graphical glitches and static. It seams to have fixed them and it runs smoother over all. Oh yeah just to let everyone know it also works on SGH-T879 T-Mobile Galaxy Note!
Sent from my SAMSUNG-SGH-T879 using xda app-developers app
Thanks For The Feedbacks Guys...
Sent from my SHV-E160L using Tapatalk
127|[email protected]:/ $ su
[email protected]:/ # xmd
XM Infinity System v1.0.0 Beta
(c) 2014 RenzkiPH @ xda-developers
Starting XM Infinity System Optimizations...
vm.min_free_kbytes = 20480
vm.page-cluster = 3
vm.dirty_expire_centisecs = 3000
vm.dirty_writeback_centisecs = 500
vm.oom_kill_allocating_task = 0
vm.panic_on_oom = 0
vm.dirty_background_ratio = 5
vm.dirty_ratio = 10
vm.vfs_cache_pressure = 10
vm.min_free_order_shift = 4
vm.laptop_mode = 0
vm.block_dump = 0
vm.oom_dump_tasks = 1
kernel.sem = 500
sysctl: error: '512000' must be of the form name=value
sysctl: error: '64' must be of the form name=value
sysctl: error: '2048' must be of the form name=value
kernel.shmmax = 268435456
kernel.shmall = 2097152
kernel.shmmni = 4096
kernel.msgmni = 2048
kernel.msgmax = 64000
kernel.panic = 30
kernel.panic_on_oops = 0
kernel.threads-max = 5000
kernel.random.read_wakeup_threshold = 1024
kernel.random.write_wakeup_threshold = 512
fs.lease-break-time = 10
fs.file-max = 65536
killall: android.process.media: no process killed
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 1
net.ipv4.conf.all.accept_redirects = 0
net.ipv6.conf.all.accept_redirects = 0
net.ipv4.conf.all.secure_redirects = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.all.accept_source_route = 0
net.ipv6.conf.all.accept_source_route = 0
net.ipv4.conf.all.log_martians = 1
net.core.rmem_max = 6777216
net.core.wmem_max = 16777216
net.ipv4.tcp_rmem = 4096
sysctl: error: '87380' must be of the form name=value
sysctl: error: '1677721' must be of the form name=value
net.ipv4.tcp_wmem = 4096
sysctl: error: '87380' must be of the form name=value
sysctl: error: '16777216' must be of the form name=value
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_keepalive_probes = 3
net.ipv4.tcp_rfc1337 = 1
net.ipv4.tcp_mtu_probing = 1
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 5
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
XM Infinity System Optimization Complete...
[email protected]:/ #
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
GPFerror said:
127|[email protected]:/ $ su
[email protected]:/ # xmd
XM Infinity System v1.0.0 Beta
(c) 2014 RenzkiPH @ xda-developers
Starting XM Infinity System Optimizations...
vm.min_free_kbytes = 20480
vm.page-cluster = 3
vm.dirty_expire_centisecs = 3000
vm.dirty_writeback_centisecs = 500
vm.oom_kill_allocating_task = 0
vm.panic_on_oom = 0
vm.dirty_background_ratio = 5
vm.dirty_ratio = 10
vm.vfs_cache_pressure = 10
vm.min_free_order_shift = 4
vm.laptop_mode = 0
vm.block_dump = 0
vm.oom_dump_tasks = 1
kernel.sem = 500
sysctl: error: '512000' must be of the form name=value
sysctl: error: '64' must be of the form name=value
sysctl: error: '2048' must be of the form name=value
kernel.shmmax = 268435456
kernel.shmall = 2097152
kernel.shmmni = 4096
kernel.msgmni = 2048
kernel.msgmax = 64000
kernel.panic = 30
kernel.panic_on_oops = 0
kernel.threads-max = 5000
kernel.random.read_wakeup_threshold = 1024
kernel.random.write_wakeup_threshold = 512
fs.lease-break-time = 10
fs.file-max = 65536
killall: android.process.media: no process killed
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 1
net.ipv4.conf.all.accept_redirects = 0
net.ipv6.conf.all.accept_redirects = 0
net.ipv4.conf.all.secure_redirects = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.all.accept_source_route = 0
net.ipv6.conf.all.accept_source_route = 0
net.ipv4.conf.all.log_martians = 1
net.core.rmem_max = 6777216
net.core.wmem_max = 16777216
net.ipv4.tcp_rmem = 4096
sysctl: error: '87380' must be of the form name=value
sysctl: error: '1677721' must be of the form name=value
net.ipv4.tcp_wmem = 4096
sysctl: error: '87380' must be of the form name=value
sysctl: error: '16777216' must be of the form name=value
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_keepalive_probes = 3
net.ipv4.tcp_rfc1337 = 1
net.ipv4.tcp_mtu_probing = 1
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 1
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
renice: invalid option -- 5
USAGE: renice [[-r] [-t TYPE] priority pids ...] [-g pid]
XM Infinity System Optimization Complete...
[email protected]:/ #
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Renice Error Causes By Toolbox... Please Symlink Renice Binary To BusyBox...
Sent from my SHV-E160L using Tapatalk
Not sure how to do that, anyone give me the command(s)?
Thanks.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
GPFerror said:
Not sure how to do that, anyone give me the command(s)?
Thanks.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Is it possible to change path in symlink using a file explorer if you're not familiar with command line?
Edited to format as question?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Is it possible to change path in symlink using a file explorer if you're not familiar with command line?
Edited to format as question?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
I found the busybox version of renice in /system/xbin , I just copied it to /system/bin and then it ran without renice errors.
I still see the errors like
Code:
sysctl: error: '512000' must be of the form name=value
GPFerror said:
I found the busybox version of renice in /system/xbin , I just copied it to /system/bin and then it ran without renice errors.
I still see the errors like
Code:
sysctl: error: '512000' must be of the form name=value
Click to expand...
Click to collapse
I will fix that bro... wait for next release...
Sent from my SHV-E160L using Tapatalk
A New Version For The AT&T Note i717 Released. See OP For More Details.
Sent from my SHV-E160L using Tapatalk
Deleted
RenzkiPH said:
I will fix that bro... wait for next release...
Sent from my SHV-E160L using Tapatalk
Click to expand...
Click to collapse
Code:
[email protected]:/ $ su
[email protected]:/ # xmd
XM Infinity System v1.0.1 Beta
(c) 2014 RenzkiPH @ xda-developers
Usage: xmd [OPTIONS]
-x Execute Infinity System
-r Discard Changes By Infinity System
-s Clear DNS Cache
-h Print Help
1|[email protected]:/ # xmd -x
Executing XM Infinity System...
XM Infinity System Executed...
[email protected]:/ #
Looks good. Should I add this to my init.d ? Or does it only need to run once?
Thanks.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
GPFerror said:
Code:
[email protected]:/ $ su
[email protected]:/ # xmd
XM Infinity System v1.0.1 Beta
(c) 2014 RenzkiPH @ xda-developers
Usage: xmd [OPTIONS]
-x Execute Infinity System
-r Discard Changes By Infinity System
-s Clear DNS Cache
-h Print Help
1|[email protected]:/ # xmd -x
Executing XM Infinity System...
XM Infinity System Executed...
[email protected]:/ #
Looks good. Should I add this to my init.d ? Or does it only need to run once?
Thanks.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
You Can Add It On Your Init.D But I Recommended To Do Not Proceed Due To Possibility Of Bootloops.
RenzkiPH said:
A New Version For The AT&T Note i717 Released. See OP For More Details.
Sent from my SHV-E160L using Tapatalk
Click to expand...
Click to collapse
So.....busybox is included in the version for i717(larger file size-busybox in system/etc folder)? Does somebody who does not already has an install of busybox still need it as a prerequisite?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
So.....busybox is included in the version for i717(larger file size-busybox in system/etc folder)? Does somebody who does not already has an install of busybox still need it as a prerequisite?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Maybe Bro. BusyBox Is Included On v1.0.1 i717 Version To Fix Errors Causes On XM By ROMs Busybox.
Do I have to run this in Terminal Emulator every time I reboot the phone? Thanks...
Thank you for the tool! I am trying to use this hoping to no avoid using Android Tweaks.
I had an issue trying to run it in the terminal emulator I run into 4 actions I can perform.. Although after trying all of them not a single one was executed.
If someone could please re-direct me as to how to make it work it would be truly appreciated!
Again, thank you!
wavv.drama said:
Thank you for the tool! I am trying to use this hoping to no avoid using Android Tweaks.
I had an issue trying to run it in the terminal emulator I run into 4 actions I can perform.. Although after trying all of them not a single one was executed.
If someone could please re-direct me as to how to make it work it would be truly appreciated!
Again, thank you!
Click to expand...
Click to collapse
su
xmd -x
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Hi guys hope someone can help, i found a guide on dual booting my tablet its a linx 7
32 gb win 8.1 , I've spent the past two days reading and flashing having all sorts of problems lol but at least now ive managed to get it into a workable state.
At the minute its only booting android 4.4.4 as i deleted the windows.old folder and will probably have to do a full reinstall.
The problem with rooting android it seems is due to the usb otg part of the tablet and the ported version of the android version comes from the cube i7. The usb debugging is disabled due to the tablet only being designed for usbotg but there seems to be other versions of the android with root available from the manufacturer but due to using google translate and dead links im having no joy.
I found this using translate and google cache
You try to disguise iWork7 to Nexus7
Famous place in Arigasu such Pazudora is is, the domestic application There are many apps that limit such as carrier restrictions and ROOT limit is provided. Do not be able to start these apps from iWork7 it is currently being adjusted.
1. Look at the source
[GitHub]
2. Check item
the following values of the defualt.prop is NG
ro.secure = 0
ro.allow.mock.location = 1
ro.debuggable = 1
persist.sys.usb.config = adb
↓
Replaced iodide
ro.secure = 1
ro.allow.mock.location = 0
ro.debuggable = 0
persist.sys.usb.config = mtp
When the following exists NG (compatible with root switching of SuperSu)
· /system/app/Superuser.apk
· / System / bin / su
· / System / xbin / su
· / Sbin / su
You want to Nexus7 beetle the build.prop
Tablet classic [Nexus Factory Image
· Au of IntelAtom machine [ASUS MemoPad 8]
ro.build.id = KTU84P
# Ro.build.display.id = U67GT_v1.0__20150117
ro.build.display.id = KTU84P
# Ro.build.version.incremental = user.jim.20150117.113528
ro.build.version.incremental = 1227136
ro.build.version.sdk = 19
ro.build.version.codename = REL
ro.build.version.release = 4.4.4
# Ro.build.date = Sat Jan 17 11:37:11 CST 2015
ro.build.date = Fri Jun 13 07:23:23 UTC 2014
# Ro.build.date.utc = 1421465831
ro.build.date.utc = 1402644203
ro.build.type = user
# Ro.build.user = jim
ro.build.user = android-build
# Ro.build.host = build-168
ro.build.host = vpbs2.mtv.corp.google.com
# Ro.build.tags = dev-keys
ro.build.tags = release-keys
# Ro.product.model = U67GT
ro.product.model = Nexus 7
# Ro.product.brand = intel
ro.product.brand = google
# Ro.product.name = CUBE
ro.product.name = razor
# Ro.product.device = U67GT
ro.product.device = flo
# Ro.product.board = baylake
ro.product.board = flo
ro.product.cpu.abi = x86
ro.product.cpu.abi2 = armeabi-v7a
# Ro.product.manufacturer = intel
ro.product.manufacturer = asus
ro.product.locale.language = ja
persist.sys.language = ja
persist.sys.country = JP
ro.product.locale.region = JP
persist.sys.timezone = Asia / Tokyo
ro.wifi.channels =
ro.board.platform = baytrail
# Ro.build.product is obsolete; use ro.product.device
# Ro.build.product = CUBE
ro.build.product = flo
# Do not try to parse ro.build.description or .fingerprint
# Ro.build.description = em_i8270_64-user 4.4.4 KTU84P user.jim.20150117.113528 dev-keys
ro.build.description = razor-user 4.4.4 KTU84P 1227136 release-keys
# Ro.build.fingerprint = intel / em_i8270_64 / em_i8270: 4.4.4 / KTU84P / user.jim.20150117.113528: user / dev-keys
ro.build.fingerprint = google / razor / flo: 4.4.4 / KTU84P / 1227136: user / release-keys
ro.build.characteristics = nosdcard, tablet
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
Dynamically edit the Defualt.prop on Android
It seems possible to edit the defualt.prop under Android-root environment when you use the setpropex, quite amazing tool ,,,. (On reboot)
----------------------------------------
su -c "setpropex ro.secure 1"
---------------------------------------
(Ro.allow.mock.location = also the same format 1 and ro.debuggable = 1)
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 without deleting the Windows area, to rewrite the image of Android !!
The standard recovery procedures, it is the initialization of the inescapable Windows, but it became a rewritable only favorite area of Android by step on this procedure. (Mr. SpecialThanks dia-sea)
Download the required files
· XDA bootimg_tools_7.8.13.zip [HP] [Download]
As basic knowledge, organize the recovery boot order
1. BIOS -> Lanch EFI Shell file filesystem device
2. Shell.efi (Shellx64.efi can not move because it does not correspond to 64bitEFI)
3. startup.nsh -> efilinux.efi -f droidboot.img
4. installer.cmd
※ seemed to make re-partition is performed when you run the droidboot.img, require modification of droidboot.img.
modification of droidboot.img
Information display
# ./boot_info Droidboot.img
PAGE SIZE: 2048
BASE ADDRESS: 0x80000000
RAMDISK ADDRESS: 0x81000000
CMDLINE: 'loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor g_android.fastboot = 1 droidboot.minbatt = 0 droidboot.use_installer = 1 droidboot.installer_usb = / dev / block / sda1 droidboot.installer_file = installer. cmd '
dismantling of droidboot.img
# Split_boot droidboot.img
Editing of partition table
# Cp /droidboot/ramdisk/system/etc/partition.tbl /droidboot/ramdisk/system/etc/partition.tbl.bk
# Vi /droidboot/ramdisk/system/etc/partition.tbl
We want to only two lines
partition_table = gpt
reload / dev / block / mmcblk0
repack of ramdisk
# .././repack_ramdisk Ramdisk /
Creating droidboot.img
# .././mkbootimg --kernel Droidboot.img-kernel --ramdisk new-ramdisk.cpio.gz --cmdline "loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor g_android.fastboot = 0 droidboot.minbatt = 0 droidboot.use_installer = 1 droidboot.installer_usb = / dev / block / sda1 droidboot.installer_file = installer.cmd "--base 0x80000000 --pagesize 2048 --ramdiskaddr 0x81000000 --output droidboot_not_clear.img
Creating a Boot USB
Prepare a USB memory that was formatted with FAT32, to copy the contents of AnTaku folder of the USB memory to the root.
You have created so far, system_rootja.img the system.img, boot_adbon.img the boot.img, and rename and droidboot_not_clear.img the droidboot.img,, with the same copy of the USB memory to the root.
and it rewrites the partition.tbl the same content as the droidboot.img you just created.
partition_table = gpt
reload / dev / block / mmcblk0
editing of startup.nsh, change to start the droidboot_not_clear.img.
efilinux.efi -f droidboot_not_clear.img
modification of installer.cmd
And comment out the partition fix part
factory, cache, system, config, logs, the data is initialized,
Fixed boot.img, recovery.img, droidboot.img, the writing of system.img appropriate.
Below, mount the / system in rw, boot_adbon.img the adb effectiveness of boot.img
root of, example of Japanese, as system_rootja.img unwanted apps deleted system.img, it has saved to a USB memory.
oem start_partitioning
REM oem partition /installer/partition.tbl
erase: factory
erase: cache
erase: system
erase: config
erase: logs
erase: data
oem stop_partitioning
REM oem wipe ESP
REM flash: ESP # / installer / esp.img
REM flash: boot # / installer / boot.img
flash: boot # / installer / boot_adbon.img
flash: recovery # / installer / recovery.img
flash: fastboot # / installer / droidboot.img
REM flash: system # / installer / system.img
flash: system # / installer / system_rootja.img
continue
Now, without initialization of Android image the Widnows became the all-you-can-****. Hail and Hail.
Incidentally is the recovery manual wrote by making full use of the translation site. [DL]
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 Rooted !! full version!
We were successful in perfect Root acquired in iWork7. Correct the previous steps and re-published as a full version. (Mr. SpecialThanks dia-sea)
1. Download the necessary environment and file
Windows7 and (even 8.1) in a virtual environment we will proceed in the Linux (VMPalyer & Ubuntu14.10).
· Ubuntu14.10 Japanese 64bit [HP] [Download]
· VMWare Player [HP] [Download]
· IWork7 factory image [HP] [Download]
· Ext4_utils_cygwin_fixed [HP] [Download]
· SuperSu 2.46 [HP] [Download]
· Busybox [HP] [Download]
· Sgs2toext4 [HP] [Download] for people who system.ext4.img does not make well. (JAVA)
· USB memory space is available formatted with NTFS of about 8GB
· USB memory space is available formatted with FAT32 of more than 2GB
· USB keyboard, OTGHUB
2. Building a home directory
Once you start the ubuntu, to make a [iwork7] directory to the home directory,
and rename ext4_utils_cygwin_fixed.zip, system.img, copy the busybox, the directory name to unzip the UPDATE-SuperSU-v2.46.zip [updatesu].
After this it will be operation in the linux console.
In order to comfortable operation with the administrative authority, operation and after you to live do not put sudo passwords many times is easy.
$ Sudo $ {SHELL}
[Sudo] password for username:
Or, it will switch to the root user with su.
$ Sudo su -
3. Mount of system.img
System.img of factory image because it is a file that was cut wasteful part (0?) At the simg format, you will need to convert it to the format of the raw image ext4.
It wants to install the zlib1g-dev necessary to ext4_utils of make.
# Apt-get install zlib1g-dev
ext4_utils of thawing
# Unzip ext4_utils_cygwin_fixed.zip
make of ext4_utils
# Cd ext4_utils
# Make
to copy to make to the finished file to iwork7 directory.
The ones where you unzipped the SuperSu to updatesu directory, to just below iwork7 your own build.prop.
Examples of Japanese correspondence build.prop
ro.product.locale.language = ja
ro.product.locale.region = JP
persist.sys.language = ja
persist.sys.country = JP
persist.sys.timezone = Asia / Tokyo
Creating system.ext4.img
# Simg2img system.img system.ext4.img
System.img remove because it is unnecessary at this point
iWorkt-Root02.png
copy of busybox
# Cp busybox-x86_64 sys / xbin / busybox
# Chown root: root sys / xbin / busybox
# Chmod 0755 sys / xbin / busybox
4. Mount of system.img
# Umount msys
# Rm -f system.img
# Rm -rf msys
# Rm -rf sys
# Mkdir msys
# Mkdir sys
# Mount -o loop system.ext4.img msys
# Cp -a msys /. Sys
# Umount msys
5. root setting
Clear root
# Rm -rf sys / bin / .ext
# Rm -rf sys / etc / init.d
# Rm -f sys / bin / su
# Rm -f sys / xbin / su
# Rm -f sys / xbin / daemonsu
# Rm -f sys / bin / .ext / .su
# Rm -f sys / etc / install-recovery.sh
# Rm -f sys / etc / init.d / 99SuperSUDaemon
# Rm -f sys / etc / .installed_su_daemon
# Rm -f sys / app / Superuser.apk
# Rm -f sys / app / Superuser.odex
# Rm -f sys / app / SuperUser.apk
# Rm -f sys / app / SuperUser.odex
# Rm -f sys / app / superuser.apk
# Rm -f sys / app / superuser.odex
# Rm -f sys / app / Supersu.apk
# Rm -f sys / app / Supersu.odex
# Rm -f sys / app / SuperSU.apk
# Rm -f sys / app / SuperSU.odex
# Rm -f sys / app / supersu.apk
# Rm -f sys / app / supersu.odex
root acquisition start
# Mkdir sys / bin / .ext
# Cp updatesu / x86 / su sys / xbin / daemonsu
# Cp updatesu / x86 / su sys / xbin / su
# Cp updatesu / x86 / su sys / bin / .ext / .su
# Cp updatesu / common / Superuser.apk sys / app / Superuser.apk
# Cp updatesu / common / install-recovery.sh sys / etc / install-recovery.sh
# Mkdir sys / etc / init.d /
# Cp updatesu / common / 99SuperSUDaemon sys / etc / init.d / 99SuperSUDaemon
# Echo 1> sys / etc / .installed_su_daemon
# Chown root: root sys / bin / .ext
# Chown root: root sys / bin / .ext / .su
# Chown root: root sys / xbin / su
# Chown root: root sys / xbin / daemonsu
# Chown root: root sys / etc / install-recovery.sh
# Chown root: root sys / etc / init.d / 99SuperSUDaemon
# Chown root: root sys / etc / .installed_su_daemon
# Chown root: root sys / app / Superuser.apk
# Chmod 0777 sys / bin / .ext
# Chmod 06755 sys / bin / .ext / .su
# Chmod 06755 sys / xbin / su
# Chmod 0755 sys / xbin / daemonsu
# Chmod 0755 sys / etc / install-recovery.sh
# Chmod 0755 sys / etc / init.d / 99SuperSUDaemon
# Chmod 0644 sys / etc / .installed_su_daemon
# Chmod 0644 sys / app / Superuser.apk
Unnecessary apps (Chinese market, etc.) Delete
# Rm -f sys / preinstall / 91hiapk_AndroidPhone_1008443.apk
# Rm -f sys / preinstall / AnZhi_KuBiMoFangFuFei_V5.4_20141002.apk
# Rm -f sys / preinstall / BaiduNaviHD_d4033_20140523.apk
# Rm -f sys / preinstall / baidusearch_Android_1_3_0_7_1009249a.apk
# Rm -f sys / preinstall / cn.keyshare.course_ku_bi.apk
# Rm -f sys / preinstall / CUBE_UgameStore_V210_20141128.apk
# Rm -f sys / preinstall / Mediaplayer.apk
# Rm -f sys / preinstall / ninegameclienthd_v2.2.0_android_release.apk
# Rm -f sys / preinstall / Tudou_Android_phone_4.2_yingyue1.apk
# Rm -f sys / preinstall / wandoujia_kubimofang_oem_fa.apk
One line below if unnecessary copy your own bulid.prop may not run
# Cp build.prop sys / build.prop
Root, installation of busybox
# Mv sys / system
# Rm / system / bin / cp
# Rm / system / bin / mv
# / System / xbin / su --install
# / System / xbin / busybox --install -s / system / bin
# Mv / system sys
6. writing of system.img
When you root reduction, to create the following command implantation system.img. (Note the space)
# ./mkuserimg.sh -s Sys system.img ext4 system 896M
Copy the file to Windows, it will overwrite the system.img to where you copied the Android system to a USB memory that was formatted with FAT32.
6. Rooted !!
To complete the installation of the Android system open the BIOS menu from the ESC key to turn on the power. All after the completion of Android has become the Root state.
iWork7-BootBIOS.png
Finally, Do not you forget the installation of Windows.
Windows will cause is initialized in the above procedure.
In the next section we will learn the steps to rewrite only Android, leaving the Windows.
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 adb daemon configuration of (tcp)
It is iWork7 ~ is the first place impossible to connect with adb in USB debugging on, but can be connected by TCP.
If editing the /ramdsik/default.prop I may, but does not use the ramdisk.img, it uses the ramdisk in the boot.img. (Mr. SpecialThanks dia-sea)
1. File downloading
· XDA bootimg_tools_7.8.13.zip [HP] [Download]
2. It will copy the necessary files
Unzip the bootimg_tools_7.8.13.zip, is located in the following
Home directory / iwork7 / bootimg_tools
Copy the boot.img to bootimg_tools.
3. information display of boot.img
# Cd boot
# Boot_info boot.img
PAGE SIZE: 2048
BASE ADDRESS: 0x80000000
RAMDISK ADDRESS: 0x81000000
CMDLINE: 'loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor '
4. dismantling of boot.img
# Split_boot boot.img
5. adb setting
# Cd boot / ramdisk
# Vi default.prop
persist.nomodem_ui = 1
ro.arch = x86
ro.com.google.clientidbase = android-google
ro.secure = 0
ro.adb.secure = 0
ro.allow.mock.location = 1
ro.debuggable = 1
persist.sys.usb.config = adb
Creating 6.boot.img
# Cd boot
# .././repack_ramdisk Ramdisk /
# .././mkbootimg --kernel Boot.img-kernel --ramdisk new-ramdisk.cpio.gz --cmdline "loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor "--base 0x80000000 --pagesize 2048 --ramdiskaddr 0x81000000 --output boot.img
# Mv boot.img ../.
iwork7 to the connected with tcp / ip after adb Enable
on the command prompt of windows
# Adb connect "iwork7 of ip address"
# Adb shell
# Su - (Since root permission prompt SuperSU exits click allowed on the tablet!)
# Ps
# Root @ U67GT: / # ps
*
| 2015-04-28 |
Mobile
*| Comments: 0
And im not sure if this helps or not.
Am i able to add root to the rom myself ?
Just to add the usb-debugging is not enabled from the way the rom is designed, when you click the build/ model number to enable it then dev options it only offers the option to revoke the rights .
Bump!
Anyone? is there a way to add superuser to the system.img by decompiling / recompling?
crickyo said:
Bump!
Anyone? is there a way to add superuser to the system.img by decompiling / recompling?
Click to expand...
Click to collapse
Check these:
http://forum.xda-developers.com/showthread.php?t=2294909
http://forum.xda-developers.com/showthread.php?t=2665283
sdeepb said:
Check these:
http://forum.xda-developers.com/showthread.php?t=2294909
http://forum.xda-developers.com/showthread.php?t=2665283
Click to expand...
Click to collapse
Hi thanks for the reply i tried those the other night , but from what i remember it was asking for ext 4 and the files i have are system.img, I read through that thread and i think it said to try open the .img in the second program when i tried this it hung and crashed.
Is it really as simple as unpacking it and repacking it?
Im a long time android tinkerer but never knew what ive been doing just following guides
crickyo said:
Hi thanks for the reply i tried those the other night , but from what i remember it was asking for ext 4 and the files i have are system.img, I read through that thread and i think it said to try open the .img in the second program when i tried this it hung and crashed.
Is it really as simple as unpacking it and repacking it?
Im a long time android tinkerer but never knew what ive been doing just following guides
Click to expand...
Click to collapse
Sorry I don't have experience with this, asking in the thread would be your best bet
Hi , I managed to find a link on a chinese site to a modified system.img the two programs dont work and the thread says as much.
Mods can close this thread if they want.
OK guys if you are still after root I can help I have a linx 7 with the dual boot I used some files I found around the internet also my android partition is 8g instead of 4g it works like a charm if you guys still want I can upload and post a link
[email protected] said:
OK guys if you are still after root I can help I have a linx 7 with the dual boot I used some files I found around the internet also my android partition is 8g instead of 4g it works like a charm if you guys still want I can upload and post a link
Click to expand...
Click to collapse
can you post tutorial or links? is there chance to root device without touching windows partition?
marcindh said:
can you post tutorial or links? is there chance to root device without touching windows partition?
Click to expand...
Click to collapse
http://linxtablet.co.uk/viewtopic.php?f=4&t=2096
Unfortunately it does wipe your windows installation and you will be flashing the bios with a Chinese dual boot but it does 100% work
[email protected] thank you for very fast reply I have dualboot but android is not rooted (tutorial from reddit). Android from your link is already rooted?
marcindh said:
[email protected] thank you for very fast reply I have dualboot but android is not rooted (tutorial from reddit). Android from your link is already rooted?
Click to expand...
Click to collapse
No i don't think it is but if you download supersu.zip file search it on xda and download it to your memory card in your tablet then turn your tablet off.... holding the volume down button in while turning on and keeping the volume down pressed it will boot to a screen where you can select recovery and install from .zip in recovery when installed reboot all done ...:good:
[email protected] said:
No i don't think it is but if you download supersu.zip file search it on xda and download it to your memory card in your tablet then turn your tablet off.... holding the volume down button in while turning on and keeping the volume down pressed it will boot to a screen where you can select recovery and install from .zip in recovery when installed reboot all done ...:good:
Click to expand...
Click to collapse
I almost forgot my copy of the dual boot has a different recovery so you might have to reinstall