Related
Ubuntu On Epic4G Touch Has Arrived!!!
Disclaimer...I am not responsible for bricked or soft bricked phones. I am also no responsible for files lost phones damaged and commands entered wrong on your part. I also would like to say that i did not in anyway shape or form come up with this method to get Ubuntu to run on Epic4G Touch i saw the GUIDE in the Epic4G forum and tested it out and it worked so this was simply trial and error.
Thanks To:BThomas22x Over at the Epic4G Forum for Creating this GUIDE. Also thanks to the Developer of the new script KellyLewis3985
Whats NeededMust be Rooted, Must have busybox, Must have superuser, Must have Android SDK, Must Download AndroidVNC & Android Terminal Emulator from market and of course patience.
Directions
1. Download File i attached at the bottom unzip and create a new folder called Ubuntu and place all the files inside of it and put on the root of your SD card.
2. Unmount SD card
3. Go into command prompt and cd to SDK. (cd C:/sdk/platform-tools) Or were ever you cd to run ADB commands
4. Now once your device is connected and you see your serial number listed type adb shell and hit enter
5. Then type su and hit enter
6. Now we want to cd into that Ubuntu folder on your sdcard so simply type cd /sdcard/ubuntu and hit enter
7. Ok now lets install ubuntu by typing sh ubuntu.sh and hit enter let it do its thing and after it does you should see at the bottom to enter type "bootlinux"
8. Type bootlinux and hit enter once you see the prompt "[email protected]" then you have just installed ubuntu side by side with your Android device!
VNC Setup
Now type the following commands in orderrm -rf /tmp/.X*
export USER=root
vncserver -geometry 1280x800
At this point everything should be setup and ready to rock and roll after shutting down your phone or shutting down VNC you will have to go into Terminal on the phone and type...
1. su
2. bootlinux
3. Once prompted with [email protected]
4. rm -rf /tmp/.X*
export USER=root
vncserver -geometry 1280x800
5. And now you have installed Ubuntu, Setup VNC, And now know how to get back into Ubuntu after a shut down or VNC exit.
Android VNC Setup Part2
Nickname: root
Password: ubuntu
Address: localhost
Port: 5901
If you have any questions,problems or comments please write on the thread or PM me thanks and ejoy!
DOWNLOAD LINK
http://www.multiupload.com/O8QVR5H203
screenshots please?
Thank you! This is awesome.
I wonder if the mhl adapter to a monitor. With a bluetooth mouse and keyboard would work...
i will post screenshots tomorrow def and im sure the mouse and keyboard will work and believe it or not its pretty fast
can you make and receive txt messages and calls in ubuntu?
Thank you!
Sent from my SPH-D710 using xda premium
your not changing from android to ubuntu your running them side by side threw vnc so there for you still will get calls and text
This sounds fun, I really want to give this a try... Anyone try it out yet?
Edit:
Holy big download batman, I'll wait until I'm on wifi and not tethering at 300kb LOL
omg thank you so much
Trying this weekend thanks... What version of ubuntu is this?
Sent from my SPH-D710 using XDA App
If you put the folder on your external sd card, you'll need to update the path in ubuntu.sh
But for some reason all of my busybox commands are failing. I've even reinstalled it several different times from different installers in the market. Any ideas?
donny could too please put a link to the original guide in the OP for quick reference
yes sorry guys im driving to work right now lol i will post the link and screen shots
ok guys heres the screen shots and after this post i will post the link to the original GUIDE but if anyone is having problems just PM me i dont bite lol
And heres the link to the original GUIDE
http://forum.xda-developers.com/showthread.php?t=823370
guys i forgot to tell you in the main post make your color 24 Bit
When trying this I get the error "VNC connection failed! localhost/::1:5901 - Connection refused" when trying to connect after all of the installation commands.
try setting the port to 5900 or 5902 or 5903 etc if that dont work let me know and will go from there
donnyevo4g said:
try setting the port to 5900 or 5902 or 5903 etc if that dont work let me know and will go from there
Click to expand...
Click to collapse
None of those worked, what would I have to do to erase all the files and start from scratch? I feel it may have been a bit of user error.
Those of you who have this working, what kernel are you guys using? I'm on the newest LOSt stable, which now has working busybox, but the modprobe command still fails.
Script to flash via CWM to fix fix perms has been done by minotauri (sorry if miss spelled will fix when on a computer) he deserves credit for the edify:
To Run Fix Perms While in Recovery Flash this file each and every time you need it run [for now]:
http://goo.gl/hrL7E
The Next Script is one you can flash via CWM and it will replace the file ROM Manager uses so this will remain between restarts and you can use it via ROM Manager or Script Manager anytime you want!:
Thank Minotauri again for another beautiful Edify!
http://goo.gl/qPpC3
Flash via CWM and it well work for that flash just flash anytime you need to run it via recovery until I see about permanently copying it over existing script or still can run manually with this guide if you choose [scroll down below the additional update on how to fix the script to run using ROM Manager while in OS!].
I posted this in a couple ROM threads and was asked to throw it out here as folks from different ROMs are all affected. I can only speak for TMobile Galaxy S2 as that is what I own, drive and work on...
I will be cleaning up the post a bit when I get time just want it posted so others can use the information add it really seems to help clean up small issues (even some report fixing multiple FCs after running fix perms this way!)
NEWEST UPDATE 2012.04.19
OK FIX FOR RUNNING FIX PERMS INSIDE OS VIA ROM MANAGER
If you adjust first line in script to #!/system/xbin/sh viola ROM Manager does not freeze [finally]
I did this with Ghost Commander [don't forget settings> check auto root] and long press fix_permissions and choose edit tapping it will have GC try to execute it.
I also moved down to set variables piece and placed 1s instead of 0s next to mount system, mount data, and remove (as in REMOVE stale data ) [should be all caps in /data/data/com.koushidutta.rommanger/files/fix_permissions
I am still working on finding a way of making those changes permanent in /sbin under recovery boots
Fix Permissions Work Around ICS
Run Fix Permissions via ADB Shell with Phone in Recovery
I have taken the time to document what should be a complete guide to running fix permissions while the phone is in the Recovery menu using adb.
I am posting the quick steps right after this, but if you scroll below that this is an extended step-by-step guide.
Code:
Running Fix Permissions
On Phone: go in to Mounts and Storage Menu from Main Menu and choose to mount /data and /system
On Computer: type adb shell
This should give you a ~# prompt
Now type "sh /sbin/fix_permissions -l -r" [without quotes]
and now you should see a bunch of text scroll by and then it will say fix permissions completed blah when done.
that's it type exit and hit enter about 3x [one will change ~# to ~$ then it will drop back to C:\blah and then one more time will close that window as well
Supplies [Phone, USB Cable and Android SDK (http://developer.android.com/sdk/index.html)
Follow the link to install Android SDK [they have directions on site]
first time installing adb? [Skip otherwise]
To Add ADB to your computers path [to run it from any directory]
Windows:
Open Command Prompt [Click Start, Click Run, Type in cmd and hit Enter [XP]]
Open Command Prompt [Click Start, type cmd in whitebox and hit Enter [Vista and 7]]
type set PATH=%PATH%;C:\android-sdk\platform-tools [or wherever you put android sdk just add platform-tools to the end [it is a hidden folder]
Linux [OSX should be same]:
PATH=$PATH:/home/user/android-sdk/platform-tools [or adjust for where you saved it]
export PATH
Now That You Have ADB and path set, time for good stuff
Opening a Command Processor
Open a Command Prompt [Windows] or Terminal [Linux or OSX]
Windows: Click Start, Click Run, Type cmd and hit enter [XP]
Click Start, type in to Whitebox cmd and hit Enter [Vista and 7]
Linux: Hold alt and hit F2 on keyboard [should see a run box now]
Type in xfce4-terminal and hit Enter [or substitute your terminal command this is xubuntus]
Once a Black and White Screen Opens...
Gaining Elevated [Admin or Root Privileges]
Ok, some further testing shows me you should have root or admin access to command processor before running ADB.
In Windows
Type The Following in to the command prompt window already open...
runas /user:%computername%\administrator cmd
hit enter when done
[yes just like that including %computername% windows will fill it in with proper info copy/paste if needed right clicking in command window should paste text for you [if not right click on the icon in left hand corner of title bar choose properties and place checks in the quick edit and insert mode boxes under Options tab]
now it will ask for a password if you have not set one you need to go to control panel users and set a password on admin account before this will work
Once you enter the password and hit enter a second command window will open and will have Administrator in the title
Now You can continue on
In Linux
With Terminal window open type:
gksudo xfce4-terminal& [sub your terminal command if not using xubuntu]
once you hit enter it may take a second but you will get a password prompt enter in your password and a new terminal will open and it will have [email protected] in the title
Now you can continue on...
Checking USB Connection
type in adb devices and hit enter
[if you get a command not found you will have to use cd to move to directory with adb [ie cd c:\android-sdk\platform-tools]
If it comes back with ?????? as serial number it is not connecting correctly follow the next steps otherwise skip the next bit if you didnt get all ?
I get ?????, what gives?
This seems due to not running command prompt or terminal as administrator or root user [Windows / Linux Respectively]
You will need to do the following in order
Disconnect USB from phone
On Phone: In Advanced menu choose restart recovery
On Computer: type in adb kill-server and hit enter
Reconnect USB cable
Be Sure To Follow Section above labeled: Gaining Elevated [Admin or Root Privileges] and then continue on
On Computer: type adb devices and you should see a mix of letters and numbers
and that means we are good to go on
Running Fix Permissions
On Phone: go in to Mounts and Storage Menu from Main Menu and choose to mount /data and /system
On Computer: type adb shell
This should give you a ~# prompt
Now type "sh /sbin/fix_permissions -l -r" [without quotes]
and now you should see a bunch of text scroll by and then it will say fix permissions completed blah when done.
that's it type exit and hit enter about 3x [one will change ~# to ~$ then it will drop back to C:\blah and then one more time will close that window as well
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
Known Issues:
-------
Issue: My computer does not connect when I use adb shell [or I get ????? when I use adb devices]
Resolution:
I have found that i have to connect my phone 2x to computer to get it to work correctly most of the time, do the following
Disconnect USB from phone
In advanced menu on phone choose Restart Recovery
on computer: adb kill-server
Reconnect USB cable
on computer: adb devices
and you should now see a mix of numbers and letters and not ????? and now adb shell should connect
Issue when I try sh fix_permissions it says it can not find the file
Resolution: This is normally caused when you have not mounted /system [via phone]
or you did not use sh /sbin/fix_permissions [or be sure to do cd /sbin before sh fix_permissions
Issue: I get UID Read-only variable error and fix permissions does not run
Resolution: This is normally caused by either not mounting /system [via phone]
or not using sh fix_permissions.
Issue: Some of my apps are listed as /data/blah and it says it can not find the file
Resolution: This is normally caused by not mounting /data [via phone]
Issue: CWM will not mount /system or /data saying it can not find or read them
Resolution: I have found CWM does not like to load mounts once they are encrypted. If you have encrypted your device /system and /data are affected, try unencrypting your phone and trying again.
(this is a good thing it shows third parties tools trying to get around booting OS to read data will not be able to get at the information in your phone)
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
SEE This post for the current script
http://forum.xda-developers.com/showpost.php?p=25023284&postcount=22
Sent from my SAMSUNG-SGH-T989 using xda premium
Well judging by the title that you have there referred to running the script via recovery adb to begin with.
A lot of users don't realize if fix perms says complete in 2 secs it had a problem so I didn't know of that thread, but hope this will be a catch all for fix perms and not just for those who already tried via recovery and adb shell and got that specific error.
Thanks for looking out though
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
jangst123 said:
This is already and has been in the Q & A section.... Not development, but I wish the developers would look at it and figure out why we have issue on ICS
http://forum.xda-developers.com/showthread.php?t=1595806[Q] Problem with Fix Permissions (line 64: UID readonly variable) [WORK AROUND FOUND]
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I think posting this in Dev section is perfect sense. Also, thanks for the fix. This has stumped me for a while trying to figure out what to do.
When trying this, I get the message:
cat: can't open '/data/system/packages.xml': No such file or directory.
It says that twice and concludes with fix permissions ended at yada yada. I followed every command and instruction to the letter, what could be the issue?
Hey I got idea,, lets make another thread in the general section and Themes,,
Sorry don't think this belongs here, IMO
MOD,, please delete 1 of the threads,, or merge them or something,, no point in having 2
Not that I'm not happy a work around has been found!
Hopefully now the developers will figure out the source of the problem
would it be possible to bake this into a rom, or to create a CWMR zip file to make the needed changes?
Dougshell said:
would it be possible to bake this into a rom, or to create a CWMR zip file to make the needed changes?
Click to expand...
Click to collapse
+1 I'm completely stumped!
I can't get adb to even reconize the damn phone im on ravers remix to ics
peppersu812 said:
I can't get adb to even reconize the damn phone im on ravers remix to ics
Click to expand...
Click to collapse
turn on debugging
RaverX3X said:
turn on debugging
Click to expand...
Click to collapse
Raverx3x any idea why we are having this problem!?
Should we be running a different fix_permissions on ICS?
Also see..
http://forum.xda-developers.com/showthread.php?t=1595806
being that we seem to be determined to have this discussion in 2 different threads
l-levit said:
Hey I got idea,, lets make another thread in the general section and Themes,,
Sorry don't think this belongs here, IMO
MOD,, please delete 1 of the threads,, or merge them or something,, no point in having 2
Not that I'm not happy a work around has been found!
Hopefully now the developers will figure out the source of the problem
Click to expand...
Click to collapse
Or you could have devs talk here and keep users in QA so this doesn't get flooded with chatter.
Our should we delete all those ROM threads in Dev that exist in QA as well?
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
OGWisdom said:
When trying this, I get the message:
cat: can't open '/data/system/packages.xml': No such file or directory.
It says that twice and concludes with fix permissions ended at yada yada. I followed every command and instruction to the letter, what could be the issue?
Click to expand...
Click to collapse
Did you forget to mount /data in mounts and storage (on phone) before running?
Did you encrypt your device? I have CWM fail to load mounts after encryption
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
Oh and other thread just ganked my fix which is cool but I did this on my own not in response to anything so seeing as how I had to put in 2 hours of actual research, scratching my head, trying many different ways and seeing as how this is more of a process then simply loading a script I wanted to maintain it here until I can edit script or another Dev does making it cleaner and easier to manage and thus ready for more casual users found in QA threads.
Sheesh, sorry I figured this out maybe next time I won't pass on the info for fear of debating where it should be posted rather than the content and how to make it better going forward.
Device: TMobile Samsung Galaxy S2 [SGH-T989]
ROM: Yaldak's Vanilla ICS RC2
Radio: Blaze ICS
Performance Mod: Supercharger v6 update 8
Client: Xparent Green TapaTalk [latest]
u mad bro
Interesting,, the other thread was started 12th April 2012, 10:35 AM,
plus it looks like he quoted your original post from BlackEdition, and gave you credit,, before you even chose to make another thread in a section that is normally reserved for developers and their ROM's, scripts, or mods. All while u r over here bashing the other thread! Thanks for helping, but grow up and follow the rules
anyway make sure you are setting the path to adb
see http://forum.xda-developers.com/showthread.php?t=1161776 for more information
peppersu812 said:
I can't get adb to even reconize the damn phone im on ravers remix to ics
Click to expand...
Click to collapse
I have instructions on that issue on post.
Did you run adb devices and get ????? unknown device?
I had to run terminal as administrator, then I issued adb kill-server and reconnected phone and then did adb devices again and then it will say starting adb blah blah blah and then I got 6f7y88 [made up it should be a series of numbers and letters and no ?]
make sure adb devices gives you a valid response and not ????? I have found I almost always have to connect phone twice and at least do the above [with regular terminal I only used admin on first run but there in case it does make a difference].
So everytime I conect [or just about] I have to connect the phone
run adb devices get ????? and then
Disconnect USB
on phone in advanced menu choose restart recovery
on computer adb kill-server
Reconnect USB
Run adb devices and get a good serial number listed
I have to do actual work for a couple hours and then will be cleaning up main post on top and adding that bit in a place it get noticed more easily bear with me as I make my boss happy [he is wondering why things aren't getting done round here now ut-oh LoL] then I will clean up the information.
l-levit said:
u mad bro
Interesting,, the other thread was started 12th April 2012, 10:35 AM,
plus it looks like he quoted your original post from BlackEdition, and gave you credit,, before you even chose to make another thread in a section that is normally reserved for developers and their ROM's, scripts, or mods. All while u r over here bashing the other thread! Thanks for helping, but grow up and follow the rules
anyway make sure you are setting the path to adb
see http://forum.xda-developers.com/showthread.php?t=1161776 for more information
Click to expand...
Click to collapse
Um, actually I just noted they used my solution and said it was cool to do so, it appears you have an axe to grind with me and are just nit picking anything I say. I am sorry if yoyu do not feel my work is not to the same level as other folks, but since I put in work and this is more of a manual fix you have to work at rather than an easy to use script [yet], I did not want to post it in QA and all until I have something better for general release.
Also, I am not mad, just wondering why you would rather start silly arguments over placement of usable useful information rather than helping to make said information better and more stable for release to others.
Are you mad I figured this out and posted it before you or something as I have never talked with you and given you no reason to troll my threads?
When I do have a stable script [well at least semi stable for release to dev then more stable for QA]. The way I view QA is for general users questions and answers and since I was going to work on DEVELOPING a script that does work I was holding off on a QA thread, once I do get a script together I will be releasing it. In the meantime I was hoping to have more advanced users and devs dissect my process here and give me feedback towards a full script.
ALSO, by using sh /sbin/fix_permission OR doing cd /sbin and then fix_permissions you negate any need to do any path variable adjustments BUT if you rather then here is how...
when in adb shell before anything
PATH=$PATH:/sbin
export PATH
will then make it so you can just fix_permissions regardless of where you are in directory tree [but so will sh /sbin/fix_permissions so either way is up to you]
or if you are reffereing to adb on the computer
in Windows with command prompt open
set path=%path%;C:\android-sdk\platform-tools [or adjust for where you saved adb]
so if setting a batch program you could use the following to copy/paste [just adjust directories if you saved files differently]
The following is off the cuff until I begin writing the full script and automate things but it is a very basic start
Code:
@Echo Off
Set Path=%PATH%;C:\android-sdk\platform-tools
adb devices
Echo If you see ????? then restart recovery and reconnect the phone
Echo and run adb kill-server and re-run this batch script
pause
Echo when you hit any key this will start adb and put you in the shell you
Echo Will have to run fix_permissions -l -r manually
Echo Be sure to mount /storage /data via phone first
adb shell
or in Linux [OSX should be similiar if not the same]:
from terminal
PATH=$PATH:/home/user/android-sdk/platform-tools [or adjust for where you saved adb
export PATH
No it just bothers me when people ignore the rules and the Developers! Raver even told you were it belonged, and you chose to ignore Raver and the rules!
The fix will be to modify recovery for use with ICS on our devices or a modified fix-permishions script baked into the ROMS
RaverX3X said:
turn on debugging
Click to expand...
Click to collapse
I did bro just having trouble getting the cmd to recognize adb I have it downloaded I changed it still nothing don't know what the hell is wrong with it but IM fixing to improve on my golf swing on this damn vista desk top !
Sent from my SAMSUNG-SGH-T989 using xda premium
AOSP JELLY BEAN 4.1.2_r1 straight from Google sources
This ROM is completely up-to-date w/ the 4AI1.7 kernel and latest ducati from TI
Download 4.1.2_r1 ROM here [10-10]
md5sum: d300fbbd65f3037f54519f7c3c2bc4a5
PLUS YOU WILL NEED TO FLASH GAPPS AFTER
Jelly Bean Gapps here
Data wipe might be required as this is 4.1.2_r1. If in doubt, wipe and use Titanium Backup to restore apps.
Make sure to WIPE Dalvik Cache.
BUILDING THIS ROM
I've updated GitHub with the local_manifest and patches for creating this rom from AOSP sources:
https://github.com/KFire-Android/android_local_manifest/tree/jb-aosp
Each patch should be applied via: git apply <patch name> in the respective project where it belongs.
Enjoy
FIXED AS OF 10/10:
[ Will fill in as bugs pop-up ]
Awesome Hash, you are the man. I don't suppose terminal emulator would work in place of ADB would it, I don't have a pc on hand.
First!
Thanks Hash ! This is were dual-boot takes its interest .
EDIT: Not the first .
neilrl79 said:
Awesome Hash, you are the man. I don't suppose terminal emulator would work in place of ADB would it, I don't have a pc on hand.
Click to expand...
Click to collapse
Seems possible except you need wifi to download terminal emulator from the play store unless you have the apk for terminal emulator saved on your kindle fire already.
Anyways thanks hashcode, I'm really looking forward to flashing this in the morning!
neilrl79 said:
Awesome Hash, you are the man. I don't suppose terminal emulator would work in place of ADB would it, I don't have a pc on hand.
Click to expand...
Click to collapse
I'm using "su" binary from AOSP.. which doesn't seem to want to work with Superuser from the market. Oddly, that puts many people who can't seem to get adb to work in a bind. Hrm. Probably the best way to fix it would be to use a "su" binary from another build and load it up in recovery by mounting system (use the recovery gui to do that), then:
adb push su /system/bin
adb shell
cd /system/bin
chmod 6755 su
chown root.root su
exit
Of course you can always wait and just play with it a bit, an I'll have all of this worked out for the next build w/ working HD codecs.
It's late and I need some sleep
Thank you hashcode and if anybody tells you how to fix the UMS bug can you say it to me i also have a bug with the nexus sense 4 rom i also need to enable it
Using terminal emulator I'm getting
"uid 10039 not allowed to su"
"1|[email protected]:/"
I can use ADB, but wondering if there's a quick way without hooking it up. (Ive got root explorer, another binary I can use, yada...)
Sent from my SPH-D710 using Tapatalk 2
Edit:
Nvmind: Adb fixed in 2 seconds.
Awesome work.
Any chance we could have TabletUI insted of PhoneUI?
Thanks. U are the best dev ever
Sent from my LG-P500 using xda premium
BTW GApps don't work well, at least I don't have any setup at first boot and Play Store crashes.
And my ADB is a mess, Windows keeps thinking the device is in a pluged in/unpluged loop... On Ubuntu it works . And I have no USB storage notification when my device is connected .
EDIT: And pictures are rotated in multitasking panel .
Did y'all notice that the superuser binary is in system/xbin and not system/bin in the ROM?
I guess that's why my root explorer isnt working, because the command for it looking in the superuser app IS sys/bin.
So, you'll have to use adb to move it.
(You don't have to grab one from another build, in other words.)
Pull it from system/xbin and push to system/bin.
Sent from my Amazon Kindle Fire using Tapatalk 2
yourbrotherrex said:
Did y'all notice that the superuser binary is in system/xbin and not system/bin in the ROM?
I guess that's why my root explorer isnt working, because the command for it looking in the superuser app IS sys/bin.
So, you'll have to use adb to move it.
(You don't have to grab one from another build, in other words.)
Pull it from system/xbin and push to system/bin.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
what i have done
1) flash base rom
2) flash gapps 29/4
3) flash superuser the latest from this website
http://androidsu.com/superuser/
and i have just a smooth rom
how to root 4.1?
go to http://androidsu.com/superuser/ and flash the newest arm zip as QuBe2 said
Is the interface the tablet interface or phone interface? Because i have installed and it seens a big phone
That's the default UI for tablets since the Nexus 7 uses it, but it can be switched to TabletUI.
nice for a beta it is pretty quick and I used the adb trick and I got wifi
Cant get adb to work, only get no device on adb
vbdss I can help maybe
what OS are you using
I have managed to get CIFS working on stock Nexus 10.
It's quite a bit more problematic on the Nexus 10 than normal.
There are 2 main issues to deal with. Newer versions of the Linux kernel require a UNC variable to be passed to them and the current version of busybox doesn't do this. There is a patch out. I have extracted the patched busybox binary from craigacomez's AOSP Nexus 10 rom.
(Check it out here: http://forum.xda-developers.com/showthread.php?t=1998585 ). Otherwise it should work on the stock mount command if you specify the unc= mount option with the share.
The other issue is the multiuser stuff. If you execute the mount command from inside Terminal Emulator (or a script program) it looks like it mounts ok and you can 'ls' in the directory but it doesn't work for Android apps, they just see an empty directory but if you do it via a 'adb shell' it works fine in Android apps. My theory is ADB is outside of the multiuser stuff. adb actually ships on the device.
1) Unlock bootloader (fastboot oem unlock)
2) Flash recovery adb flash recovery whatever.img
3) Root device (flash CWM-SuperSU-0.98.zip)
4) Install BusyBox (from the market)
5) Copy md4.ko and cifs.ko to device. The files can go anywhere you like. In this example I will just use the root of the sdcard. Some people like them in /system/modules or /system/lib/modules
6) busybox mount -o rw,remount /
7) adb shell
8) Override /system/bin/busybox with the patched version (maybe move it first so it's backed up).
9) insmod /sdcard/md4.ko
10) insmod /sdcard/cifs.ko
11) busybox mount -t cifs -o username=MYUSER,password=MYPASS,unc=\\\\192.168.1.1\\storage //192.168.1.1/storage /data/media/0/cifs/Storage
You will need to manually preform the last 3 commands each time you reboot the device from a adb shell.
NOTE: You can probably get rid of the -o flags completely. In theory the patched version of busybox makes the UNC bit redundant. Possibly you can use the stock busybox with the UNC flag and avoid using the patched one totally. I have just included it to be sure.
Make sure you type 'busybox mount' not 'mount', by default they are different binaries. Otherwise you can remove the /system/bin/mount command and make a new one linking /system/bin/mount to /system/bin/busybox.
Possibly there is some way to get the mount working in the multiuser environment without requiring busybox. If you figure it out please tell ☺
Some threads on the issue:
http://forum.xda-developers.com/showthread.php?p=34397868#post34397868
http://forum.xda-developers.com/showthread.php?t=733490&page=6
http://www.mail-archive.com/[email protected]/msg17650.html
The modules are for 3.4.5-g4e6298b.
EDIT: I added nls_utf8.ko by request
EDIT2: Since adb comes on the device, it is possible to use it to connect to local host:
1) Install cifs modules to /system/lib/modules
2) Install Script Manager from the play store
3) Copy script to device
4) Start SManager
5) Find your script and open it.
6) Tick the su box
7) Hit save
8) Goto home sccreen
9) Add a 'SMShortcuts' widget to your home screen
10) "Add one script shortcut"
11) Choose your script
12) Optionally use this pretty icon ☺
13) Give it a nice name like "Mount Shares"
Here is a shell script...
Code:
#!/system/bin/sh
# Your settings here
USERNAME="USERNAME"
PASSWORD="PASSWORD"
IPADDRESS="192.168.1.1"
SHARE="storage"
MOUNT_POINT="/data/media/0/cifs/Storage"
# If you need to change the mount command edit this
MOUNT_CMD="\
mount -t cifs \
\
-o \
user=$USERNAME,\
password=$PASSWORD,\
unc=\\\\\\\\\\\\\\\\$IPADDRESS\\\\\\\\$SHARE \
\
//$IPADDRESS/$SHARE \
$MOUNT_POINT"
COMMANDS="\
insmod /system/lib/modules/md4.ko; \
insmod /system/lib/modules/nls_utf8.ko; \
insmod /system/lib/modules/cifs.ko; \
$MOUNT_CMD
"
# Starting ADB...
PORT=`getprop service.adb.tcp.port`
setprop service.adb.tcp.port 5555
adb kill-server
adb start-server
stop adbd
start adbd
adb connect localhost
# Make sure we only use the first device (sometimes there is more than one)
SERIAL=`adb devices | head -n2 | tail -n1 | cut -f1`
if [ "$SERIAL" = "" ] ; then
echo "ERROR: Could not find ADB device.";
fi
echo Mounting share via adb...
adb -s $SERIAL shell su root -c "$COMMANDS"
# If you started adb, then stop it here for security:
adb disconnect localhost
stop adbd
setprop service.adb.tcp.port $PORT
start adbd
RESULT=`mount | grep $MOUNT_POINT`
if [ "$RESULT" = "" ] ; then
echo "Mounting failed..."
else
echo "Mounting sucess!"
fi
echo Done... You may close this script window.
EDIT3: Added usbserial.ko, option.ko and usb_wwan.ko
EDIT4: Some users have reported that the need to modify the script to get it working with their version of SU.
EDIT5: I have uploaded modules for 4.2.2, kernel 3.4.5-gaf9c307 but I haven't actually tested them myself (still on 4.2.1). Apparently the adb loophole has also been patched but it is possible to reenable it by putting a RSA key onto the device. Check out this set of instructions here.
EDIT6: I have updated to 4.2.2 on my Nexus 10 and can confirm the new modules work.
You must setup the adbkey or you will get a "device: offline" message. By default adb when adb first runs it tries to create the keys in the $HOME dir which is /data/.android, but the data directory isn't accessible by the 'shell' user.
I got it working simply by setting the HOME variable to /sdcard and restarting the adb server in the script then Android popped up a query (I have update the script above).
IMPORTANT: The Android Media scanner recursively scans folders for media to add the the database so it shows up in programs like Google Music. On large shares this can be a long process and use heaps of battery life. To prevent this add a blank file with the name ".nomedia" to the root of your mount points (or each individual share if you aren't used 1 folder for all your mounts). This will stop music showing up in programs though.
If you find that the device stops responding (the launcher might work but apps fail to load) or you get reboots (often after the previous bug) this is probably due to a bad wifi connection.
Is it posible to make a CWM flash file?
Great
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
alias_neo said:
This is great progress, do you know if there is some way I can use the same to mount my usb OTG with ADB shell so that I can read/write to my pen drives from my android apps/file managers?
I have tried using the busybox mount but that didn't work, do I need the modified mount or will none of this help anyway?
Click to expand...
Click to collapse
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
craigacgomez said:
Code:
busybox mount -t FSTYPE /dev/block/sda1 MOUNT_LOCATION
Example:
Code:
busybox mount -t vfat /dev/block/sda1 /storage/sdcard0/usbotg
Click to expand...
Click to collapse
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Although I don't have nexus 10, I am having the similar mounting issue on my nexus 7 until I saw this post.
Advise about "adb shell" really helps me resolve the multiuser issue.
Thanks for sharing.
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
H3g3m0n said:
1) Unlock bootloader (adb oem unlock)
Click to expand...
Click to collapse
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
momulah said:
Is it posible to make a CWM flash file?
Click to expand...
Click to collapse
Not a high priority right now as currently you need to do the manual adb shell stuff by hand to get things mounted, a little extra setup work isn't a huge difference.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
Are you mounting in a 'adb shell' or locally in something like terminal emulator? My OTG cable won't be here for a while so I can't really test myself.
weasal said:
Any chance you could post the nls-utf8.ko for utf8 support?
Thanks!
Click to expand...
Click to collapse
Posted, haven't tested it but it seemed to insmod fine.
espionage724 said:
Isn't it fastboot that unlocks the bootloader, and not adb? (unless adb can do it too; I've only heard of fastboot though)
Click to expand...
Click to collapse
Yeh typoed, i'll fix that now.
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
alias_neo said:
How is this different to what I'm doing already? Mounting this way doesn't work, only the process that mounted it can see the files.
Click to expand...
Click to collapse
I've been working on getting OTG support natively in my AOSP based custom ROM and I have had some success... check out my ROM for details
H3g3m0n said:
Currently I'm thinking of ways to hack around the 'adb shell' requirement, as a basic hackish fix would be to make a program that turns on adb wireless, connects to the local device and issues a command. Of course possibly there is a 'proper' way to do mounting. Another lazy way for those with their shares on a Linux system would be a script issue commands to the server via a ssh, getting it to log back into the phone and mount stuff over adb wireless.
Click to expand...
Click to collapse
Just wanted to thank H3g3m0n as I was able to successfully mount over adb. Also came up with a workaround to bypass connecting to a PC, grabbed the arm fastboot binary from this thread and installed it on my nexus 7. Used it to connect wireless adb on the 10 and ran the mount commands on the 7.
H3g3m0n said:
Posted, haven't tested it but it seemed to insmod fine.
Click to expand...
Click to collapse
Thanks, I'll give it a try!
You might find my posts #156 and #162 at http://forum.xda-developers.com/showthread.php?t=1781411&page=17 helpful.
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
spdwiz18 said:
Sorry for the noob ? ...
What are the KO's do?
What is the practical use of then.
Sorry I did a little research on then but I could not find an answer in layman terms
Thank you for allowing me to learn.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Loadable_kernel_module
craigacgomez said:
http://en.wikipedia.org/wiki/Loadable_kernel_module
Click to expand...
Click to collapse
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
These modules are needed to enable support for CIFS (Windows share) mounts...
spdwiz18 said:
That helps allot.... Now i have an understanding of ko's in general. But what specificly do the modules this thread refers to do and the practical use of then. Thanks foot the help.
Sent from my toroplus using xda premium
Click to expand...
Click to collapse
Basically you can setup a shared folder from a remote computer. It allows you to have files on another system accessible as if it was part of the internal storage in the device.
Just found out that Android ships with the adb binary on the device itself (after crosscompiling it myself :/, oh well the experience was useful).
It should be possible to setup a script to start the adb server, connect to the localhost and execute the mount without too much difficulty.
Ok, added a script and instructions to the front page for simple on tablet mounting.
This is Ubuntu Touch
Disclaimer: Don't touch if your not experienced! You are responsible for what happens not me understand you agree that im not responsible in any way when you download!
Justsueme has been working on this rom for a while and now I bring it to a locked bootloader! Not possible Ubuntu says but im good a scrips, so test it out let us know READ EVERYTHING BEFORE FLASHNG...its not a normal rom!
Link to his threadhttp://forum.xda-developers.com/showthread.php?t=2564187
instructions:
New Experimental method
Wipe device ready for new rom
Flash Rom : Rom
Reboot device
IF no wifi on boot you may need set
chmod +x /data/local/userinit.sh
(pm or comment if you need with terminals)
I didn't add reverse tether by default so head to manual fixes section to find how to.(buggy fixes soon with gsm)
this is not an update to functionality its just a quick knock-up putting both .zips into one and adding fix for no PC to boot.
Old Method(outdated) use if not working
At this point youll have a black screen and no activity except ADB
plug phone into pc
grab this file : (70-jfltexx.rules) http://www.datafilehost.com/d/17d6dd77
now open terminal
$ su
$ adb push 70-jfltexx.rules /usr/lib/lxc-android-config/
$ adb shell "reboot"
phone will look like its doing nothing for a bit, but wait.
now it will boot back up like normal but you will have a ubuntu touch gui
BUGS:
celluar
BT
IR?
no sound (works with headphones)
camera (maybe needs libjnigraphics ?)
frame jump
app not loading
adb or ssh for cli
Manual Fixes:
now have connectivity via reverse tether:
adb root
adb shell setprop sys.usb.config rndis,adb
ubuntu network manager will show that samsung android is connecting.
open network settings edit that connection and change auto DHCP to shared
run this command (logged into phone)
dhclient usb0 -v
now on phone open webbrowser or ping 8.8.8.8 to test connection
just got WIFI !
make it auto load at boot
touch userinit.sh
nano userinit.sh
add to the file :
-
#!/bin/bash
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
-
adb push userinit.sh /data/local/userinit.sh
adb shell
chmod +x /data/local/userinit.sh
Contributors
JustSueMe, Warg-Razdroid
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: cyanogenmod
Reserved
Whoaaa man. This is big.
Sent from my SGH-I337 using XDA Premium 4 mobile app
jaythaovadose said:
Whoaaa man. This is big.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
download up!
Sweet! I am stoked to play with this!
Sent from my SGH-I337 using XDA Premium 4 mobile app
Bigbabyjesus said:
Sweet! I am stoked to play with this!
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cant get the zip booting will fix soon someone else please confirm?
Yeah, I'm stuck on splash screen. Can't even get to boot animation. Possibly a kernel problem?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Yeah I'm guessing you can flash the original phablet zip from his thread but he has a fix coming soon with kernel and I'm searching too
Sent from my SGH-I337 using Tapatalk
Dang... if this requires a custom kernel, then SafeStrap is out of question... I really wanted to try this one out, but have the dreaded MF3...
Fix is slow, but making progress
Sent from my SGH-I337 using Tapatalk
NNagendran said:
Dang... if this requires a custom kernel, then SafeStrap is out of question... I really wanted to try this one out, but have the dreaded MF3...
Click to expand...
Click to collapse
It needs a custom kernel sorry
Sent from my SGH-I337 using Tapatalk
You need to link his thread to this one. And give him proper credit. He is the one that has worked hard on this. Not being mean but I'm just saying.
Sent from my SGH-I337 using Tapatalk
toxicpaulution said:
You need to link his thread to this one. And give him proper credit. He is the one that has worked hard on this. Not being mean but I'm just saying.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Learn reading it's in op...
Sent from my SGH-I337 using Tapatalk
uploading new
up
Hey guys just wanted to thank you for taking this initiative. All the best.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
junooni.1980 said:
Hey guys just wanted to thank you for taking this initiative. All the best.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
nice!
Joeyxc said:
This is Ubuntu Touch
Disclaimer: Don't touch if your not experienced! You are responsible for what happens not me understand you agree that im not responsible in any way when you download!
Justsueme has been working on this rom for a while and now I bring it to a locked bootloader! Not possible Ubuntu says but im good a scrips, so test it out let us know READ EVERYTHING BEFORE FLASHNG...its not a normal rom!
Link to his threadhttp://forum.xda-developers.com/showthread.php?t=2564187
instructions:
New Experimental method
Wipe device ready for new rom
Flash Rom : Rom
Reboot device
IF no wifi on boot you may need set
chmod +x /data/local/userinit.sh
(pm or comment if you need with terminals)
I didn't add reverse tether by default so head to manual fixes section to find how to.(buggy fixes soon with gsm)
this is not an update to functionality its just a quick knock-up putting both .zips into one and adding fix for no PC to boot.
Old Method(outdated) use if not working
At this point youll have a black screen and no activity except ADB
plug phone into pc
grab this file : (70-jfltexx.rules) http://www.datafilehost.com/d/17d6dd77
now open terminal
$ su
$ adb push 70-jfltexx.rules /usr/lib/lxc-android-config/
$ adb shell "reboot"
phone will look like its doing nothing for a bit, but wait.
now it will boot back up like normal but you will have a ubuntu touch gui
BUGS:
celluar
BT
IR?
no sound (works with headphones)
camera (maybe needs libjnigraphics ?)
frame jump
app not loading
adb or ssh for cli
Manual Fixes:
now have connectivity via reverse tether:
adb root
adb shell setprop sys.usb.config rndis,adb
ubuntu network manager will show that samsung android is connecting.
open network settings edit that connection and change auto DHCP to shared
run this command (logged into phone)
dhclient usb0 -v
now on phone open webbrowser or ping 8.8.8.8 to test connection
just got WIFI !
make it auto load at boot
touch userinit.sh
nano userinit.sh
add to the file :
-
#!/bin/bash
insmod /system/lib/modules/dhd.ko firmware_path=/system/etc/wifi/bcmdhd_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt
-
adb push userinit.sh /data/local/userinit.sh
adb shell
chmod +x /data/local/userinit.sh
Contributors
JustSueMe, Warg-Razdroid
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: cyanogenmod
Click to expand...
Click to collapse
Sent from my Deadly Venom SS 3.0 S4 ~ 20GB free cloud https://copy.com?r=vtiraF
Is anyone actively working on this? Will it work with AT&T phones, or do I need to be concerned with the whole Loki Doki thing here as well? Until it is working with the cellular radio, I fear there is no reason to even play with this for now. Unfortunately, I don't think I have the skills to help out.
Subscribing.
Edit: Just tried to load this rom via TWRP v2.5.0.2 and it failed.
purdone said:
Is anyone actively working on this? Will it work with AT&T phones, or do I need to be concerned with the whole Loki Doki thing here as well? Until it is working with the cellular radio, I fear there is no reason to even play with this for now. Unfortunately, I don't think I have the skills to help out.
Subscribing.
Edit: Just tried to load this rom via TWRP v2.5.0.2 and it failed.
Click to expand...
Click to collapse
You do need Loki and such. I think development on this was merged into the international S4, if you check the Ubuntu wiki for Ubuntu touch you'll find the thread listed.
EDIT: It links to the same thread as OP, so I don't know if anyone is continuing it but I don't think so.
Sent from my SGH-I337 running Light ROM