Jump to content


Photo

[ROOT] Motoshare 2: Old Bug, New Exploit


  • Please log in to reply
985 replies to this topic

#841 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 44,208 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 10 May 2013 - 09:05 PM

You're running a 64 bit Linux install. You need the 32 bit libs.

Sent from my Xoom using Tapatalk HD
  • Int_Rnd_Pooka likes this

Non potest esse nisi unus


#842 tmyinc

tmyinc

    Resident Insomniac

  • News Writer
  • PipPipPipPip
  • 1,276 posts
  • Twitter:TMYINC
  • LocationPA
  • Current Device(s):Razr M, GN2, Nexus 10

Posted 10 May 2013 - 09:18 PM

sudo apt-get install ia32-libs



#843 sibujacob

sibujacob

    n00b

  • Members
  • Pip
  • 7 posts
  • Locationkuwait
  • Current Device(s):XT910

Posted 11 May 2013 - 03:52 AM

 

Moderator,

 

I spent the weekend working on something really lightweight to get this done easily, and I've finally got it working and ready.

Using Oracle VirtualBox with a Tiny Core Linux VM, I've managed to get this down to a 46 MB download.

Everything is automatic... helps the user get connected to SMB, then helps with getting connected with USB debugging before running the exploit.

I spent most of the entire weekend tweaking with Tiny Core Linux to get this ready. Please share. Where's the best place to start a new thread to get the word out about this?

 

Please Login or Register to see this Hidden Content

 

 

Here are the steps:
 
1) Install Sun VirtualBox on your Windows PC.
 
2) Download the VirtualBox .ova file here:
dl.dropboxusercontent.com/s/bb53ayj5c3nd5ie/Root_Bionic_JB.ova?token_hash=AAGSOYfPuDXTur_e9qlYl2JRERovPyfMwe-2xNzHXg4Lxg&dl=1
 
3) Import the .ova file into VirtualBox. (Click "File" then "Import Appliance".)
 
4) Start the imported VM in VirtualBox (Click the big "Start" Button. It has a green arrow icon.)
 
5) Follow the instructions on the Linux console.

 

SORRY TO SAY BUT YOUR DROPBOX LINK IS BROKEN. ...THANKS ANYWAY



#844 marty45714

marty45714

    Member

  • Members
  • PipPip
  • 45 posts

Posted 11 May 2013 - 05:12 AM

That's because you're looking at an old post. There is now a thread devoted to this:

Please Login or Register to see this Hidden Content

 

SORRY TO SAY BUT YOUR DROPBOX LINK IS BROKEN. ...THANKS ANYWAY



#845 Int_Rnd_Pooka

Int_Rnd_Pooka

    Member

  • Members
  • PipPip
  • 284 posts
  • Current Device(s):Bionic

Posted 11 May 2013 - 06:22 AM

anyone can confirm whether a wifi tethering could work?

 

I have setup a linux box (with samba). It's been connected to a router.

The Bionic surely will wifi connect to the router.

 

Will this connection work to replace the "usb" method (neither the router nor the linux box has a usb port)?

 

 

No you need both WIFI and the USB connection for the exploit to work.
The WIFI to set up the samba share and USB to push and run the exploit.

Sent from my Nexus 7 using Tapatalk HD

 

While it's always good to try new things, if you're wanting to take shortcuts or find an alternative method, just TRY it. Don't ask someone here if it's REALLY necessary to do ALL the steps to get this to work.

 

Yes. It is necessary to do all the steps. This is a ridiculously simple procedure. Meet the meager requirements for sharing, and run the script. End of story.

 

If you're trying to pioneer another method or to make it simpler for future users, just try it and see if it works. The worst that could possibly happen is you have to FXZ and start over because your idea didn't work. No harm done. If you're just trying to get away with not doing everything and want someone to give you the go ahead to cut a corner somewhere, then don't bother asking. Especially don't ask that question, then do it anyway when you're told not to, then come back asking for help on how to fix it. I'm not saying you're personally going to, just pointing out a pet peeve of mine from many other threads where people ask if they actually HAVE to do all the steps in a process and are told that they do, then they don't listen and do it how they want to anyway and come crying when they've bricked their phones

 

**Endrant**



#846 taller238

taller238

    n00b

  • Members
  • Pip
  • 6 posts

Posted 11 May 2013 - 10:14 AM

i think the debian I installed on pogoplug E02 is 32 bit, according to this link:

Please Login or Register to see this Hidden Content

"

Pogoplug (E02)

images.jpg
  1. ISA: 32-bit ARMv5TE

  2. CPU: Sheeva Feroceon @ 1.2 GHz (single-issue) – In a Marvell MV88F6281 (2008)

  3. Memory: 256 MB (not expandable), 16K/16K L1 caches

  4. Cost: $30 and external hard drive.

  5. Acquired: 7/2012 (new via Amazon.com)

  6. Installation:

    Please Login or Register to see this Hidden Content

    .

