I'm really enjoying remix OS, So much so, I seldom use my windows partition at all any more except for one thing. Bootloader updates and firmware installations on my various android devices. (Most Nexus Player android TV boxes)
Remix shipped with adb support and I have been using it to push bulk installs onto my own and customer devices, I would like to perform the firmware updates as well and found remix does not ship with fastboot installed in system/bin. There is a fastboot file but it is for the Intel 915 graphics support libs.
Is there a way I can add it? been looking at a few pre compiled bin packages for linux but can't seem to get any of them to work correctly. can't seem to get the fastboot.bin to be executable.. even with root.
Any help would be appreciated. Asked the remix folks as I am on the beta program but have not gotten an answer.
Thanks!
MrJinx123 said:
I'm really enjoying remix OS, So much so, I seldom use my windows partition at all any more except for one thing. Bootloader updates and firmware installations on my various android devices. (Most Nexus Player android TV boxes)
Remix shipped with adb support and I have been using it to push bulk installs onto my own and customer devices, I would like to perform the firmware updates as well and found remix does not ship with fastboot installed in system/bin. There is a fastboot file but it is for the Intel 915 graphics support libs.
Is there a way I can add it? been looking at a few pre compiled bin packages for linux but can't seem to get any of them to work correctly. can't seem to get the fastboot.bin to be executable.. even with root.
Any help would be appreciated. Asked the remix folks as I am on the beta program but have not gotten an answer.
Thanks!
Click to expand...
Click to collapse
Try the one here: it's seems to show the help page fine. Haven't checked any of the command though;
alternatively you could compile a version from source
Thanks for the lead
Looking around thru XDA , I found a few fastboot packages that should have worked. My device filesystem is RW and root is obviously present. I copy the file and chmod it as executable but still get access denied trying to execute it as root, Most the versions I found expect you to adb copy it into the device, With remix OS, I'm not sure how to to do that since there is no OTG port. If the filesystem is RW, Should I need to use adb to copy the file in? Looking at compiling a copy since the remix install I'm using is x64 on intel and maybe the fastboot executable needs to be for this specific target?
MrJinx123 said:
Looking around thru XDA , I found a few fastboot packages that should have worked. My device filesystem is RW and root is obviously present. I copy the file and chmod it as executable but still get access denied trying to execute it as root, Most the versions I found expect you to adb copy it into the device, With remix OS, I'm not sure how to to do that since there is no OTG port. If the filesystem is RW, Should I need to use adb to copy the file in? Looking at compiling a copy since the remix install I'm using is x64 on intel and maybe the fastboot executable needs to be for this specific target?
Click to expand...
Click to collapse
Definately at least executes for me; will check tomorrow if it can detect a fastboot device. One from @osm0sis : http://forum.xda-developers.com/showthread.php?t=2239421 also seems to run fine and I think its a different one; some of the others posted are a copy of that first one I posted without giving credit.
Looks like you did point me to the right one.
Since remix OS on a laptop doesn't support an OTG adb transfer... I manually copied adb, adb.bin and fast boot to the system/xbin directory as root.
Then used
chown 0:0 on all 3 files, As found in the included install script (adb shell script)
then chmod +755 (all 3 files) also tried chmod +777
No errors or complaints from the command line..
attempt to execute as user or root, Get permission denied..
"ls" the file shows -rwxrwxrwx root root ?
When I compare against other files in xbin, they all have lrwxrwxrwx. I'm assuming the "l" is a symbolic link pointing to the busybox install.
Am I missing something? that is preventing fastboot from being executable? I don't claim to be a linux expert in any way...
MrJinx123 said:
Since remix OS on a laptop doesn't support an OTG adb transfer... I manually copied adb, adb.bin and fast boot to the system/xbin directory as root.
Then used
chown 0:0 on all 3 files, As found in the included install script (adb shell script)
then chmod +755 (all 3 files) also tried chmod +777
No errors or complaints from the command line..
attempt to execute as user or root, Get permission denied..
"ls" the file shows -rwxrwxrwx root root ?
When I compare against other files in xbin, they all have lrwxrwxrwx. I'm assuming the "l" is a symbolic link pointing to the busybox install.
Am I missing something? that is preventing fastboot from being executable? I don't claim to be a linux expert in any way...
Click to expand...
Click to collapse
adb is already installed (/system/bin/adb); other than that I have it as 777 root:root as well, any chance you have forgotten to execute fastboot as root [su]?
Screenshot attached; and just checked if device detected in fastboot and it is.
NB with adb you might have to use adb -s 0123456789ABCDEF reboot bootloader for example as theres an emulator device running on RemixOS.
Related
I just extracted the Gentoo Stage3 package for ARM7A and I am playing around trying to get the binaries to run either through terminal emulator or adb shell on my Galaxy Tab running Gingerbread.
I am FULLY aware of how PATH works and all of the normal reasons you would get a "not found" error when trying to run a command, but this one has me stumped.
I tried setting my path to include a subdirectory of /system/bin as follows:
PATH=/system/bin/gentoo:$PATH and gentoo is where I put my gentoo binaries.
When I do which (command) it says:
/system/bin/gentoo/(command)
When I try to run it, it runs the same command from one of the other directories such as /system/xbin (from busybox) instead.
I tried renaming one of the binaries so it has a unique name mv ps wtf I can still do which wtf and get /system/bin/gentoo/wtf
THEN when I try to run it I get wtf: not found.
Obviously the file is there. Even if I go directly to /system/bin/gentoo and do ./wtf I get wtf: not found. If I copy one of the Android system binaries to /system/bin/gentoo/wtf it will run just fine.
Why would I get a not found error for a binary that is obviously there??
I would expect a different error if it wasn't an acceptable binary, so I am lost.
Any ideas?
rustyshack3 said:
I just extracted the Gentoo Stage3 package for ARM7A and I am playing around trying to get the binaries to run either through terminal emulator or adb shell on my Galaxy Tab running Gingerbread.
I am FULLY aware of how PATH works and all of the normal reasons you would get a "not found" error when trying to run a command, but this one has me stumped.
I tried setting my path to include a subdirectory of /system/bin as follows:
PATH=/system/bin/gentoo:$PATH and gentoo is where I put my gentoo binaries.
When I do which (command) it says:
/system/bin/gentoo/(command)
When I try to run it, it runs the same command from one of the other directories such as /system/xbin (from busybox) instead.
I tried renaming one of the binaries so it has a unique name mv ps wtf I can still do which wtf and get /system/bin/gentoo/wtf
THEN when I try to run it I get wtf: not found.
Obviously the file is there. Even if I go directly to /system/bin/gentoo and do ./wtf I get wtf: not found. If I copy one of the Android system binaries to /system/bin/gentoo/wtf it will run just fine.
Why would I get a not found error for a binary that is obviously there??
I would expect a different error if it wasn't an acceptable binary, so I am lost.
Any ideas?
Click to expand...
Click to collapse
Just a guess, but I'd bet that the linker path for the binary is having trouble finding a library.
Hello everyone!
I've recently purchased a Vodafone Smart Tab 10 running Honeycomb 3.2.
I would like very much to root the device and kill the bloat a bit.
The hardware is good, but it seems that Honeycomb + bloatware is not the best way to go for a smooth experince...
Maybe the process would be similar for the Vodafone Smart Tab 7, too:
[Q] How to root Vodafone Smart Tab 7
Smart Tab on Vodafone's site:
Vodafone Smart Tab 7/10
Thanks.
We need a compatible CW recovery. There is the 3e recovery onboard like in Samsung devices. We have a working adb and fastboot. Bootloader is unlocked.
Sent from my SmartTab10 using Tapatalk
You can get source on
HTML:
http://www.vodafone.com/content/index/about/what/devices/vodafone_smart_tab.html
You can pull config from device.
Yeah, this device is cheap and good, but we need root for it. Come on, I'm sure that someone can make custom recovery and root for this device.
I would go and try this.
But downloading of the source would take me years on my sucky hotel internet now. Maybe when I get home.
Yes but you'll need a rooted devices to dump recovery.img and to read the partition layout. We need to root it first. I have tried the gingerbreak with gingerbreak.apk and oneclickroot but without success. Any ideas?
Sent from my SmartTab10 using Tapatalk
Does anyone know the password to bluez package of the source?
Noup. Whay they set the password at all? Any progress with the recovery buildup?
Sent from my SmartTab10 using Tapatalk
BlueZ
Unless I'm mistaking, BlueZ is a package dealing only with bluetooth functionality.
It should be of no concern in the early stages of root/custom ROM implementation.
sangemaru said:
Unless I'm mistaking, BlueZ is a package dealing only with bluetooth functionality.
It should be of no concern in the early stages of root/custom ROM implementation.
Click to expand...
Click to collapse
You are right about BlueZ. Any idea of the method we could use to root this device?
Sent from my SmartTab10 using Tapatalk
To my understanding, it's possible to perform a root through ADB.
Since the device is unlocked in just about every other possible way, it shouldn't be too much of a chore.
I'll be having a look over possible ways to do that tonight.
$ adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
liuyuanyuan prjName is <V11A>
liuyuanyuan exit adbd if usb_mass_storage is enabled on V66 or V68
error: device not found
What the f this liuyuanyuan wants from me He is good o yes
EDIT: This device does not have cmdclient & cmd_server_daemon running!
mobilx said:
$ adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
liuyuanyuan prjName is <V11A>
liuyuanyuan exit adbd if usb_mass_storage is enabled on V66 or V68
error: device not found
What the f this liuyuanyuan wants from me He is good o yes
EDIT: This device does not have cmdclient & cmd_server_daemon running!
Click to expand...
Click to collapse
I think it's more likely that you don't have the proper device drivers on your computer.
I have the links at work, I'll try to see about them tomorrow. Were you in Recovery or Development mode?
I'm using a pached by myself drivers from ZTE 3g phone archive that I found somewhere. ADB works fine. This is a root method for the Acer iconia 100 but it doesn't work because our device does not have cmdline binary in /sys/bin. I tried to pull it out from some Iconia ROM and adb pushed it to /data/local but there is the catch also. Cmd_server_daemon needs to be started which is impossible without the root permissions.
If you have the original drivers for this device please provide us a link.
Sent from my SmartTab10 using Tapatalk
Here's a link to the original V71 drivers, which I'm assuming would be the same for the V11 here.
For my device, the daemon runs properly with these drivers, but I need to have no drivers installed first, connect the device, then install the drivers with the device connected. The drivers came included on the device.
You should first try uninstalling all drivers relating to tablets/phones, then connecting the device and seeing if any drivers show up in a new detected "CD Drive" (ZTE loves doing this).
Also, any owners of the SmartTab7/SmartTab10 a.k.a v71a or v11a please vote for these devices on the new device voting thread. We need all the effort we can spend if we're going to see these devices properly supported.
mobilx said:
I'm using a pached by myself drivers from ZTE 3g phone archive that I found somewhere. ADB works fine. This is a root method for the Acer iconia 100 but it doesn't work because our device does not have cmdline binary in /sys/bin. I tried to pull it out from some Iconia ROM and adb pushed it to /data/local but there is the catch also. Cmd_server_daemon needs to be started which is impossible without the root permissions.
Click to expand...
Click to collapse
For me, i could push files to /data/local just fine, i can perform apk installations through adb, however i can't execute almost any command.
Everything would have been fine if we could do $adb shell su, but i get permissions error even with modified su file, so i have no idea what to do.
The weird thing is that cmd_server_daemon runs just fine for me, however i can't get any permissions at all.
Using adb root tells me that root is not available for production models.
Do you have the cmd_server_daemon listed in ls -l /system/bin ?
If you have you can use this Method
Sent from my SmartTab10 using Tapatalk
No, i don't have it listed. Which is weird, because I've seen mentions of it booting and running successfully... i think.
We are pretty stuck. If someone could get stock firmware. We need a boot.img or a hc 3.2 exploit.
We're not stuck at all, actually.
We have the source code, remember?
If i can find any instructions on how to integrate root with it, I can just build the rom.
Hello,
Veteran SW guy here; but newbie at Android.
I have three tablets. All of them are Ematic Model EGS004. All three were bought for the sole purpose of being used by children to watch educational videos (in mp4 and flv formats) and read PDF documents. Absolutely nothing else. No games. No internet access whatsoever. Etc.
Two of the tablets are still in the box and have not been touched. I'm hoping that they may be useful for making/restoring an original image of the tablets.
To implement the requirements of this project, I did the following to one of the tablets:
1) Used the instructions at http://forum.xda-developers.com/showthread.php?t=2495069 to get root access with Cydia Impactor and Chainfire SuperSU.
2) Installed Titanium Backup (root). Using this, I uninstalled most of the Google applications (excluding Google Play), messager, YouTube, games, etc.
3) Installed File Manager (Explorer) by Rhythm Software.
4) Installed Shell Terminal Emulator by MobilDev. Using the shell, I went to the /system/lib directory and renamed libwifidisplay.so
and libwpa_client.so to libwifidisplay.disabled and libwpa_client.disabled.
Unfortunately, upon reboot, the tablet gets stuck in the bootup screen (with the ematic logo). Obviously, something about Android causes a hang if an expected kernel module is missing...
I tried using the shell in Cydia Impactor. But, the file system was read only. I tried:
mount -o rw,remount /system
But, I get an "Operation not permitted" since I am not root.
I downloaded the ADB bundle for windows at http://developer.android.com/sdk/index.html#download and successfully installed adb on my PC. I could get into a shell with the "adb shell" command. But, the /system/lib directory still is read only and I can't seem to remount it since I am not root.
I tried "adb remount". "Operation not permitted" was the result, again.
Cydia Impactor installs its "su" binary in /system/xbin. I tried running it from there using various invocations like "su -c mount -o rw,remount /system" Each time, the shell hung and I never got a shell prompt afterwards.
Questions:
1) Surely there's a way that I can get back in to rename these files now... I can "ls" them from the adb shell. I can pull them to my PC with adb pull. (adb put doesn't work either since the file system is read only.) Ideas?
2) Once I get this solved, what is the best way to get rid of the wireless capability so that children can never use it? I would like to move videos and PDF's between it and a PC strictly via USB.
3) Is there a way to image/restore one of the untouched tablets - or, for that matter, this one once its up and running like it needs to be?
Thanks everyone!
Jim
Let's try a simpler question since there have been no responses:
Once I get into a shell (non-root) using ADB or Cythia Impactor, I believe I can rename the files if I can only get SuperSU to work. However, when I invoke su, the shell hangs:
su -c ls
su
etc. All of these hang. I assume that SuperSU is waiting for a confirmation from the android display. But, since I'm stuck at the startup screen, there's never an opportunity. How can I get the shell to interact with me as root so that I can remount the file system as RW and rename files?
Thanks,
Jim
rivkah613 said:
Hello,
Veteran SW guy here; but newbie at Android.
I have three tablets. All of them are Ematic Model EGS004. All three were bought for the sole purpose of being used by children to watch educational videos (in mp4 and flv formats) and read PDF documents. Absolutely nothing else. No games. No internet access whatsoever. Etc.
Two of the tablets are still in the box and have not been touched. I'm hoping that they may be useful for making/restoring an original image of the tablets.
To implement the requirements of this project, I did the following to one of the tablets:
1) Used the instructions at http://forum.xda-developers.com/showthread.php?t=2495069 to get root access with Cydia Impactor and Chainfire SuperSU.
2) Installed Titanium Backup (root). Using this, I uninstalled most of the Google applications (excluding Google Play), messager, YouTube, games, etc.
3) Installed File Manager (Explorer) by Rhythm Software.
4) Installed Shell Terminal Emulator by MobilDev. Using the shell, I went to the /system/lib directory and renamed libwifidisplay.so
and libwpa_client.so to libwifidisplay.disabled and libwpa_client.disabled.
Unfortunately, upon reboot, the tablet gets stuck in the bootup screen (with the ematic logo). Obviously, something about Android causes a hang if an expected kernel module is missing...
I tried using the shell in Cydia Impactor. But, the file system was read only. I tried:
mount -o rw,remount /system
But, I get an "Operation not permitted" since I am not root.
I downloaded the ADB bundle for windows at http://developer.android.com/sdk/index.html#download and successfully installed adb on my PC. I could get into a shell with the "adb shell" command. But, the /system/lib directory still is read only and I can't seem to remount it since I am not root.
I tried "adb remount". "Operation not permitted" was the result, again.
Cydia Impactor installs its "su" binary in /system/xbin. I tried running it from there using various invocations like "su -c mount -o rw,remount /system" Each time, the shell hung and I never got a shell prompt afterwards.
Questions:
1) Surely there's a way that I can get back in to rename these files now... I can "ls" them from the adb shell. I can pull them to my PC with adb pull. (adb put doesn't work either since the file system is read only.) Ideas?
2) Once I get this solved, what is the best way to get rid of the wireless capability so that children can never use it? I would like to move videos and PDF's between it and a PC strictly via USB.
3) Is there a way to image/restore one of the untouched tablets - or, for that matter, this one once its up and running like it needs to be?
Thanks everyone!
Jim
Click to expand...
Click to collapse
Erratic Ematic
rivkah613 said:
Let's try a simpler question since there have been no responses:
Once I get into a shell (non-root) using ADB or Cythia Impactor, I believe I can rename the files if I can only get SuperSU to work. However, when I invoke su, the shell hangs:
su -c ls
su
etc. All of these hang. I assume that SuperSU is waiting for a confirmation from the android display. But, since I'm stuck at the startup screen, there's never an opportunity. How can I get the shell to interact with me as root so that I can remount the file system as RW and rename files?
Thanks,
Jim
Click to expand...
Click to collapse
I rooted my son's EGS004, installed busybox, and played around with it without any apparent problem. When I rebooted it, I was prompted to set up the device then and every subsequent time I rebooted it. I could not install any apps and could not redo the Cydia Impactor rooting procedure. The reason was that /data was reporting itself as 0.00B in size. Factory reset didn't change anything. Ematic wants me to return it.
Your issue sounds different, but it could be something as simple as the device being very unforgiving. There's a pinhole with a reset button (never worked for me but tech support suggested it) which may help.
So...some mistake in update-script with setperm on stock slot and now I have a device:
- device is turning on
- clean, pure unregistered stock firmware
- adb work (pull/push)
- adb shell/install doesn't work (bin/sh not found)
- adb backup/restore doesn't work
- i have no safestrap (its missing after unsuccessful flashing)
- com.amazon.dcp.apk renamed, so future ota doesnt help
- wifi bluetooth doesn't work (no mac-address)
- I can copy files to/from sdcard
- i have su and daemonsu in /xbin (maybe....)
Any method to install apk ? Something like "file:///sdcard.1apk" like other android device, or maybe through silk debugging I could make same html-code to access sdcard? or fastboot flashing something to restore to stock. If I could install safestrap or es file explorer its would be great...
Thanks. Sorry my English.
./adb install mypackage.apk
on linux or
adb install mypackage.apk
on windows
dieter_m said:
./adb install mypackage.apk
on linux or
adb install mypackage.apk
on windows
Click to expand...
Click to collapse
As a note and just to clear it up a little, should someone find this while researching. When i was looking for this command and found the answer elsewhere, it wasn't quite clear on where the APK was taken from. It's from the system you issue the command from, not the device where you want the APK to be installed.
So for example. If you have the APK on your harddrive (D:\) in windows, you would issue this command in the command line:
adb install D:\APK_to_be_installed.apk
Adb install doesn't work, I already write this.
I am not responsible for any damage that may or may not occur to your device.
If you use my recovery in your project link back to this thread, and give me credit in your thread for my recovery.
This is the Linux version of TWRP tethered recovery and CWM tethered recovery.
TWRP 2.8.6.0 recovery, currently tested on two tablets, venue 3830, iview -1700
screen for 1-700 is 1024x600 landscape
screen for venue 3830 800x1280 portrait
Purpose of this guide is to root intel tablets using Linux computer.
This project includes the work of 4 people perhaps more.
@vampirefo
Linux Fastboot Binary, intel compatible cwm recovery.
http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925
@Chainfire
super user package update-supersu-vxxx.zip
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
@social-design-concepts
recovery.launcher, recovery.envsetup, recovery.trigger, triggers and for sharing his work.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
http://forum.xda-developers.com/showthread.php?t=2681783
TeamWin for their great recovery.
Download
https://www.androidfilehost.com/?fid=24052804347784850
Download 7-31-recoveries.zip extract some where, choose which recovery you want to run, rename to recovery.zip, then execute trigger choice. make sure trigger script is executable All four triggers are included in the trigger script.
1. cwm_recovery.zip
2. twrp_3830_recovery.zip
3. twrp_i700_recovery.zip
To use trigger script, open terminal in directory where files have been extracted.
Code:
adb reboot bootloader
choose which trigger you want to use.
Trigger 1
Code:
sudo ./trigger 1
Trigger 2
Code:
sudo ./trigger 2
Trigger 3
Code:
sudo ./trigger 3
Trigger 4
Code:
sudo ./trigger 4
-----------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------
Below is older version, it's recommend to use version above.
Download for older version.
http://www.mediafire.com/download/c4kdv4qv7nkq3gv/Linux_tethered_cwm.zip
Download Linux_tethered_cwm.zip to your desktop extract set start_recovery as executable, make sure usb debugging is setup and working.
Place UPDATE-SuperSU-v2.37.zip on micro sdcard or on internal sdcard or both wont hurt anything.
open terminal in folder where you extracted files.
Code:
adb reboot bootloader
once you are in fastboot
Code:
sudo ./start_recovery
now use recovery to navigate to UPDATE-SuperSU-v2.37.zip and install it, after finished reboot to system, select no on su question.
Update thread, below are the latest adb and fastboot binary files from Google, the fastboot binary from Google is smaller then the one I compiled., as of Dec 9, Googles latest fastboot binary now supports intel devices.
http://www.mediafire.com/download/qvlw80zebqfmbxx/adb_fastboot.tar
Change log 7-31-2015
Twrp has been updated to 2.8.7.0
This version includes @social-design-concepts latest trigger (fbrl.trigger) and launcher (recovery.launcher), Also included is a script for Tesco Hudl 2 users, this device requires addition info to launch fastboot commands.
For Tesco Hudl 2 users use hudl2 script instead of trigger, or you can still manually edit trigger if you want.
Code:
adb reboot bootloader
Code:
sudo ./hudl2
Hi vampirefo I can get to recovery mode and when I select SuperSU 2.35 or 2.37 it starts to install then I get an error saying "E: failed to verify whole-file signature from /tmp/sideload/package.zip" "E:signature verification failed" Installation aborted. I'm Kinda stuck now
vampirefo said:
This is the Linux version of @social-design-concepts windows version of Tethered CWM Recovery.
Purpose of this guide is to root intel tablets without a windows computer, using Linux computer.
This project includes the work of three people perhaps more.
This method uses 3rd trigger, if you want to use another trigger simply edit start_recovery, to reflect the trigger you want to use.
@vampirefo
Linux Fastboot Binary, intel compatible cwm recovery.
http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925
@Chainfire
super user package update-supersu-v2.37.zip
http://forum.xda-developers.com/showthread.php?t=1538053
@social-design-concepts
recovery.launcher, recovery.envsetup, triggers
http://forum.xda-developers.com/showthread.php?t=2681783
Download
http://www.mediafire.com/download/c4kdv4qv7nkq3gv/Linux_tethered_cwm.zip
Download Linux_tethered_cwm.zip to your desktop extract set start_recovery as executable, make sure usb debugging is setup and working.
Place UPDATE-SuperSU-v2.37.zip on micro sdcard or on internal sdcard or both wont hurt anything.
open terminal in folder where you extracted files.
Code:
adb reboot bootloader
once you are in fastboot
Code:
sudo ./start_recovery
now use recovery to navigate to UPDATE-SuperSU-v2.37.zip and install it, after finished reboot to system, select no on su question.
Click to expand...
Click to collapse
You can't flash anything from stock recovery, you need to use my cwm recovery.
Sent from my i700 using Tapatalk
vampirefo said:
This is the Linux version of @social-design-concepts windows version of Tethered CWM Recovery.
Purpose of this guide is to root intel tablets without a windows computer, using Linux computer.
This project includes the work of three people perhaps more.
This method uses 3rd trigger, if you want to use another trigger simply edit start_recovery, to reflect the trigger you want to use.
@vampirefo
Linux Fastboot Binary, intel compatible cwm recovery.
http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925
@Chainfire
super user package update-supersu-v2.37.zip
http://forum.xda-developers.com/showthread.php?t=1538053
@social-design-concepts
recovery.launcher, recovery.envsetup, triggers
http://forum.xda-developers.com/showthread.php?t=2681783
Download
http://www.mediafire.com/download/c4kdv4qv7nkq3gv/Linux_tethered_cwm.zip
Download Linux_tethered_cwm.zip to your desktop extract set start_recovery as executable, make sure usb debugging is setup and working.
Place UPDATE-SuperSU-v2.37.zip on micro sdcard or on internal sdcard or both wont hurt anything.
open terminal in folder where you extracted files.
Code:
adb reboot bootloader
once you are in fastboot
Code:
sudo ./start_recovery
now use recovery to navigate to UPDATE-SuperSU-v2.37.zip and install it, after finished reboot to system, select no on su question.
Click to expand...
Click to collapse
for 3730 or 3830?:laugh:
Dagege said:
for 3730 or 3830?:laugh:
Click to expand...
Click to collapse
Should work on both, as well as other intel tablets, this isn't just for dell tablets.
Sent from my i700 using Tapatalk
Added Google's latest adb and fastboot binaries files to first OP. I always recommend and use the latest version of these binaries myself. I had to compile my own fastboot binary cause Google didn't have one that supported intel, now they do, I recommend people use it.
Updated recovery binary.
This worked perfect on my Acer A1-840FHD.
I have a stupid question.
How use command: sudo ./start_recovery in fastboot mode?
I use this tutorial: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 to root my tab but when i'd like to use this mod: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443 it doesnt work... error 255, how about this method?
Fajfie said:
I have a stupid question.
How use command: sudo ./start_recovery in fastboot mode?
I use this tutorial: http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 to root my tab but when i'd like to use this mod: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443 it doesnt work... error 255, how about this method?
Click to expand...
Click to collapse
This is for Linux, not windows, you type the command in terminal.
sent from my kingSing T1 via taptalk
Fajfie said:
this mod: http://forum.xda-developers.com/and...mod-projct-mod-boost-nitro-x-edition-t2809443 it doesnt work... error 255, how about this method?
Click to expand...
Click to collapse
Umm the recovery saved you from bricking your tablet, had the recovery installed that mod, most likely you would be calling Dell to find out how to return the tablet, and get a quote on repair cost, as your warranty is void.
Excellent , happy 2015
Wow ! Great!
As I fumbled with many problems in Windows, I got the first shot easily from Linux.
Thank you all for your excellent work.
I will now install a dual Android / Linux on my tablet (Iconia Tab 8 FHD + SDCard)
My advice to this method of rooting , even with a bootable Live CD .
Thank you and ... Happy New Year 2015 !
Stuck trying to root....!! Please help me out of this...
My auditor sir said me that he has forgotten password for dell venue 7 - i just wanted to help him out with the help of " adb shell unlock code method " but didnt succeed..... then in fastboot mode i just typed the code " Fastboot erase system " now when i boot the device it stops at dell logo screen for hours & hours.... Now i dont know what to do... I just want to hand him over the phone but not like this..... he will kill me.... kindly please help me ... i beg u guyz..... Please
vampirefo said:
This is the Linux version of @social-design-concepts windows version of Tethered CWM Recovery.
Purpose of this guide is to root intel tablets without a windows computer, using Linux computer.
This project includes the work of three people perhaps more.
This method uses 3rd trigger, if you want to use another trigger simply edit start_recovery, to reflect the trigger you want to use.
@vampirefo
Linux Fastboot Binary, intel compatible cwm recovery.
http://forum.xda-developers.com/dell-venue/general/dell-venue-8-cwm-unsecure-boot-recovery-t2866925
@Chainfire
super user package update-supersu-v2.37.zip
http://forum.xda-developers.com/showthread.php?t=1538053
@social-design-concepts
recovery.launcher, recovery.envsetup, triggers
http://forum.xda-developers.com/showthread.php?t=2681783
Download
http://www.mediafire.com/download/c4kdv4qv7nkq3gv/Linux_tethered_cwm.zip
Download Linux_tethered_cwm.zip to your desktop extract set start_recovery as executable, make sure usb debugging is setup and working.
Place UPDATE-SuperSU-v2.37.zip on micro sdcard or on internal sdcard or both wont hurt anything.
open terminal in folder where you extracted files.
Code:
adb reboot bootloader
once you are in fastboot
Code:
sudo ./start_recovery
now use recovery to navigate to UPDATE-SuperSU-v2.37.zip and install it, after finished reboot to system, select no on su question.
Update thread, below are the latest adb and fastboot binary files from Google, the fastboot binary from Google is smaller then the one I compiled., as of Dec 9, Googles latest fastboot binary now supports intel devices.
http://www.mediafire.com/download/qvlw80zebqfmbxx/adb_fastboot.tar
Click to expand...
Click to collapse
surajmal said:
My auditor sir said me that he has forgotten password for dell venue 7 - i just wanted to help him out with the help of " adb shell unlock code method " but didnt succeed..... then in fastboot mode i just typed the code " Fastboot erase system " now when i boot the device it stops at dell logo screen for hours & hours.... Now i dont know what to do... I just want to hand him over the phone but not like this..... he will kill me.... kindly please help me ... i beg u guyz..... Please
Click to expand...
Click to collapse
You deleted the system, you have to download the stock images and use fastboot to flash system
http://forum.xda-developers.com/showthread.php?p=51090040
[TOOL KIT] myKIT_BATCHV1.1.x
surajmal said:
My auditor sir said me that he has forgotten password for dell venue 7 - i just wanted to help him out with the help of " adb shell unlock code method " but didnt succeed..... then in fastboot mode i just typed the code " Fastboot erase system " now when i boot the device it stops at dell logo screen for hours & hours.... Now i dont know what to do... I just want to hand him over the phone but not like this..... he will kill me.... kindly please help me ... i beg u guyz..... Please
Click to expand...
Click to collapse
?????????????? " Fastboot erase system "
This command isn't part of rooting, this command removes your OS, you can't boot cause you have nothing to boot, no way you got that command from my root instructions.
My root instructions are two lines.
Code:
adb reboot bootloader
Code:
sudo ./start_recovery
You are going to have to install a OS, 3 to choose from, I would go with 4.4.2
Can this be done without any of sdc binary files?
Vamp, a few questions for you.
Can this be done without any of sdc's binary files? Can this be done with just script files or command line?
Can we root, and or use your recovery without closed source files?
@social-design-concepts hasn't released his source yet, and he has implied it can't be done without his binary files. I don't know just asking.
When sdc releases his source will we be able to make scripts, and not use binary files? script files or command line, shows users exactly what is happening closed binaries files don't.
tomtom1265 said:
Vamp, a few questions for you.
Can this be done without any of sdc's binary files? Can this be done with just script files or command line?
Can we root, and or use your recovery without closed source files?
@social-design-concepts hasn't released his source yet, and he has implied it can't be done without his binary files. I don't know just asking.
When sdc releases his source will we be able to make scripts, and not use binary files? script files or command line, shows users exactly what is happening closed binaries files don't.
Click to expand...
Click to collapse
Sorry i'm taking so long, took some personal time for the holidays it can be done via script well t1 and t3 but then you run into the issue of being dependent on shared libraries in the droidboot.img which was what prevented restoring the system partition you would still be dependent on setpropex for changing read only props I tried to spell out everything in the splash but well see if I get around to adding the check that the adbd deamon has started and if not execute the binary direct tonight so I can post the source
Sent from my XT907 using XDA Free mobile app
tomtom1265 said:
Vamp, a few questions for you.
Can this be done without any of sdc's binary files? Can this be done with just script files or command line?
Can we root, and or use your recovery without closed source files?
@social-design-concepts hasn't released his source yet, and he has implied it can't be done without his binary files. I don't know just asking.
When sdc releases his source will we be able to make scripts, and not use binary files? script files or command line, shows users exactly what is happening closed binaries files don't.
Click to expand...
Click to collapse
@social-design-concepts has already answered your question, I will expand some what, Yes one can root via command line or via script I do it myself. You need to stop droidboot then start adbd, setup recovery, the recovery is set to be pushed or just use busybox to untar, temp mount /data to get adb key permission or adb wont connect. I have a special adbd which is 100% root all the time, so need to patch or change files to get root out of adbd, I also use the same adbd on my iview i700, to give me adb remount, I have a script to replace the stock adbd on each reboot, so I have adb root or adb remount anytime I want.
This adbd is private though, at the moment not share able.
But to answer your questions yes it can be done.
Here are my scripts, nothing fancy but they work.
adb reboot bootloader
setup_adb
Code:
#!/bin/bash
fastboot flash /sbin/adbd-recovery ./adbd-recovery
fastboot flash /sbin/partlink ./partlink
fastboot flash /tmp/busybox ./bb
fastboot flash /tmp/recovery.tar ./recovery.tar
fastboot oem stop_partitioning
partlink
Code:
#!/system/bin/sh
stop adbd
mount -t ext4 /dev/block/mmcblk0p9 /data
#stop fastboot
stop droidboot
rm -r /sbin/adbd
chmod 755 /tmp/busybox
/tmp/busybox tar -xvf /tmp/recovery.tar
mv /etc/recovery.fstab /etc/recovery.fstab.bak
cp /sbin/recovery.fstab /etc/recovery.fstab
chmod 755 /sbin/adbd-recovery
mv /sbin/adbd-recovery /sbin/adbd
/sbin/adbd
start adbd
umount /data
adb shell
/sbin/recovery &
vampirefo said:
Here are my scripts, nothing fancy but they work.
adb reboot bootloader
setup_adb
Code:
#!/bin/bash
fastboot flash /sbin/adbd-recovery ./adbd-recovery
fastboot flash /sbin/partlink ./partlink
fastboot flash /tmp/busybox ./bb
fastboot flash /tmp/recovery.tar ./recovery.tar
fastboot oem stop_partitioning
partlink
Code:
#!/system/bin/sh
stop adbd
mount -t ext4 /dev/block/mmcblk0p9 /data
#stop fastboot
stop droidboot
rm -r /sbin/adbd
chmod 755 /tmp/busybox
/tmp/busybox tar -xvf /tmp/recovery.tar
mv /etc/recovery.fstab /etc/recovery.fstab.bak
cp /sbin/recovery.fstab /etc/recovery.fstab
chmod 755 /sbin/adbd-recovery
mv /sbin/adbd-recovery /sbin/adbd
/sbin/adbd
start adbd
umount /data
adb shell
/sbin/recovery &
Click to expand...
Click to collapse
WOWW!!!!!!!!!
Beautiful work man, no more closed binary files.
As always very impressive.