Related
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,
My brother's desperate to get a bluetooth keyboard working with his HTC Hero (UK). Currently runs the stock HTC 2.1-update1.
It's easy enough to pair them (we've tried two) but they remain paired but unconnected. With my Galaxy S (stock 2.2.1) they work fine. I gather this is because the Hero doesn't support the SPP or HID profiles.
We've also tried most of the apps we can think of: Keypro (sits on 'connecting'), Blueinput (force-closes when you click to select they keyboard), the JP one (sits on 'connecting'). Looking at the forum for keypro it looks like they're aware of this issue and haven't yet been able to correct it.
I've heard rumours that people running custom ROMs (eg based on Cyanogenmod) have been able to get keyboards working.
So - has anyone managed to get a bluetooth keyboard working with one of these devices, and if so how? Would prefer a solution that keeps Sense installed but he says he'll let me go to vanilla android.
Thanks in advance.
For the benefit of future users (and because the forum seems to be littered with questions like this!) we managed to get it working by installing FroydVillain 1.7.2.
Main problem was the lack of a flash_image binary to install the nandroid recovery image, but we copied over one we downloaded and it worked without issue.
Keyboard was recognised immediately and works fine as an HID device.
That's interesting! But could you detail, what were the steps of this successful installing? I also have an old bt keyboard, which I'm unable to use with the hero... Thank's if you can explain any more...
Mostly we used the instructions from http:##www|villainrom.co.uk/vBwiki/index.php/Installing_Custom_ROMs , though with a change for flashing the rom as the binary wasn't available on his phone.
More specifically - use the Froydvillain download mirrors at http:##www|villainrom.co.uk/forum/showthread.php?3698 and the wiki page above, and download:
Froydvillain 1.7.0
Froydvillain 1.7.1 upgrade
Froydvillain 1.7.2 upgrade
Universal Androot
AmonRA Recovery image
Stick everything onto the SD card - either using a USB cable and your phone, or we just used a USB card reader.
Install Universal Androot. We used HTC sync and just double-clicked on the .apk but you could also use a file manager (the wiki recommends Astro).
Install Android Terminal Emulator from the market.
Root the phone using Androot (he was running the latest 2.1 so we used the 2.0-2.2 root button).
The next bit is where we differed from the wiki instructions. They tell you to type:
Code:
su
flash_image recovery /sdcard/[I]<name of recovery image file>[/I]
reboot recovery
We found that there was no flash_image binary on my brother's phone (the error read 'flash_image: not found' so downloaded one - there's a copy at http:##cyanogen-files.carneeki.net/flash_image.zip ; I can't remember exactly where we got the one we used.
The instructions we found with the binary suggested something complicated involving remounting the system partition (it's normally read-only so you can't copy the binary there). Equally, you can't run it directly from the sd card without remounting as it's set not to allow executables. We just ran it from the data partition:
Copy the flash_image file to the sd card and use:
Code:
su
cp /sdcard/flash_image /data/flash_image
chmod 700 /data/flash_image
/data/flash_image recovery /sdcard/[i]<name of recovery image file>[/i]
sync
Then just power off the phone and turn it back on with the 'Home' button pressed. You should find yourself in recovery mode using your new recovery image.
We then used Backup/Restore > Nand backup to backup the current ROM to the SD card. Then from the Wipe menu we ran through each option in turn to ensure a fully fresh setup (I gather this isn't essential, but is advised). Lastly we used Flash zip and sequentially flashed 1.7.0, 1.7.1, then 1.7.2.
Then we rebooted, and waited... and waited... and waited... The VillainROM logo with the scary red-eyed android pulsated for about 30 minutes before I gave up and removed the battery. I took out the SD card and turned the phone back on; this time it was only a few minutes before we found ourselves with a fully functional (and factory-fresh) phone.
We put the sd card back in and set up the phone as normal; then turned on bluetooth and paired the phone with the keyboard (with ours it was a matter of typing a PIN on the keyboard and pressing enter, and duplicating the number on the phone) - it was instantly recognised as an HID device and worked perfectly!
Hope that's of some use - as I mentioned before it's essentially the same as the standard instructions except for the step involving the missing flash_image binary.
[edit: sorry, I'm not allowed to post links it seems! You'll have to cut and paste, and replace the '##' with '//', and the '|' with '.']
Thank you, you were very kind! But it seems basically only a normal fv installation on a rooted phone... Only I become a bit confused with all the /data/system operations... I can try installing fv 1.72, but at the moment I don't want to give back my floyo 1.20, which is more responsive (in my phone), but gives no sinal of accepting to connect the paired bt...
Yes - it was just a new ROM install which did the job - only the lack of flash_image and the lengthy bootup before we removed the sd card confused us so hopefully it's useful to someone trying the same.
I've not heard of Floyo - but the reason I decided to try FroydVillain was that it was CyanogenMod-based rather than HTC sense based as I heard that HTC don't include bluetooth HID support in their ROMs.
The CyanogenMod changelog http:##wiki.cyanogenmod.com/index.php?title=Changelog suggests that HID support has been included since 6.0.0 so I'd expect anything based on CyanogenMod since that should be fine. I chose FroydVillain simply because my brother's not very techy and I wanted a fairly mainstream ROM for him...
Not so simple...! Out of curiosity, I went to install froyd villain, but as I imagined the result was the same! "Paired but not connected"... It seems that when you rooted the hero, something remained in /system, no idea what was it! If a developer could read this, perhaps he could understand what happened... Floyo is simply another rom based on cm... the difference is all in the rooting process, seemingly...
Not for me
Hi Guys,
as I have been running Froyd Villain 1.7.2 for a rather long time now I thought I might give it a try. As there is an Apple Bluetooth keyboard dusting around here I had quite high hopes.
The pairing process worked well and it shows an Icon with the BT Symbol encased in Black and two arrows. In the BT settings it tells me that I am connected to a BT device, never the less, no matter what input field I choose, I cannot type on the BT keyboard. There is no other Input method I could choose from either so it's still not working for me.
Damn.
What keyboard where you using?
I'm running Dexter's mod. When the A7 goes to sleep, it loses its wifi connection at wake up.
I have to go into "Wireless and network settings" to turn wireless on, and then the A7 gets stuck in the "scanning..." mode, even though I have a real good, strong wifi signal.
I toggle the on/off wifi several times (about 2-3 minutes of playing), and eventually the A7 sees all the available signals and connects immediately to my home network...
I really want to stop trying tablets, but the A7 is really testing my resolve.
This has happened to most everyone that flashes Dexter's mod. It has to do with wpa_supplicant though honestly I don't know the root of it.
Another forum member replaced the file with the original that shipped on the device after he had market enabled and the problem stopped happening and he retained market access.
I'm running 1.0b and haven't had the issue since I flashed it.
Have you installed Dexter's ad-hoc hack? that causes this problem to aggravate. If you have the wlan and wpa-supplicant files from 1.0c (System/bin) you will be fine..
I am running Dexter's 1.0c and upon re-awakening, it connects right back up with no problems. The only issue I have is not being able to keep the wi-fi connected when the unit goes to sleep. I don't want to keep the screen on 100% of the time as this really sucks the battery down fast. I have tried 5-6 apps that are supposed to fix this, but so far no luck. Anyone else been able to keep the wi-fi connected when the tablet goes off?
I had the same issue until I changed to this supplicant. Now no problems.
View attachment Supplicant.zip
Thanks, Craig118. Did you have to install the same as Dexter's mod and wipe all data, or does it install without deleting files?
Just copy and paste that wpa_supplicant into your sys/bin folder. That was all I needed to fix mine. Two weeks now with no sleep /wake issues.
Craig 118:
Thanks for the help, am just getting around to trying this. I have copied the Supplicant.zip file onto a USB stick and have tried to copy to the system/bin folder but keep getting an error message that file cannot be copied. My /sys folder does not have a bin subfolder. Any suggestions? I have copied files from this same USB previously.
Have now copied onto my sd card, and still get the message cannot copy file. Anyone have any suggestions?
Are you using root explorer? You have to change it to read/write in order to overwrite the file.
I am using the standard OI file manager on the machine.......
That app. will not work. You need superuser permissions to change sys files. Download/Install Root explorer and use it to copy the file your sys/bin folder (must click on write).
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
SweetBearCub said:
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
Click to expand...
Click to collapse
OK can only answer some of these. I heard Launcher Pro can take a little while to read icons from the sd card. You may want to download and try Zeam launcher.
The Plants v Zombies may be a result of overclocking/undervolting. Try it again with no undervolting and your speed set to 1Ghz max and 200 Mhz min.
Not sure why you are mounting the sd card in clockwork. Sounds like either your cable is flaky or you need to reinstall the Samsung drivers to connect your USB. Also try different USB ports and turn USB debugging on. I had to reinstall the drivers for each port on my laptop as it would only recognize my phone in one of them originally.
No, journaling does not carry through other ROM flashes. If you flash a no-journaling ROM, you will have no journal unless you turn it back on. Some can be turned on simply be making a nand backup then immediately restoring it. Others work fine with the journal on flash. And some are more special and need a specific script like Bonsai.
Hope some of this helps.
SweetBearCub said:
Hi.
I'm running SyndicateROM Frozen 1.1.1, and I've observed several bugs. I need to know if the bugs are the fault of the ROM (and thus something I should take up with the ACS developers) or if they're my fault due to something I'm doing wrong.
1) I use folders on my LauncherPro* homescreens to organize apps. For this example, I'll use my Games folder. In it, all the games except 1 are installed onto my microSD card. After I drag the icons to the folder the first time, they are fine. However, after a reboot, the icons of the apps installed to my microSD card that are in folders change to the generic Android green/white icon. The apps still load properly, and the icons appear fine in the App drawer.
*LauncherPro is included as the only homescreen in this ROM.
2) I'm having an odd issue with Plants vs. Zombies. It loads to the main screen, and I can manage the player names, but after I click to start the adventure, it locks up with the Adventure button depressed. The main screen music also dies. No FC/wait dialog appears. I have to press the Home button to get out of it. PvZ is unplayable in this condition. Rebooting does not help, nor does formatting /cache or Dalvik-cache in custom recovery.
3) JuiceDefender Ultimate tells me in the log that it cannot toggle 2G/3G data, and that this is likely to be a kernel issue. As far as I know, this reduces the effectiveness of JD.
4) In ClockwodMod Recovery 3.0.0.6, I cannot mount my microSD card for the PC to read/write it. I get "E:Unable to open ums lunfile (no such file or directory)". I've seen posts that indicate this is a bug that was corrected in later versions, but I don't know if the custom ROM I am running is compatible with later versions,or where to find later versions. EDIT: I found CWM 3.0.2.5, and flashed it. It still reports the same error when attempting mount my microSD card for my PC to work with.
5) When I connect the phone's cable to my PC and get the the "Charging/Mass Storage/Tethered" popup and click Mass Storage, and then click "Turn On" at the next screen, it appears to work fine, except that my PC shows no new removable media drives. Sometimes, even though I touched the "Turn On" button, nothing happens. The button does not turn into a spinning wait indicator, nothing.
6) I found a post (that I've since lost track of) that purported to provide instructions to see if journaling was enabled. (I'm already formatted as EXT4). The instructions errored out, apparently because I have the wrong version of tune2fs. I'm not sure how to copy the correct version over, so I flashed the "Journaling On" zip shortly after I re-flashed this ROM. Does EXT4 and journaling stick between ROM re-flashes?
Click to expand...
Click to collapse
1) you can get a different launcher from the market. I've never had any luck with pushing apps to sd.
2) that's a issue with the game. Try changing your max and min cpu.clocks. If you uved you may be to low.
3)jd is a pos and you don't need it. I go on average of 12-16hrs a day with 3+ hours of screen on. And a synce interval of every hour
4) no versions of cwm on the epic has allowed you to mount your sd to pc for the epic. Cwm was ported to the epic and not created by koush him self so some things are broken.
5) try a different cable and usb ports. This is a known problem even while on a stock rom
6) yes it sticks unless the rom your flashing changes it.
Sent from my SPH-D700 using Tapatalk
Thanks Mystery for validating my advice...LOL. Would like to see you around here more.
cwm 3.1.0.1 allows mounting the sd card to pc in recovery..
chris41g said:
cwm 3.1.0.1 allows mounting the sd card to pc in recovery..
Click to expand...
Click to collapse
I forgot they fixed that. But anything before that don't allow this
Sent from my SPH-D700 using Tapatalk
kennyglass123 said:
Thanks Mystery for validating my advice...LOL. Would like to see you around here more.
Click to expand...
Click to collapse
I'm knee deep on working on sfr1.2
Sent from my SPH-D700 using Tapatalk
Good evening everyone.
To start with, yes I've read all the similar topics and none of them helped me
To my problem now. My phone has been flashed with a custom ROM for 1-2 months now (I don't remember exactly) and this morning I woke up to find my phone turned off. While trying to turn it on, no matter how much time has passed, it's stuck on the splash screen refusing to load the home screen
Is there any suggestion that does not involve me losing all my data because I have no backup of them?
Waiting for any suggestions.
See if you can connect with usb, and adb can communicate with device.
If yes, you can save the /data/data folder(in which are all configurations) + /data/app folder(in which are all apps except these on sdcard if any).
You can also run adb logcat from command prompt and see if you can find what app causes the error and the bootloop, and if maybe you can uninstall/reinstall this app, or delete the folder of that app on /data/data folder, to hopefully solve the error.
Try to install a program like QtADB, droid explorer or Android manager to avoid use command line and simplify some of above operations as copy/delete folders or install/uninstall apps.
If you need more help, PM me to speak in greek(it' s better)
I've just installed QtADB and connected the phone while being inside ClockwordMod v4.0.0.5.
The truth is that from here I don't get almost any useful information (don't know why). One positive aspect is that I can copy data from/to the phone.
While stuck in the splash screen I can't connect through adb though.
You mean not at all? Usually when appears IDEOS screen you can connect via adb, after some time and when the error start maybe the device freezes and then adb probably disconects, but until then you can take some useful logcat info for the error.
You can also have some more functions with QtADB on recovery mode if you mount the partitions first.
Maybe and the app manager work then(I haven't tested though).
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
gkaran said:
Managed to get logcat information while turning on the phone. I'm attaching the log file with the error lines.
Trying to read them right now to find a solution. Any help appreciated.
Click to expand...
Click to collapse
By reading your log i think the problem is permissions. Try to fix permissions with recovery tool.