"

 

Also I tried to apt-get install the 32bit libs but it's not found.

 

 

You're running a 64 bit Linux install. You need the 32 bit libs.

Sent from my Xoom using Tapatalk HD



#847 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 44,208 posts
  • Current Device(s):S21 Ultra, Pixel 6

Posted 11 May 2013 - 10:59 AM

Then good luck.  No idea.


Non potest esse nisi unus


#848 maros

maros

    n00b

  • Members
  • Pip
  • 6 posts

Posted 11 May 2013 - 11:55 AM

i think the debian I installed on pogoplug E02 is 32 bit, according to this link:

Please Login or Register to see this Hidden Content



"
...
Also I tried to apt-get install the 32bit libs but it's not found.
 
 


You're running a 64 bit Linux install. You need the 32 bit libs.


Sent from my Xoom using Tapatalk HD


In this case you need to run arm version of adb tool. The version in archive is for x86 architecture. It cannot be run on arm processor.

In fact, I don't understood your current setup. Are you running the exploit on popoplug? Where you have connected the phone? The USB cable.

In fact, the samba is only needed to store the exploit binary. The script itself could be started on windows. You only need to rewrite it to dos or extract commands and run them manually on windows.

Sent from XT910

#849 sibujacob

sibujacob

    n00b

  • Members
  • Pip
  • 7 posts
  • Locationkuwait
  • Current Device(s):XT910

Posted 12 May 2013 - 04:34 AM

Items needed to use the Bootable USB file:
1) A PC that can boot off of a USB drive.
2) 2GB or larger USB flash drive.
3) 2.2 GB free space on your Windows PC HDD
4) Linux image with the hack (Found here:

Please Login or Register to see this Hidden Content

)
5) Alex's USB Image Tool  V1.61 (Found here:

Please Login or Register to see this Hidden Content

)

Steps to run to gain root access.
1) Unzip Alex's Image tool to your hard drive.  (Keep all the files together.  Note Where you unzip the files to.)
2) Unzip the Linux image.  (Note where you unzip the file to.)
3) Insert your USB drive into your PC.  Note we will overwrite the entire USB.  Backup your files first if needed.)
4) Run Alex's Image tool. "USB Image Tool.exe"
5) Select your USB drive in the screen to the left.
6) Choose restore in the menu at the bottom.
7) Select the linux image you downloaded. "Linux-JB.img"
8) Confirm the overwrite of the drive.  (Wait for the process to finish and tell your the image is complete.)
9) Reboot your PC and boot off of the USB drive.
      (This is where we follow the original instructions.)
10) Once in Ubuntu open a terminal window and get your IP with the "ifconfig" command.
      At this point, you'll need to know the IP address of your Linux host, which you can get by running "ifconfig" from your terminal (it should be of the form "192.168.x.x").
11) cd /tmp/share
12) On your Android device. Ensure you have enabled USB Debugging Mode (under Settings -> Development Settings). Ensure your device is connected via Wifi.
13) Open the "Files" app, and select "Remote storage". Click "Add storage", and fill in fields as follows:

Host IP address:         [your Linux machine's IP address]
Domain name:            WORKGROUP
Shared folder name:  share
User:                          guest
Password:                  droidrzr
setup the share on your phone.

14) On the linux machine, in the terminal window, execute this command. "./run.sh"


Helpfull hints:  
Phone needs to be in "Media device (MTP)" mode NOT "Mass Storage."  If you don't change this you will just get stuck at the following:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

 

If you are running the following command: "sudo apt-get install samba" and get an error.  run "sudo apt-get upgrade"  Then run "sudo apt-get install samba"  This should fix the issue.

The USB image file is HUGE about 1GB.

 

I will be on as much as I can to help support.

 

Good Luck,

Rap

Oh please, you know very well that it is not simple to connect via a wiFi on a mobile especially when you are in a JB environment. none of these are useful unless people can connect their mobile to their computer using a wifi connection !!!



#850 Int_Rnd_Pooka

Int_Rnd_Pooka

    Member

  • Members
  • PipPip
  • 284 posts
  • Current Device(s):Bionic

Posted 12 May 2013 - 05:42 AM

Wifi on
Select AP

Done

#851 SirEagle

SirEagle

    Member

  • Members
  • PipPip
  • 41 posts

Posted 12 May 2013 - 06:35 AM

Oh please, you know very well that it is not simple to connect via a wiFi on a mobile especially when you are in a JB environment. none of these are useful unless people can connect their mobile to their computer using a wifi connection !!!

Why do you say this? Connecting to WiFi is about the easiest thing there is.


