Related
I just got back to my desk and had the notification that an update was available. I ran it and my GTablet is running noticibly faster.
Not sure what was all included, but it was a nice surprise...
I'm ripping it apart, now. 1800 on Quadrant, AB works (so they grabbed something from the new Tegra drivers), no Flash that I can see.
roebeet said:
I'm ripping it apart, now. 1800 on Quadrant, AB works (so they grabbed something from the new Tegra drivers), no Flash that I can see.
Click to expand...
Click to collapse
roebeet,
So this is apparently not the update (with Flash) that's suppose to be coming out mid-December (12/16?)?
Jim
well.....
well it would seem that the update really did fix some problems. Angery Birds now runs on the factory ROM (video driver improvement)
Fixed WPA Enterprise or EAP support?
the factory linked (G-market) seems to work now to.
(For TnT Lite users) I am underwhelmed -nothing I can see worth mentioning, yet. Not even a kernel update.
I'm going to release a TnT Lite 2.3.0 tomorrow most likely, but this is not the 3.0.0 I was hoping for. Maybe you can find a bug fix in there that I might have missed.
Hi,
On my new (just picked up) Gtab, settings=>About is showing:
Tap UI version: 1.0-2736
Kernel: 2.6.32.9-000000-10.8.2-dirty
Build: FRF91
Where is that on the revisions from Viewsonic (e.g., is it the original? Or an update?)?
The reason for the question is that I haven't configured WIFI yet, and am assuming that I'll get that notification when I do, and am trying to figure if I should do the new update or not?
Jim
Update failed.
After the update downloads and then reboots the gtablet, I get an andriod image with an exclamation mark. After power down the gtablet boots find and informs me that the update failed.
The only two customizations I have are:
Z4 Root
ClockworkMod
Does anyone have any suggestions on what I should do?
jimcpl said:
Hi,
On my new (just picked up) Gtab, settings=>About is showing:
Tap UI version: 1.0-2736
Kernel: 2.6.32.9-000000-10.8.2-dirty
Build: FRF91
Where is that on the revisions from Viewsonic (e.g., is it the original? Or an update?)?
The reason for the question is that I haven't configured WIFI yet, and am assuming that I'll get that notification when I do, and am trying to figure if I should do the new update or not?
Jim
Click to expand...
Click to collapse
Hi,
Any comments about the above? The reason for the question is that I'd seen comments about how slow the stock software was, but the tablet seems to be reasonably responsive (to me)...
Jim
Let me know when you solve this one. I have the same problem. I have looked all over Google and nothing about removal
hartTamale said:
After the update downloads and then reboots the gtablet, I get an andriod image with an exclamation mark. After power down the gtablet boots find and informs me that the update failed.
The only two customizations I have are:
Z4 Root
ClockworkMod
Does anyone have any suggestions on what I should do?
Click to expand...
Click to collapse
Hi, Have you tried contacting Viewsonic tech support?
Jim
Even though this update means nothing to my gtab, it certainly does increase my respect for VS. At least they are somewhat following through with what they say.
Wise. Yes, I will do that.
hartTamale said:
Wise. Yes, I will do that.
Click to expand...
Click to collapse
Hi,
This is an older thread:
http://forum.xda-developers.com/showthread.php?t=847653&page=4c
There are some posts saying that that older update doesn't install with CWM installed. Maybe that's your problem?
Jim
jimcpl said:
Hi,
This is an older thread:
http://forum.xda-developers.com/showthread.php?t=847653&page=4c
There are some posts saying that that older update doesn't install with CWM installed. Maybe that's your problem?
Jim
Click to expand...
Click to collapse
It doesn't - you need standard recovery to use their update process. Or, just grab it from here: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3053-user.zip
and drop it somewhere and run cwm against it. It will work, but it will change cwm back to standard recovery.
roebeet said:
It doesn't - you need standard recovery to use their update process. Or, just grab it from here: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3053-user.zip
and drop it somewhere and run cwm against it. It will work, but it will change cwm back to standard recovery.
Click to expand...
Click to collapse
Roebeet does this zip restore the gtab to completely stock?
Bought mine today, charged it up, downloaded the update....and now I am stick in a boot loop. Had not even tried to do anything yet, just getting it updated to the latest. Any ideas what I can do, or am I doomed already?
jfholijr said:
Roebeet does this zip restore the gtab to completely stock?
Click to expand...
Click to collapse
Yes, except the user data which should be retained. This link is straight from TnT Inc. and it's what they've been pushing down to devices today.
Just ran update, and it removed GMail, Gtalk,Maps, and.... Market.
in ADW the icons are there, but they say not installed
Oh Superuser icon same thing.
I'm not expert enough to say this is the answer to a lot of people's problem -- but I'm going to throw it out anyway and hopefully some of the "really expert" people will jump in.
Several times when I have had major problems, I have found that the file structure/files/etc. on my tablet were messed up. Before I could reinstall, I had to re-partition, wipe caches, etc.
I read a lot of posts about people having major lockups or loops and then just trying to reload and reload software assuming that is the only problem -- and not getting good results.
It seems to me that if there is a serious enough malfunction to have to nvflash or do a major recovery -- it would be good to re-partition, wipe caches, etc. in case there is corruption or other structure problems.
What I think we need is for one of the gurus to make us a procedure for "Rebuilding the /sdcard File Structure" (or something like that. Repartition to 2048 and 0 --- and then what else? Which things need to be wiped, formatted, etc.
I'm pretty good a discerning what's wrong -- and I think some of these rebuilds are failing because of this problem.
Right? Wrong? Other ideas? Procedure?
Rev
P. S. -- Enough folks are having these problems right now that this could be an important help for them if I am right......
I PM'd, but the short version for the forum.
I've obviously seen a lot of issues with the TNT Lite 5.0.0, and I've whittled it down to two major problems. First off, not everyone reads instructions. This was fine pre-TNTL 5.0.0 as the instructions really were the same for every version preceding it. But 5.0.0 changed the playing field drastically. Which leads me to the my second point....
I think that some of us have been using mods for so long now that stock was no longer an option without an nvflash. Viewsonic, for example, had a bootloader update in December and I believe a recovery change with 3588. But since a lot of us have been using mods for months, we never got those updates. So, when the time came to revert back to stock, there were problems.
In some ways, TNT Lite 5.0.0 is almost like a tablet cleanup - it's the first update I've had where a stock pre-req was required, and the first one in a very long time where I added a stock bootloader and recovery.
nvflash and tnt 5.0
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Charles77 said:
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Click to expand...
Click to collapse
Not sure -- sounds like you did it correctly. nvflash to 2967, OTA to 3588 and then TNTL 5.00. You didn't install clockworkmod, correct? You need 3588 recovery for this to work.
oops yes I did. ok
Charles77 said:
oops yes I did. ok
Click to expand...
Click to collapse
That would do it. The reason why 3588 recovery is needed is because it updates the bootloader, whereas I believe clockwormod does not.
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
darthbubba said:
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
Click to expand...
Click to collapse
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Deleted dupe
FIXED IT!
jimcpl said:
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Click to expand...
Click to collapse
I FOUND A FIX!!!!
Link here: http://forum.xda-developers.com/showpost.php?p=12030351&postcount=14
I got my wish, now I'm back to status quo ante...
I sent tcrews a PM with this link, hopefully it'll fix his too...
darthbubba et all,
The files from otreblada that are in this download are the same files roebeet and others have provided -- just packaged together in one set.
To nvflash you have to have:
1. the files for the program nvflash
2. the .img, boot, etc. files
3. the USB driver files.
All of these are referenced and available in several places.
I am glad, however, that this might be a solution for some of you who seem to
have recurring problems.
Rev
(At the request of management). Even with all the unsticking / mod intervention and warnings up the wahzoo, there are still a lot of user problems. It may return in a week , but for now it is PULLED. The moderators have hidden the thread, at least for the short term.
For those of you on TNT Lite 5 / TTx, just keep using it and no worries. Once we know where VS is headed, I will have a plan to either ask you to downlevel or upgrade. Again, depending on what they do.
EDIT: For those of you who had issues, could you please write up the steps you used before it failed? It would help everyone to understand why there are so many problems with this 3991 stock / TNTL 5 / TTx. From the posts and PM's I've seen, the majority have been either:
1- The device was flashed with clockworkmod to 3991/TNTL5/TTx and gets stuck at the birds or
2- The device was being prepped to stock 3588 and recovery was broken, after the 3588 reversion.
But I'm hearing that others might have applied all the proper steps and still had problems. We're trying to gauge just where the problem lies with this 1.2 UAT of Viewsonic's.
From my own device, I know that clockworkmod flat-out does not work. That's because the BCT partition is being touched by standard recovery, which clockworkmod does not replicate (and seems to be required). But as long as I have a clean 3588 stock ROM running on my device, I have not had an issue upgrading to 3991/TNTL5/TTx, it has worked for me 100% of the time.
Stock 3991 / TNT Lite 5.xx / TTx .9x backout instructions:
There are two way I know of to back out of these:
- Flash to stock 3588. This assumes you have NOT added clockworkmod and have standard recovery. I have done this several times and never had a problem. Stock 3588 link: http://forum.xda-developers.com/showthread.php?t=842000
- nvflash using bekit's 1105 image: http://forum.xda-developers.com/showthread.php?t=861950. This is still the best way to back out, as far as I'm concerned. You can do a full erase first, to wipe user data as well, thread is here: http://forum.xda-developers.com/showthread.php?t=974422
NOOOOOOOOO. Hopefully VS will decide what they are going to do by the end of the month. I am enjoying TnT Lite 5.0 with no issues at all. Thank you for all your hard work Roebeet, it is unfortunate that so many have had problems with this.
Damnnn, was about to install it
Really sucks that people have had problems maybe people should read and then re-read instructions instead of jumping into things and just assuming devs and mods can help them out. They have a life and dont think that after putting in all the work in to create something they want to hear from whiny a$$, irresponsible people that probably caused their own problem
Now people, like me, that wanted to install cant. nice.
thank roebeet tho and all the other g tab devs
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
One of the obstacles I've had in the last 2 weeks is that this is a UAT, not a released firmware from Viewsonic - so its validity is in question (and understandably so). If they release it with the same bootloader and upgrade requirements, it's going to shake things up here a bit.
I still think the odds are that they will - from their standpoint, they are only supporting stock users so, as long as they can ensure that a user is on 3588 stock, then the upgrade should work. In our case, many of the issues were either getting from a mod to 3588 stock, or using clockworkmod by mistake. Viewsonic doesn't have to worry about either of those issues.
But, there's still the X-factor -- everything is 3588 stock and the upgrade still fails. That might be what's holding them back.
bkbrod said:
I'm running two tap x. 9.0.2 with absolutely no problems. Never did have any problems from the beginning of 5.0.0. I'm am ferry close to being a noob, but I just had the instructions up on my laptop and followed them step by step. Will the new version of clockwork work to go back to 3588 if nessacery?
Thanks for all your hard work Roebeet. I barely use my laptop now that I have this tab.
Click to expand...
Click to collapse
No, clockworkmod won't work (even the new one) - if you wanted to backout to old stock (3558, for example), you'd have to use Viewsonic's recovery. Clockworkmod will kill your device, trust me on that. nvflashing to bekit's 1105 also works, that's how I've been backing out to old stock.
Hmmm
In the last 24Hrs, my gTab v.9.02 just decided to go totally nuts. Constant FC's, lockups, lost sound. Tried every fix listed on XDA, wiped /data , re-downloaded apps from Market instead of restoring with TiB; wotked for a little bit, then the same FC's. And random loss of sound.
Going back to 3558 and CWM and 4.2.5.
We'll see what VS throws our way.
Keep up the good work Mr.Roe!!!
roebeet said:
The backout, btw, is the same -- run stock 3588 and it will downlevel you back to the old bootloader. BUT, make sure it's standard recovery and not clockworkmod.
Click to expand...
Click to collapse
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
TwoTapsX works great for me so far. Had TNT Lite 5.0.1 but it wouldn't run some apps correctly. Tried all the ROMS and they all had sleep of death problems. TwoTapsX works the best for me without giving any glitches.
TwoTaps .9.2
Thanks Roebeet for all you do here. I am finding this ROM easier to work with than any other. I have noted that periodically it will flash the home screen while I am working. Mostly this has been while in Dolphin Brower HD.
jholmes5 said:
Perhaps you should post the method and files in this thread. I know that it's in multiple places, but it never hurts to have them handy in a thread that is this important. Just a thought.
Click to expand...
Click to collapse
Good point, since the other thread is hidden.
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
P00r said:
So far I have installed both version and removed them a few time without issue but the last time I removed it...
I needed to re-flash and wipe a few time, it was booting into the launcher but flashing the screen like crazy...
but since the nvflash recovery doesn't erase the root of the device something was making the screen flash black and reload of the desktop repeatedly.
I was able to run root explorer (that survived the nvflash restore) and copied another rom (calkulin) and even there after using his erase tool and running all wipe available from clockwork and calkulin one after the other... (I load clockwork with the part9.img trick) I had to re flash twice until the desktop loaded properly without flashing..
I would like to find a tool that can erase and rebuild the WHOLE tablet...
I have away updated to 3588 thru the online download each time. Anyway I will hold to the current rom for a bit!
Click to expand...
Click to collapse
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It does not... if you install a custom boot animation it stay there... so it's not full even if after the unit doesn't even start (red text) it's not fully wiped...
I have used clockwork with the partition option, this seem to perform a full format with either the nvflash format or bekit recovery but I am not sure why we can't get this done tru the nvflash...
manikin13 said:
In the dev sub forum there is format utility thread that will completely wipe out all the partitions on the tab.
Click to expand...
Click to collapse
It's in my first post, as well. Run that nvflash first to erase the device, then the bekit 1105 nvflash to complete the process.
What seems to happen is that the old stock / new stock user data setups are not compatible. When going to new stock, it's not so bad because new stock has a better recovery. But when reverting, old stock has a crappy recovery with no user data wipe options. Even Viewsonic understood the limitations which is why they changed their recovery in this UAT of theirs.
I mentioned to jerdog that I wanted to see if I could port their new recovery to old stock (using an old kernel). If that works, we could conceivably offer a "bekit 1105 enhanced" version that adds it. This is better than clockworkmod in that it's the vendor's own recovery and includes the ability to wipe user data, calibrate the device AND update / downlevel the bootloader. For the purposes of getting users backed out if needed, it might be a critical piece of the puzzle.
EDIT: No go. The recovery functionality is actually IN the kernel, my bad. So it can't be ported over. Oh well.
You guys are GODS at this. Simply amazing what you are all doing with this G Tab. So I guess I'm one, of some lucky few, that ACTUALLY READ the install instructions for 5.0 and 5.0.1.
Glad I did because I love the market on this thing.
Eagerly watching what happens with Viewsonic......Any chance they did this as a step to make a Honeycomb upgrade easier? I doubt it since the original G Tab with OTA updates is still crippled.
First off just want to give my thanks to roebeet and the devs here at XDA. I've been running TnT Lite 5.0 / TwoTapsX ??? since the day I bought my Gtablet on 3/11 with no problems. On Friday the 11th I was itching for a Xoom somehow managed to find out Staples had the Viewpad 10 but not in store and somehow managed to end up finding out that Office Depot had the Gtablet for $379.99 in store. I read roebeet's at the time TnT Lite 5.0 thread several times before walking to my nearest Office Depot and brought home a Gtablet within minutes of reading that thread.
Out of the box from 2967 I went to 3588 through stock recovery and not OTA; and then did the same thing to go to TnTLite 5.0.0
I have successfully backed out of TNT Lite 5 in two ways:
1- Re-run a stock ROM. Specifically, I tested 3588. STOCK is important, as the bootloader will be downleveled to the necessary revision.
2- nvflash, using bekit's 1105 image.
In the case of stock, you might get stuck in a boot hang due to the possible need to wipe user data. So, I would recommend running the update.zip off a microSD so you can install clockworkmod .8 (old version) to give you the ability to wipe data.
Once you have old stock back, you'll be able to install older versions of TNT Lite, VEGAn, zPad, etc. as the bootloader is downleveled again.
Click to expand...
Click to collapse
My question to roebeet or anyone who has gone from TnTLite / TwoTapsX back to 3588 using stock recovery. I could swear the above quote from roebeet had an additional line about using stock recovery to run the 3588 stock rom and then wiping user data from stock recovery. From TnTLite 5.0.0 can I go back to 3588 using the stock recovery and wipe user data with the stock recovery after running 3588 but before rebooting?
Android system recovery <3e>
Wipe Data/Factory Reset
Wipe Cache Partition
Click to expand...
Click to collapse
If it is possible to wipe user data after flashing back to 3588 do I need to just wipe data or do I need to use the 'wipe cash partition' as well.
edit: never mind my rambling probably better to wait until we know what Viewsonic is going to do and at that point roebeet will let TTx users know how to proceed from TTx to whatever comes down the pipe from VS
I did have a line (I think in the TwoTaps thread) about reversion and wiping data before you reboot into 3588 stock. But, I tried this once myself and it didn't work.
Maybe I should make a special 3588 "mostly stock" with clockworkmod, as a backout solution (so that, if you get into a bootloop situation post downgrade, you already have clockworkmod installed to fix it - that could work). It's the "wipe data" option, btw.
But first, lets see what the vendor does - if they stick with this new bootloader then TNTL5 / TTx users might already be one step ahead of everyone else - you may not want to backout.
Using it since first release with no problems. I always read the entire first post as well as user issues prior to updating. There are probably many users that try before reading which can lead to issues.
I think this is a great ROM.
Sent from my GTablet-TwoTapsX using Tapatalk
I'm one of the ones who ran into troubles getting this to load and I honestly believed I followed all the instructions when doing so. I've tried mostly all of the custom ROMs and was on the Vegan experimental before loading TTx. Not sure what the problem was but nvflashing with or without recovery didn't take. Kept getting stuck in APX mode. I wasn't really worried since I could always get the tablet to take the nvflash so I just kept playing with it until lo and behold, I was able to enter the TTx recovery mode. Been working fine since. I really like this ROM but I definitely feel like the disclaimer is justified - if you're not into tinkering this isn't something you wanna try.
The only problem I've run into so far is that when I recover my Angry Birds file and run the app it FC's. Runs fine if I just install either version, but when I try to restore my saves by using TB, the app refuses to run. Weird. Other than that, no problems. I don't really like the default browser, but understand that it's required at this point. FLash works fine and I haven't had any issues at all with the market. Even found a few apps that were supposedly only available with XOOM builds.
Many thanks Robeet and hopefully we can get a more "idiotproof" upgrade process.
T
roebeet,
Where can we obtain the bekit 1105 file?
I remember seeing the name somewhere but don't remember seeing the D/L source.
Rev
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.