Related
Hello,
I know this is not the first time this topic is brought, although it is usually part of an unrelated thread.
I have this AllWinner A10 mk802 , a strange device (it looks like a usb flash drive, but is an Android 4.0.4 computer on which you plug your own screen, mouse and keyboard, making it a Desktop PC on a stick running Android).
Not being a big fan of tablets, I thought I'd give it a try -- Android with a keyboard and a mouse (!). It doesn't look too bad even if it is not powerful enough for my tastes and I can't install CM9/10 on it because of the issue I'll bring here in a second. (In the meantime I installed Uberoid 1.2, which is the stock chinese Android 4.0.4 image which most of its cruft removed -- still doesn't feel right, though.)
There are experimental builds of CyanogenMod 9 and 10 for it, there is a ClockworkMod for it, but I can't use it: when I get into recovery mode, I get a visually awkward-looking (see http://i.imgur.com/Nchso.png ) CWM screen, which wouldn't be a problem if I were able to move through the menus. I've tried with three different mice, three different keyboard, the only thing I was able to do was to flash the screen (it turns black 2 ou 3 seconds) and that's all.
Now, I'm almost there. I just need to be able to wipe the existing system, install CM10, its support (legacy) file and GApps. For that, all I have to do is a dozen of key presses. But I think that I've tried everything.
Has anyone here fought this or a similar issue and won? If so, how did you proceed?
Thanks!
cpl593h said:
Hello,
I know this is not the first time this topic is brought, although it is usually part of an unrelated thread.
I have this AllWinner A10 mk802 , a strange device (it looks like a usb flash drive, but is an Android 4.0.4 computer on which you plug your own screen, mouse and keyboard, making it a Desktop PC on a stick running Android).
Not being a big fan of tablets, I thought I'd give it a try -- Android with a keyboard and a mouse (!). It doesn't look too bad even if it is not powerful enough for my tastes and I can't install CM9/10 on it because of the issue I'll bring here in a second. (In the meantime I installed Uberoid 1.2, which is the stock chinese Android 4.0.4 image which most of its cruft removed -- still doesn't feel right, though.)
There are experimental builds of CyanogenMod 9 and 10 for it, there is a ClockworkMod for it, but I can't use it: when I get into recovery mode, I get a visually awkward-looking (see http://i.imgur.com/Nchso.png ) CWM screen, which wouldn't be a problem if I were able to move through the menus. I've tried with three different mice, three different keyboard, the only thing I was able to do was to flash the screen (it turns black 2 ou 3 seconds) and that's all.
Now, I'm almost there. I just need to be able to wipe the existing system, install CM10, its support (legacy) file and GApps. For that, all I have to do is a dozen of key presses. But I think that I've tried everything.
Has anyone here fought this or a similar issue and won? If so, how did you proceed?
Thanks!
Click to expand...
Click to collapse
I just got one also and have found a forum that is pretty comprehensive. I am doing a lot of reading before I jump to it. Try here:
http://www.rikomagic.co.uk/forum/index.php
Let me know how it goes as I am sure to root and flash CM10 as soon as some one gets it figured out.
Mac N Ts Daddy said:
I just got one also and have found a forum that is pretty comprehensive. I am doing a lot of reading before I jump to it. Try here:
http://www.rikomagic.co.uk/forum/index.php
Let me know how it goes as I am sure to root and flash CM10 as soon as some one gets it figured out.
Click to expand...
Click to collapse
I have dug this site also and wasn't able to find anything (or anything actually working) for my CWM problem. If you find something there that helps you, please share.
Thanks!
I have the same issue, Maybe someone can make Livesuit .img from the CM9/10 packages and compatible gapps and comp zips?
I just got a MK802 for testing and if it works fine with CM I will keep it or even better get a new one, but I am dealing with the same issue, the mouse/keyboard entry reboots the recovery, as if any movement is an enter and reboots the MK into recovery...
If anyone of you guys were able to fix this I would appreciate the info..
LuciusK said:
I just got a MK802 for testing and if it works fine with CM I will keep it or even better get a new one, but I am dealing with the same issue, the mouse/keyboard entry reboots the recovery, as if any movement is an enter and reboots the MK into recovery...
If anyone of you guys were able to fix this I would appreciate the info..
Click to expand...
Click to collapse
+1
Hi all.
I had the same problem.
My mouse works perfectly in both versions of stock MK802+ firmware, but in CWM it switches the screen off for a few seconds every time I move it. The same is happening with my keyboard, so I am struggling to flash cyanogenmod.
SOLUTION:
I changed the mouse to a wireless one (not bluetooth, but standard 2.4), I had lying around and it worked fine.
I think it's because the first mouse I tried has a laser pickup which draws more power or maybe its just a cwm driver issue.
The keyboard and mouse I originally used are quite fancy gaming products, so maybe they are just too "high-tech" for Clockword Mod.
Cheers
Steve
CWM video anomaly on MK802
Hey Everyone !
XDA noob here but I've been modding my junk for several years now since HTC Eris.
I'm having the exact same problem as cpl593h, screenshot is identical.
I wanted to use TWRP, I love that recovery -best thing in device modding ever IMHO, but I can't see anythig about mouse support. It's all touchscreen I guess. I tried GooManager but it were a no go. Still trying to find a recovery alternative to CWM. I know it's been around a long time but I've had more trouble with it that successes.
If I find a workaround, I'll post it here!
CyberCorgi3K
CM10 livesuit image
avishayil said:
I have the same issue, Maybe someone can make Livesuit .img from the CM9/10 packages and compatible gapps and comp zips?
Click to expand...
Click to collapse
hey there,
btsimonh from miniand.com managed to make a livesuit compatible .img of CM10. What's also included is zulu99's work of including droidmote compatibility. So no need to struggle with CWM any more.
Simon said that he will put some efforts in optimizing the ROM further.
So if there's any progress, I'll post that.
Sadly, as a new user, I'm still not allowed to post some links.
So I guess it's good to PM me until I reached URL posting threshold.
cpl593h said:
Hello,
I know this is not the first time this topic is brought, although it is usually part of an unrelated thread.
I have this AllWinner A10 mk802 , a strange device (it looks like a usb flash drive, but is an Android 4.0.4 computer on which you plug your own screen, mouse and keyboard, making it a Desktop PC on a stick running Android).
Not being a big fan of tablets, I thought I'd give it a try -- Android with a keyboard and a mouse (!). It doesn't look too bad even if it is not powerful enough for my tastes and I can't install CM9/10 on it because of the issue I'll bring here in a second. (In the meantime I installed Uberoid 1.2, which is the stock chinese Android 4.0.4 image which most of its cruft removed -- still doesn't feel right, though.)
There are experimental builds of CyanogenMod 9 and 10 for it, there is a ClockworkMod for it, but I can't use it: when I get into recovery mode, I get a visually awkward-looking (see /*NO LINKS*/ ) CWM screen, which wouldn't be a problem if I were able to move through the menus. I've tried with three different mice, three different keyboard, the only thing I was able to do was to flash the screen (it turns black 2 ou 3 seconds) and that's all.
Now, I'm almost there. I just need to be able to wipe the existing system, install CM10, its support (legacy) file and GApps. For that, all I have to do is a dozen of key presses. But I think that I've tried everything.
Has anyone here fought this or a similar issue and won? If so, how did you proceed?
Thanks!
Click to expand...
Click to collapse
Hi2all!
I have exact the same problem with device "appolo-mele" (allwiner a10 platform) - graphics looks to bad, also when i try to switch menu entry - screen turns off and then turns on (on next menu entry), but CWM works fine (backup and restore functions).
I tried:
1. CWM for Allwiner A10 ("CWM 6.0.2.8 for Allwinner A10 & A13 Tablets - v2a") - "graphics problem"
2. Some other CWM 5... and 6... versions for Allwiner A10.
3. Build cwm recovery from sources, using native boot.img, following the "[GUIDE] Build CWM recovery " by buffo1987 and "[GUIDE] Compile CWM Recovery" by Shaaan. - "graphics problem", anything else works fine.
Here is some info about device:
1. It is a TV Box device with HMDI, WiFi, LAN, SPDIF optical audio out and AV-TV out ("3.5 4contact jack in device to 3 tulip connectors to TV"), 2 usb
2. Complied 6.0.3.7 CWM
3. cpuinfo: ARMv7Processor rev 2 (v71) , sun4i
4. other info is similar to "Rikomagic MK802+"
Maybe I should try to use custom "graphics.c"?
Can some help me with my problem?
Attached is the latest version of the recovery file.
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
misteral1970 said:
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
Click to expand...
Click to collapse
Mate, it doesn't sound good.
What I would do, at this point, is Fastboot the 4.1 image again.. And stay the heck out of CWM. If you Fastbooted the 4.0.4 image, and you still have it showing 4.1, then you have a serious issue. So boot to fastboot, and try it again. Clearly, whatever you did with CWM, didn't work,
Installing a rom from CWM, requires certain things to be done, either in the install script, or via CWM.
Most notably, Formatting User data, cache, dalvik, system, and data. If any of these do not get done, chances are, the rom install will not go good. The basic install script, generally only formats System and Flexrom. This is because Acer distributes a full rom with the understanding there is nothing on it. Most rom modders know this, which is why they give extra instructions via cwm.
The big thing, is when you boot your tablet, is if it says which bootloader you are on. So you have to look,. You want to be on the JB bootloader.
MD
Thanks for the response MD,
A tiny bit unsure how to proceed. I understand everything that you said (well, I think I understood correctly!)
I have in fact tried to fastboot the 4.1.1 image again, and again I am stuck on the language and location screen (did this last night before giving up for the day)
I have read and understood "Stay away from CWM" (and I know that it is in this case only - have used CWM on my Gnex without issue)
Please forgive me if what I am about to write is ridiculous - this is kind of where we'll see whether I understood correctly or not.
I'm thinking that if the various areas were not wiped, and that could be the reason for the snafu, then it would be worth going into CWM (which I have been warned to stay away from, and which I would stay away from except for this one thing) and formatting the user data, system, dalvik etc, then applying either the 4.1 or 4.0.4 to result in a working tablet.
Or possibly flashing the bootloader to make sure it is JB
Or going back to the weird 4.0.4/4.1.1 hybrid which works but doesn't allow Play Store and finding a way around that issue.
Mate, I'm not sure which way to go at this point!
Fastbooting 4.1 is a dead end at the moment (but could that be a bootloader issue....)
Fastbooting 4.0.4 gives me the hybrid (though I can check this again tonight)
BTW, the only CWM Rom work I have tried to do has been with the patched update (second downloadable file I think) - everything else has been done via ADB
So.....CWM to wipe/format caches? (I'm thinking 'NO! DID YOU NOT HEAR WHAT I SAID ABOUT STAYING AWAY FROM CWM????' but I'm asking anyway!)
Flash a new bootloader on? If so, any idea where I would find it (will obviously search here and Google)
Thanks anyway, and thanks in advance if you have any more advice. I really do appreciate the support!
Al
Well Al,
This is perplexing to say the least. Clearly fastbooting the 411 results in frozen at the wizard. My question, when you have the unlocked bootloader, does it say JBxxxxxxxx unlock mode when you boot the tab? Because it should. If it doesn't, then you're still on ICS bootloader. And will have to do the CWM thing to get JB installed. The 411 image flash, is to get a rooted version.
And this is the point. Personally, I do not trust the CWM's at this point. That's just me (already bricked 1 tab 3 months ago with a faulty CWM) I know the folks with ICS are using Pawitp's CWM, and haven't reported issues. But I don't know if they are doing wipes or not.
As with the 404 image, well, why playstore doesn't work is perplexing. You could try reinstalling the playstore via manual method (root required). Which is to delete the vending.apk, install a new vending.apk (making sure permissions are the same as the other files), then reboot. Go to settings, wipe the playstore cache's. Then try Playstore again. This was an old method we used with market issues in HC.
Personally, I feel the issue is with the wipes before running the patch. But I would hate you do the wipes and formats, then discover the emmc chip bricked. So it's 50/50.
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
Wish I could give you a definitive answer, but these processes are too new.
MD
Keep warranty
Moscow Desire said:
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
MD
Click to expand...
Click to collapse
Can you make a short tut how to replace the old unlocked Bootloader?
My Tab has some Problems with the Display so it need a service ...
witch cwm to use?
witch update.zip?
remove cwm and su if necessary
Android Version: 4.0.4
Baseband: 11.810.922.00
Kernal:2.6.39.4+
Image:ACER_AV043_A701_RV08RC02_EMEA_DE
Build: ACER_AV043_A701_1.017.00_EMEA_DE
Hi MD,
Thanks for such a speedy and useful response!
Warranty: nope! I'm in China, bought the tablet in Shanghai (now way down south in Shenzhen) and it was a dodgy deal to say the least. I suspect they were being lifted from the factory. No complaints from me about this, or about any difficulties caused by rooting/flashing/CWM. My choice of action all the way along and I am aware of the risks
Just flashed 404 again and it is fine so far, again very nice and smooth. Going to look at the Play Store and see how it behaves, see what I can do as far as vending.apk is concerned (although I'm lost when it comes to permissions. Obviously I know what permissions are in tech terms, but no idea where they would be set, how to change them, what to use as a reference) I figure this is the path of least resistance for right now.
Then I'm going to see if I can apply the standard A701 update to JB (which I won't be able to because of rooting/unlocking but I will fiddle around) and see if I have any joy.
Got my keen eyed gf to check the message on boot, you were right that with the 411 image applied it still had an ICS bootloader, so that's good to know if I want to try going back to the flashed JB image. However, I have no idea how to flash the JB bootloader/kernel, and the CWM process for the patched update fails each time (despite editing the first line of the necessary file in META-INF/Google/Android)
So, I will keep you up to date with progress. Fingers crossed!!!
Al
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
misteral1970 said:
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
Click to expand...
Click to collapse
Well, seems like Nova is the culprit. I assume you are talking about nova launcher? Or nova the game?
Hi MD
Yes, Nova launcher but no, it's not the culprit. At least I don't think so.
The play store stopped as soon as I ticked 'Install from unknown sources', before I installed Nova.
Very odd.
Quick questions:
1) Any advice/links/downloads for changing to JB bootloader if I apply the 4.1.1 again? Given that I cannot run the patched update/flash from CWM, I am guessing I would need to directly install/flash the bootloader from ADB...
2) Don't kill me for asking this. I know to stay away from CWM, I have seen you post it a good few times here, I heed the warning....BUT.....
Given that I have CWM installed and it's working ok (apart from failing to apply updates) - I have 6.0.1.4 - many of the guides to updating the 701 say it needs 6.0.1.1. Would the slightly more recent version of CWM make a difference in terms of success or failure of the update? Update is failing with a 'set_perm:some changes failed' very early in the update.
Seriously, I am being extremely wary of CWM, it's just that currently I have a slightly disabled tablet and it would be great to get this sorted.
Thanks, once again, for all your help,
Al
Update again, put 404 back on (after issue with play store and unknown sources)
Opened play store, downloaded Apex launcher - all good.
Ran Apex, all good....then suddenly Play Store stops, Apex stops, never to return.
With 404 img on, About Tablet still says 4.1.1
The saga continues!!
Aaaand that's the end of that!
Put 4.1.1 back on, pushed the boot.img from the official update.
Now no CWM, so it seems no recovery mode....if I try to get there by volume down and power on, it goes into update mode.
And of course neither the official update nor the 'patched' one will apply.
Can boot to the first start screen (language/location) but can't get any further.
Maybe I can find a service center here in Shenzhen who can sort it out.....as I said before, no harm no foul, I knew the risks!
Thanks one more time MD for all your support and advice )
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
misteral1970 said:
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
Click to expand...
Click to collapse
HA HA, you found the User Data wipe.... Yeah, a little known secret from the 500 forums.
MD
It's so strange....so now I'm back to having flashed 404 but the tablet thinks it's 411.
Play store was fine for about 40 minutes, I quickly got chrome, currents and BBC news.
I turned off the Acer ring and play store died...
But here I am, typing to you on the tablet and it's fine. And what a change in performance. It's most noticeable in currents..the increase in speed and smoothness when scrolling between pages makes it at least ten times better than before.
But the last flash was 404....weird....
I'll leave it like this for now. No market but at least it's not semi bricked!
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
misteral1970 said:
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
Click to expand...
Click to collapse
Well, good news then. I think it's an interesting set-up. Hybrid. Still not sure though, why it pulls 411 from the build.prop as it should have been changed when you flashed the 404image. But honestly, after reading the OP's steps, I believe he references going back to 404 via CWM, and not fastboot. This of course would mean installing a full 404 original rom. I'll have to look over my JB system dump and see where the other prop would be. Maybe something changed in JB.
So if you can live with it, it's probably better to leave it be till we come up with something more definitive.
MD
"So if you can live with it, it's probably better to leave it be till we come up with something more definitive"
Yeah, totally agree.
Mate, seriously, thanks for the support and advice on this. It makes a big difference. Even as I sat there last night with what seemed to be an unusable tablet, being able to chat to you about it meant that at least I didn't feel completely adrift!
Big big thanks
Something very strange happened yesterday.
I got the latest OTA and installed it, after this the touch screen is not responding at all.
I managed to control the tablet with an usb mouse, so I have been able to do a factory reset, but to no avail.
Just now I'm clueless on what to do.
I actually did on more thing in the same process; the initial reason for why I took up the tablet yesterday, was to put on a screen protector film.
So while it was updating I put on the screen protector, after all this was done the touch screen was not responding. I don't think this issue has nothing to do with the screen protector, and I have also now removed the film. But still the screen does not react to touch.
But what to do from here?
Is it possible to revert to a previous version of the firmware?
I doubt reversion is the best option.
If this was common this forum would be flooded with complaints.
It might have been something to do with putting on the screen protector DURING an update.
Factory reset may help. Did you try the pinhole reset switch?
Sent from my HTC One X using Tapatalk 2
I can use the tablet with a usb mouse, and have been able to do a factory reset. But this did not difference.
I have also tried the pinhole reset, no luck...
I have the same issue.
I tried back to ICS stock rom. Touch screen is not responding too. :crying:
imtheyoyo said:
I have the same issue.
I tried back to ICS stock rom. Touch screen is not responding too. :crying:
Click to expand...
Click to collapse
Interesting.
Was it after the latest OTA the touch screen stopped working? Or was it something else that started this?
My tablet is stock in every way, never been rooted or had other roms installed.
I could of course send it in to service, but since I bought the tablet while on holiday in Washington DC and I reside in Norway, it's a little unpractical.
owangen said:
Interesting.
Was it after the latest OTA the touch screen stopped working? Or was it something else that started this?
My tablet is stock in every way, never been rooted or had other roms installed.
I could of course send it in to service, but since I bought the tablet while on holiday in Washington DC and I reside in Norway, it's a little unpractical.
Click to expand...
Click to collapse
what is your image version and touch FW version? my A700 touch function is normal after OTA update.
my image is Acer_AV051_A700_RV19RC01_TWN_GEN1
touch FW version:AT0-22F40-F6935B
My touch screen work again.
I back to ICS stock rom (Acer_AV043_A700_RV07RC06_EMEA_FR), then I apply the update (Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR).
Now I'm on JB (Acer_A700_AV043.RV23RC04_AV051.RV10RC01_EMEA_FR). All Work fine.
jacksonkuo said:
what is your image version and touch FW version? my A700 touch function is normal after OTA update.
my image is Acer_AV051_A700_RV19RC01_TWN_GEN1
touch FW version:AT0-22F40-F6935B
Click to expand...
Click to collapse
Thanks. Compared to yours I see that there is some problem with my touch FW version. On my tablet it says AT0-0-0.
Image version reads Acer_AV051_A700_1.052.00_PA_CUS1
Is it a way for me to fix this? Could I perhaps reapply some of the patches?
Sent from my U8860 using Tapatalk 2
owangen said:
Thanks. Compared to yours I see that there is some problem with my touch FW version. On my tablet it says AT0-0-0.
Image version reads Acer_AV051_A700_1.052.00_PA_CUS1
Is it a way for me to fix this? Could I perhaps reapply some of the patches?
Sent from my U8860 using Tapatalk 2
Click to expand...
Click to collapse
Seems the touch FW is incorrect.Maybe you can download the OS upgrade image from Acer website and reflash OS. I checked the image and it should packed touch FW. If still failed, maybe contact Acer service is good way to solve your problem.
Good luck.
I had the same problem this week, bought the Tablet on monday, made the OTA Update and boom, no Touch input.
I resolved it by unlock my device, flash CWM and then flashed a older full rom.
After that i made the OTA Update again and this time it worked well.
I can upload the ROM i used for this if it's needed.
MfG Frank
via Acer Iconia Tab A700 mit Tapatalk 2.0
Thanks. I have fixed my tablet now.
I managed to reflash an older rom, taken from Acer site. And then upgraded via ota to the latest version.
I did not need to use cwm. Just started the tablet the power + volume - combination
Sent from my A700 using Tapatalk 2
Problem: Screen touches are bugged..
Hi,
I need some urgent help..
I upgraded my A700 (was shipped with 4.0.4) to JB but the screen touches are completely off track. I did the following:
1) unlocked the bootloader
2) flashed CWM Rom 6.0.1.5
3) installed cm-10
Don't know what to do next..
I have an Acer A700 and I'm having the same problem as others here.
Once I upgarded my ROM, the A700 touch-screen did not work.
I found a post that explained a fix. Here's what I did:
* Flashed the non-touch CWM v6.0.1.5
* Wiped everything (system, data, cache, dalvik)
* Installed the IconiaN ROM (by Vorbeth) and choose the option to have IconiaN upgrade my "Touch Firmware"
* The A700 is now booting with version JB-653b3d3 (Unlocked)
* The ROM loads just fine
However, in the ROM, the touchscreen does not work. Clicking in one place on the screen will trigger a click in an entirely different area of the screen.
I then tried installing one of the stock Acer ROMs from their website through CWM. None of them would load, not sure why?
Other people here seem to have solved the problem by flashing an "older ROM" from Acer. I could not find any trace of this older ROM.
I'm running an American version (PA1_CUS) if that makes any difference? I've also tried installing CM 10.1 with the same problems in the touchscreen.
Thank you in advance for any suggestions!
RKM
Where can i get the acer software to update? i've tried to find it on the acer website but i cant find it.
please help. i just got the device and i updated it and now a portion of the screen becomes unresponsive to touch input.
toggling the screen on and off will fix it temporarily but that only lasts for 5 minutes max before it stops being responsive again.
Every thing on it is stock so i want to keep it that way
pyrochance said:
Where can i get the acer software to update? i've tried to find it on the acer website but i cant find it.
please help. i just got the device and i updated it and now a portion of the screen becomes unresponsive to touch input.
toggling the screen on and off will fix it temporarily but that only lasts for 5 minutes max before it stops being responsive again.
Every thing on it is stock so i want to keep it that way
Click to expand...
Click to collapse
Try Google and search for your Rom Build number. Should be able to find the update file. You can also try some of the Acer support sites. I remember they have some ICS full roms for the 700.
Next of course, you're going to ask how to install it?
1. Decrypt the original update file (tool is in the themes and apps forum)
2. Using 7zip, OPEN the decrypted file (DO NOT UNZIP IT)
3. Pull the "update.zip" (NO NOT UNZIP IT)
4. Copy the update.zip to your ext sd card
5. Start tablet holding PWR & Vol- or + (can't remember which) until you see the text in upper left corner then release. Now, JB may have a different stock recovery which offers a small menu. I believe you can select the install update from there.
If the update doesn't install, it may be the wrong update file, so you'll have to search for another.
Anyhow, should work for you. But you may have to roll back to the original ICS rom (full version) then OTA update again.
Remember though, you do this at your own risk, so if things get messed up, don't blame anybody
Moscow Desire said:
Try Google and search for your Rom Build number. Should be able to find the update file. You can also try some of the Acer support sites. I remember they have some ICS full roms for the 700.
Next of course, you're going to ask how to install it?
1. Decrypt the original update file (tool is in the themes and apps forum)
2. Using 7zip, OPEN the decrypted file (DO NOT UNZIP IT)
3. Pull the "update.zip" (NO NOT UNZIP IT)
4. Copy the update.zip to your ext sd card
5. Start tablet holding PWR & Vol- or + (can't remember which) until you see the text in upper left corner then release. Now, JB may have a different stock recovery which offers a small menu. I believe you can select the install update from there.
If the update doesn't install, it may be the wrong update file, so you'll have to search for another.
Anyhow, should work for you. But you may have to roll back to the original ICS rom (full version) then OTA update again.
Remember though, you do this at your own risk, so if things get messed up, don't blame anybody
Click to expand...
Click to collapse
Thank you for the detailed help!
after many google searches i finally found the update files on the acer website!
i managed to go back to ics then re update to jb
and for a while my screen had no issues but they came back again. Im begining to think that its a hardware related issue because it comes and goes. I am going to see if my warranty with square trade will get it fixed.
My wife has finally decided she'd like me to put a custom ROM on her TF101. I have experience (both good and bad) on my phones and tablets, but she doesn't want hers "messed up." So, I'm a lot less comfortable taking chances with her device than I am with mine. She still loves her TF101 and uses it daily and I don't want to mess it up. Her TF101 is still stock, not rooted, and has the last available ASUS update on it (IML74K.US_epad-9.2.1.27-20120615).
Initially my research indicated this was going to be the quickest and easiest Root/Recovery process I've ever gone though! Download Razorclaw to the device, run it to get root. Download Recovery Installer to the device, run it to get CWM. Easy peasy mac and cheesy. But, Razorclaw seems to be gone. The link to the tool gives a Page Not Found error. Another link on that site outlines a complicated process with a bunch of adb shell commands that made me a little uneasy. Recovery Installer likewise is no longer available at the link given in the first post of that thread. There's a link to a mirror location later in the thread, but if it's not available from the person who made it, then I have to worry. I've also now realized that her firmware version is not compatible with those tools to begin with!
So with my reluctance to upset my wife, some outdated information floating around in the threads, I just wanted to confirm my current plan was the proper way to go.
Use the PERI-0.42 tool to root and install TWRP. I wish I could find a video or screen shots of the process so I can know what to expect. (Or should I use the "1-Click Transformer Root" tool? I'm thinking not as TWRP would be preferable to Rogue Recovery?)
Nandroid backup from TWRP
Flash ROM following ROM's instructions
That about it?
As for which ROM, Root-Box looks interesting, but it says the camera doesn't work and my wife uses the camera (and the CamScanner app) frequently, so that's a no go. So, I was thinking about Paranoid-Android or No-name CM10?
First, Razorclaw only works on a very few firmwares, and the .27 is not one of them.
I wrote a guide on rooting the TF here: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
This uses EasyFlasher and APX mode. It does install an older TWRP, but if you replace the twrp.SOS file in the EasyFlasher "tools" folder with the latest official 2.3.2.3 file found here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob (rename to twrp.SOS and replace the file) then EasyFlasher will flash the 2.3.2.3. EasyFlasher will show the old version in the menu drop down, however it will flash the newer version. If you want TWRP 2.5.0.0 you will need to get it from the thread in the development section.
I have used Peri 0.4 in the past, and it is very easy to follow the prompts. I have not made a tutorial or video of it, but as I said it is pretty straight forward.
As far as the ROM to flash, I am using Domination right now and have flashed the RootBox one as well. At the current time the keyboard dock has little support for both of these ROMs. Many users have had issues with SOD and RR on the CM10.1 no-name. My favorite for stability and features is still TeamEOS 4. It has full dock support and is very very fast and stable.
I am actually looking to restore my EOS 4 Nandroid later today.
Easyflasher is about as no-brainer as you can get, I would recommend using that to install TWRP recovery (note: and update to a newer version as per above poster).
http://forum.xda-developers.com/showthread.php?t=1688012
I've used it with three different PC's and three different TF101's without any issues, and I've used it to revert to stock a couple times on mine.
As far as ROMs are concerned, I have had the best luck in term of a happy blend of fully-baked (everything works)/stability/compatibility/features/speed-smoothness with the EOS 4 ROMS and KAT kernals, though I have as of yet only given the latest PA ROMs (with halo) a quick look. I am admittedly biased on that front since I switched to EOS 3.0 long ago, but I also haven't heard of any complaints from my folks or a friend who are running slightly older versions of the EOS 4 ROM.
Some people say they aren't pleased with smoothness with the stock launcher in EOS (I run Nova Prime on mine and Nova free version on the other two I've helped "upgrade", seems quite smooth to me). I don't know if that is a perception issue, a difference in hardware, or maybe installed apps/widgets. Or if it is still even an issue.
The only issues I have had on mine (SOD's/RR's) in many months was with one short-lived version of the Kat Kernal, which was fixed asap. For me, it's just as stable as the last official ASUS ICS update, and way way more stable the the preceding one.
By all means, give them all a shot, but I have never really had a problem with using EOS as a daily driver.
Thank you, Gentlemen! That's just the sort of help and information I needed. I don't know how I overlooked EasyFlasher in my research.
I had the same firmware - I used PERI to root and went with EOS nightlies v118 and KatKernel v103. Best decision I ever made. Stable, fast and enough features to sink a battleship.
I overlock to 1400mhz using smartassV2 governor. IO scheduler is set to 'sio' (settings->EOS control center->syste,->Performance settings). Since then its been a dream to use, no lag, no waiting. I stuck the dolphin browser on for good measure. Since all that was done, its smooth, fast and really enjoyable. To think a week ago I was ready to sell it and get something new, no need to do that now!
good luck!
About a month ago I had what I thought was a hardware issue with my microSD card reader and started a thread in this subforum about that. Someone suggested I try flashing a custom ROM before I try replacing hardware. Long story short I am now running TeamEOS + Kat kernel and everything is great. Tablet is faster and more stable than it ever was on stock and its nice to be running JellyBean. Only warning, you'll need TWRP not CWM to flash ROMs using Android 4.1+ but otherwise there really isn't too much to worry over.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
I got my wife set up with the Team EOS 4 ROM last night. I ended up having to use PERI instead of EasyFlasher. I couldn't seem to get the tablet into APX mode. Vol UP + Power either did absolutely nothing, or the PC just couldn't "see" the tablet in APX mode. It could see it just fine upon regular boot, and I got the "new device" ding as soon as it started booting, but nothing when trying to enter APX. Vol DOWN + Power, then Vol UP to enter RCK mode brought up the "dead" android with the red triangle for a few seconds, then it rebooted.
But, PERI worked like a charm to root and install TWRP. Then I flashed TeamEOS 4, and she went to work setting it back up.
Thanks for the help!!
HeathicusF said:
I got my wife set up with the Team EOS 4 ROM last night. I ended up having to use PERI instead of EasyFlasher. I couldn't seem to get the tablet into APX mode. Vol UP + Power either did absolutely nothing, or the PC just couldn't "see" the tablet in APX mode. It could see it just fine upon regular boot, and I got the "new device" ding as soon as it started booting, but nothing when trying to enter APX. Vol DOWN + Power, then Vol UP to enter RCK mode brought up the "dead" android with the red triangle for a few seconds, then it rebooted.
But, PERI worked like a charm to root and install TWRP. Then I flashed TeamEOS 4, and she went to work setting it back up.
Thanks for the help!!
Click to expand...
Click to collapse
Awesome!
Check out my FAQ guide on EOS 4 to help explain many questions you may have, and how to set it up the way you (or your wife) likes.
let us know how she gets on with it ,it really is a great rom my tab has never been so quick i use nova launcher and dolphin overclock it in setting to 1400 i have mine on 1504 and still see good battery life ,,,,,,install goo manager from play for updates to rom and also pimp my rom is good for a few tweaks here and there ,,but first when its all set up and working good MAKE A BACK UP i always make back ups as i go along i have 2 all the time only takes 320 seconds ,,,,,enjoy
Sent from my Transformer TF101 using xda premium
She told me last night that she really liked the new ROM, so I think we have a winner. I like it too and wish it was available for the TF700 I recently got!
HeathicusF said:
She told me last night that she really liked the new ROM, so I think we have a winner. I like it too and wish it was available for the TF700 I recently got!
Click to expand...
Click to collapse
[AOSPA-4.2.2][June 13,2013(build #4)]ParanoidAndroid-3.6 | HALO IS HERE
[KERNEL][CM10.1 PA Liquid]bryce[overclock, gov, sched][VER 4.0][04/05]
Glad it was a smooth process. The TWRP install via peri worked? Did you use 2.5 or 2.3?
Thing O Doom said:
[AOSPA-4.2.2][June 13,2013(build #4)]ParanoidAndroid-3.6 | HALO IS HERE
[KERNEL][CM10.1 PA Liquid]bryce[overclock, gov, sched][VER 4.0][04/05]
Click to expand...
Click to collapse
I tried that ParanoidAndroid and it wouldn't get past the boot animation. I didn't try that Kernel, or an older non-Halo'd version of PA.
Thing O Doom said:
Glad it was a smooth process. The TWRP install via peri worked? Did you use 2.5 or 2.3?
Click to expand...
Click to collapse
Yep, the TWRP install via Peri worked flawlessly. It was vesion 2.5 of TWRP (Peri v0.42)
I bought an Acer A700 tablet off ebay, was supposed to be new unused condition. Booted it up and it had no system bar at bottom of page. That means you can't get out of any app you have to reboot, useless. Thru reading on site and exploring this tab i found out it has super user installed on it and on bootup in the left hand corner it reads "boot loader ICS-MRI 7173de1 (unlock mode)" every thing on the tablet seems to work except no navigation bar, no circle in center, and no status info no bar at all full screen. I have played with this thing been on Acer chat and they say hard ware failure. That is before i new it was rooted, i guess that is the reason the update he wanted me to try did not work. I don't know if i try a new OS system if that will even work. I am 68 years old and this is my first android tablet, new ground for me. Most every thing i read is above my knowledge, would appreciate any advice i might just try it. thanks ahead of time
demo mode
Is there a demo mode on this acer A700 and if so where to look thanks
easyreble said:
I bought an Acer A700 tablet off ebay, was supposed to be new unused condition. Booted it up and it had no system bar at bottom of page. That means you can't get out of any app you have to reboot, useless. Thru reading on site and exploring this tab i found out it has super user installed on it and on bootup in the left hand corner it reads "boot loader ICS-MRI 7173de1 (unlock mode)" every thing on the tablet seems to work except no navigation bar, no circle in center, and no status info no bar at all full screen. I have played with this thing been on Acer chat and they say hard ware failure. That is before i new it was rooted, i guess that is the reason the update he wanted me to try did not work. I don't know if i try a new OS system if that will even work. I am 68 years old and this is my first android tablet, new ground for me. Most every thing i read is above my knowledge, would appreciate any advice i might just try it. thanks ahead of time
Click to expand...
Click to collapse
Ok, so whoever you bought it from, told you an outright lie. The bootloader is unlocked, and, it most likely has a custom OS installed on it. You can check this by going into "Settings" "About Tablet" and seeing what is installed on it.
Or,
The previous owner had root access (obviously) and went mucking around with the SystemUI.apk and goobered something up (most likely). In fact, I would guess he had CM installed and didn't like the way the nav icons were (in the center) and tried doing something about it by modifying files he had no idea of what to do.
The most simple fix, would just be to install a fresh version of either a custom ROM, or, revert it back to a stock factory ROM. Both of which are relatively easy to do.
MD
EDIT: Other things to look for now that I think about it. Check your applications and see if any of the following are installed.
Launcher (Nova, Go, etc) These sometimes have an option to disable the system bar (Nav Bar).
ExPosed Installer - This allows loading of custom exposed frameworks mods that several have the option to disable the System Bar (nav bar)
Any Nav Bar/System Bar "Hide" application. These at one time were useful to open more display real estate for games. (not many use them anymore)
Those applications you can safely uninstall through Settings/Applications, then reboot.
Other than that, I can't think of anything else. Will wait till you tell us which OS is installed (CM; Cyanogen Mod, PA; Paranoid Android, etc)
Oh, and one more thing. Stop talking to those folks on Acer Chat. This is a software issue, and not a Hardware issue. This I can promise.
easyreble said:
Is there a demo mode on this acer A700 and if so where to look thanks
Click to expand...
Click to collapse
"Demo" mode, is not a configurable option on most devices. In reality, it is a custom software from Acer that is installed for Store Display purposes. Several items have been left out of the build, specifically to prevent casual customers from mucking things up.
This is generally fixed by installing a full ROM.
MD
Moscow Desire said:
Ok, so whoever you bought it from, told you an outright lie. The bootloader is unlocked, and, it most likely has a custom OS installed on it. You can check this by going into "Settings" "About Tablet" and seeing what is installed on it.
Or,
The previous owner had root access (obviously) and went mucking around with the SystemUI.apk and goobered something up (most likely). In fact, I would guess he had CM installed and didn't like the way the nav icons were (in the center) and tried doing something about it by modifying files he had no idea of what to do.
The most simple fix, would just be to install a fresh version of either a custom ROM, or, revert it back to a stock factory ROM. Both of which are relatively easy to do.
MD
EDIT: Other things to look for now that I think about it. Check your applications and see if any of the following are installed.
Launcher (Nova, Go, etc) These sometimes have an option to disable the system bar (Nav Bar).
ExPosed Installer - This allows loading of custom exposed frameworks mods that several have the option to disable the System Bar (nav bar)
Any Nav Bar/System Bar "Hide" application. These at one time were useful to open more display real estate for games. (not many use them anymore)
Those applications you can safely uninstall through Settings/Applications, then reboot.
Other than that, I can't think of anything else. Will wait till you tell us which OS is installed (CM; Cyanogen Mod, PA; Paranoid Android, etc)
Oh, and one more thing. Stop talking to those folks on Acer Chat. This is a software issue, and not a Hardware issue. This I can promise.
Click to expand...
Click to collapse
You are correct, i will never talk to acer support again. I am getting ready to install a rom if i can figure out which one to start with. It has Adroid Veersion 4.0.4 Kernal version 2.6.39.4+ Boot loader ICS-MRI 7173de1 (unlock mode) It has superuser app installed, I did download an app which gave me a navigation bar that i am using till i can get a rom installed. My problem is that looks like i need to upgrade this 4.0.4 ICS before i can install the up to date roms is that correct. Thanks for helping be get this straight this is a lot for an old man to take in lol.
easyreble said:
You are correct, i will never talk to acer support again. I am getting ready to install a rom if i can figure out which one to start with. It has Adroid Veersion 4.0.4 Kernal version 2.6.39.4+ Boot loader ICS-MRI 7173de1 (unlock mode) It has superuser app installed, I did download an app which gave me a navigation bar that i am using till i can get a rom installed. My problem is that looks like i need to upgrade this 4.0.4 ICS before i can install the up to date roms is that correct. Thanks for helping be get this straight this is a lot for an old man to take in lol.
Click to expand...
Click to collapse
4.0.4 should be the original ICS ROM. If you get it installed, it should get you a locked bootloader, and hopefully offer the upgrade to JellyBean (4.1.x I believe)
Don't worry about age, I'm not far behind you
Have an issue, just PM me and I'll see if I can help.
MD
Moscow Desire said:
4.0.4 should be the original ICS ROM. If you get it installed, it should get you a locked bootloader, and hopefully offer the upgrade to JellyBean (4.1.x I believe)
Don't worry about age, I'm not far behind you
Have an issue, just PM me and I'll see if I can help.
MD
Click to expand...
Click to collapse
No that is what is on my tablet now unlocked and rooted. thanks. i am not clear as to get it upgraded form 4.0.4 and not sure if i need to upgrade to put new rom on it, and which one to work with. I have all my info downloaded on my computer, got to get a cable to work with. Just not sure if i can put the newest version on it without flashing it back to stock locking the boot loader upgrading and then rooting it again just to much i may need to take a break after 3 days of reading, but i have learned a lot. thanks what do u think
easyreble said:
No that is what is on my tablet now unlocked and rooted. thanks. i am not clear as to get it upgraded form 4.0.4 and not sure if i need to upgrade to put new rom on it, and which one to work with. I have all my info downloaded on my computer, got to get a cable to work with. Just not sure if i can put the newest version on it without flashing it back to stock locking the boot loader upgrading and then rooting it again just to much i may need to take a break after 3 days of reading, but i have learned a lot. thanks what do u think
Click to expand...
Click to collapse
Well, 4.0.4 ICS (ice cream sandwich) is the OS these tablets were shipped with. Then, it generally, after some days, would upgrade to 4.1x (jelly bean) Gotta love Google and the names.
Now, considering your tablet has SU (Superuser), and and unlocked bootloader, means somebody mucked with it, hence the missing NAV(Sys) bar. Dude undoubtedly mucked around with things.
As I stated before, this can happen due to several different reasons. How it got to that point, who knows.... In testing ROMs, Ive had this issue by installing a different SystemUI.apk that didn't match all the other files, Or, by "dirty" flashing a ROM without wiping /System partition.
Basically, to get it back to a completely stock A700, you will need to install a stock Factory A700 ROM. the 4.0.4 version. Should be able to find one quite easily, but if not, let me know and I'll help.
Basically, you rename that Stock ROM to "update.zip", copy it to ext SD, then boot the tablet holding "VOL+ then PWR and it "should see the zip and start to install it. "Should".
If not, then I can walk you through the steps to install a custom recovery, and we can do it that way. Acer, with JellyBean, actually has a somewhat recovery menu. Not sure if the 4.0.4 has it or not. Been too long. It may just look for "update.zip" and try and install it.
So will just have to see how it plays out.
For my own, I use "fastboot" so install image files to revert back, but that's just me. Also I have an A701, so it wouldn't do you much good
Same hardware so to speak, except for the 3g part and some different files.
MD