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.
Related
OK. Firstly, I have extensive experience with rooting moto droids and custom roms. That said I got cocky and didn't do enough homework trying to root my girls Eris and proceeded following the instructions in the "1.5 to rooted 2.1" thread. Step 1 went fine. I THINK I have root access. Anyway, like I was tired and couldn't get adb shell working so I left it at that with intent to finish today when I get home from work. Now she's telling me her icons are different and some are linking to different programs. Any ideas? Second, can someone point me in the direction of an adb shell how to, on my Droid I can just use terminal emulation and don't actually need a computer so I'm not too familiar with the process... sorry for the stupid newborn questions, don't pull the flame throwers out yet, thanks!
You can use terminal emulator, same thing for the most part as adb... I use that more then adb, faster then having to connect to a pc IMO.
I tried the terminal emulator and got adb not found or not allowed or some craziness like that. Does that mean I didn't root like I thought? Also, any clue about the icon s changing or linking to other apps like shes claiming? I'm going to try again when she gets home
In the terminal emulator you would not need to type adb.. adb is the program you would be using on a pc to talk to the phone... what is it that you are trying to type through adb or the terminal?
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
step 3. im an ass. ok so dont type the adb. like i said, not much exp in this part... im guessing i dont tye shell either, but i do type mount?
evilsway said:
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
step 3. im an ass. ok so dont type the adb. like i said, not much exp in this part...
Click to expand...
Click to collapse
Oh I see, for that yes you will need to get the SDK setup on your PC as per step 2... There is another thread that has a batch file that does all of this for you. You still need the SDK though.
see: http://forum.xda-developers.com/showthread.php?t=651669
ok, i have the sdk, i followed these instructions to the letter, and i still couldnt get it running last night, where in the sdk do i do this from or is it a command promp, or can i use the terminal emulator?
yes in the command prompt, typically adb.exe will be in your tools folder.
also, and i know im being a pain now, but by adb does it mean the adb in the tools directory of the sdk, i click it and it runs a script then dissapears.
evilsway said:
also, and i know im being a pain now, but by adb does it mean the adb in the tools directory of the sdk, i click it and it runs a script then dissapears.
Click to expand...
Click to collapse
yes, adb needs to be ran through the command prompt, if you click on it in windows it wont work... read the thread I linked you to, you wont need to run adb if you use that method, it does it all for you.
yeah im downloading the file now, but im just curious, now i want to be able to do it just to do it. i hate when i cant figure crap like this out,
so far ive done this, opened command promp, put in C:\androidsdk\android-sdk-windows\tools\adb.exe and it runs a script then nothing
evilsway said:
yeah im downloading the file now, but im just curious, now i want to be able to do it just to do it. i hate when i cant figure crap like this out,
so far ive done this, opened command promp, put in C:\androidsdk\android-sdk-windows\tools\adb.exe and it runs a script then nothing
Click to expand...
Click to collapse
go to start, run and type cmd and enter. then in that window
you have to change to the tools directory at the command prompt like so"
cd androidsdk\android-sdk-windows\tools
then type adb
Renocat said:
go to start, run and type cmd and enter. then in that window
you have to change to the tools directory at the command prompt like so"
cd androidsdk\android-sdk-windows\tools
then type adb
Click to expand...
Click to collapse
Yeah, once you do what he states and type...
cd androidsdk\android-sdk-windows\tools ... or where ever you have your SDK saved at on your computer ... you should be good to start running those scripts in the directions.
Hi,
Did a search and someone said they were able to root with thecubed method on Mac via Terminal, but I've had no luck so far. Are there any other options for us Mac users?
Thanks
BTW I did see some instructions but it only applies to Verizon. I have the international version D802.
Any help would be greatly appreciated.
use virtual machine and use windows?
I haven't found any easy way to do it, other that running bootcamp and windows on the mac..
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
I opened root.bat as a text file but as far as how to input the commands I'm not sure what to do as it seems to differs from the video. Sorry I'm not that familiar working with Terminal.
If you could help out that would be great.
Thanks
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
sell ur POS apple and get a pc...?
digitard said:
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
Click to expand...
Click to collapse
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
xdabbeb said:
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
Click to expand...
Click to collapse
Yes already have adb set up. Thanks for this. Really appreciate it.
No problem. What version of the G2 do you have?
---------- Post added at 11:49 PM ---------- Previous post was at 11:48 PM ----------
Ignore that, I just saw you mentioned the international version
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Has anyone tried this method?
Sent from my LG-D802 using Tapatalk
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
ck37 said:
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
Click to expand...
Click to collapse
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
xdabbeb said:
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
Click to expand...
Click to collapse
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
ck37 said:
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
Click to expand...
Click to collapse
What I did was installed flashify from the market. This app allows you to backup and then flash a new recovery. Make sure you dl the right one for your device!
Sent from my LG-VS980 using Tapatalk
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.
Hello everyone,
I have a Samsung Galaxy S II (I9100) with Cyanogenmod 11 (Snapshot M12) installed. Recently I dropped my phone and the screen was completely shattered. The display does not work, neither does the touch. However, the phone works fine as I can turn it on and connect it via USB to my computer and access the data on my internal memory. Although USB debugging is enabled on my phone, I am unable to do anything because the computer isn't authorised i.e. I cannot press "OK" on the authentication prompt that I would have otherwise normally seen on the screen (screenshot attached). Is there any way to bypass this prompt or a workaround for it? I basically need to get a Nandroid backup of my phone and then factory reset it.
P.S.: I tried to access my phone via a program called "Android Control" but apparently it is practically useless without the debugging privileges.
Thanks.
Solved!
This guide assumes that USB debugging was enabled on your device before you broke it. You can enable USB debugging via recovery using:
Code:
adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
After digging through various threads I finally managed to bypass the secure USB prompt on my Galaxy SII with a shattered screen.
For this method to work you need another device running Android 4.4.2 or above with USB debugging enabled and the same computer authorised from that device i.e. connect that device to your computer and press "OK" on the authorisation prompt that appears on screen for secure USB debugging. Let us call this device the "authorised device".
"adb_keys" is the file we need from the authorised device which is located in /data/misc/adb/
Normally you must be rooted to take the adb_keys file from the device using "Root explorer" or "ES File Explorer" but I will assume that the authorised device is unrooted. You don't need to root it. However, if your authorised device is rooted then simply copy the adb_keys file on your computer and jump directly to Step 5.
Steps:
Connect the authorised device to your computer using USB (debugging enabled) and open a command prompt with administrator privileges.
To get the "adb_keys" file, use this command:
adb pull /data/misc/adb/adb_keys <destination path>/adb_keys
For example:
adb pull /data/misc/adb/adb_keys c:/adb_keys
The above command will save the adb_keys file to the root of your C: drive. You can change the destination folder to your liking. Now the job of the authorised device is done. You can disconnect it and disable USB debugging.
Once you get a copy of adb_keys, reboot the phone with the broken screen into recovery.
Now connect the broken phone to the computer using USB.
We need to copy the adb_keys file to the broken device. Use the command below:
adb push <file location> /data/misc/adb
For example:
adb push c:/adb_keys /data/misc/adb
After the file is copied, reboot your device using "adb reboot" and voila! You can now use adb shell.
Special thanks to torankusu for this post which helped me compile this guide.
Check out this thread by k.janku1 if you want to have full control over your device even with a broken screen (requires Java Runtime Environment and Visual C++ redistributable). This tool lets you use your device through your Windows PC even if your touchscreen doesn't work or you can't see anything.
P.S.: My broken device was a Samsung Galaxy SII running Cyanogenmod 11 (M12) and my authorised device was an unrooted Moto G running stock ROM.
Thanks man.
I'm (noob) trying to follow the guide which exactly fits my situation.
Status : Broken SGS7 screen with USB debugging enabled but cannot accept the computer
SGS4 backup phone where i extracted the adb_key
both are not rooted and running stock OS
Unfortunately i get stuck between step 6/7... When i reboot to recovery mode the windows does not recognize neither of the phones when conneted to USB. Therefore i cannot run the ADB command and copy the key on my broken phone (SGS7).
i can choose the "aply update From ADB" and then the computer recognizes the phone and i can find it in ADB devices "sideload" but here i cannot use the command "adb push....."
Ii've tried updating drivers googled alot, but without luck...
what am i missing?
input very appreciated
I too am a noob who was trying to follow this guide, which also exactly fit my situation. My status was a broken Sony Xperia screen with USB debugging enabled, but I was unable to click on the "accept" button whenever I hooked my phone up to my PC. I extracted a working adb_key from my new Asus ZooXS phone; neither phone is rooted, and both are running stock Android OS.
Unfortunately, I got stuck right between Steps 7 & 8; Windows did not allow me to use the ADB Push command to copy the key onto my broken Sony Xperia. I could Pull the key from my Asus using ADB just fine, but not the other way around.
I did eventually find an alternative solution: I used an OTG device & hooked up a mouse to my Sony Xperia so that I could get past the broken screen issues & navigate to Settings > Bluetooth. I then borrowed a Bluetooth Mouse & "discovered" it with my broken Sony Xperia. I could then unplug the OTG device & re-connect my phone to my PC via USB, & then click on the screen using the Bluetooth Mouse to "accept" my computer as always being authorized to perform USB debugging. Afterwards, I was able to use Helium backup to pull off most of my important data from my phone.
Hope this helps others who are running into the same problem....
i don't get it - authorizing adb via adb
The steps maq_ posted helped me rescue my data from my broken OP3. Combined with the information from here: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android which indicates the files between the computer (running adb) and the key file you copy to /data/misc/adb should "match" with each other. Indeed, you might need to have been bootloader unlocked (with a custom recovery) to use adb push to copy the adb_keys file to your broken phone. For me, since my broken phone was rooted I used a terminal emulator with the 'su' command (after successfully getting the file onto my broken phone) to copy the file over to /data/misc/adb.
Some tips that might help newbs before following maq_'s steps: First, re-install another copy of adb (remember the path you installed to on your PC). Second, erase contents of c:\Users\$name\.android\ (which contains existing keys generated by adb). Third, run adb kill-server to make sure other instances of adb don't confuse things.
maq_ said:
This guide assumes that USB debugging was enabled on your device before you broke it. You can enable USB debugging via recovery using:
After digging through various threads I finally managed to bypass the secure USB prompt on my Galaxy SII with a shattered screen.
For this method to work you need another device running Android 4.4.2 or above with USB debugging enabled and the same computer authorised from that device i.e. connect that device to your computer and press "OK" on the authorisation prompt that appears on screen for secure USB debugging. Let us call this device the "authorised device".
"adb_keys" is the file we need from the authorised device which is located in /data/misc/adb/
Normally you must be rooted to take the adb_keys file from the device using "Root explorer" or "ES File Explorer" but I will assume that the authorised device is unrooted. You don't need to root it. However, if your authorised device is rooted then simply copy the adb_keys file on your computer and jump directly to Step 5.
Steps:
Connect the authorised device to your computer using USB (debugging enabled) and open a command prompt with administrator privileges.
To get the "adb_keys" file, use this command:
adb pull /data/misc/adb/adb_keys <destination path>/adb_keys
For example:
adb pull /data/misc/adb/adb_keys c:/adb_keys
The above command will save the adb_keys file to the root of your C: drive. You can change the destination folder to your liking. Now the job of the authorised device is done. You can disconnect it and disable USB debugging.
Once you get a copy of adb_keys, reboot the phone with the broken screen into recovery.
Now connect the broken phone to the computer using USB.
We need to copy the adb_keys file to the broken device. Use the command below:
adb push <file location> /data/misc/adb
For example:
adb push c:/adb_keys /data/misc/adb
After the file is copied, reboot your device using "adb reboot" and voila! You can now use adb shell.
Special thanks to torankusu for this post which helped me compile this guide.
Check out this thread by k.janku1 if you want to have full control over your device even with a broken screen (requires Java Runtime Environment and Visual C++ redistributable). This tool lets you use your device through your Windows PC even if your touchscreen doesn't work or you can't see anything.
P.S.: My broken device was a Samsung Galaxy SII running Cyanogenmod 11 (M12) and my authorised device was an unrooted Moto G running stock ROM.
Click to expand...
Click to collapse
Thanks for clarifying TWRP and UNLOCKED bootloader is required.
TWRP is not available for some devices. Luckily i found a ported recovery.img for my broken tablet. Unfortunately adb shows device as offline in TWRP, adb does not work in recovery.
I finally managed installing adbkey.pub via script. does not work on dm-verity, KNOX enabled or locked devices!
1. install ODIN (Samsung) or SPFLASH tool (MTK)
2. get the firmware for your device (fw.updato.com)
3. unpack system.img
4. add your own shell script (backdoor) to /system/etc/init.d, /system/etc/install-recovery.sh or whatever
5. repack your custom system.img
6. flash system.img
7. copy RSA Key to /sdcard via MTP
My (backdoor) shell script was a watchdog looking for another shell script on /sdcard. The second shell script was copying adbkey.pub from /sdcard to /data partition. This worked without root because init scripts run with root permissions on boot.
With this method i was able to backup userdata from my broken tablet via adb. TWRP has adb backup option too, in case touch screen is broken.
I will explain in detail on request.
edit: for experts only: instead of flashing whole system.img, you can do slight modification using Tarek Galal inception Utility via ODIN, for example "Place your adb keys, configure USB debugging"
edit2: most recent version of that backdoor script can be found here
https://forum.xda-developers.com/showthread.php?t=4111923
my touch is broken and i cant select usb authorization as ok... device is not rooted...
device name is sony z3...
i have another device with 4.4 and with that device i made a backup of drm keys... now what should i do?
sorry if english is bad... helpwill be really appriciated....
hello, i have te same problem with my huawei p smart. does this work for huawei to?
no, but you can connect OTG keyboard and unlock screen. that should unlock MTP you can at least transfer pictures. even Monitor via MHL/HDMI is possible for some devices
https://dtmedia.tech/list-of-mhl-compatible-phones
speedin said:
I'm (noob) trying to follow the guide which exactly fits my situation.
Status : Broken SGS7 screen with USB debugging enabled but cannot accept the computer
SGS4 backup phone where i extracted the adb_key
both are not rooted and running stock OS
Unfortunately i get stuck between step 6/7... When i reboot to recovery mode the windows does not recognize neither of the phones when conneted to USB. Therefore i cannot run the ADB command and copy the key on my broken phone (SGS7).
i can choose the "aply update From ADB" and then the computer recognizes the phone and i can find it in ADB devices "sideload" but here i cannot use the command "adb push....."
Ii've tried updating drivers googled alot, but without luck...
what am i missing?
input very appreciated
Click to expand...
Click to collapse
Hi
I have the same connection impact when I use adb command too. Is there any solution for this situation?
Thank you.
aIecxs said:
Thanks for clarifying TWRP and UNLOCKED bootloader is required.
TWRP is not available for some devices. Luckily i found a ported recovery.img for my broken tablet. Unfortunately adb shows device as offline in TWRP, adb does not work in recovery.
I finally managed installing adbkey.pub via script. does not work on dm-verity, KNOX enabled or locked devices!
1. install ODIN (Samsung) or SPFLASH tool (MTK)
2. get the firmware for your device (fw.updato.com)
3. unpack system.img
4. add your own shell script (backdoor) to /system/etc/init.d, /system/etc/install-recovery.sh or whatever
5. repack your custom system.img
6. flash system.img
7. copy RSA Key to /sdcard via MTP
My (backdoor) shell script was a watchdog looking for another shell script on /sdcard. The second shell script was copying adbkey.pub from /sdcard to /data partition. This worked without root because init scripts run with root permissions on boot.
With this method i was able to backup userdata from my broken tablet via adb. TWRP has adb backup option too, in case touch screen is broken.
I will explain in detail on request.
edit: for experts only: instead of flashing whole system.img, you can do slight modification using Tarek Galal inception Utility via ODIN, for example "Place your adb keys, configure USB debugging"
Click to expand...
Click to collapse
ThanK You Senior for posting the solution.
Can you please help me in this.
I am using mediatek device
Didn't find /system/etc/init.d
Didn't find /system/etc/install-recovery.sh
But found "" install-recovery.sh "" inside /system/bin folder
Now do i have to only paste the your given rsa_copy.sh scrip in this file?
and paste the pub_keys from authorize device to /sdcard/
That method will most likely fail because dm-verity deny booting if any modifications detected. You can however patch boot.img with Magisk (to disable dm-verity). What android version/mediatek device you have?
Yes you can replace install-recovery.sh or add line
Code:
/system/bin/sh /path/to/rsa_copy
/system/bin/sh /path/to/99userinit_daemon
But I do not recommend this method any longer, modifications in /system should be avoided. Instead you could simply disable RSA authorization and enable usb-debugging in default.prop
https://forum.xda-developers.com/showthread.php?t=1867446
I recommend AIK it is capable of re-signing AVBv1-signed boot.img
I have android 7
mt6753
init.d is n't here
placing code inside install-recovery.sh didn't work because it runs with root privileges
now i am trying to cp /system/adbkey.pub /data/misc/adb/adb_keys
and tring to modify boot.img
aIecxs said:
That method will most likely fail because dm-verity deny booting if any modifications detected. You can however patch boot.img with Magisk (to disable dm-verity). What android version/mediatek device you have?
Yes you can replace install-recovery.sh or add line
Code:
/system/bin/sh /path/to/rsa_copy
/system/bin/sh /path/to/99userinit_daemon
But I do not recommend this method any longer, modifications in /system should be avoided. Instead you could simply disable RSA authorization and enable usb-debugging in default.prop
https://forum.xda-developers.com/showthread.php?t=1867446
I recommend AIK it is capable of re-signing AVBv1-signed boot.img
Click to expand...
Click to collapse
Senior Help. (I am extra noob)
I also noticed data folder inside boot.img can I directly put " adb" folder here?
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
aIecxs said:
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
Click to expand...
Click to collapse
I attempted this trick with working phone's boot.img (working img) but even after repacking boot.img without edits phone stuck/hangs on boot (without animation)
Recommend me a good tool for unpacking and repacking boot.img with guide.
(I already tried with android kitchen on Linux (This one's boot.img make phone report after boot animation) and unpack/repack Tool on windows ( http://www.mediafire.com/file/nvo2popw26k4mit/IMG_Extractor_2.0.rar/file) and this one's boot.img doesn't boot phone to boot animation and hangs on initial logo)
I tried this on other working phone
@osm0sis may have a look into boot.img can you upload please?
aIecxs said:
no. data directory is just mount point. no longer required to place adb_keys, just edit default.prop with Notepad++
Click to expand...
Click to collapse
I attempted this trick with working phone's boot.img (working img) but even after repacking boot.img without edits phone stuck/hangs on boot (without animation)
Recommend me a good tool for unpacking and repacking boot.img with guide.
(I already tried with android kitchen on Linux (This one's boot.img make phone report after boot animation) and unpack/repack Tool on windows ( http://www.mediafire.com/file/nvo2popw26k4mit/IMG_Extractor_2.0.rar/file) and this one's boot.img doesn't boot phone to boot animation and hangs on initial logo)
aIecxs said:
@osm0sis may have a look into boot.img can you upload please?
Click to expand...
Click to collapse
Yes please,
LT700 is for testing purpose workig phone.
Both phones are almost from the same manufacturer (Note: but different models) Even unmodified repacked file does make phone boot success.
Uploading both stock and magisk patched working images of both phone
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.