4th Update 5/2/2013 - Found a bug... Nothing that would affect the overall functionality, but it could cause some users to think that their phone is successfully connected via USB debugging, when it really isn't.
Update: 5/2/2013 - Per user requests, adding link to VirtualBox download site on the original post.
3rd Update 5/1/2013 - I changed the code that 'finds' the exploit file to make sure it get executed successfully. It's now using the "PATH" environment to do this. This is more reliable than the actual Linux 'find' command I was using before. Also added some additional instructions to clarify some steps based on feedback from users. Finally, added code to detect if the network adapter is not configured correctly. It will alert the user to configure the network adapter properly in the VirtualBox application.
2nd Update 5/1/2013 - I added some lines to the script to stress the importance of pressing one of the three hardware buttons on the phone (Volume up, Volume Down, or Power) once the exploit has been executed. After discussing this with the author of the exploit, this is an important step to obtaining root.
UPDATE 5/1/2013 - New and improved .ova file. Contains improved logic in the exploit script to help with some of the problems that have been encountered by users.
If you've had trouble rooting, please download the new version and try again!
Hey folks, I'm a UNIX admin by profession, so I took the challenge over the weekend to come up with an easy root process for Bionic stock Jelly Bean, specifically for those who aren't familiar with Linux.
I decided to build a Linux VM under Oracle VirtualBox on my Windows PC. This seemed like the logical choice since VirtualBox is free, a relatively small download, is easy to install and it's easy to import VMs.
My first attempt was using CentOS Linux. It worked, but the file required for users to download was over 450MB... Back to the drawing board!
Started looking for very small Linux distros and found Tiny Core Linux. This worked well. The file required for download is 50 MB.
Everything you need to root the Bionic is here and it is automatic. The process will walk you through connecting to the Samba file share, connecting the phone in USB debugging mode, and OF COURSE, it will run the process to root the phone.
Here are the steps:
1) Install Sun VirtualBox on your Windows PC.
http://download.virtualbox.org/virtualbox/4.2.12/VirtualBox-4.2.12-84980-Win.exe
Note: We've had one report that this file also works with VMWare Workstation and VMWare Player. If you don't want to install VirtualBox feel free try the file with VMWare.
2) Download the VirtualBox .ova file containing the Linux VM from one of the following links:
http://www.knite.net/Bionic/Root_Bionic_JB_20130501-4.ova
http://www.mediafire.com/?a2i6forosp77xrd
https://dl.dropboxusercontent.com/s...fhiAIiSwc0jD1AdVFNY27QdoeKP9ot_7IdDetSvw&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.
That should do it. If you need help I will be monitoring this thread.
Willing Tester
I am not familiar with Linux but I am familiar with root, supersuser, recovery, and fxz/rsd lite. I am up for a new phone next month so I am willing to try this on my Bionic. This doesn't sound too hard....(famous last words). Will try on my Windows 7 laptop.
Will report if this works. Won't be able to until later today.
Thank you OP!
Found a problem with the script. Should work now. Download and import again, if you've already downloaded. I also managed to get the download down to 46MB by defragging and compacting the .vmdk file.
dl.dropboxusercontent.com/s/bb53ayj5c3nd5ie/Root_Bionic_JB.ova?token_hash=AAGSOYfPuDXTur_e9qlYl2JRERovPyfMwe-2xNzHXg4Lxg&dl=1
Downloading new link now. Haven't tried to root yet. I'm at work right now.
Do you have any other suggestions before I start? I don't have to be completely stock do I...? (all stock apps, no superuser, etc.) I am on stock jelly bean 4.2.1, ver. 98.72.22.XT875.Verizon.en.US, stock recovery...but I did use OTA Rootkeeper so I have a (semi-functioning) superuser install. Do you suggest starting fresh with fxz?
I will be home in a couple hours to give it a try.
Well....my problem is that I can get my phone to connect to the share. My guess is that its due to a network thing on my laptop. Is the phone supposed to be connected via USB when I try that?
Awesome! I've got root again thanks to this. Was very easy to follow your instructions, great job!
Great, I just wanted to do something to make it easier for everyone, since so many seemed to be struggling with Linux.
lc75 said:
Awesome! I've got root again thanks to this. Was very easy to follow your instructions, great job!
Click to expand...
Click to collapse
So, in order for the phone to connect to the share, your phone needs to be connected by wi-fi to the same network as the computer that is running VirtualBox and the VM.
TechnoHippie said:
Well....my problem is that I can get my phone to connect to the share. My guess is that its due to a network thing on my laptop. Is the phone supposed to be connected via USB when I try that?
Click to expand...
Click to collapse
marty45714 said:
So, in order for the phone to connect to the share, your phone needs to be connected by wi-fi to the same network as the computer that is running VirtualBox and the VM.
Click to expand...
Click to collapse
Ok that's gonna be my problem then ...I'll give it a shot when I get home and I'm not connected to my office network.
USB 3.0?
My laptop only has USB 3.0 ports. Is that why I am having trouble connecting to the VMbox? SMB share connected over WIFI no problem. USB fails every time.
I am struggling with the directions and feeling dumb about it... Not sure what to put for the "Host IP Address"
EDIT: Restarted the virtual machine and it gave me the information I needed. The first time around the field was blank.
I appear to still lack root because the SU app wants to update the binary and fails to do so.
I'm not sure, but one thing you can check. When the Linux console is up in the VirtualBox window, there is a section in the lower, right hand corner of that window that shows a bunch of icons. Click the USB icon and very that you see your Bionic as an option for hardware that is connected to your laptop.
Also, I'm making an assumption that you have the Motorola UBS drivers already loaded on your Windows system before you even started this whole process. Maybe I shouldn't make that assumption???
cakessi said:
My laptop only has USB 3.0 ports. Is that why I am having trouble connecting to the VMbox? SMB share connected over WIFI no problem. USB fails every time.
Click to expand...
Click to collapse
First of all, thank you very much for creating a easy root tool for those of us who thought the previous methods were too daunting.
I've got a 32bit Windows PC and followed the instructions as you listed them. The problem I kept encountering was that my phone would not accept the IP address or group name suggested by the VirtualBox. When I looked up IP address of the VirtualBox my computer (cmd/ipconfig) I noticed it conflicted with the address that the box was telling me to enter into my Bionic. I wonder if this is the cause of the connectivity issue, and I have a hunch it's because my router is set to give dynamic IPs to the devices on my home network (which is larger with multiple routers and devices).
Any input would be greatly appreciated. Thanks.
You can test the connectivity to the SMB share from your Windows PC first. That's what I suggest.
In your Windows PC, go to My Computer and type in:
\\192.168.1.11\share
where 192.168.1.11 represents the IP address that the Linux server is telling you to use.
You can also go to the windows command line (cmd) and type:
telnet 192.168.1.11 445
which will show if your windows computer can connect to port 445 (SMB).
If these are successful, you probably have an issue that your phone and computer are not connected to the same network.
If you believe they are, you may want to see if your router is set up to not bridge the wireless and LAN traffic, which would mean that the computers on the LAN segment cannot communicate with the computers on the WI-FI segment.
Hopefully something here will help you out.
Please post your results.
Also, make sure when you are typing in names, passwords, groups and IP addresses, that you are not leaving trailing spaces on the ends of things.
MNEman13 said:
First of all, thank you very much for creating a easy root tool for those of us who thought the previous methods were too daunting.
I've got a 32bit Windows PC and followed the instructions as you listed them. The problem I kept encountering was that my phone would not accept the IP address or group name suggested by the VirtualBox. When I looked up IP address of the VirtualBox my computer (cmd/ipconfig) I noticed it conflicted with the address that the box was telling me to enter into my Bionic. I wonder if this is the cause of the connectivity issue, and I have a hunch it's because my router is set to give dynamic IPs to the devices on my home network (which is larger with multiple routers and devices).
Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Any way we can get another link for this. I'm really wanting to try this out.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
New link. See original post. I have it on Mediafire now.
dcmcc99 said:
Any way we can get another link for this. I'm really wanting to try this out.
Error (509)
This account's public links are generating too much traffic and have been temporarily disabled!
Click to expand...
Click to collapse
marty45714 said:
You can test the connectivity to the SMB share from your Windows PC first. That's what I suggest.
In your Windows PC, go to My Computer and type in:
\\192.168.1.11\share
where 192.168.1.11 represents the IP address that the Linux server is telling you to use.
You can also go to the windows command line (cmd) and type:
telnet 192.168.1.11 445
which will show if your windows computer can connect to port 445 (SMB).
If these are successful, you probably have an issue that your phone and computer are not connected to the same network.
If you believe they are, you may want to see if your router is set up to not bridge the wireless and LAN traffic, which would mean that the computers on the LAN segment cannot communicate with the computers on the WI-FI segment.
Hopefully something here will help you out.
Please post your results.
Also, make sure when you are typing in names, passwords, groups and IP addresses, that you are not leaving trailing spaces on the ends of things.
Click to expand...
Click to collapse
Thanks for the help and instructions. After a few hours of fiddling around I still cannot get my phone to connect to the SMB. My computer connects successfully and after I connect via \\192.168.1.11\share the VirtualBox even progresses a bit to the point where it asks me to plug in my Bionic, but without my phone's wifi file share the process stalls. I am sure that both phone and PC are connected to the same network, sharing is all on, and firewalls are down. At this point I must assume that my router isn't bridging for some reason. Tonight I'll do some more investigation into the Airport Express settings and see if it will fix this issue.
Alright, you can also verify the network connectivity between the phone and the VM by using the 'ping' command.
Find the IP address of your phone by selecting Settings, then Wi-Fi, then click your left most menu button on the bottom and select Advanced. You will see the IP address of the phone. The first 3 octets of that address (xxx.xxx.xxx) should be the same on both the computer and the phone on MOST networks.
So from the Linux console, if you press Ctrl-c, it will drop you to a Linux prompt, from here you can try to ping the phone:
ping 192.168.1.11
Again, where 192.168.1.11 represents the IP address of your phone, that you just found from the menu.
Also, you can try to ping the Linux VM from your phone. If you've installed the Android Terminal app, you can lauch it and type:
ping 192.168.1.11
Where 192.168.1.11 represents the IP address of the Linux server. This is presented to you by the Linux console when it gives you the information to put into your phone in order to connect to the SMB share.
MNEman13 said:
Thanks for the help and instructions. After a few hours of fiddling around I still cannot get my phone to connect to the SMB. My computer connects successfully and after I connect via \\192.168.1.11\share the VirtualBox even progresses a bit to the point where it asks me to plug in my Bionic, but without my phone's wifi file share the process stalls. I am sure that both phone and PC are connected to the same network, sharing is all on, and firewalls are down. At this point I must assume that my router isn't bridging for some reason. Tonight I'll do some more investigation into the Airport Express settings and see if it will fix this issue.
Click to expand...
Click to collapse
I made it all the way through and the exploit said it was successful, but I don't have root. Any thoughts there?
marty45714 said:
Alright, you can also verify the network connectivity between the phone and the VM by using the 'ping' command.
Find the IP address of your phone by selecting Settings, then Wi-Fi, then click your left most menu button on the bottom and select Advanced. You will see the IP address of the phone. The first 3 octets of that address (xxx.xxx.xxx) should be the same on both the computer and the phone on MOST networks.
So from the Linux console, if you press Ctrl-c, it will drop you to a Linux prompt, from here you can try to ping the phone:
ping 192.168.1.11
Again, where 192.168.1.11 represents the IP address of your phone, that you just found from the menu.
Also, you can try to ping the Linux VM from your phone. If you've installed the Android Terminal app, you can lauch it and type:
ping 192.168.1.11
Where 192.168.1.11 represents the IP address of the Linux server. This is presented to you by the Linux console when it gives you the information to put into your phone in order to connect to the SMB share.
Click to expand...
Click to collapse
Here are some tips that I posted for someone over on Droid Forums. Hopefully some of this will help us figure out what is going on:
Need you to do some investigation. Run the exploit again. Once your phone is connected to the SMB share and the Linux script verifies the connectivity, press Ctrl-C to break out of the script and return to the Linux command prompt. Make sure your phone is connected to USB. From there execute the following commands and share the output with me:
sudo ash
cd /home/guest/share
./adb.linux shell
(if you execute the above command and DO NOT see this prompt: [email protected]_targa/ $
then you have USB connectivity issues and need to make sure you get your phone successfully connected
to VirtualBox and the Linux VM)
ls -l /storage/rfs0
I want to see the output of the "ls" command to verify that the SMB share is being mounted to /storage/rfs0
This can cause the exploit to fail is it's not.
If you see no output from that command, run this command:
find /storage -name pwn
If you get that far and this looks good. Can you type:
su -
and see if you get a root prompt? A root prompt means your prompt will end with '#' instead of '$' before the cursor.
If you do get this, it could be that your Superuser app is simply broken and need re-installed.
The command that the exploit runs to root the phone, once you get this far is:
/storage/rfso/pwn 1
You can try running that manually and see what happens.
caskieadam said:
I made it all the way through and the exploit said it was successful, but I don't have root. Any thoughts there?
Click to expand...
Click to collapse
Related
OK, I have the program installed on the Kaiser, I have the port 3389 forwarded on my router. For the life of me, I can't figure out why I can't connect to the PC.
I even have the PCs alternate account and password and it's just not working. Someone please help.
you have to enable remote access on your host PC
I have also done that.
Try...
LogMeIn.com
Make sure your data connection on your phone is active before you try to connect.
The RDP client on this site does not seem to initiate the network on it's own.
I use bandswitch to close my idle connection and have to disable it when I try to rdp to home.
Do have something that you can telnet from? If so try telnetting to the PC you are trying to connect to via RDP.
telnet <ip> 3389
That will at least tell you if your PC is listening for rdp connections.
hmm, I tried telnetting myself using absolute telnet. Not exactly sure how to use it, but I entered in my IP address, and the port I have forwarded on my router and it kinda worked, but maybe not.
When I try to connect to 192.168.1.1, it won't connect.
when I try to connect to 192.168.1.101, it connects but does nothing.
I also tried initiating the data connection first, and it still didn't work...
Hmm, any other advice? I'd really like to get this working.
Try this, Jay...
JayIV said:
hmm, I tried telnetting myself using absolute telnet. Not exactly sure how to use it, but I entered in my IP address, and the port I have forwarded on my router and it kinda worked, but maybe not.
When I try to connect to 192.168.1.1, it won't connect.
when I try to connect to 192.168.1.101, it connects but does nothing.
I also tried initiating the data connection first, and it still didn't work...
Hmm, any other advice? I'd really like to get this working.
Click to expand...
Click to collapse
Now, just forwarning I am not very technically enclined about this stuff at all. Not yet anyway. I worked with exactly what you're working with. Trying to get RDP working... I found this article and it is now working for me beautifully. One word of warning, disable your PC's Firewall. I have McAfee and it was stopping the incoming request. Bad thing is we are all wireless, our IP's are changing at the drop of a hat. So if you figure out how to beat that be sure to share. LOL. Here's the link. Good luck!
http://www.aximsite.com/boards/vbarticles.php?do=article&articleid=210
mmmkay, got it working, kind of...
I was using the wrong ip address, not even realizing it. I was using my router assigned IP address- not the right ip address obviously. For future reference, and also because I have not seen this documented ANYWHERE else, you must use your ISP ASSIGNED IP ADDRESS, and the port forwarded on your router to connect to your desktop.
So, I got connected to my computer and all, great great. Now I need some help tackling my next problem. Apparently, I am not allowed to connect to my alternate account because of some kind of permission problem. I am not in the group RDC or whatever on the remote machine and I must be added manually. OK, sounds easy.... not. How the eff do I do this?
Yes, I am running Windows Vista Home Premium. I am aware that it came "missing remote". However, I have added the hack, and as far as I understand, I should now be able to RDC to my computer using my mobile...
Who can help?
JayIV said:
mmmkay, got it working, kind of...
I was using the wrong ip address, not even realizing it. I was using my router assigned IP address- not the right ip address obviously. For future reference, and also because I have not seen this documented ANYWHERE else, you must use your ISP ASSIGNED IP ADDRESS, and the port forwarded on your router to connect to your desktop.
So, I got connected to my computer and all, great great. Now I need some help tackling my next problem. Apparently, I am not allowed to connect to my alternate account because of some kind of permission problem. I am not in the group RDC or whatever on the remote machine and I must be added manually. OK, sounds easy.... not. How the eff do I do this?
Yes, I am running Windows Vista Home Premium. I am aware that it came "missing remote". However, I have added the hack, and as far as I understand, I should now be able to RDC to my computer using my mobile...
Who can help?
Click to expand...
Click to collapse
Having never used vista (yuk, yuk yuk) I don't know where the settings are, but being a fisher price os it should be fairly obvious.
Just add yourself to the remote desktop user group in the users and groups settings. If your account is an admin account you should have RDP access by default I believe
right click my computer, go to properties, click the remote tab. Click the "select remote users" button
I've already tried to things you two just mentioned. However, these options are not there. I think it has something to do with vista home premium...
I'm not sure about how or what you "hacked" to get RDP on your version of Vista, but there is a setting for RDP versions.
Under system properties -> remote tab
There are three options which essentially break down to this:
-Don't allow any RDP
-Allow all RDP (RDP 5 and RDP 6)
-Allow only RDP with NLA (RDP 6)
Vista and updated XP machines can have the RDP 6.0 program. Otherwise most systems are still RDP V5.
I found the allow all RDP (the second option) works well with from my kaiser to my Vista machine.
Just found this. Works great. Install this on your phone, http://code.google.com/p/android-notifier/downloads/detail?name=AndroidNotifier-0.2.4.apk&can=2&q= and this on your PC (Windows/Linux) http://code.google.com/p/android-notifier-desktop/ or this for Mac http://code.google.com/p/android-notifier/downloads/detail?name=MacDroidNotifier-0.2.6.dmg&can=2&q=
For users who need a guide in setting up the application may visit the following web pages:-
- http://droidbar.net/2010/09/setup-guide-on-remote-notifier-for-android-via-wi-fi-windows/ (Connect via Wi-Fi on Windows)
- http://droidbar.net/2010/10/setup-guide-on-remote-notifier-for-android-via-wi-fi-ubuntu-linux/ (Connect via Wi-Fi on Ubuntu Linux)
- http://droidbar.net/2010/11/setup-guide-on-remote-notifier-for-android-via-bluetooth-windows/ (Connect via Bluetooth on Windows)
- http://droidbar.net/2010/11/setup-guide-on-remote-notifier-for-android-via-bluetooth-ubuntu-linux/ (Connect via Bluetooth on Ubuntu Linux)
Should also note that to use the 64 bit version of the windows software you must be running 64 bit java.
Now this is just awesome.
However it needs a fair bit of setting up in Windows as the balloon notifications are ugly.
Maybe I'll try Growl for windows!
I have had this for about 2 weeks now. The latest update is becoming annoying because it gives me a battery notification every 5 minutes. Maybe its the rom im using.
I cant seem to get this working. I would assume that since my desktop is connected to the network via Wired Connection, and my phone via wifi, but my pc wont see any of the services.
[edit] turns out i had to set it to sent to my custom IP and it works
I just saw this and downloaded it... It's perfect for me!
It worked perfectly first time, no configuration needed... just start the app and start the .exe on my PC and it works great.
One question I do have though is, what is Growl and how do I get it?
ya, i set up custom ip, which i assume would be the ip address of my desktop? and no go for some reason. too bad, i could actually use this. any suggestions would help but if not, Ill try and email the dev..vista with a wired connection to my router, if that makes a difference
bbrosen said:
ya, i set up custom ip, which i assume would be the ip address of my desktop? and no go for some reason. too bad, i could actually use this. any suggestions would help but if not, Ill try and email the dev..vista with a wired connection to my router, if that makes a difference
Click to expand...
Click to collapse
Try double checking your IP address?
Control Panel > Network and Internet > Network and Sharing Center (If you're on Windows)
1. Click on "Local Area Connection" (If you're on Wired Connection)
2. Click on "Details..."
3. Look for your IP address at "IPv4 Address"
However, if the IP address of your desktop is not static. I’m afraid it will vary whenever you reboot your router/modem.
Alternatively, you may set the Target IP address to “Global broadcast address” on your phone.
ADeadlySpoon said:
I just saw this and downloaded it... It's perfect for me!
It worked perfectly first time, no configuration needed... just start the app and start the .exe on my PC and it works great.
One question I do have though is, what is Growl and how do I get it?
Click to expand...
Click to collapse
http://www.growlforwindows.com/gfw/default.aspx
Just install that, pick a nice display, then go in android-notifications and enable the Growl and disable System default.
Does not work for me using windows7
Downloaded client..run ...SAVE..send test ping.. nothing happen
Im sure ma phone and PC are in same network.Firewall is disabled.
Some ideas?
castaway1 said:
Does not work for me using windows7
Downloaded client..run ...SAVE..send test ping.. nothing happen
Im sure ma phone and PC are in same network.Firewall is disabled.
Some ideas?
Click to expand...
Click to collapse
Are you on 32-bit or 64-bit Operating System (OS)?
Did you download the 32-bit or 64-bit client for Android Notifier Desktop onto your desktop?
If you're on 64-bit OS and downloaded the 64-bit client for Android Notifier Desktop, you also need 64-bit Java.
Additionally, is the Target IP address set to “Global broadcast address” or "Custom IP or host" on your phone?
If it is on "Custom IP or host" you need to manually add the IP address of your desktop to it.
For users who need a guide in setting up the application may visit the following web pages:-
- http://droidbar.net/2010/09/setup-guide-on-remote-notifier-for-android-via-wi-fi-windows/ (Connect via Wi-Fi on Windows)
- http://droidbar.net/2010/10/setup-guide-on-remote-notifier-for-android-via-wi-fi-ubuntu-linux/ (Connect via Wi-Fi on Ubuntu Linux)
- http://droidbar.net/2010/11/setup-guide-on-remote-notifier-for-android-via-bluetooth-windows/ (Connect via Bluetooth on Windows)
- http://droidbar.net/2010/11/setup-guide-on-remote-notifier-for-android-via-bluetooth-ubuntu-linux/ (Connect via Bluetooth on Ubuntu Linux)
Android-notifier and DHCP networks
Does anyone have any clever ideas on how to get the following to work:
DynDNS hostname used on home network.
Router set to forward packets on the proper port.
I'd like it if I could forward to the broadcast address rather than a fixed IP. I.E., it doesn't matter WHICH computer receives the broadcast after it gets to my home network, just that SOMETHING does.
(I can't guarantee which computer I'll be using)
Ideally, I'd also like to be able to use this on my laptop, regardless of where I am: home or elsewhere, tethered or not.
make sense?
I can't keep a constant wireless connection on my nexus one but it works as long as the wireless doesn't hang which never happens...
so I tried to get Bluetooth working, I fainally got able to pair with my PC (Windows 7 64bit.) And it says paired but not connected on the phone. I try to send the test notification from the phone, but never got anything on the PC.
Can this work over the internet?
kristopherson said:
Just found this. Works great. Install this on your phone, http://code.google.com/p/android-notifier/downloads/detail?name=AndroidNotifier-0.2.4.apk&can=2&q= and this on your PC (Windows/Linux) http://code.google.com/p/android-notifier-desktop/ or this for Mac http://code.google.com/p/android-notifier/downloads/detail?name=MacDroidNotifier-0.2.6.dmg&can=2&q=
Click to expand...
Click to collapse
Link for Windows/Linux download is broken. Please fix or remove, thanks!
You got it here:
code.google.com/p/android-notifier/downloads/list
thnx anyway ,, but it didn't work for me
403. That’s an error.
Your client does not have permission to get URL /p/android-notifier-desktop/ from this server. That’s all we know.
can anyone upload it?
here
locknes said:
403. That’s an error.
Your client does not have permission to get URL /p/android-notifier-desktop/ from this server. That’s all we know.
can anyone upload it?
Click to expand...
Click to collapse
http://code.google.com/p/android-notifier/downloads/list
been searching all over the internet and have tried a few methods but nothing seems to stick on the tab. im doing this because my mac address is something funky, 12:34:56... and i cant connect to my schools wifi. my IT department doesnt service "gadgets" so im on my own. ive tried the instructions here:
http://blog.thecodecracker.com/hacks/spoof-mac-address-in-android/
but they dont seem to stick. when i connect back to my wifi network (at home) it just goes back to the corrupt one. anyone have any experience with this?
i havent been able to connect in about 3 months so as you might imagine, im really getting frustrated with it. any help would be great.
Ayman
been searching all over the internet and have tried a few methods but nothing seems to stick on the tab. im doing this because my mac address is something funky, 12:34:56... and i cant connect to my schools wifi. my IT department doesnt service "gadgets" so im on my own. ive tried the instructions here:
http://blog.thecodecracker.com/hacks/spoof-mac-address-in-android/
but they dont seem to stick. when i connect back to my wifi network (at home) it just goes back to the corrupt one. anyone have any experience with this?
i havent been able to connect in about 3 months so as you might imagine, im really getting frustrated with it. any help would be great.
Ayman
Edit*
Temporary Fix:
1) Go to wireless & network settings
2) Disconnect and forget ALL previous SSID's that you connected to before
3) download a terminal emulator from the market
4) type the following, make sure you hit enter after every line
Code:
su
busybox ip link set eth0 address XX:XX:XX:XX:XX
Where XX:XX:XX:XX:XX is, make you have to put the MAC address you want there.
to confirm if it worked type:
Code:
busybox ip link show
it should show the new MAC address. Go connect to your network as normal.
NOTE:
If you go to the status option in the settings, you will see that the MAC Address DID NOT CHANGE. This is normal. It wont show the new MAC Address; at least it didnt for me.
One thing to keep in mind, sometimes you cant just put in an hexadecimal combination and expect it to work. It didnt work for me. So what I did is I connected to the school's network from my vibrant making sure I could surf the internet. then i disconnected and copied its MAC address to my tab. when i tried putting in my own custom MAC address, it didnt work. I could connect but packets wouldnt be sent.
Unfortunately when I reboot, my settings are not saved and I have to repeat the procedure. Simplest fix is to just download gscript lite from the market and put in the command I wrote above and whenever i restart my tab run the script quickly. If someone knows of a permanent fix, please let me know so I can update this.
feels good to finally be able to connect after 3 months.
I wrote a quick app that will do this - but i hardcoded the script for something else. I will modify it tomorrow so you can customize the script it runs and put it up here tomorrow or sunday if i get the time.
I would sincerely appreciate that!
Sent from my GT-P1000 using Tapatalk
ayman07 said:
One thing to keep in mind, sometimes you cant just put in an alphanumeric combination and expect it to work.
Click to expand...
Click to collapse
"alphanumeric"?
More like "hexadecimal"
Valid charachters are 0123456789abcdef and nothing more, if you used something else that would explain why it didn't work.
Sent from my GT-P1000 using Tapatalk
AlexTheStampede said:
"alphanumeric"?
More like "hexadecimal"
Valid charachters are 0123456789abcdef and nothing more, if you used something else that would explain why it didn't work.
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Fixed
Sent from my GT-P1000 using Tapatalk
Ok here is the boot script loader.
I didn't spend any time on the interface or layout for you:
Obviously requires root to run
you don't need to start script with "su"-everything runs as su
enter the script in the edit box, click test to test it, click save to save it. It will run whatever has last been saved every boot.
Do NOT move to SD card or it will not pick up the BOOT_COMPLETED intent
i haven't tested if it runs before the SD card is fully mounted: so don't get carried away with your scripts. I suppose I could add options to run only after SD card is mounted but... i probably don't have time
Since this runs as root, do stupid things in your script things at your own risk. I'm not responsible in anyway.
the output from testing or from the boot log is:
stdOut
..some stdOut text
stdErr
..some stdErr text
where stdOut text is the results of your commands (you can see testing with a simple script containing just "ls" without the quotes)
and stdErr is any errors that occurred while running the script (you can see testing with a simple script containing "aasdf" without the quotes
click the "Thanks" button if you use this and it works
i really appreciate this. unfortunately i wont be able to try it out till monday when im at school. ill update it then.
thanks a lot of the script loader. it seems to do its job. but it seems my situation is a bit more complex than i thought. see i can only change the MAC address if i delete all the previously connected SSID. if i remove the dchp.list will that remove/forget all the previous SSIDs? i would have to run a cmd to forget all the SSIDs prior to running the MAC address change cmd.
I typed busybox ip link set eth0 address XX:XX:XX:XX:XX
i am receiving " bad address"
Pls help me
****Follow Info, Warnings & guides on associated links / pages****
For those of you reading this and in this forum, and if you've rooted before, flashed a rom, or anything like that and got it to work, DO NOT be intimidated by using this method.
I found I actually quite liked Ubuntu (it was my first time using it myself). And it's rather easy.
This is the page I followed, and if you scroll down most of the way (use the one at post #30 ircc) there's a video too. I set up my screen so it was just like in the video, plus a "window" to watch the video too. The directions are exact, what I liked about the video is you could see it run and the results, which helped me realize where things went wrong after it failed about 3 times or so.
***Thanks to drjbliss (method), SamuriHL (HoB & more), & Tomsgt123 (video)***
Things upfront:
I used a Bootable USB, You can do it with a Bootable / "live" CD, but admittedly I thought USB was quicker to set-up and in hindsight probably was beneficial. So that's what I recommend.
Get Ubuntu (img/iso) & follow the directions from HERE.
Make the USB, then restart your computer, and at boot screen, choose boot from USB.
Here's where it saved me and and I'll recommend something else here, not in the instructions... yes it's going to take a bit longer but in the end I spent almost a whole Saturday doing this and this would've made it about an hour had I done it first. It was the solution to 2 errors I had, that took a while to realize where they were and find a fix.
In Ubuntu, open a "terminal" which is like a windows cmd / command window.
I couldn't find a button or anything on a menu to do this so I found out it's either alt + t or ctrl + alt + t.
at the Ubuntu terminal command prompt:
use these 2 commands to update Ubuntu and Samba.
sudo apt-get update
sudo apt-get upgrade
[IIRC] The Ubuntu one will tell you it needs and additional 250 (or so) MB's hit ok or accept and let it update. Then do the next and update Samba.
I'm not exactly sure but I doubt I would've been able to do this with a cd being that it couldn't write to it.
This took care of all errors I ran into using this Root method, and it was a bit frustrating because if you don't know what you're looking for or at, you can get to the end and it says exploit finished or complete or something and you think you're good to go.
On to the root instructions & Video...
I opened (2) terminal windows, you have to manually put them on the same screen or it will move them to multiple ones and that doesn't help so much.
If it does, use the button on the side that looks like (4) windows and pick & drag everything back to one screen.
Errors or what to look for:
when you run this command: sudo apt-get install samba
if it says (something) "unknown" or "Failed" - Samba didn't install, try again. (update if you skipped that part)
when you try to connect remotely over WIFI...
If you get "network connection error / failed", Samba didn't install, or Samba needs update (if you skipped that), or make sure you use the right IP address, a few of them will come up. I found for me it had nothing to with my network and I had the right IP the first time I tried.
****NOTICE****
Ubuntu will let you keep going and continue to run the commands seemingly normally. Even to the end and tell you "exploit complete" (or something like that) So if you get to the end and you don't have root go back and examine your terminal screen. Compare it to the one in the video, something won't match, and there's the issue.
I did notice the "numbers" didn't always match as it ran thru the processes, but make sure it looks like your getting the same type of results and runs thru the process.
I needed to update Ubuntu to update Samba that's why I recommend doing both first.
Once you set-up & update your USB the whole thing shouldn't take more than 15-20 mins or so.
Good luck.
It's really not hard, just follow the instructions.
I tried following the steps for Jelly Bean root, but I think the samba share thing may be holding me back. I know how to do it, that's not the problem. The problem is, I don't have a wifi setup at home, so I wouldn't be able to connect to the Ubuntu live image even if I could set up my Files app the way I'm instructed to. When I go to the section in the Files app to input the information, I don't have all the fields show up for the necessary information. Plus I have a version of Ubuntu running on my laptop that shouldn't require a wireless connection between my phone and the computer, since I can just plug the thing into it. I know this method has worked for many people, and I'm not exactly a noob, my first Android phone was the very first one, the G1. With each Droid style phone I got, I had it rooted within either hours or days, so I am capable of doing it. Also, I know there either isn't a one-click method yet or if there is I can't find it, but is there a way to circumvent the whole samba thing so I don't have to mess with the wifi connect? Finally, and thank you for your patience in reading such a long text, worst case scenario; if I were to try to fxz back to ICS stock (I know it'd more-than-likely brick my phone), is there an unbrick method for those of us who've let themselves spend way to much time obsessing over their phone (I tend to get a little tunnel visioned when it comes to this stuff), or would I be totally screwed? As many on this forum, thanks for all the hard work, and I apologize in advance if I seem a little whiny about this. I should point out that even without the wireless connection between the phone and the computer, the program still runs and displays the terminal screen that roots the phone. It stops just a few lines after the "push a hardware button" phase to make it vibrate. It never vibrates, but Superuser does get copied to the phone, it just install the binaries for it.
I just got my new P20 Pro and wanted to try out Huawei's share aka Air drop. Anyway I've managed to locate my phone on my PC [windows 10] but , I can't connect to it. It says error check my name or network ? Any one know a fix for this ? I've tried changing the name from my phone but nothing works. Huawei suggest to clicl the diagnose button which also does nothing.
Help please! Thanks in advance
FIX!
For anyone with this problem I found a fix. Go to control panel > Programs > Turn on or off windows features > Scroll down to SMB 1.0 File sharing support, Click the plus to expand and then check all 3 sub boxes!
windows can not get access to \\ P20PRO
It is possible that the name of the location is not well written or that there is a problem with the network.
Error code: 0 * 80070035
Works fine here and on my Mac.
you need to activate smb direct/client/server
Hijacking this thread. Tried this and still can't connect. Using a Sky Q router.
Yea, i have problems also with the P20 pro and windows 10. I have turned on the SMB settings and still no luck while i can see all my other device in the network just fine...
i did it on widows 10
1. Plug the USB cable into the phone and the computer.
2. Touch Settings.
3. Touch Wireless & networks.
4. Touch Tethering & portable hotspot.
5. Touch the USB tethering slider to turn it on.
6. The phone is now tethered.
7. On the computer, wait for the device drivers to install then click Home network.
8. Wait while the computer automatically applies the settings and connects to the network.
9. Setup is complete. Click Close.
10. Unplug ur phone and it will be working
good luck ^_^
MennaSamir said:
i did it on widows 10
1. Plug the USB cable into the phone and the computer.
2. Touch Settings.
3. Touch Wireless & networks.
4. Touch Tethering & portable hotspot.
5. Touch the USB tethering slider to turn it on.
6. The phone is now tethered.
7. On the computer, wait for the device drivers to install then click Home network.
8. Wait while the computer automatically applies the settings and connects to the network.
9. Setup is complete. Click Close.
10. Unplug ur phone and it will be working
good luck ^_^
Click to expand...
Click to collapse
Worked for me Thanks:good:
U must enable tethering on the comp or laptop and voala, on the network is appearing my phone wuth all folders
I also had this problem and followed all advice but in the end something else did the trick for me (albeit proposal for activating SMB was mandatory in the end).
So in my case, the problem was that the DNS wasn't resolving my P20 Pro's name. In order to finally access my phone's storage I had to manually open a file explorer window and type in \\<P20's Pro IP address> for example \\192.168.1.8 (you can find this IP address if you check the wireless devices connected to your router via its admin page).
Then in order to make it easier for the future, I went in my router's settings and set it as a static LAN Ip and Pinned the connection on my file explorer, so now I can simple click on it and connect whenever I enable Huawei Share.
I hope this helps people who still couldn't connect via Huawei Share. Just don't forget you still need to activate SMB as OP indicates in his follow-up post.
Lyssion said:
I also had this problem and followed all advice but in the end something else did the trick for me (albeit proposal for activating SMB was mandatory in the end).
So in my case, the problem was that the DNS wasn't resolving my P20 Pro's name. In order to finally access my phone's storage I had to manually open a file explorer window and type in \\<P20's Pro IP address> for example \\192.168.1.8 (you can find this IP address if you check the wireless devices connected to your router via its admin page).
Then in order to make it easier for the future, I went in my router's settings and set it as a static LAN Ip and Pinned the connection on my file explorer, so now I can simple click on it and connect whenever I enable Huawei Share.
I hope this helps people who still couldn't connect via Huawei Share. Just don't forget you still need to activate SMB as OP indicates in his follow-up post.
Click to expand...
Click to collapse
Nope, not working and i think huawei is pretty **** when it comes to pc connectivity
It wasn't working for me, for a while, until I realised I had to turn on "computer share" in Huawei Share settings! Duh, like..
It wasn't working for me. Why? Is there another way?
---------- Post added at 07:13 PM ---------- Previous post was at 07:12 PM ----------
Darian John said:
For anyone with this problem I found a fix. Go to control panel > Programs > Turn on or off windows features > Scroll down to SMB 1.0 File sharing support, Click the plus to expand and then check all 3 sub boxes!
Click to expand...
Click to collapse
It wasn't working for me. Why? Is there another way?
Lyssion said:
I also had this problem and followed all advice but in the end something else did the trick for me (albeit proposal for activating SMB was mandatory in the end).
So in my case, the problem was that the DNS wasn't resolving my P20 Pro's name. In order to finally access my phone's storage I had to manually open a file explorer window and type in \\<P20's Pro IP address> for example \\192.168.1.8 (you can find this IP address if you check the wireless devices connected to your router via its admin page).
Then in order to make it easier for the future, I went in my router's settings and set it as a static LAN Ip and Pinned the connection on my file explorer, so now I can simple click on it and connect whenever I enable Huawei Share.
I hope this helps people who still couldn't connect via Huawei Share. Just don't forget you still need to activate SMB as OP indicates in his follow-up post.
Click to expand...
Click to collapse
This worked for me, Thanks :good::good:
Lyssion said:
I also had this problem and followed all advice but in the end something else did the trick for me (albeit proposal for activating SMB was mandatory in the end).
So in my case, the problem was that the DNS wasn't resolving my P20 Pro's name. In order to finally access my phone's storage I had to manually open a file explorer window and type in \\<P20's Pro IP address> for example \\192.168.1.8 (you can find this IP address if you check the wireless devices connected to your router via its admin page).
Then in order to make it easier for the future, I went in my router's settings and set it as a static LAN Ip and Pinned the connection on my file explorer, so now I can simple click on it and connect whenever I enable Huawei Share.
I hope this helps people who still couldn't connect via Huawei Share. Just don't forget you still need to activate SMB as OP indicates in his follow-up post.
Click to expand...
Click to collapse
Thank u very much. I had the same problem and now it's working:good::good::good:
Darian John said:
For anyone with this problem I found a fix. Go to control panel > Programs > Turn on or off windows features > Scroll down to SMB 1.0 File sharing support, Click the plus to expand and then check all 3 sub boxes!
Click to expand...
Click to collapse
That worked. Thank you very much. :good:
If it still helps i think i got it.
Use the original huawei charging cable you got with the phone.
I tried it all.. tethering, debugging, hisuite etc.. but nothing worked
1. step Install HiSuite on computer,
2. step plug in your phone with original cable,
3. step HiSuite on computer will run by itself,
4. step select transfer files on your phone,
5. step computer will ask you if you all it to install HiSuite on your phone and click ok,
6. step on your phone pop up will show to install HiSuite on Huawei.
Maybe also go to settings - connections - usb thetering (if needed) and thick it.
Hope it helps, it did for me - but barley lost my mind...
Good luck,
Toni
@frozenflame123
Topic is for "Huawei share" not for "HiSuite"
You great! Thank a lot! I had the same problem with the Honor9 Lite e I solved it thanks to your suggestion!