Related
Hello everybody, before all, I hope there isn't a thread already with this topic, if there is, my apologies.
I have an european (ww) stock rom Transformer on 3.1, I did the first update (3.0 to 3.1) manualy, it worked great, but now, its been since the 3rd of august (OTA 3.2 release date in France) that I've been waiting for my tranformer to receive the OTA, but it just won't.
I've tried to push the "search for update" button thousand times and reboot it almost everyday since then without result.
Do someone have had the same problem and solve it?
By the way, I don't have the keyboard dock yet; doest it play a role in my problem?
I bought my transformer 2 weeks ago i was in 3.1 and i had the update to 3.2 as soon my tab was connected on wifi. But i have the dock.
Are you sure that you never rooted your tab?
You can also ask asus france on their facebook page.
Yes I'm positive, unless the manual 3.0 to 3.1 update implied to root. But I'm quite sure it doesn't.
Apparently you are only offered the update once, if it fails it wont offer it again unless you delete a certain file
Not sure which one it is, but a factory reset should sort it if you can cope with wiping it
that's the odd thing, I wasn't offered it even once. I will search for the file you mentioned and in last ressort, go for a factory reset. But honestly I would prefer not to go that far. That's why I asked for other solutions.
Tried updated manually? ie downloading update from
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
I've tried it too, I've followed the steps, I've put the "asus" folder on a micro sd card, put it in my transformer, but it did not detect the update, I've tried different ways to put the update folder on the sd card so that the tablet can find the update, but still, it didn't work. I just can't figure out why it doesn't want to update.
Thanks for your clues anyway, I will keep searching for a solution or a way to make this manual update...
If I find the thread with the location of the offending file, I`ll update this thread with it
Thanks, it will be very helpfull
seagle77 said:
Thanks, it will be very helpfull
Click to expand...
Click to collapse
You may already know about this forum, but Im beginning to wonder if the posts I am remembering are infact here
http://www.transformerforums.com
Great place either way
Yes great place indeed, i'll try to find it there
I had a similar issue. The tablet update section said 'There is an update available. Please check notifications'. The search for updates button was therefore greyed out. However, nothing ever appeared in the notifications.
I updated manually in the end. However, the update section remains the same: Telling me there is an update and not allowing me to check for any further updates. I'd really like to get this functionality working again.
OK can you please tell me wich folder did you put on the micro sd card for the tablet to detect the update?
Seagle77 go to settings/applications/manage applications/all and scroll down to DMClient click on it and hit clear data and clear catche if i remember right thats what i cleared when the ota failed to install for the first time, once you clear it u might have to restart but it should show you the ota notifiction after that, hope it helps.
V.
I tried it, but after the reboot, there is still no notification of the OTA and nothing more on the update menu.
Update.zip file you downloaded for manual update should go under /removable/microsd/update.zip try placing it there and seeing if u get the notification after a reset , if not then try booting into stock recovery and starting the update from there using update.zip
I've downloaded a file nammed "UpdateLauncher_WW_epaduser8659.zip" on asus website. Do I have to rename it before put it on the micro sd card, or leave it like this?
Ok, problem solved here, someone told me to check the update version on "transformerforum", and the origin of the bug was my first manual update, were I used the US update, istead of WW version.
Therefore, I just needed to update with the US 3.2 file and it worked perfectly.
Thanks for the help given here. Have a good one everybody
Enjoy 3.2 !
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
Hey guys, been a long time lurker here and just encountered my first issue, so made an account to hopefully get some advice.
I received the note 10.1 8010 (UK) as a gift for Christmas. I was disappointed to see it was running 4.0, when devices like the Nexus 7 are already on 4.2. And Germany had the 4.1 update for over a month. Samsung as always refuse to give a solid answer.
I followed a guide to install the German 4.1.1 update. I first installed the German version of ICS via Odin. I then applied the update.zip from here:
HTML:
d-h.st/lLB
Prior to this, I rooted the device, but I believe the above process removed the root anyway.
After my device rebooted, the S Pen isn't working at all. It recognises when I take the pen out, but I cannot use it. It doesn't do a thing. I've read about 1,000 forum threads and cannot find an answer, as to how I can get it working again.
I tried deleting cache and user data, then reapplying the update.zip to no avail.
When I boot up in to recovery mode, it does come up with a message about CSC and then the little drop falls over and I have the usual options.
Any idea what I need to do, to get my S Pen working again? Or what I've done wrong?
Many thanks
This is how I rooted the device.
HTML:
rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
I have a feeling this is the "root" of the issue. I'm not sure how to remove it.
I know previously I wasn't able to change my CSC via CSC switcher, but I am now.
So I guess installing the German ICS and then update.zip, hasn't completely undone whatever rooting it above did.
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Tehkseven said:
Removed the custom recovery and the pen started working again. At this point I was back on ICS, trying to see whether JB was the issue.
Now update.zip will not apply, despite the fact I'm on the German ICS stock. I get an error status 7 in package.zip.
This is the worst experience I've ever had, with any device in my life.
If this wasn't a present I'd have smashed it in to tiny pieces. I will never buy a non Nexus device ever again.
I know this may seem trivial, but when I'm running 4.2 on all other devices, I don't want to be stuck on 4.0 with my brand new tablet.
Samsung have really put me off ever buying their devices in the future.
Click to expand...
Click to collapse
This a pretty bummer situation. Sorry you're dealing with it.
I find this interesting, as I followed the exact same procedure to root as you. I haven't experienced any pen issues though.
Could it be the 4.1 you flashed?
This is one of my fears too, so I really hope this can be solved.
I finally managed it.
I downloaded a different German ICS from a different guide and this time it worked no problems.
The one that worked, had a file name: N8010XXALI3_N8010OXAALI3_DBT
Update.zip worked first time after I installed the above ICS.
Hope that helps.
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
Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?
WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions
Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.
Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope