Been trying for a couple of hours now, and have succeeded in creating an FTP server for my phone using this app, I got it set up the exact same way I did on my old phone and previous tablets and everything works properly, I'm able to fire up Cyberduck and access all the files the device, but for some reason I just can't transfer files. It just seems to get stuck on "Making directory [Directory Name]" and won't progress. Just wondering if anyone else has been able to get this to work, or if there are others facing the same issue as me?
Theta1996 said:
Been trying for a couple of hours now, and have succeeded in creating an FTP server for my phone using this app, I got it set up the exact same way I did on my old phone and previous tablets and everything works properly, I'm able to fire up Cyberduck and access all the files the device, but for some reason I just can't transfer files. It just seems to get stuck on "Making directory [Directory Name]" and won't progress. Just wondering if anyone else has been able to get this to work, or if there are others facing the same issue as me?
Click to expand...
Click to collapse
In past i have used Es File Explorer FTP between J5 and Galaxy S Advance. I have used J5 make folders/move/copy on S Advance, it worked fine.
Related
I want to fix this myself -- I'm a Linux-savvy Comp Sci grad student -- but I'm having trouble figuring out this phone. Wireless connects fine at home (WPA) but won't connect at school (open network.) In the process of trying to figure this out for myself, I've discovered I'm pretty clueless about this phone.
Phone is unlocked and rooted, I'm in "adb shell" as root, and I can't find any log files. In the gui I can find my university wireless and try to connect. It starts connecting, then says disconnected, and I get no indication of what the problem was.
Where are the log files? Or are there any, even in a ramdisk? I couldn't find anything resembling a syslogd to start if I really want the device to start filling up valuable memory with log file spam, briefly so I can identify the problem. Or is there a way to attempt to connect to wifi via command line, in a way that will spit out error messages instead of failing silently?
I know you guys are super helpful and you can probably guide me through a solution, but I really want to figure this out for myself. Unless it's a known problem with a quick-to-explain solution.
Thanks in advance for all your help.
Edit: ooh ooh I forgot to ask . . . before I start digging into making a mountable 1 or 2 GB loopback-mountable e2fs filesystem on my SD card and putting proper Linux tools on there (full-sized system tools, none of this busybox crap -- plus system libraries and GCC) . . . has anyone already started working on that? (Yes I'm going to be one of these insane folks who wants to compile software on his cell phone. Specifically, SWI-Prolog would be handy and practical for me right now.)
Hello, I'm having an issue, I'm rooted with the nand unlock method. I was on flipz .1d but have now moved to .2. I've had this issue a number of times now specificly the "unable to turn on" which seems to be caused by the owner of the /data/misc/wifi/wpa_supplicant.conf file changing to root. but I am not sure what causes the unable to scan for networks to happen.
Some of the things I have done that seem to be a part of the cause: I ran flipz vanilla lock screen fix and I team douche menu unlock, both seem to make changes to /system/framework/
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Was having the same problem (came across your post from a Google search).
I got a hint from code.google.com (can't post the link). I renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak (rather than delete it), rebooted and all is well.
Seems you can just delete the file, and it'll be respawned on a reboot.
I am having this problem, but on a vibrant that has not been rooted yet.
I cant seem to find the wpa_supplicant.conf, I have tried browsing for it using the built in file manager and using ASTRO, but the data directory is always empty.
Is there a way to fix this without rooting the phone?
if your phone has not been rooted then that means your phone is f**ked up and might need to be exchanged. but this is the evo forum not vibrant. the only way to mess with system files is to be rooted
Appreciate info*, worked in a heartbeat, saved from reloading everything from scratch, which was my way out last time. Witstech A81E Froyo 2.2
*renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak
Good eye there mate!!!!
InstantKarma said:
Was having the same problem (came across your post from a Google search).
I got a hint from code.google.com (can't post the link). I renamed the /data/misc/wifi/wpa_supplicant.conf to /data/misc/wifi/wpa_supplicant.bak (rather than delete it), rebooted and all is well.
Seems you can just delete the file, and it'll be respawned on a reboot.
Click to expand...
Click to collapse
I was experiencing the same issue and read this and it works, good looking out.
same issue on mytouch 4g
i used root explorer renamed tried no good the file stays renamed but the conf. appears under it after i try to enable wifi again help plz?
Who But BilL$ said:
i used root explorer renamed tried no good the file stays renamed but the conf. appears under it after i try to enable wifi again help plz?
Click to expand...
Click to collapse
It just recreates the file when your phone gets rebooted. My Thunderbolt is having the EXACT same issue. Ive tried renaming this and deleting as well and still no luck. Im now kicking over any rocks that I can find to get my wifi working.
I have exactly the same problem.
With Root Explorer deleted the file 'wpa_supplicant.conf' but no changes.
WiFi starts up and closes down again with the famous line: "unable to scan for networks"
anyone?
shoppy said:
I have exactly the same problem.
With Root Explorer deleted the file 'wpa_supplicant.conf' but no changes.
WiFi starts up and closes down again with the famous line: "unable to scan for networks"
anyone?
Click to expand...
Click to collapse
I actually ended up having to get a whole new phone. My insurance company couldnt fix it.
joeavery2 said:
2. I've had this issue a number of times now specificly the "unable to turn on" ......... but I am not sure what causes the unable to scan for networks to happen.
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Click to expand...
Click to collapse
I had the same problem. I installed the software from the sony erikcon website to my computer, and then followed the process for updating the phone software. That did not work, since I had the latest software already. So then, I tried to REPAIR my phone software, and after that was done, my phone was functional again, and the wifi works without any problems.
Requirements:
* A PC connected to the Internet (preferably broadband)
* USB phone-to-PC connection. Please see the accessories compatibility list for your phone.
1. Run the software on the computer after it is installed.
2. Follow the procedure for UPDATE or REPAIR (if you already have the latest version).
SOLVED WIYH THIS D12r a33_8723-8703_v11_0312 20141211.IMG
joeavery2 said:
Hello, I'm having an issue, I'm rooted with the nand unlock method. I was on flipz .1d but have now moved to .2. I've had this issue a number of times now specificly the "unable to turn on" which seems to be caused by the owner of the /data/misc/wifi/wpa_supplicant.conf file changing to root. but I am not sure what causes the unable to scan for networks to happen.
Some of the things I have done that seem to be a part of the cause: I ran flipz vanilla lock screen fix and I team douche menu unlock, both seem to make changes to /system/framework/
anyone that might know where to look to fix the scan issue? I've searched the forum and have seen a few people have the problem but no solutions yet.
Click to expand...
Click to collapse
I SOLVED WITH FLASH THIS: D12r a33_8723-8703_v11_0312 20141211.IMG
People still use this phone?
Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston
Hmm. I have a mytouch 4G and the A500 connects to the hotspot easily. No mods, rooting etc. needing.
Is this in relation to phones that are using less than carrier proposed methods for enabling hotspots?
Hi Neo,
According to what I have had known so far, it seems that google blocks this function,
so someone modified the wap_supplicant to enable the hotspot functionality.
franva said:
Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston
Click to expand...
Click to collapse
Solution 2 depends on your specific phone and its implementation. My Droid for instance doesn't support infrastructure hotspot (outbound), so I had to use the "magic wpa_supplicant" approach. Other phones may support infrastructure mode, either directly or through a 3rd-party wifi tether app.
In terms of solution 1 - if you get the wpa_supplicant (apparently a new version has been posted for those of us w/ 3.1 update) you also need to reset the permissions on the file to match that on the original file (which I know you backed up, right? ); easiest way would be through Root Explorer and set Read: (Owner/Group/Others), Write (Owner only) and Execute (Owner/Group). I'm too lazy to remember what the Terminal Emulator chmod command would be
As a reminder to all who do choose to replace wpa_supplicant, keep a copy of the original file, you never know when Acer's going to require a specific original file for any future updates (wpa_supp wasn't needed for the 3.0.1 update but was for 3.1)
Yes I would say do not delete or move the old file just rename by adding old to end of file name. Its how I done it renamed did the update changed back. And now all is well again.I used the same replacement file from before. No need for a new. Version
Hi Vereyn,
Thanks a lot.
Could you please provide the link to download?
Frankly, I have tried all wpa_supplicant in this forume.
None of them works for me.
My version is Android 3.0.1
Acer ICONIA A5011, rather than A500.
Cheers
franva said:
Hi guys,
Since the mobile hot spot is an adhoc networks, so tablet cannot recognise it
directly.
So I found a instruction which is called can solve this problem.
We simply replace the original wpa_supplicant with the new one.
And put it in /System/Bin/.
I did the root and copy, but it still cannot find the adhoc hotspot for me.
So anyone have any idea?
Solution 1: solving it with the magic "wpa_supplicant"
Solution 2: changing the configuration of hotspot in my mobile to a normal wifi.
I'm waiting for anyone who can solve this.
Cheers
Winston
Click to expand...
Click to collapse
Soo... Which rock have you been hiding under exactly? This is pretty old news, and there are already a few threads detailing exactly what you need to do... Hell, there's one on the first page of this forum section!
Dear Floating,
Could you please send the link to me? or at least give me the title of that article which
you are talking about?
Because it disappeared again now >_<;
Again,
yes there are many ad hoc articles, but none of them work for me....
franva said:
Again,
yes there are many ad hoc articles, but none of them work for me....
Click to expand...
Click to collapse
The links are in the forum, just scroll down a bit.
As for the articles not working... If they're not working for you, maybe you're doing something wrong or missing one of the steps?
I must be doing something stupid, but no matter what combination of options I user in Developer Options and USB transfer type, AFT does not recognize the device and asked to restart or reattach. What am I missing? Thanks in advance. p.s. I made the switch from an iPhone and have forgotten most of the Android stuff I knew several years ago.
jsamuels said:
I must be doing something stupid, but no matter what combination of options I user in Developer Options and USB transfer type, AFT does not recognize the device and asked to restart or reattach. What am I missing? Thanks in advance. p.s. I made the switch from an iPhone and have forgotten most of the Android stuff I knew several years ago.
Click to expand...
Click to collapse
It unfortunately does not work.
Download Smart Switch from here: http://www.samsung.com/us/smart-switch/assets/downloads/SmartSwitch_Mac_setup.dmg
Once it has been downloaded, it will tell you to unlock your phone and connect it.
Once that has been done, click the down arrow beside "Samsung Galaxy S7 Edge"; You will see a folder beside Internal Memory, so click on that folder, and from here, it will look similar to Android File Transfer.
You should be able to drag and drop files into the folders, create new folders, move sh*t around, etc.
Thanks. I'll give it a shot. When I first used the other day I didn't see the file transfer capability, only the basic backup and restore functions.
jsamuels said:
Thanks. I'll give it a shot. When I first used the other day I didn't see the file transfer capability, only the basic backup and restore functions.
Click to expand...
Click to collapse
Yeah unfortunately this is the only way I found to do it on a Mac.
Mac and Android don't really go well together
Worked perfectly. Too bad AFT doesn't work. I assume Google will update to support this phone. Again, thanks.
But Smart Switch is painfully slow in file transfer. There has got to be a way to get AFT working again. Mine just stopped, and when connecting the device, USB debugging on or off, the phone does not ask me if I want to allow the file transfer. I think mine stopped working after installing SideSync, and I never had Kies installed so that solution does not apply. This should not be rocket science!
this used to work just fine for me now i get on my phone when i start/restart widget can't load and for some reason i feel is connected to me not being able to transfer files from computer to the phone or the other way around .. Please help me on fixing this
Thank you! <3
ps i have another phone where file transfer works just fine
i guess its worth mentioning that this started after a software update, and right after that they released another one hopping they will fix it but NO :crying:
I was in your situation. I fixed that by install dex on my pc. I don't know if it will help but I think it's worth a try.
FrozenLemon said:
I was in your situation. I fixed that by install dex on my pc. I don't know if it will help but I think it's worth a try.
Click to expand...
Click to collapse
I forgot to mention that i already tried that and does not work .. i also looked at the supported devices and galaxy s10+ is not supported even tho for some people does work