Droid Bionic - JB - Rooted

 


#852 Int_Rnd_Pooka

Int_Rnd_Pooka

    Member

  • Members
  • PipPip
  • 284 posts
  • Current Device(s):Bionic

Posted 12 May 2013 - 07:14 AM

I'm going to assume you're actually referring to mounting a samba share on your phone. That's really not so terribly difficult either.

I'm not normally one to discourage people from doing new things, but if you can't mount a shared directory when you're the one who shared it and you know the username and password, maybe obtaining root is not something you need to be doing. It opens up whole new ways to destroy your phone if you aren't careful and do a little looking into what you're doing before you do it. If you're not going to research how to mount a share (when the instructions are laid out fairly plainly in the OP), then I suggest you don't root your phone and save everyone else the trouble of fixing your phone for you later.

#853 Int_Rnd_Pooka

Int_Rnd_Pooka

    Member

  • Members
  • PipPip
  • 284 posts
  • Current Device(s):Bionic

Posted 12 May 2013 - 07:14 AM

TL;DR - RTFM

#854 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,272 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 12 May 2013 - 07:27 AM

Oh please, you know very well that it is not simple to connect via a wiFi on a mobile especially when you are in a JB environment. none of these are useful unless people can connect their mobile to their computer using a wifi connection !!!

The only known issue that I am aware of is if you have an older router. A list was posted somewhere with a dozen or more router/manufacturers that had older code and couldnt sync properly with JB


  • Int_Rnd_Pooka likes this

#855 thesantorini

thesantorini

    n00b

  • Members
  • Pip
  • 9 posts
  • LocationFlorida
  • Current Device(s):Droid Bionic

Posted 12 May 2013 - 11:14 AM

The entitlement hack enables BT, USB, and WiFi (assuming but I never use this)! I can confirm that BT and USB tethering work! Thank you Samuri for telling me about that!


So this hack works, but with one small problem which is kind of a big deal for me. It seems that I can only tether one device at a time. It's either USB tether, or BT tether. Not both simultaneously like before. I have confirmed that WiFi tethering allows multiple devices, but I would like to avoid this if possible. Any other tricks out there that addresses this that I haven't found yet?

#856 fwtx

fwtx

    n00b

  • Members
  • Pip
  • 19 posts

Posted 13 May 2013 - 07:40 PM

