Related
So I got sick of typing
$su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#chmod 777 /system
So I wrote a script and I just click on it in gscript.
Does this officially make me a white belt, lowest rank possible dev? Aahaha
Pm me and I can send you the script if you want haha.
(Yes, you are all supposed to laugh and make fun of me now)
Sent from my HTC Vision using XDA App
Ill give you a pat on the back. That's one small step to being a scripter
Also note you can do things in dos for adb
Sent from my T-Mobile G2 using XDA App
might as well post it publicly, i'd be interested in that script, i'll send pm as well
jontornblom said:
So I got sick of typing
$su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#chmod 777 /system
So I wrote a script and I just click on it in gscript.
Does this officially make me a white belt, lowest rank possible dev? Aahaha
Pm me and I can send you the script if you want haha.
(Yes, you are all supposed to laugh and make fun of me now)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Atleast u know how to do a script, I dnt even know how to use ADB.. root guided by youtube, I dnt mod my phone w/o watching video carefully n step by step method..
Cheers.. future DEV
Sent from my HTC Vision using XDA App
Congrats on the script! It's get's easier now that you have the concept - then it gets hard again lol.
While we're on the subject of scripting - any reason you choose that system rw mount script? There's 3 ways I've seen it done and they are all completely different... maybe the have different functions?
Again, good job and I like your idea. I saves a lot of typing especially with those commands since we type them a lot.
I think just by writing a successful script.. you are already above MANY xda users.
Kudos.
jontornblom said:
$su
#mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#chmod 777 /system
Click to expand...
Click to collapse
So this is the part where you tell me what it does, right?
omarsalmin said:
So this is the part where you tell me what it does, right?
Click to expand...
Click to collapse
His script mounts the system as rw.
Sent from my T-Mobile G2 using XDA App
Nice script
What I do is a little different. I have it saved as my initial command for terminal, so it starts whenever I use terminal.
The code I use is this:
export PATH=/data/local/bin:$PATH
su
mount -o rw,remount /system
I am obvlious though as to why you put yaffs2 and mtdblock3 and all that, I never thought it was necessary since it works just fine without it. I'm not too keen on linux syntax though so its probably obvious but I'm curious anyway.
Sent from my HTC Vision using XDA App
mejorguille said:
Nice script
What I do is a little different. I have it saved as my initial command for terminal, so it starts whenever I use terminal.
The code I use is this:
export PATH=/data/local/bin:$PATH
su
mount -o rw,remount /system
I am obvlious though as to why you put yaffs2 and mtdblock3 and all that, I never thought it was necessary since it works just fine without it. I'm not too keen on linux syntax though so its probably obvious but I'm curious anyway.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
That's what my question was too lol. It's a great script especially for his first but now he should make it less bulky. If it's being ran in terminal as a script then all he would really need is this:
Code:
#!/system/bin/sh
mount -o remount,rw /system
I don't believe you need to use su before running it but I always do just in case.
Of course you'll want to make a /system ro script (unmount) too so you're not always in mounted in rw access.
funkadesi said:
I think just by writing a successful script.. you are already above MANY xda users.
Kudos.
Click to expand...
Click to collapse
Haha, thanks!
I found that leaving out the yaffs2 etc didn't work. I read somewhere that you need this line with certain kernels. I wish I could give you a more learned answer though.
I'm thinking it's a good idea to put the system back in ro too, actually. Now I'll have made two scripts haha
Sent from my HTC Vision using XDA App
Not positive on all of this, so someone can correct me if I'm wrong, but
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
is used to mount system by accessing the NAND (hence the yaffs2 filesystem and mtdblock device). Many of the older Android guides use this command (since the older phones all used raw flash).
The Vision (and many of the newer phones) use an eMMC though, which has an FTL to present the NAND as a block device to the OS (just like a hard drive). This is why in many of the guides written nowadays, you'll see something more like this:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
This accesses the eMMC as a native block device (hence the ext3 filesystem). This is probably the "more correct" way of mounting the partition as it utilizes the actual FTL controller on the NAND as opposed to the more inefficient linux virtual block driver (what mtdblock does), so it's a little cleaner from a software development standpoint. Both commands accomplish the same thing though, so you could really use either.
The shortened form of the remount is what others have been listing:
Code:
mount -o rw,remount /system
Basically, since the system partition had already been mounted by the OS on boot, it should already know the proper way to remount it (i.e., you don't have to retell it the device or filesystem used). I don't believe this command will work on every ROM out of the box though (requiring either Busybox to have been installed or ro.secure=0 to be set in your default properties, maybe both).
Excellent and informative post! So is the reason why the
Mount -o rw,remount /system
Command doesn't't work for me is because busybox isn't installed? I'll test this out right now...
Also, I was thinking chmod 777 might be redundant because the system is already rw. Is this true? My understanding is the chmod 777 simply sets whatever path after it as modifyable. Is there a difference between rw and being able to modify files in linux?
Sent from my HTC Vision using XDA App
Hmm. When I try the stripped down command, I get the usage message...
Sent from my HTC Vision using XDA App
jontornblom said:
Excellent and informative post! So is the reason why the
Mount -o rw,remount /system
Command doesn't't work for me is because busybox isn't installed? I'll test this out right now...
Also, I was thinking chmod 777 might be redundant because the system is already rw. Is this true? My understanding is the chmod 777 simply sets whatever path after it as modifyable. Is there a difference between rw and being able to modify files in linux?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Well if you want to know if you have busybox just do this:
Code:
su
cd /system/bin
busybox
That should start busybox. It will say 'not found' if you don't have it - so if you need it the easy way is to use titanium backup to install it.
Btw, ianmcquinn that was very informative and well written. Thanks for explaining it so well.
Definitely have busybox. Definitely still just gives me the usage information...weird.
How do I set secure=0?
Sent from my HTC Vision using XDA App
ro.secure=0 is standard on most roms, so I asume you are just using a rooted stock build? You will need to unpack your kernel, change the ro.secure from a 0 to a 1, and repack the kernel. If you don't know how to do that, use this.
jontornblom said:
Definitely have busybox. Definitely still just gives me the usage information...weird.
How do I set secure=0?
Click to expand...
Click to collapse
What ROM you are using now? VillainROMZ?
Sent from my HTC Desire Z, using magic XDA app
AllWin said:
What ROM you are using now? VillainROMZ?
Sent from my HTC Desire Z, using magic XDA app
Click to expand...
Click to collapse
Virtuous 0.9.0
Sent from my HTC Vision using XDA App
I don't use Virtuous, but I would be shocked if it didn't already have ro.secure=0 set already. You can check by typing this in terminal:
Code:
getprop ro.secure
It should return a 0. This property is set in the ramdisk within your boot.img. To set it yourself, you would have to unpack the image, modify the setting in the default.prop file, repack the image, and then flash it back to your phone. As was said earlier though, pretty much all of the custom roms set this for you already.
Not sure what is going on in your case then. Maybe try running the mount command explicitly through busybox to see if that is the problem.
Code:
busybox mount -o rw,remount /system
If this works, sounds like you may want to reinstall busybox since the symlinks were not properly set up. Another thing maybe worth trying is to swap the order of remount and rw in the options. I've seen reports of this making a difference for some people, but have no clue why it should (maybe different versions of the mount command/busybox). Kind of a long shot. So try either of these commands:
Code:
mount -o remount,rw /system
busybox mount -o remount,rw /system
EDIT: In case you were curious, here's a link I had bookmarked about how to edit the boot.img. I'm sure there are others out there as well.
How To Deodex Your Device Tutorial
What is odexing?
What is deodexing?
Why you may consider deodexing over odexing.
Disclaimer: This tutorial is meant as a guide for education purposes only. If you decide to take the initiative to perform a deodexing operation on your device a family member’s device or a friend’s device – you (the surgeon) assume all responsibility for you own actions. In other words… Your problems are your own… Read before dissecting!
What is Odexing? – Within the Android Operating System applications come in the form of .APK packages compiled with .odex files that work with the primary application. Odex files are compiled with portions of the main application manifests and hold partial instructions for how this application will boot, how it will run and how it will act within the entire file structure. These odex files hold instruction for an application to pre-boot, pre-launch and how the service (if any) will function. Some assumptions are that the speed of the file system and application will be increased by way of pre launching the application prior to usage. My thoughts on this are that battery usage and memory are also being consumed while you may not even draw on that particular application. Simply put, the Odex file holds a set of functioning instructions for the application it belongs with. Think of it as sort of a pre-buffer and caching at the same time.
What is Deodexing? – Deodexing is the process of removing the child instruction file from the parent file and importing all the information that has been removed from the odex file into the APK. Full freedom to perform on its own without the aid of little odex.
Why may you consider deodexing a file system over having an odexed file structure? – Application modifying can be near impossible with many instructions for a single application existing in various places of the file structure. Consolidating all the functions of an APK in a single location will help to simplify the process.
Are you ready to become deodexed…?
So, get your scalpel ready and let’s begin…
This process will be described working within a Windows environment.
You will need to have a few things in order before we begin:
1) A Rooted phone – (A Must)
2) A working Windows workstation or desktop
3) xUltimate Utility v2.2.1 (see the link from my prior post to download the tool)
http://forum.xda-developers.com/showpost.php?p=12024563&postcount=126
4) Developers SDK toolkit – or – the ability to run adb commands
5) A little time to burn
Let’s get started:
1) Assuming that you have already downloaded xUtility v2.2.1 – unzip the package to a directory you can easily access.
2) Make sure to put your device in debugging mode and plug the USB cable from the PC into your device.
3) You can run the Test.exe to verify that the xUtility sees your device, but it’s not necessary and may cause a doubling effect with adb so that your device won’t be seen – so just execute the Main.exe and wait for the device to communicate with the application.
4) Once your device has been read by the xUtility, answer the questions in the prompts according to your make and model. (You do not need to upgrade to a newer version of xUtility because this is the newer version – regardless of what the application states)
5) Execute Action 1 then follow the instruction at the prompts
6) Execute Action 2 then follow the instruction at the prompts
*Note: For any reason the process fails to begin or hangs during the process – verify that there is only one instance of adb running on your PC or this could result in issues.
*Note: If issues occur, you can always perform an adb pull to the origi_app directory (within xUtility) and then the origin_frame directory (within xUtility)
*Note: This could take some time depending on the size of the directories
7) When the migration is complete - perform Action 3 in xUtility - This will perform the deodexing of the application APKs.
8) When the Application Deodexing is complete - perform Action 4 in xUtility - This will perform the deodexing of the framework APKs. (Mainly Java Files)
9) For safety purposes – backup the files in both the origin_app and the origin_frame directories and put them in a safe place just in case.
10) Close the prompt for xUtility – the process should be complete.
11) Exit debugging mode with your device and enter into mass storage mode. You will need to remove the USB cable before performing this, then plug the USB cable back in once the mode shift has occurred.
11) You should now see your device in Windows as a mass storage drive.
12) Go into the xUtility directory and copy the 2 folders named – “done_app” and “done_frame” to the root of your internal SDCard.
13) Get your command prompt open and get ready to type some code
Just my preference - Prior to migration of the deodexed files I chose to wipe the dalvik-cache from my device to ensure no rouge variant cached instructions would be present after the next boot. – You could CWM into the next soft boot and perform a dalvik wipe if you choose.
At The Command Prompt: Code Below:
adb shell
# su
# stop
# mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# rm /system/app/*.odex
# rm /system/framework/*.odex
# chmod 644 /system/app/*
# chown root.root /system/app/*
# chmod 644 /system/framework/*
# chown root.root /system/framework/*
# mount -o ro,remount -t ext4 /dev/block/mmcblk1p21 /system
# reboot
After your device reboots it will take longer than usual to load the new file settings – so be patient and don’t panic.
You now have a deodexed device!
If you found this tutorial useful and helpful or you just enjoy reading my posts Show your gratitude by hitting that thanks button on this post.
All the best
Peace-
Liv33viL
Might want to point out that this is completely useless for anyone on a custom ROM.
MikeyMike01 said:
Might want to point out that this is completely useless for anyone on a custom ROM.
Click to expand...
Click to collapse
Might want to say why?
MikeyMike01 said:
Might want to point out that this is completely useless for anyone on a custom ROM.
Click to expand...
Click to collapse
If they knew enough to flash a custom ROM then they should know if the ROM that they flashed was deodexed or not if posted by the developer.
Then they wouldn't be on this thread reading this post unless they wanted a bit of an education on the topic.
Hence making your remark quite pointless!
Liv33viL said:
If they knew enough to flash a custom ROM then they should know if the ROM that they flashed was deodexed or not if posted by the developer.
Click to expand...
Click to collapse
O ye of far too much faith.
opcow said:
O ye of far too much faith.
Click to expand...
Click to collapse
agreed. so many people dont even bother to read the OP on a rom thread and ask if feature X exists, when its clearly labeled as such in the OP
not something I'd be willing to do regardless if my phone has a deodexed rom or not. seems a lot could go wrong if you made a slight mistake especially with running commands on your phone.
but at least I now know what deodexing is now
bunnsguy said:
not something I'd be willing to do regardless if my phone has a deodexed rom or not. seems a lot could go wrong if you made a slight mistake especially with running commands on your phone.
but at least I now know what deodexing is now
Click to expand...
Click to collapse
Yep, didn't know what it was.
You Take Your Shots When the Opportunity Presents Itself
opcow said:
O ye of far too much faith.
Click to expand...
Click to collapse
Yeah, I guess I was reaching on that statement... anticipating the best - but real world scenarios prevail!
What can I say... I prefer to be an eternal optimist.
But the statement was written to read "they should know" like as in if you lick the inside of a freezer door... "you should know" that it is highly likely that one would remain there until the thaw...minus a few layers of skin of course
Basically I got the idea to write this tutorial when reading a few threads whereas many users wanted to make some cosmetic mods to their devices, but really didn't want to jump out of their factory installed file systems. I noticed a few theme developers creating a skin pack for certain features, such as lock screens, docks, etc... and it required a deodexed file system. Many people didn't understand or even know what deodexed meant, let alone some never even heard of the word.
I posted in one of the threads that If I were feeling ambitious that I would create an educational tutorial and guidelines to perform the operation if one was interested... after getting injected with some knowledge.
You Take Your Shots When the Opportunity Presents Itself
Education = Key
Key = Knowledge
Knowledge = Insight
Insight leads to Applied Knowledge
Applied Knowledge = Power
Peace-
Very interesting, I learned a thing or two but of course the guys who really should be reading this are the ones that wont :/
Sent from my SGH-I897 using XDA App
Glad to have another resource just in case I ever decide to start developing my own custom ROM.
Herp derp Captivate XDA app.
Fantastic! - Glad to see an interest in some of the nuances of this file structure.
Peace-
A Common Philosophy
Liv33viL said:
Yeah, I guess I was reaching on that statement... anticipating the best - but real world scenarios prevail!
What can I say... I prefer to be an eternal optimist.
But the statement was written to read "they should know" like as in if you lick the inside of a freezer door... "you should know" that it is highly likely that one would remain there until the thaw...minus a few layers of skin of course
Basically I got the idea to write this tutorial when reading a few threads whereas many users wanted to make some cosmetic mods to their devices, but really didn't want to jump out of their factory installed file systems. I noticed a few theme developers creating a skin pack for certain features, such as lock screens, docks, etc... and it required a deodexed file system. Many people didn't understand or even know what deodexed meant, let alone some never even heard of the word.
I posted in one of the threads that If I were feeling ambitious that I would create an educational tutorial and guidelines to perform the operation if one was interested... after getting injected with some knowledge.
You Take Your Shots When the Opportunity Presents Itself
Education = Key
Key = Knowledge
Knowledge = Insight
Insight leads to Applied Knowledge
Applied Knowledge = Power
Peace-
Click to expand...
Click to collapse
I Agree with you on this.....WELL SAID! And Thank You for the time invested on a great tutorial/ lesson. I too learned a thing or two.
I would like to add four lines of code to the set of commands you type in adb shell
adb shell
# su
# stop
# mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# rm /system/app/*.odex
# rm /system/framework/*.odex
# chmod 644 /system/app/*
# chown root.root /system/app/*
# chmod 644 /system/framework/*
# chown root.root /system/framework/*
# mount -o ro,remount -t ext4 /dev/block/mmcblk1p21 /system
# reboot
The reason for these additional commands is that when any files get moved to /sdcard, and directories under it, the ownership of the files becomes system.sdcard_rw and the permissions for the files become rwxrwxr-x. When these files are copied back to their original subdirectories under /system, they retain the new ownership and permissions. The original proper ownership and permission for the files before any changes were made was root.root and rw-r--r--. The four commands I added restores them to that original state, and therefore does not create any unintentional security risk. If anyone has already done the procedure. They can fix the files by doing just this in an adb shell.
adb shell
# su
# stop
# mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
# chmod 644 /system/app/*
# chown root.root /system/app/*
# chmod 644 /system/framework/*
# chown root.root /system/framework/*[/COLOR]
# mount -o ro,remount -t ext4 /dev/block/mmcblk1p21 /system
# reboot
ytt3r said:
Very interesting, I learned a thing or two but of course the guys who really should be reading this are the ones that wont :/
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
This statement kind of worries me coming from a developer. Haha.
Wisdom
AA “Information is not knowledge.”
whiteguypl said:
This statement kind of worries me coming from a developer. Haha.
Click to expand...
Click to collapse
I thought the same thing when I saw it.
[OP] Edit: See Edit Tag in OP For Details
rajendra82 said:
I would like to add four lines of code to the set of commands you type in adb shell
adb shell
# su
# stop
# mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# rm /system/app/*.odex
# rm /system/framework/*.odex
# chmod 644 /system/app/*
# chown root.root /system/app/*
# chmod 644 /system/framework/*
# chown root.root /system/framework/*
# mount -o ro,remount -t ext4 /dev/block/mmcblk1p21 /system
# reboot
The reason for these additional commands is that when any files get moved to /sdcard, and directories under it, the ownership of the files becomes system.sdcard_rw and the permissions for the files become rwxrwxr-x. When these files are copied back to their original subdirectories under /system, they retain the new ownership and permissions. The original proper ownership and permission for the files before any changes were made was root.root and rw-r--r--. The four commands I added restores them to that original state, and therefore does not create any unintentional security risk. If anyone has already done the procedure. They can fix the files by doing just this in an adb shell.
adb shell
# su
# stop
# mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
# chmod 644 /system/app/*
# chown root.root /system/app/*
# chmod 644 /system/framework/*
# chown root.root /system/framework/*[/COLOR]
# mount -o ro,remount -t ext4 /dev/block/mmcblk1p21 /system
# reboot
Click to expand...
Click to collapse
Raj, thank you for providing the additional lines of code. Yes, you are absolutely correct. It was very late.... uhm very early in the AM when I was was proofreading and it didn't pop out at me then. Now, it pops.
The OP now reflects the additions and credit was given to you for the additions in the edit.
Thank you again my friend.
Peace-
This is the tutorial that I'm looking for. I already ask many times how to deodex my captivate but nobody answer it until I find this thread. Two thumbs up.
ps: could you add a video tutorial? I think a video is more informative for me because I don't have any experience with adb so that I little bit confuse if there is a command line using adb.
max_82 said:
This is the tutorial that I'm looking for. I already ask many times how to deodex my captivate but nobody answer it until I find this thread. Two thumbs up.
Click to expand...
Click to collapse
Fantastic Max!
Glad you finally found what you were looking for!
Peace-
Hope this is the right place to post this.
My Atrix is rooted stock 1.83 .
I'm trying to "adb push" some OGG files to "/system/media/audio/" to add-to and replace some of the existing system sounds, especially that bloody annoying keypress (typewriter) sound, but I'm getting the following error (which makes sense):
Read-only file system
Tried using Root Explorer, same issue...again makes sense since its mounted as Read only on boot.
I tried booting into recovery mode, but I can't access the phone via ADB at all, even with USB Debug enabled. I also tried "adb remount" command, no luck either. I get an error "operation not permitted".
So, does anyone know the correct sequence of commands I need in ADB to remount the Atrix /system folder as RW??
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
when you access root explorer, does it let you know that it has been granted supervisor privilages? Does it give you the option to change from read to write? what did you use to root? I had to run the original Aroot three times before if finally gave me root.
You're the best, worked perfectly Can't believe that hideous typewriter sound is gone, it only took me 1.5 years as an Android user to finaly say enough is enough. Whomever thought it was a good idea to mimic the sound of an 1800's typewriter on a 21st century device needs to be fired.
Thanks again.
aver2one said:
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
Click to expand...
Click to collapse
i need help
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Obiechina said:
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Click to expand...
Click to collapse
Well congrats! that was the dumbest thing ever. NEVER attempt something like that unless you have CWM or equivalent installed, have a backup, and know what you are doing.
Have you tried to read your device's xda forum?
Please Help
Hahaha, can you help me?
i want to change my /system/framework folder by using the POWER and UP volume keys
i had a backup of my system/framework in my SD..
What should i do?
Hi Guys,
I have just gotten Wifi Ad Hoc connection working in the Samsung 10.1v (don't see why it won't work on the 10.1 either)
You need to have adb installed and your Tablet needs to be rooted.
I used 2 threads as reference for making this work:
http://forum.xda-developers.com/showthread.php?t=1069569
and
http://forum.xda-developers.com/showthread.php?t=1033314
As a newbie to this i will show you what i did, maybe someone can clean up the process with a simple approach:
You need to turn on Airplane mode to disable wifi, or you will get an error when trying to copy the wpa_supplicant file later on in the instructions...
I had trouble with the adb push command (shown in the above threads) so I did this instead.
Unzip and copy wpa_supplicant file (attached) to Tablet (I used downloads directory)
Get ES File Explorer from Market
Open ES File Explorer and in settings menu select Root options.
Set Root Explorer and use HiAPK
Then Tick Mount File System, then exit menu and navigate to /system/bin and copy wpa_supplicant to somewhere safe (I made backup directory in storage/ sd memory)
Now copy new wpa_supplicant file from where you saved it (downloads directory) to /system/bin
Now in windows command box type:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 755 /system/bin/wpa_supplicant
# chown system.wifi /data/misc/wifi/wpa_supplicant.conf
# exit
Now reboot and turn off airplane mode and enjoy.
Usual conditions if you follow this and something bad happens please don't blame me i used the above method (with trial and error) which worked for me (but maybe i just got lucky)
Also I want to acknowledge the hard working devs that pioneered the process and created the file - great work!!
Good luck...
drnackers said:
Hi Guys,
I have just gotten Wifi Ad Hoc connection working in the Samsung 10.1v (don't see why it won't work on the 10.1 either)
You need to have adb installed and your Tablet needs to be rooted.
I used 2 threads as reference for making this work:
http://forum.xda-developers.com/showthread.php?t=1069569
and
http://forum.xda-developers.com/showthread.php?t=1033314
As a newbie to this i will show you what i did, maybe someone can clean up the process with a simple approach:
You need to turn on Airplane mode to disable wifi, or you will get an error when trying to copy the wpa_supplicant file later on in the instructions...
I had trouble with the adb push command (shown in the above threads) so I did this instead.
Unzip and copy wpa_supplicant file (attached) to Tablet (I used downloads directory)
Get ES File Explorer from Market
Open ES File Explorer and in settings menu select Root options.
Set Root Explorer and use HiAPK
Then Tick Mount File System, then exit menu and navigate to /system/bin and copy wpa_supplicant to somewhere safe (I made backup directory in storage/ sd memory)
Now copy new wpa_supplicant file from where you saved it (downloads directory) to /system/bin
Now in windows command box type:
adb shell
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 755 /system/bin/wpa_supplicant
# chown system.wifi /data/misc/wifi/wpa_supplicant.conf
# exit
Now reboot and turn off airplane mode and enjoy.
Usual conditions if you follow this and something bad happens please don't blame me i used the above method (with trial and error) which worked for me (but maybe i just got lucky)
Also I want to acknowledge the hard working devs that pioneered the process and created the file - great work!!
Good luck...
Click to expand...
Click to collapse
what about the usage of battery after install that wpa_supplicant.conf
Because i used to transfer a similar file like wpa_supplicant.conf to help my samsung Galaxy S i9000 to connect the adhoc WIFI. The usage of battery is horrible, I charged my phone whole night and there is no more battery remaining next morning
I will keep you posted, but been using it on ad hoc for a couple of hours now and nothing out of the usual. Battery seems just same as on wifi.
I will leave it on overnight and report back tomorrow
Sent from my GT-P7100 using XDA App
OK well it has been connected all night to Xperia x10 running barnacle no issues downloading through swarm bittorrent client.
Battery was 78% now at 58% so I would see this as acceptable.
Only 1 issue I have noticed, every time you connect to ad hoc it asks for password and adds it as new connection, so you end up with a few in the list but hold on old connections and 'forget' works fine
Sent from my GT-P7100 using XDA App
drnackers said:
OK well it has been connected all night to Xperia x10 running barnacle no issues downloading through swarm bittorrent client.
Battery was 78% now at 58% so I would see this as acceptable.
Only 1 issue I have noticed, every time you connect to ad hoc it asks for password and adds it as new connection, so you end up with a few in the list but hold on old connections and 'forget' works fine
Sent from my GT-P7100 using XDA App
Click to expand...
Click to collapse
woooo! Wonderful!
I had used the ad hoc wifi and knew that issue already. Anyway, thank you for remining!!
Maybe something should do with the usage of battery, because there is 20% drop during the whole night.........
well, in that case, my cellphone cannot tolerate it
just installed the JuiceDefender app on my 10.1v.
before that, the wifi/3G standby overnight will consume about 10% of battery.
after installing it, and the night more, it went down by 4%.
2nd day of using it and battery life SEEMS better.
I created a zip flashabile on recovery, we'll post it and put it in the first thread?
Anyone try this on 10.1?
DroidHam said:
Anyone try this on 10.1?
Click to expand...
Click to collapse
I haven't tried but it works
I cant seem to get it working right...
After following these steps my wifi drops every 10 seconds... It will see the adhoc though ;-D
I have to disable wifi and re-enable then it will auto join a network for another 10sec before it drops. any advice?
I used adb and it worked "MAKE SURE THAT YOU LOCK THE PERMISSION with CHMOD 755 or it will not work"
put the tablet in airplane mode
I download the file put into C:\ of desk top
I had backup my original by using adb pull /system/bin/wpa_supplicant
these are commands and responses
>adb shell
[email protected]:/ # su
su
[email protected]:/ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/bin
chmod 777 /system/bin
[email protected]:/ # chmod 777 /system/bin/wpa_supplicant
chmod 777 /system/bin/wpa_supplicant
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
>adb push c:\wpa_supplicant /system/bin/wpa_supplicant
1267 KB/s (295964 bytes in 0.228s)
>adb shell
[email protected]:/ # su
su
[email protected]:/ # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
[email protected]:/ # chmod 755 /system/bin/wpa_supplicant
chmod 755 /system/bin/wpa_supplicant
[email protected]:/ # chmod 755 /system/bin
chmod 755 /system/bin
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
Tried the flashable zip using cwm 4.0.0.4 but I keep getting installation not successful message. The installation starts, file is opened but the result is unsuccessful. Any suggestions?
10.1v /unlocked / rooted / cwm 4.0.0.4
Edit: Just saw the manual push method above. It will just be so much easier if the flashable version would work.
pushed to system/bin w/ root explorer and edited permissions with RE too.
works so far on my 10.1 retail rooted
nick7920 said:
1267 KB/s (295964 bytes in 0.228s)
Click to expand...
Click to collapse
Works perfectly. The only thing different is the file size reported. Typo?
1762 KB/s (295964 bytes in 0.164s)
baggenismo said:
I cant seem to get it working right...
After following these steps my wifi drops every 10 seconds... It will see the adhoc though ;-D
I have to disable wifi and re-enable then it will auto join a network for another 10sec before it drops. any advice?
Click to expand...
Click to collapse
I have exactly the same issue. I did this same procedure on my galaxy tab (the original 7" one) and it worked great. Replacing the wpa_supplicant file on my galaxy tab 10.1 has the connections work for 10 seconds and then drop. Incidently, I find this is true for all connections (ad-hoc and regular). Switching back to the original file fixes this. I've played around with the config file in /data/mis/wifi/wpa_supplicant.conf and added ap_scan=1, but I've had no luck. I have the 16 GB retail version. My version also had a locked bootloader. Any suggestions would be most appreciated.
Thanks,
Ben
I don't seem to have this problem of wi-fi disconnecting on my 10.1v. So far working perfectly with Connectify, even when the device has screen off, connection seems to persist - I did select never switch to mobile data from settings. I don't know how long it will stay connected though, haven't done a time test yet.
makbil said:
I don't seem to have this problem of wi-fi disconnecting on my 10.1v. So far working perfectly with Connectify, even when the device has screen off, connection seems to persist - I did select never switch to mobile data from settings. I don't know how long it will stay connected though, haven't done a time test yet.
Click to expand...
Click to collapse
My tablet is wifi only. Perhaps this is the issue. Has anyone gotten this to work who has a wifi only tablet (retail edition)?
does not work...
Left the tablet aside for an hour. I unlocked the screen, and instantly opened the web browser. The connection was working. So maybe it does have something to do with 3G connection even though it is turned off. I am using Connectify (free version) on my notebook.
Just thought of something. I have juicedefender set to turn off 3g when my phones screen turns off. This could cut connectivity without dropping wifi signal. Will test theory tomorrow...
Sent from my Galaxy Tab 10.1 using Tapatalk.
Hi guys,
I'm really new here, I can't post in this thread: http://forum.xda-developers.com/showthread.php?t=836022
I created a working ubuntu11.04 .img, with unity-2d. I don't know if anybody cares, it was funny to make.
It is just a minimal install with unity-2d and tightvncserver. Really minimal. Firefox, office applications, anything else DOES NOT installed.
However, you can install anything using apt-get install.
I installed wget and nano, because it was needed to configure the vnc. I plan to make a bigger one with all the programs and stuff installed. Maybe tomorrow. Or next week.
How to use: Unzip, rename to ubuntu.img and simply replace the original ubuntu.img with this one. Use root as user/nickname and ubuntu as password, as usual.
Download link to .img:
Download link to the other files needed:
Links tomorrow. "New" .img too.
If you are a mod and you're reading this, please move this post it the thread I linked in the beginning, or anywhere where this post is in its place.
-Sorry for my english.
Please help! Give me additional space by using my referral: http://db.tt/W0knUea
edit1: So, now I've got 10 comments, I don't have to write everything in separate comments. What I've done yet: make some simple script to automatically turn on/off the vncserver (1024x600, tab native res, I found it enough), and get tired of the resource hungriness of unity-2d. I mean it needs about the same CPU power (I guess) as the galaxy tab has, and it needs about 200MB RAM. But this is to run native. The VNC version is far from native, so it's slow as f..., I mean, very slow. Then I looked for a little less resource-hungry desktop environment, and I found lxde. I made an image with that. It's slow too, but much faster than unity-2d. I need to configure it a little more, to be more touch-friendly. And I want to do a few other thing, and write a how to make your own .img file thing. If you want to do it now, here some links, I will write about it sometimes.
http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
https://wiki.ubuntu.com/ARM/RootfsFromScratch
http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.html
http://galaxytabhacks.com/galaxy-ta...tall-ubuntu-linux-on-galaxy-tab-10-1-tabuntu/
http://androlinux.com/android-ubuntu-development/how-to-build-chroot-arm-ubuntu-images-for-android/
I also suggest reading mount, umount and rootstock man pages.
This image works quite well. As with every VNC build, its a bit slow and Unity doesn't help that (even in its nice Unity-2d form), but if you want Ubuntu on your Tab this is a pretty sweet image. Ultra-lightweight, too. Nice work, OP!
Firstly, thankyou for not making 10 spam posts just to get this posted in the Development section, shouldnt take you long to get 10 posts under your belt in this thread then I'll move it into the dev section for you
Good job by the way..
how to run this?
http://forum.xda-developers.com/showthread.php?t=836022
It's writen down here.
The link to the files is in the first post.
Do I write 'bootubuntu' in command line instead of 'bootlinux' or do I have to change the filename of 'bootubuntu' file? I guess first of the two is correct, but it's better to ask than to brick
Oh and is the AndroidSDK really needed? I don't see anything about usage of it in instruction....
maslak666 said:
Do I write 'bootubuntu' in command line instead of 'bootlinux' or do I have to change the filename of 'bootubuntu' file? I guess first of the two is correct, but it's better to ask than to brick
Oh and is the AndroidSDK really needed? I don't see anything about usage of it in instruction....
Click to expand...
Click to collapse
Hi!
The SDK is not strictly necessary since you could use a Terminal Emulator to run the necessary commands but using an ADB shell is just bit easier sometimes. That being said, you should install the SDK if you ever want to do much with an Android. It's easy to install and very powerful.
And yes, write bootubuntu instead of bootlinux when prompted. I know what you mean
Allright, I went through it and now got it installed . But I can't see firefox nor any office application... How to access them? Also can't get into terminal to write 'apt-install' there.....
maslak666 said:
But I can't see firefox nor any office application... How to access them?
Click to expand...
Click to collapse
sisa7 said:
Really minimal. Firefox, office applications, anything else DOES NOT installed.
However, you can install anything using apt-get install.
Click to expand...
Click to collapse
I'll write a howto tonight or next day or I don't know. I need to study to university too. You need adb or android terminal emulator (from the market) to use apt. Short version: when your prompt is "[email protected]:/#" simply do this command: "apt-get install firefox"
Just poked around a little. Now I know (or at least I think I now) what else I have to do.
http://dl.dropbox.com/u/41806444/bootubuntu2
Cleaned up version of bootubuntu. Copy it to /sdcard/ubuntu and simply run it. You need to use the sh command, so type "sh bootubuntu2" in android terminal emulator or adb shell in /sdcard/ubuntu foler.
Oh, sorry I forgot to mention, this script only works with overcome kernel and rom. You shold modify the
mount -o remount,rw -t ext4 /dev/block/stl9 /system
and the
mount -o remount,ro -t ext4 /dev/block/stl9 /system
rows. Enter "mount" to android terminal to see your /system dir type and path.
Synaptic looks like to work, software-center doesn't even start.
To really enjoy full linux distros like this, one should have a swap-enabled kernel. Instead, kernel on the Tab has no swap, and if you dare open some large app, the lack of ram makes it slow and unresponsive.
This is the main problem imho.
Ernesto de Bernardis
N900 - Galaxy Tab 7"
sisa7 said:
Oh, sorry I forgot to mention, this script only works with overcome kernel and rom. You shold modify the
mount -o remount,rw -t ext4 /dev/block/stl9 /system
and the
mount -o remount,ro -t ext4 /dev/block/stl9 /system
rows. Enter "mount" to android terminal to see your /system dir type and path.
Click to expand...
Click to collapse
Or keep it simple silly
mount -o remount,rw /dev/block/stl9 /system
mount -o remount,ro /dev/block/stl9 /system
cdesai said:
Or keep it simple silly
mount -o remount,rw /dev/block/stl9 /system
mount -o remount,ro /dev/block/stl9 /system
Click to expand...
Click to collapse
The /dev/block/stl9 part is changing too.
debernardis said:
one should have a swap-enabled kernel. Instead, kernel on the Tab has no swap
Click to expand...
Click to collapse
Thanks. I didn't know this is the problem. I will try out http://forum.xda-developers.com/showthread.php?t=483110 this and see what happens.
@sisa7 do you have any update?
debernardis said:
@sisa7 do you have any update?
Click to expand...
Click to collapse
Yep.
This email is an automated notification from Dropbox that your Public links have been temporarily suspended for generating excessive traffic. Your Dropbox will continue to function normally with the exception of Public links.
This suspension is temporary (3 days for the first time).
Sorry guys. Anybody know a decent upload site?
Also, I'm working on LXDE desktop. But the university makes me busy, so I haven't got too much time. Sorry.
Minus.com
Box.net
Multiupload.com
Is this still alive?
I tried installing the one in the other [MOD] Forum but when I try to install apps to Ubuntu I get a conection "404" error
Do you guys think this image will work?