I am following the instructions as per the below thread to allow my Acer a500 see my Nokia N900 for tethering purposes.
http://forum.xda-developers.com/showthread.php?t=1033314
I have copied the wpa_supplicant file over the one thats already there.
Now when I open the Terminal Emulator to try ADB remount it comes with an error saying device not found.
I have the wifi turned off, I also have Root Explorer, but I found File Manager HD quite handy.
Now after trying the instructions I now dont have wifi - it comes with an error.
I have tried copying the stock wpa_supplicant file across, with no success.
Can someone please help.
to get AD-Hoc working you first need root and either root explorer (paid app but worth the money) or es file explorer (free but you have to enable root privaleges inside the app. its under the settings menu)
1. navigate to system/bin and copy wpa_supplicant
2. past this to your sd card as a backup
3. rename wpa_supplicant to wpa_supplicant.old
4. extract the file from the download and past it into the system/bin folder. (should be wpa_supplicant)
4. Long press on the file once copied
6. select Permissions and set to User: RWE, Group & Others:RE only
This is the easiest way to fix this... make sure in root explorer you set to rw at the top left in order to rename copy or past into this directory..
Good luck
this is the file .
View attachment wpa_supplicant.zip
Thanks for that, your a genius.
Now that my device can see my phone, I cannot see any web pages.
Is there something else I need to do?
That is very odd .. try rebooting the phone and the tablet..
also try on the tablet
go to settings / applications.. go to the web browser.. and clear cache and data..
is only thing i can think of ..
never had a issue other then my cell sometimes get hung on a cell tower and a reboot fixes this.. .
try connecting another wifi device to the phone to determine if its the tablet or phone..
I ended up changing the program I use to tether on my N900 and now works a treat.
Once again, thanks for your help
Thanks erica_renee . Worked right on point !
You are way too much girl....)))
So I guess THAT's why we should be nice to her!
Thsnks guys.
Now bring me my coffeee
erica_renee said:
Thsnks guys.
Now bring me my coffeee
Click to expand...
Click to collapse
I'll bring nothing, but the world
Works on Ideapad K1
Erica_renee, you are awsome!
I followed your instructions and BAM worked first time.
Thanks
You are Very welcome..
But i do want to point out They are not my instructions..Its been so very long ago i dont remember who to give the credit to.. I think someone from the Zoom Forum..
I just remembers how to do it and do not mind sharing what i have learned with anyone...
So i guess i should say thanks to everyone who is actually a developer or close.. for all the hard work they have done to make my tablet enjoyable to use..
erica_renee said:
to get AD-Hoc working you first need root and either root explorer (paid app but worth the money) or es file explorer (free but you have to enable root privaleges inside the app. its under the settings menu)
1. navigate to system/bin and copy wpa_supplicant
2. past this to your sd card as a backup
3. rename wpa_supplicant to wpa_supplicant.old
4. extract the file from the download and past it into the system/bin folder. (should be wpa_supplicant)
4. Long press on the file once copied
6. select Permissions and set to User: RWE, Group & Others:RE only
This is the easiest way to fix this... make sure in root explorer you set to rw at the top left in order to rename copy or past into this directory..
Good luck
Click to expand...
Click to collapse
I clicked the "Thanks" button but this one deserves more than that! Thank you so much GG, you've made my day!
Regards,
Bob
Ahhh!
Thanks.
Now I can use more than my phone while travelling.
erica_renee said:
to get AD-Hoc working you first need root and either root explorer (paid app but worth the money) or es file explorer (free but you have to enable root privaleges inside the app. its under the settings menu)
1. navigate to system/bin and copy wpa_supplicant
2. past this to your sd card as a backup
3. rename wpa_supplicant to wpa_supplicant.old
4. extract the file from the download and past it into the system/bin folder. (should be wpa_supplicant)
4. Long press on the file once copied
6. select Permissions and set to User: RWE, Group & Others:RE only
This is the easiest way to fix this... make sure in root explorer you set to rw at the top left in order to rename copy or past into this directory..
Good luck
Click to expand...
Click to collapse
I downloaded es file explorer and enabled root exploring as well as "Mount File System" (which is supposed to make the system writable) and with or without the mount file system, I cannot find the System file nor bin. I have the Samsung Galaxy Tab 8.9 Wifi Only. It's running Honeycomb 3.2. Any suggestions?
Not my credit
This fix is not from me.. I just re posted something that has been around since our tablet was released.. I would say give that person the credit. I am not sure who actually did it .. I think that file originally came from the ZOOM FORUM.
Anyway Just wanted to make sure that was POINTED OUT.I only know from what i have read for my own personal use.
Thanks All ... Erica Renee
Firecracker_RC said:
I downloaded es file explorer and enabled root exploring as well as "Mount File System" (which is supposed to make the system writable) and with or without the mount file system, I cannot find the System file nor bin. I have the Samsung Galaxy Tab 8.9 Wifi Only. It's running Honeycomb 3.2. Any suggestions?
Click to expand...
Click to collapse
Can anyone help me with this?
check you su. update the su root binaries . make sure busybox is installed and updated..
you can check the last two with root checker . a app on the market..
There iss also somewhere in the settings. that show a mount point . .something like /mnt/sdcard.
this should be just a / in there to have access to the system folder. I dont have es file explorer installed as i did not like it.. but i do remember having to change this defalt mount or folder option.. Astro file manager and some others also have this defalt . You can also keep going back and will take you there ..
Even though Titanium Backup says I have BusyBox, another app I tried to install said I did not and needed to install, so I went to the market to install and BusyBox says I need to perform Nand Unlock before installing BusyBox. Can you point me in the direction for doing that. I have the Galaxy Tab 8.9 Wifi Only. I see alot of stuff out there but not sure if it's right for my tab or if the instructions are universal to android users. How did you do Nand Unlock?
So I rooted by Galaxy S5 SM-G900V running 4.4.4. (please be specific, Im new to this). My device is ALREADY rooted and 100% confirmed, as I used root checker.
And now everytime I open gallery or do certain things, It tells me "Unfortunately, Context Service has stopped working."
I read on a thread you can Rename or replace the ContextService.apk file located under /system/priv-app to fix it, So where do I get a non corrupt copy? And how do I access the /system/priv-app area? Connect to a pc?
Also, wouldnt replacing with a non corrupt version be more important that renaming it and no longer working? Do we not need it?
update
So I downloaded Root Explorer app to find that "/system/priv-app area" and nothing. I can not find any "system" file or Priv-app area.
Thanks
You need to root your device. For file explorer try ES File Explorer for root browsing.
already rooted
Riyal said:
You need to root your device. For file explorer try ES File Explorer for root browsing.
Click to expand...
Click to collapse
My Device IS rooted already.
One of the main drawbacks of 5.1.1 update on Yureka was that the stock dialer had been replaced by Truecaller dialer. I, for one, liked the original dialer a lot. It had dynamic speed dial tiles which changed according to how much you called, which is probably one of the best features. Also, there's privacy issues associated with Truecaller dialer, if you're into that sort of thing.
To change the dialer, we'll simply replace the phone UI components with blisspop components. Blisspop has stock Android dialer.
Also, this is my first guide, so if mods think this is not in appropriate section, please move it to proper section.
Prerequisites:
1. You should have Yureka [duh]. I don't know if this works on Yureka+. Maybe someone can test & tell me so that I can update this guide.
2. You should have write access to the root partition of your phone.
What is root partition you ask? Yureka has Internal memory [Sdcard0], External memory card [Sdcard1] & a third partition, root partition[/].
You can access this partition using any reputed file manager such as ES file Explorer, Solid Explorer, Root Explorer etc.
However ES, Solid etc. had problem writing files in my phone. I therefore went with Root Explorer which works flawlessly.
From hereon, I'll consider you are using Root Explorer. However using any other file manger will be similar.
The only caveat in using Root Explorer is that writing permission requires root access.
Steps:
1. Open Root Explorer. Tap "Mount R/W". Grant it the superuser permission when it asks. This puts the Root explorer in Write mode for root partition & we can now write or over-write files which we want.
2. Download the zip file from here & extract it somewhere on you phone.
3. In root partition [the one with symbol "/"], go to system-->app and replace or overwrite the InCallUINext folder with the folder which you have downloaded from the zip file. Make sure you have backed up the original folder which was previously present i.e copy it somewhere on phone memory just in case.
4. Then go to system-->priv-app and replace or overwrite the DialerNext folder with the folder from the zip. Again make sure you've backed it up.
5. That's it. Reboot the phone & you have the stock dialer.
Credits to @Sundara Prakash & also to @Vams for prodding me in the right direction.
Hit Thanks if you think this helped!
Due to a new policy, after rooting the Galaxy S phones, you can't use Samsung Health and some other apps anymore.
Here is an easy way to "bypass" this policy.
1. You need a file explorer with root acces to / (Root Explorer, ES File Explorer etc)
2. Open "/system"
3. Open "build.prop"
4. Find line "ro.config.tima=1"
5. Change the value from 1 to 0
6. Reboot your phone
7. Done :fingers-crossed:
the system does not allow me to save the file after i change the value? please help.
I just restored my S7 Edge to as stock as possible using Odin and software from Sammobile. Now I can't use my Gear properly because of 'security reasons'. (Gear app works, but not SHealth)
I was planning on using SuperStock to bypass the tripped Knox, but afaik it's not working anymore. Is there another method? I don't really need SPay or stuff like that. Im willing to root or installing TWRP again if I have to, but not a custom ROM.
Follow the steps below to remove the S-Health block.
Download a root file explorer (such as Root Explorer, Root Browser or ES File Explorer).
Open the root file explorer and go to the /system folder.
Open the file named build.prop in text editor
In the build.prop file look for ro.config.tima=1
Change this line to ro.config.tima=0, simply changing the 1 to a 0
Reboor phone
Run the S-Health app
From this thread; https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Can confirm it works on Oreo following these steps.
Great White said:
Follow the steps below to remove the S-Health block.
Download a root file explorer (such as Root Explorer, Root Browser or ES File Explorer).
Open the root file explorer and go to the /system folder.
Open the file named build.prop in text editor
In the build.prop file look for ro.config.tima=1
Change this line to ro.config.tima=0, simply changing the 1 to a 0
Reboor phone
Run the S-Health app
From this thread; https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
Can confirm it works on Oreo following these steps.
Click to expand...
Click to collapse
my phone wasnt rooted and I forgot about the encryption stuff so now I had to wipe everything, but the fix you linked to worked perfectly. Thanks.