Most people know about the wi-fi problem with the tablet randomly disconnecting from wi-fi. Does anybody know of a fix or if their is development going in to fix this problem?
Are u on stock or custom rom. Also try changing your wifi ip settings from dhcp to static
Sent from my PG86100 using Tapatalk
i was on taboonary but just changed to lightspeed and i think it's gone
cordell507 said:
i was on taboonary but just changed to lightspeed and i think it's gone
Click to expand...
Click to collapse
Yea I didn't experience any dropouts on the newest lightspeed and civato has a fix for his rom that has been working great for me.
Sent from my PG86100 using Tapatalk
This problem is new to me since the 3.2 update OTA. Worked fine until then. I've tried the factory data reset, and the hard reset turning it off and holding the volume up button and flipping the rotation lock back and forth. All that did is give me the joy of waiting for it to download everything again, but still have wifi probs.
I was going to try a different ROM to see if it works, but I can't seem to get any of the methods in the developer methods to work. Method 1 or Method 2 doesn't work for me. Method 1 stops running before it begins, Method 2 gives me an android fellow with an exclamation point inside a triangle, then it just reboots normally. Any ideas are welcome. I don't think I should have to hack my tablet in order to get it to work normally, but I'm willing to if it works ;P
xdasupporthelpedme said:
This problem is new to me since the 3.2 update OTA. Worked fine until then. I've tried the factory data reset, and the hard reset turning it off and holding the volume up button and flipping the rotation lock back and forth. All that did is give me the joy of waiting for it to download everything again, but still have wifi probs.
I was going to try a different ROM to see if it works, but I can't seem to get any of the methods in the developer methods to work. Method 1 or Method 2 doesn't work for me. Method 1 stops running before it begins, Method 2 gives me an android fellow with an exclamation point inside a triangle, then it just reboots normally. Any ideas are welcome. I don't think I should have to hack my tablet in order to get it to work normally, but I'm willing to if it works ;P
Click to expand...
Click to collapse
You could change your IP settings from dhcp to static. That might work but if your trying to root your device to flash other roms you first have to downgrade from 3.2 to 3.1. There's a thread somewhere here explaining the process.
Sent from my PG86100 using Tapatalk
I have the same problem with the stock rom 3.2
____________________________________________________________
My Devices:
Acer Iconia Tab A500 - Stock 3.2 no root
Milestone - CM7
Bummer. I was hoping that if I tried stock, that would fix the problem. I have Taboonay 2.2 currently. I think changing to static has helped quite a bit, but it still acts up occassionally.
If those with Lightspeed truly aren't suffering from frequent wifi disconnects, I'll give that a shot.
loda7 said:
Bummer. I was hoping that if I tried stock, that would fix the problem. I have Taboonay 2.2 currently. I think changing to static has helped quite a bit, but it still acts up occassionally.
If those with Lightspeed truly aren't suffering from frequent wifi disconnects, I'll give that a shot.
Click to expand...
Click to collapse
Civato has a fix for his rom. I don't know if it will work with taboonay but you could give his fix a shot or try his rom, its probably the fastest rom I tried.
Sent from my A500 using Tapatalk
Related
Wifi no longer works on my 2.3.1 Nexus S after rooting. Can anyone please help? I see possible driver solutions to the same problem under Nexus S, but assume the driver for Nexus S is not the same. When I try to enable wifi it says ERROR. I just discovered the camera also is not working.
Edit: Momohamed20's stock NAND fixed all my problems YAY!!
I've seen Wifi not work on mine running 2.3.1, I haven't rooted, usually it's after I try to turn on Wifi Hotspot and get the "Error" message, then Wifi won't work again until I reboot.
well i've rebooted and gone to fastboot and restore boot many times ... no difference
heinrich said:
well i've rebooted and gone to fastboot and restore boot many times ... no difference
Click to expand...
Click to collapse
A friend of mine just returned his to Best Buy because he was having the same issues. His new one doesn't have the issue
Dudes this is totally not cool. My phone is hosed. All I did was take a working 2.3.1 and unlock/root it
heinrich said:
Dudes this is totally not cool. My phone is hosed. All I did was take a working 2.3.1 and unlock/root it
Click to expand...
Click to collapse
Have you flashed either the MCR or CM7 ROMs in the Development section and still had the same problem?
Or the stock 2.3.1 NAND backup floating around in there too.
I just got my NS today its rooted with working camera and wifi, I'm also on 2.3.1. What I did was unlock the bootloader and rooted using the superboot method. You don't have to mess with anything else. I've read in several posts if you use other methods it can cause the issues your having
Sent from my Nexus S using XDA App
I just flashed the boot image from http://forum.xda-developers.com/showthread.php?t=884194 and the camera now works again, but not wifi. I can't find the stoclk NAND or I'd flash that. I see a link to the stock system.img in the thread I link to in this post, but it's a broken link
No I haven't tried the MCR o CM7 -- no idea what they are but will go find out.
heinrich said:
No I haven't tried the MCR o CM7 -- no idea what they are but will go find out.
Click to expand...
Click to collapse
Ah, okay, MCR is Modaco Custom Rom and CM7 is Cyanogenmod 7. They're both very good custom ROMS based on Android 2.3.1 with some added features and/or other changes. MCR is closer to stock, imo, if that's something you're interested in.
In order to flash them to your device you need to be rooted(which you said you are), and be able to flash Clockwork Recovery via fastboot or ROM Manager. If you're not familiar with Clockwork recovery/ROM Manager, check out this thread before proceeding: http://forum.xda-developers.com/showthread.php?t=875875
yep I have clockwork recovery and rom manager and all that
If someone can help me find the stock system rom I think it will fix tghe wifi problem .... camera now works.
Oh my goodness isn't there someone who knows how to get wifi working again?
RESOLVED
Momohammed20 resolved my issue with his full restore stock image and excellent write-up here: http://forum.xda-developers.com/showthread.php?t=884093
I have been trying out a couple Ics roms, all of which claim have no SOD, but I'm still having problems. I have tried
Lightspeed 4.2
Latest icylicious
Tabooney 3.0.1
I guess to be sure, what I'm experiencing is every seems to work fine, but if the screen goes off for more than a couple seconds, it won't come back on. I have to hold the power button for a few seconds, then let go, the hold down the button again it turns on again fine.
What bootloader did you flash?
FloatingFatMan said:
What bootloader did you flash?
Click to expand...
Click to collapse
I guessed that I still have the boot loader that I installed back when I got my a500 last summer. I thought the ICS boot loader was unstable or something. Should I try the other bootloader that is posted?
Edit: I checked in thee Acer Recovery Installer app and it says I have bootloader 3.01
The SoD is usually caused by the bootloader, but it's possible you didn't wipe something when you flashed one of the ROMs. Personally, I'm running the version of AmonRA we have (though that's not fully compatible with Acer Recovery Installer), and on top of that I have Vache's ICS leak, complete with his 3.0.1 patch. I have no SoD issues at all with this configuration.
You DID do a full wipe, right?
veidt_industries said:
I have been trying out a couple Ics roms, all of which claim have no SOD, but I'm still having problems. I have tried
Lightspeed 4.2
Latest icylicious
Tabooney 3.0.1
I guess to be sure, what I'm experiencing is every seems to work fine, but if the screen goes off for more than a couple seconds, it won't come back on. I have to hold the power button for a few seconds, then let go, the hold down the button again it turns on again fine.
Click to expand...
Click to collapse
I tried both icylicious and flexreaper and could not get rid of the SOD either. I have the 3.01 bootloader and have wiped and formatted and wiped some more. Everyone keeps saying the SOD is because I didn't do a full wipe. I'm back on 3.2.1 now.
Did you check if an ICS incompatible app might be the reason?
Best regards, maris
maris__ said:
Did you check if an ICS incompatible app might be the reason?
Best regards, maris
Click to expand...
Click to collapse
I thought an app might have been at fault so I did fresh formats/wipes and didn't restore any apps to be sure but still got SOD. The screen goes to sleep normally then after a short time reboots and gets stuck until I press power to turn off, then power back on.
Thanks everybody, it was the bootloader. Just for closure, here is what I did.
Install leaked ICS from here
Fix the bootloader and recovery from this thread
Install ROMs like normal
Thanks again
Had SOD all the time with flexreapper, installed newest thor's and all SODs gone. I guess the issue is specific to ICS' ROMs based on the leak.
Whats the newest version of thor clockworkmod recovery for Iconia a500?
veer01_42 said:
Whats the newest version of thor clockworkmod recovery for Iconia a500?
Click to expand...
Click to collapse
NEXT time, Google should become a resource for you..... But this time, V1.7.1 I believe is latest 'touch' version.
SOD ain't there on LEAK version...
ROOT can be done on LEAK version...
the problem for sure is from CUSTOM
There's no SOD in the custom ROM's built from the leaks, either; as long as you followed the instructions properly.
Try this out. Finally worked for me.
Hey a little late here, but I have had SoD for months. I have tried everything (new bootloader, several roms), but nothing seemed to work. I finally tried flashing a custom kernel separately after I flash the rom and it seems to be working now.
Here is the ezterry A500 rom, http://forum.xda-developers.com/showthread.php?t=1703590 and its a zip so you flash just like a rom. Good luck everyone who has the same problem.
I was running Thor Rom, but I installed the update, but from This thread and others, even the ones I had to decrypt first. The update always went smooth and ICS looks and works great; except....
Any time the screen goes to sleep, or I press the power button to turn off the screen, the screen won't wake up. OK, correction, it WILL wake up if I turn it on within ~10 seconds, but wait longer than ~20 seconds and it won't come back on. I have to press and hold the power button to apparently shut it down (hard to tell because you can't see anything and there are no indicator lights). Then I have to press and hold it again and it boots back up.
Hence, I have to press and hold the power button for several seconds twice each time I want to use it.
I'm not sure if it's shutting down or just hard freezing. I can't seem to shake this. It didn't do this with the old stock rom or Thor.
Ideas?
Currently Running the following on my A500 1.0
Image: Acer_AV041_A500_RV05RC01_PA_CUS1
Build: Acer_AV041_A500_1.033.00_PA_CUS1
same problem
I have the same problem, I updated my tablet via the acer update and now it does that :/
First I thought it was some problem with a program I had installed, but then did a factory reset and left a couple programs and still doing that.
Im going to try to hold the reset button to see what happens.
This issue is known to occur with several custom ROMs and is referred to as the Sleep of Death or SoD. It occurs when the tablet goes into deep sleep and refuses to wake up. Thor has suggested those affected and using his ROM to increase the voltages of their CPU or flash his performance kernel. If you are using Stock ICS from Acer then I think there's a thread documenting issues with it. You can check that, it should be in the general section. Hope this helps. It happened to me only once and I can't recall which ROM, but it never happened again.
Sent from my Iconia A500 using Tapatalk 2 Beta-6
That's just the thing, I want the stock ICS and I thought I had it (still think I do!). I'd like to go back to stock to make things work correctly. However, there is no 'check update' button for me in my settings. I have no way of looking for an OTA update that I can find. I'm dumb at times, but not that dumb.
I have the same problem and I'm running CM9 now. I started with the same ICS update that you listed in your first post. I have two GEN1 ICS updates I think I'm going to try. Since the problem has transcended roms (Stock ICS to CM9) I'm thinking this is a firmware issue with the CUS update. I read a thread that said (man I'm rhyming tonight...) the CUS didn't come with some firmware images that the GEN ones did.
EDIT: Since I'm on the V3 Bootloader I don't think I can install these updates. I decrypted them, but it's still failing to install. Probably have to be on the stock bootloader for these to work.
Frostcall said:
That's just the thing, I want the stock ICS and I thought I had it (still think I do!). I'd like to go back to stock to make things work correctly. However, there is no 'check update' button for me in my settings. I have no way of looking for an OTA update that I can find. I'm dumb at times, but not that dumb.
Click to expand...
Click to collapse
I downgraded my tablet back to 3.2 using info in one of the Dev threads. Then I let it update with OTA updates to 3.2.1. I then had to install the Acer Update Helper app on the play store in order to get it to update to ICS. The point of all this is that until I went back to a stock 3.2 I could not do an OTA update as the roms were not stock.
Then once I was on stock 4.0.3 ICS I was STILL getting SoDs. I put in a trouble ticket to Acer and the response I got was to do a full hardware reset (power off, hold power and volume up until it vibrates, then toggle the screen lock switch a couple times.) I finally got back to installing a custom rom (flexreaper r13) and I now no longer have SoDs. A lot of work but I think I'm finally stable.
Sent from my A500 using XDA Premium HD app
BakaNeko59 said:
I downgraded my tablet back to 3.2 using info in one of the Dev threads. Then I let it update with OTA updates to 3.2.1. I then had to install the Acer Update Helper app on the play store in order to get it to update to ICS. The point of all this is that until I went back to a stock 3.2 I could not do an OTA update as the roms were not stock.
Then once I was on stock 4.0.3 ICS I was STILL getting SoDs. I put in a trouble ticket to Acer and the response I got was to do a full hardware reset (power off, hold power and volume up until it vibrates, then toggle the screen lock switch a couple times.) I finally got back to installing a custom rom (flexreaper r13) and I now no longer have SoDs. A lot of work but I think I'm finally stable.
Sent from my A500 using XDA Premium HD app
Click to expand...
Click to collapse
I wonder if this will work with the V3 bootloader?
naviathan said:
I wonder if this will work with the V3 bootloader?
Click to expand...
Click to collapse
That's what I had installed when I started the process. Of course it eventually got overwritten with the unpatched stock bootloader, but that was easily fixed.
Sent from my A500 using XDA Premium HD app
How did you manage that? I need to figure something out because right now I can't set my tablet down for two minutes without doing a hard reset. Over clocking helps, but it's got limits. Not to mention the wifi...Man it's horrible now!
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
UPDATE
See post 7 & 13 Below
I had this issue but after i wired data using code *2767*3855# everything worked smoothly.
You can try this at your own risk as it might brick if yor device has emmc bug. I have already done it over 15 times and no issue
Sent from my GT-N7000 using XDA
olivespin said:
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
Click to expand...
Click to collapse
I rooted my Note after about two days so not sure if this will work on non-root....
Reboot into recovery (Power+Vol Up + Home) then clear cache and clear Dalvik cache. Reboot then see if lag continues. Clearing caches and reboot seems to get rid of lags and gives phone a new life
Today again phone got frooze on homescreen for 5mins and got back to life again after pressing Home key numerous times
So yes, something is wrong with this ICS update.
Plz provide a solution and also mention if tht solution can lead to bricking bug..
BUMP.
I had exactly the same problems while updating Gb to ICS using OTA update. Anywhow, I never got to fix this. I would try following steps:
Clean the cache of your ICS installations/apps using any Cache-cleaning tool on the Play Store
Reboot your phone like 2-3 times (sometimes this seems to fix some problems with your kernel/rom since they have to settle down.
Update all your apps to their latest versions, since most apps have fixes for ICS installations, and might slow your phone a bit down in some way
Click to expand...
Click to collapse
When you still would have problems with your ICS installations I would recommend installing a custom rom over your stock ICS installation. This did the trick for me eventually.. But depends on if you would like to have a stock or custom ICS rom.
HELP
I tried the above suggestion and done Factory Format via *2767*3855#.
Now, after entering code the device havent rebooted for the next 15mins, so i pressed the power key to reboot manually and then i got the message format failed or sumthing similar which i dont seem 2 recall.
Now, all my Smemo data & camera images is wiped... but phone numbers and messages intact.
and the originally mentioned problem is still there..... So wht is my solution now ?
I want to delete every old system files & Clean-install ICS - So Is it via kies?
Dont know much abt all this so a detailed help would be highly appreciated.
olivespin said:
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
Click to expand...
Click to collapse
Facing the EXACTLY the same problem man.. Feel i have done a mistake by upgrading to ics
Sent from my GT-N7000 using xda premium
androidlover1 said:
Facing the EXACTLY the same problem man.. Feel i have done a mistake by upgrading to ics
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Somebody give us proper solution to this.. HELP!
Sent from my GT-N7000 using xda premium
Flash gingerbread again with odin, then do a factory reset... then upgrade to ics again using odin...
I dont want to go to GB again..... All i want is fresh clean install of ICS on my phone... So how to do tht ? (i dont wana play with my phones warrenty)
You can use pc odin to flash stock ics, not recommended though as you're on ics kernel now. Best to follow previous poster, fladh gb stock kernel first.
please hit thanks if i helped
SpyderTracks said:
You can use pc odin to flash stock ics, not recommended though as you're on ics kernel now. Best to follow previous poster, fladh gb stock kernel first.
Click to expand...
Click to collapse
If i use odin to flag GB first, will i loose my phones warrenty? (And i dont even knw how 2 use it)
Second, can i go 2 samsung service centre and let them delete all old files and install fresh copy of ICS? If i do, will i run a chance of bricking..... Coz i dont want to run into parts replacements and repairs problem...
What is the best solution now.
olivespin said:
If i use odin to flag GB first, will i loose my phones warrenty? (And i dont even knw how 2 use it)
Second, can i go 2 samsung service centre and let them delete all old files and install fresh copy of ICS? If i do, will i run a chance of bricking..... Coz i dont want to run into parts replacements and repairs problem...
What is the best solution now.
Click to expand...
Click to collapse
Since you did nothing wrong that could void your warranty, and you don't know too much about fixing it yourself, save yourself the hassle and let a Service center take cre of it for you .
Title says it all guys blowing of the dust of this thing can anyone point me to the most stable ROMs out there CM10 prefer
Sent from my HTC6435LVW using Tapatalk 2
I'd like to know this too. I often have to turn wifi off then on to reconnect.
Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings
Team EOS 4, Katkernel here too, make sure you reboot a few times after installing it. follow the guide in this forum, install it like it directs you to.
FULL wipe(cache, dalvik, factory, system), install ROM, cache/dalvik wipe, install gapps, cache/dalvik wipe, install Kernel, cache/dalvik wipe, reboot.
Get Kat apk to boost volume and GPS fix.
I was having systemUI issues, reinstalled everything a few times and now it's running great. Keep it under 1400mhz, 1200mhz seems to work well for me. Nightly 109 was eating up my battery too quickly, 111 is doing better, I hope they can improve more if possible, great ROM either way, I'm very grateful.
Sent from my Transformer TF101 using xda app-developers app
I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.
Astania said:
I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.
Click to expand...
Click to collapse
Just reply to a few other threads, XDA has thousands
+1 for EOS4/KAT kernel. No-name is pretty good as well if you like CM 10.1.
EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing
+1
talman26 said:
EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing
Click to expand...
Click to collapse
Aye...EOS 4.2.2 (v109) + 1400, very stable, no big issues, suitable for daily drive tab
+1
Team EOS4, Been using it for months and not a WiFi hicup.
*Detection* said:
Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings
Click to expand...
Click to collapse
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
Can you still get into recovery? If so, can you flash from the microSD?
danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs
Team EOS 4 + Kat Kernel = FAST and STABLE :victory:
PS: If you wish to use Phablet UI i suggest you use Trebuchet from CM 10.1
*Detection* said:
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs
Click to expand...
Click to collapse
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!
danilimpsy said:
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!
Click to expand...
Click to collapse
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Sent from my Transformer TF101
zAlbee said:
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Click to expand...
Click to collapse
As I already said...flashing ROM FAILED over 5 to 7 times...and I CAN´T get to APX...i´m stucked at NO SYSTEM...just can get to Recovery, but NO flashing!
Try a different PC, or reinstall APX drivers
99% that APX mode does work, either you are doing something wrong, or your PC is struggling with the APX drivers
APX mode is volume up & power from powered off state while already plugged into PC, the only notification for entering APX mode is USB connect sound, nothing will appear on TF screen
I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment
hulk69 said:
I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment
Click to expand...
Click to collapse
Have to ask, what recovery did you use and did you do a full wipe before installing?
I find EOS 4 to be MUCH more stable on WiFi than any ICS ROM (including Stock and stock based ROMs)