Related
When I turn on wifi it say 'Unable to scan networks' and automatic turn off.
I'm on FolioMod1.4.
Jon2555 said:
When I turn on wifi it say 'Unable to scan networks' and automatic turn off.
I'm on FolioMod1.4.
Click to expand...
Click to collapse
This is a common Froyo problem - a reboot usually solves it
I try rebooting, but that don't work. I try reflashing, but when I turn it on my wifi work only for 5 min.
Can anyone help me, please
What version of foliomod you are using?
Did you try to connect to other networks?
Ive also experiencing such problems, but turning off wifi, restart and
turning on after restart usually solved this.
You may try this, but I'm not sure it will solve your problem.
Install Clockworkmod
(http://forum.xda-developers.com/showthread.php?t=923722)
Go to the Clockworkmod recovery (same way as toshiba).
In clockwork do:
Factory reset
Cache cleaning
Dalvik cache cleaning
Install clean stock rom, factory reset, install foliomod, factory reset
setup folio and check the wifi.
Regards,
headblow
1.I use FolioMod1.4 and also I try with FolioNotion1.2, but no luck.
2.When I turn on wifi it scan. After 5 sec. it say"Unable to scan network" and automaticlly turn off(you have this in first post).
3.Thank you very very much for your help, but Dexter's server is down and I can't download stock rom, FolioMod1.4. or older version. Secondly, Clockwork Mod recavery can't install stock rom.
4.I try to delete and rename to *.bak /data/misc/wifi/wpa_supplicant.conf(see this on other forum) and reboot. After reboot system make same file.
5.But thank's for your help. If you have another idea can you post it here.
Sent from my GT-I5700 using Tapatalk
Hello,
You've wrote that: Clockwork can't install stock rom,
but what do you mean?
Did you install Clockwork but you dosen't have
stockrom or you were just unable to install Clockwork recovery?
Regarding Dexter webpage, yes it is off, but if you will search
a little bit, you will find out that there is a mirror that
host most of files from dexter webpage.
http://mirror.ddevnet.net/tegra/folio100/folio100
There you have:
Foliostock.zip
FolioModv14.zip
Regards,
headblow
1. That you can't install stock rom via Clock recavery I see here http://forum.xda-developers.com/showthread.php?t=923722&page=3(post 27)
2.Thank you for page
Jon2555 said:
1. That you can't install stock rom via Clock recavery I see here http://forum.xda-developers.com/showthread.php?t=923722&page=3(post 27)
2.Thank you for page
Click to expand...
Click to collapse
My only tip is that you need to clean all cache and
user data, especially if you've been using other roms, which
probably left something there.
IMO the best way to do this is to use Clockwork.
If you already have clockwork in update.zip file (link to thread is in
my previous post), put it to your SD card, run Toshiba recovery
as you would with Foliomod, and choose to recovery from SD card.
Now you should have Clockwork, but in order to use it, you need
to rebot and go to Toshiba recovery once again, select to
update from file (again like in Foliomod), but then you
should see Clockwork instead of selected update.zip install.
In Clockwork you use volume up/down and home screen button on
the right as enter, or back screen button on the right as go back.
In Clockwork do the following as Ive wrote before:
Factory reset
Cache cleaning
Dalvik cache cleaning
Later you can install stock rom and folimod anyway you like it.
Regards,
headblow
1.If I understand, when I install Clocwork Mod I will have 2 recaveries?
2.When I flash stock rom, I can't install customs roms.
Yes but you can go back anytime to Toshiba recovery only.
Regards,
headblow
OK, I install ClockMod recavery and do factory reset. After that I clean cache and Dalvik cache but problem is still here. I try to flash FolioStock with original and ClockMod recavery. I get installation aborted without reason.
I have the same problem, wifi - error.
I tried all the stock firmware - no result, I did factory reset before and after update.
I've tried everything.
My Toshiba has 8 Gb memory.
Please HELP - who have another stock rom? Stock Rom by Dexter Im installed - no result.
Or tell me what should I do?
Thanks to all very much.
y0kiua said:
I have the same problem, wifi - error.
I tried all the stock firmware - no result, I did factory reset before and after update.
I've tried everything.
My Toshiba has 8 Gb memory.
Please HELP - who have another stock rom? Stock Rom by Dexter Im installed - no result.
Or tell me what should I do?
Thanks to all very much.
Click to expand...
Click to collapse
i have this problem too
I found the description and the settings and files that are responsible for ar6003
in my opinion, this chip is in folio 100
but I'm not a programmer can someone make a patch that will make WiFi work
i"m said:
i have this problem too
I found the description and the settings and files that are responsible for ar6003
in my opinion, this chip is in folio 100
but I'm not a programmer can someone make a patch that will make WiFi work
Click to expand...
Click to collapse
Thanks for the pdf. Have been struggeling a while to compile the drivers from scratch. Atm I have imported them into the kernel to compile as a module. But it somehow does not insmod correctly (well, it does insmod, but it seems that it doesn't load the firmware files). Perhaps this pdf has some answers for me.
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the two files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?) Now DON'T reboot before you made the next step, cause you have to start from zero if you reboot before making the next step
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
9Lukas5 said:
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?)
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
Click to expand...
Click to collapse
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
where can i download FreeXperiaRecovery?? I will tray this!
avez197 said:
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
Click to expand...
Click to collapse
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
9Lukas5 said:
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
Click to expand...
Click to collapse
Thanks. Will give feedback after trying
barsom said:
where can i download FreeXperiaRecovery?? I will tray this!
Click to expand...
Click to collapse
If you download Flashtool 0.2.9.1 there is FreeXperiaRecovery included. Look into the list, there wrote to click on the xrecovery button for installing FreeXperiaRecovery. The files are included in flashtool.
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
nadiros said:
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
Click to expand...
Click to collapse
Yes i ment this.............maybe you're right, cause it will be formatted by installing the rom, too.........hm..will correct op.
Edit: I made it that way always, and had never problems, so i haven't thought about it.
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Hello 9lukas5,
I thought I might mention that I've finally managed to fix my wlod but by installing setcpu on the earlier version of J's rom I was using, and setting it up to on boot run the processor at the usual 998 speed. Then I flashed the update.zip (from j's latest release, just formats the system) which didn't remove setcpu so the cpu was running at 998, this stopped all the random reboots and wlods.
I tried for a couple of weeks to use an update, trying so many different ways of stopping my phone being unusable as soon as I flashed the updates due to wlods.
Just though I'd mention it in this thread as it was on topic. Not everyones fix I'm sure, but helped me.
Cheers for all your support and help with installing the roms.
Sent from my X10 using XDA App
BULL3TPR00F said:
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Click to expand...
Click to collapse
K - Right on, ty. Just so it's out there and people know ;-)
I believe the majority of WLODs are to due with the CPU constantly running at full speed.
I was getting a lot of WLODs with FreeXperia Kernel-10 on my ROM until I manually set the CPU governor to on demand.
Just go into Cyanogen Settings and change the CPU governor to on demand (it probably already is set to on demand, so change it to something else and then change it back to on demand).
After that my CPU was running at more than the max frequency and I haven't had many WLOD's (think I've had one since, a major improvement).
Erm not to be funny but their are no WLOD due to the changes J has made in his new version, regardless of how I flash it, no WLOD anymore... It has nothing to do with the way you flash the rom that caused this...
Hi guys,
I have follow ALL step from the step 1.
The phone boot, ask for the PIN code, then the page to change the language and then WLOD...
Do you think it come from the CPU frequency ?
I can't found the BTS kernel for this ROM.
Thank you for your help.
hmm....I shared it cause I hadn't any problems of WLODs yet on Cm7 since J019
Hello all,
the main trouble I had causing wlod, was definitely the clock speed. When I flashed the rom (about twenty times, different ways) I would not get enough time to configure any cpu settings, or any other settings, before my phone crashed and it would just start to bootloop with wlod.
I had to install setcpu on an older version of j's rom which didn't have overclock. Checked the box to apply settings on boot. So that when I flashed j's latest rom which is just the update of the system, all my apps were there (didn't bother wiping cache, data, etc) setcpu was still running on boot to keep the cpu set to 998.
Haven't had a single problem since, apart from low battery phone crash.
I tried so many different ways to flash before trying this, hope this helps someone.
Sent from my X10 using XDA App
Any body make a stock kernel image to flash to check sleep state vrs miniloader issue?????????
Worked a treat!! Thank you!
Hi guys,
I'm having issues with my SGS2 and I would appreciate very much if you guys could lend me a hand.
I had VillainRom 2.4.2, Ninphetamine 2.0.5 and modem KG6.
I tried to install this Dark theme but something went terribly wrong and I had processes crashing, couldn't see any links to the phone dialer, messaging, etc.
I'm trying to wipe the phone back to full stock but I can't for some reason.
I tried booting into recovery mode, wiping cache and all information but when the phone boots I'm back to a black skin with several crashing warnings.
I tried to reflash KG6 with odin and selecting repartitioning but when I boot again I'm back to the same black skin missing functions and receiving some crashing alerts.
I tried to factory default through Settings -> Security -> Factory Default to no avail.
All the guides I was able to find on the net to put the phone 100% back to stock failed as I always boot to a non-working dark theme.
Can someone please provide me some help?
Would appreciate very much any pointers.
EDIT: After I boot into this dark theme, I'm getting messages like process android.process.acore has stopped unexpectedly for example.
Factory reset does not mean that it removes all your custom rom stuff and all that. That's a nice thought, but that's not how it works
You need to flash a different rom on your phone after having wiped everything. This will fix your problem. And if you so very much want to go back to stock, you could always flash a stock rom through ODIN which you can get from one of the available threads.
Boot to recovery mounts and storage format system data and sd card ,
Power off boot to download mode flash stock firmware via Odin .
jje
I don't know if I'm understanding.
I did reflash the phone with samsfirmware Europe KG6 after a complete wipe of data through the recovery menu (vol.up+power+home).
That didnt work.
Am I missing some steps in my procedure?
I noticed that my default dialer apk, contacts apk, etc are not working. Which method will also replace all my original APKs?
Thanks once again for your time and attention.
Boot to recovery mounts and storage format system data and sd card ,
Power off boot to download mode flash stock firmware via Odin .
Nothing more to add.
jje
Just wanna thank you for your help. For some reason I wasn't getting the expected behavior by flashing KG6. Went with KG5 and now I'm back on stock.
Cheers. Thanks button went your way btw.
Hi, i have been using XWLP9 stock rom + DXLP9 stock kernel for some days but i'm having weird lag issues with lock screen. I have had the same issues before with LP4 rom.
I use simple slide lock screen, but it also happens with pattern lock screen. Sometimes after pressing power or home buttons, after that screen turns on, screen is very unresponsive and i have to slide 3 times to unlock because it is laggy. Pressing home button again or waiting a bit before sliding reduce the problem, but it is irritating to do this every time i want to use my phone
I wiped everything before flashing and i'm not using external sdcard.
¿Is my phone faulty or is it a common problem on ICS roms? I never had this problems using stock GB rom.
Thanks for your help
Did you tried wiping?
I say backup your stuff, do a full wipe using cwm including format of system partition.
After that flash stock dxlp9 not xwlp9.
Wipe again using the dial code.
Don't think its your phone, might be bad flash.
atifsh said:
Did you tried wiping?
I say backup your stuff, do a full wipe using cwm including format of system partition.
After that flash stock dxlp9 not xwlp9.
Wipe again using the dial code.
Don't think its your phone, might be bad flash.
Click to expand...
Click to collapse
Hi, thanks for your answer.
My phone is not rooted so i have not used cwm, but i did the following wipes in recovery mode before flashing: Wipe Data/Factory reset. After that i wiped sd. I flashed my phone twice doing that, first LP4 and then XWLP9.
I use that rom instead of DXLP9 because it has Spanish language. However, I flashed DXLP9 kernel on top of XWLP9 to avoid SOD issues.
What are the differences between cwm wipes and the wipes i did?
as atifsh said ,follow tht an get it rooted to enjoy the benefits of android.....read few posts for ,begginers,rooting,flashing it will help u instead of asking minor issues.....
http://forum.xda-developers.com/showthread.php?t=1501719
get the cwm.zip, install it using the stock recovery, you will get touch version of cwm.
now goto mount and storage
format data, system, cache
goto advanced
wipe dalvik cache
reboot into download mode flash stock dxlp9 using odin
without signing let your phone start.
now see if you have those issues.
i think you will not have those issues anymore.
now you can flash any stock rom but please stay away from xwlp9. use xwlp7 instead.
Edit:
you never got rooted in the process above, if you dont want you are still as stock as you were before.
wiping the way i told will completly erase the OS from your phone thus you will have clean slate to start with.
if you want to stay on dxlp9, let me know ill tell you how to get spanish language for swype keyboard.
atifsh said:
http://forum.xda-developers.com/showthread.php?t=1501719
get the cwm.zip, install it using the stock recovery, you will get touch version of cwm.
now goto mount and storage
format data, system, cache
goto advanced
wipe dalvik cache
reboot into download mode flash stock dxlp9 using odin
without signing let your phone start.
now see if you have those issues.
i think you will not have those issues anymore.
now you can flash any stock rom but please stay away from xwlp9. use xwlp7 instead.
Edit:
you never got rooted in the process above, if you dont want you are still as stock as you were before.
wiping the way i told will completly erase the OS from your phone thus you will have clean slate to start with.
if you want to stay on dxlp9, let me know ill tell you how to get spanish language for swype keyboard.
Click to expand...
Click to collapse
Thanks again for your help, I'm going to do what you suggest and I'll let you know after that
Im having the same problem with rooted device running DXLP9, even with custom kernels, someone advice plz.
AbuS3ood said:
Im having the same problem with rooted device running DXLP9, even with custom kernels, someone advice plz.
Click to expand...
Click to collapse
What about flashing the latest XWLPD and see if the problem exists? The non-wipe from Intratech should do if you have already wipe/clear everything prior to updating from Gingerbread to ICS..
I'm having the same problem with the unlock screen. I have stock XXLPH, but rooted. I've been having this issue almost since day 1.
It is so annoying that I decided to disable the lockscreen at all for now
atifsh said:
http://forum.xda-developers.com/showthread.php?t=1501719
get the cwm.zip, install it using the stock recovery, you will get touch version of cwm.
now goto mount and storage
format data, system, cache
goto advanced
wipe dalvik cache
reboot into download mode flash stock dxlp9 using odin
without signing let your phone start.
now see if you have those issues.
i think you will not have those issues anymore.
now you can flash any stock rom but please stay away from xwlp9. use xwlp7 instead.
Edit:
you never got rooted in the process above, if you dont want you are still as stock as you were before.
wiping the way i told will completly erase the OS from your phone thus you will have clean slate to start with.
if you want to stay on dxlp9, let me know ill tell you how to get spanish language for swype keyboard.
Click to expand...
Click to collapse
I have just flashed my phone again (XWLPD Nordic Conuntries) following your steps but the problem persists. I formatted data, system, cache, wiped dalvik cache but the annoying issue is still there
Another idea?
It's called wake up lag or something like that. It's horrible, sometimes the screen is unresponsive 2 seconds after pressing the power button. Correct me if I'm wrong but i don't think GB had this problem, I've only noticed it on ICS. So no, it's not just you.
Guys, I got the damn issue solved, I flashed the leaked TW launcher(attached) from the SGSIII rom, then everything went fine and the device is soft and fast.
If flashing the new TW launcher didn't solve the problem flash the latest version of Siyah Kernel (im using 3.2.5.2)
http://www.gokhanmoral.com/gm/
I don't have that issue, yes if screen is of for some time waking it takes 2 3 secs, but it never lags to Swype, even if I hurry and unlock it right when screen shows.
Hi.
Met a problem with my GT-I9300. When I shut the phone off it just reboots. The phone was rooted and running a custom rom when this started. Now I have unrooted with mobile Odin and flashed a official firmware but the problem persists.
I have even tried a battery pull. When battery is inserted again the phone remains off til I push the powerbutton. But when I try to turn it off after this it just reboots again.
Anyone else had this? Tips on what to do?
I've never had any luck fixing this problem. I always had to wipe and flash. However, as a temporary fix, you can power off from recovery.
Sent from my GT-I9300 using Tapatalk
can I ask what you are doing when you turn it off?
Sent from the asylum
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
basse10000 said:
Just to clarify, even wipe the phone and restore it to stock completely by flashing official firmware doesnt solve it.
When I turn it off I hold powerbutton til i get the powermenu. From there I choose "turn off". Phone does what it should, screen goes off and everything, only a few seconds later the phone boots again.
Click to expand...
Click to collapse
If the phone was totally cleaned formatted sd card and stock firmware installed then its a hardware problem .
But my guess is it as not totally clean .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
I have now tried to wipe and format sys/data/cach/sd in cwm. Flashed stock firmware via odin. Still same issue. Guess its hardware.
Thanks anyway.
This may sound strange, but is this the clock problem the Desire HD had.
In time settings, uncheck the auto update.
Change time & date to something random.
Power off and pull the battery before it reboots.
Give it a min, power up, reselect auto update and reboot.
Should be good to go. If its the same problem that is.
Sent from the App that Time Forgot.
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
r0uzic said:
It also happens to me yesterday, I wipe cache, system, data, reinstall roms (CM and AOKP) and is still happening
Click to expand...
Click to collapse
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Solved
I solved it by flashing a later official firmware - XXALF6.
Darkrider82 said:
It happened also to me once. I flashed my rom in the same order as you did. But what my problem solved was, I made a wipe AFTER I installed the ROM. After that, I didn't had this issue anymore.
These are the steps I did...
- Get into the CWM recovery
- Wipe Data/factory reset
- Wipe Cache
- Wipe Dalvik-Cache
Hope it works also to you...
Click to expand...
Click to collapse
basse10000 said:
I solved it by flashing a later official firmware - XXALF6.
Click to expand...
Click to collapse
Thanks, I'll try twice methods
Update: It's rare, but has returned to work normal and I doing nothing
Hello,
i found a solution for that problem. You will lose some sd card files.
go to settings-storage-others (or other) and mark all files. Then delete them an go to downloadmode to reflash you firmware. Reboot and the problem is missing.