alright so firstly forget all this samba and guest account nonsense. that got me nowhere. somewhere along the line of setting up samba i enabled root access (this doesn't seem to matter but including it to be thorough) which is trickier on 10.6 osx because useradd is a linux command and dscl echoed back domain admin errors so if you WANT to do this go to preferences, accounts, click the lock and log in, click log in options then network account server "join/add" then "open directory" click the lock again, now running "directory utility" access the edit menu which allows you to either enable or disable root user. Again, not sure if this was totally necessary but netinfo manager is gone in 10.6

 

ok real next step is making the smb shares on your mac available.

go to system preferences again but open up sharing instead of accounts

turn on file sharing and go to options. I disabled afp and ftp and only enabled SMB

instead of using /tmp/share or /public I just put motoshare2 in the root of my HD and shared it 

make sure that motoshare folder can be read and written to and that you can share on SMB using an account to which you have the password

 

go to the files app on your bionic. Make sure both mac and bionic are on the same wifi network.

add network storage, using the IP address from the sharing preference pane on your mac. Then use WORKGROUP, motoshare2 for shared folder, and log in using your (i used my default which is an administrative account) account which was enabled to access the shared files/folder.

once the bionic has logged into the network share just ensure debugging is enabled, plug in the bionic to the mac

then go to the terminal and cd to motoshare2

then sudo /motoshare2/run.sh and bob's your uncle

 

if you want to make sure you don't get typos i drag and drop a lot of stuff into the terminal window from the finder when I can. (for instance just typing sudo and a space then dragging in run.sh and hitting enter.

I want to reiterate the clean up process did not work i think the adb server needed to be restarted or something. maybe look at the script to see where that fell down. Clean up was not necessary for me as superuser was present upon reinstall and voodoo indicated the device was rooted.

 whenever i try to set up my share i get an error on the bionic side saying there is a problem with remote host, repair your network.

im doing:

IP: ip from share window 

domain: WORKGROUP

shared folder: motoshare2

user name: my name (first last) because thats my admin account

password: my admin password

 

my motoshare2 is on the root of my HD and i have SMB sharing on.

 

any idea whats going wrong?



#857 livinginkaos

livinginkaos

    I don't know what I'm doing anymore.....

  • Administrator
  • 15,282 posts
  • Google+:Hangouts - livinginkaos@gmail.com
  • LocationOregon
  • Current Device(s):Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7

Posted 14 May 2013 - 03:29 AM



alright so firstly forget all this samba and guest account nonsense. that got me nowhere. somewhere along the line of setting up samba i enabled root access (this doesn't seem to matter but including it to be thorough) which is trickier on 10.6 osx because useradd is a linux command and dscl echoed back domain admin errors so if you WANT to do this go to preferences, accounts, click the lock and log in, click log in options then network account server "join/add" then "open directory" click the lock again, now running "directory utility" access the edit menu which allows you to either enable or disable root user. Again, not sure if this was totally necessary but netinfo manager is gone in 10.6
 
ok real next step is making the smb shares on your mac available.
go to system preferences again but open up sharing instead of accounts
turn on file sharing and go to options. I disabled afp and ftp and only enabled SMB
instead of using /tmp/share or /public I just put motoshare2 in the root of my HD and shared it 
make sure that motoshare folder can be read and written to and that you can share on SMB using an account to which you have the password
 
go to the files app on your bionic. Make sure both mac and bionic are on the same wifi network.
add network storage, using the IP address from the sharing preference pane on your mac. Then use WORKGROUP, motoshare2 for shared folder, and log in using your (i used my default which is an administrative account) account which was enabled to access the shared files/folder.
once the bionic has logged into the network share just ensure debugging is enabled, plug in the bionic to the mac
then go to the terminal and cd to motoshare2
then sudo /motoshare2/run.sh and bob's your uncle
 
if you want to make sure you don't get typos i drag and drop a lot of stuff into the terminal window from the finder when I can. (for instance just typing sudo and a space then dragging in run.sh and hitting enter.
I want to reiterate the clean up process did not work i think the adb server needed to be restarted or something. maybe look at the script to see where that fell down. Clean up was not necessary for me as superuser was present upon reinstall and voodoo indicated the device was rooted.


 whenever i try to set up my share i get an error on the bionic side saying there is a problem with remote host, repair your network.
im doing:
IP: ip from share window 
domain: WORKGROUP
shared folder: motoshare2
user name: my name (first last) because thats my admin account
password: my admin password
 
my motoshare2 is on the root of my HD and i have SMB sharing on.
 
any idea whats going wrong?


How long is your password? Short and simple is key.

b2wvCBn.png

Sig by livinginkaos
Samsung S8+ / Pixel XL 128gb / iPhone 7+ 256gb / iPad Pro 12.9" / Samsung Chromrbook Plus / Pixel C / Nexus 6p 128gb / Nexus 6 / Nexus 6 on Fi / Nexus 9 / Moto 360^2 / Nvidia Shield TV Pro / Nvidia Shield Tablet / HTC EVODesign on FreedomPop / Chromecast / Surface Pro 3 i7 / Samsung Tab Pro 12.2 / Lenovo Win8 Tab / Eee Slate / '13 Nexus 7


#858 bioniccrazy

bioniccrazy

    n00b

  • Members
  • Pip
  • 7 posts

Posted 14 May 2013 - 11:17 AM

When I try to set up my remote storage i get an error on the bionic side saying there is a problem with remote host, repair your network. Anyone have any ideas ?



#859 junnu007

junnu007

    n00b

  • Members
  • Pip
  • 1 posts

Posted 15 May 2013 - 12:02 AM

 

Moderator,

 

I spent the weekend working on something really lightweight to get this done easily, and I've finally got it working and ready.

Using Oracle VirtualBox with a Tiny Core Linux VM, I've managed to get this down to a 46 MB download.

Everything is automatic... helps the user get connected to SMB, then helps with getting connected with USB debugging before running the exploit.

I spent most of the entire weekend tweaking with Tiny Core Linux to get this ready. Please share. Where's the best place to start a new thread to get the word out about this?

 

Please Login or Register to see this Hidden Content

 

 

Here are the steps:
 
1) Install Sun VirtualBox on your Windows PC.
 
2) Download the VirtualBox .ova file here:
dl.dropboxusercontent.com/s/bb53ayj5c3nd5ie/Root_Bionic_JB.ova?token_hash=AAGSOYfPuDXTur_e9qlYl2JRERovPyfMwe-2xNzHXg4Lxg&dl=1
 
3) Import the .ova file into VirtualBox. (Click "File" then "Import Appliance".)
 
4) Start the imported VM in VirtualBox (Click the big "Start" Button. It has a green arrow icon.)
 
5) Follow the instructions on the Linux console.

 

 

Thank you very much.... got it in one go!!!!!

but my superuser is asking su binary to be updated but when I tap on install it gives error installing superuser.... any help would be appreciated..



#860 robinroy

robinroy

    n00b

  • Members
  • Pip
  • 1 posts

Posted 16 May 2013 - 06:26 AM

I started ubuntu.  but there is no share folder under tmp






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users