Related
Hi all, I'm quite new to this forum and I hope I dont break any netiquette with my question.
Now I have a N1 I bought on ebay, used, rooted and perfectly functioning.
I don't remember how, but I was able to update it to FRG83D downloading the rom, renaming it, copying on my sdcard etc ...
Now ...
I can't update to FRG83D.
I understood that having a rooted N1 NO OTA UPDATE shall ever work for me, not the manual update is available.
I was able to skip the "no signature verification" error suing clockwork mod, but i can't install the patch anyway, the system alway replies "assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk" ... then a serie of letters and number follows.
I know nothing about this, I must confess, but my suspect is that the update fails because something doesn't match between the update and the ROM which is working on my N1 (which is by the way the original one build frg83d
baseband version
32.36.00.28U_4.06.00.12_7
kernel
2.6.32.9-27240-gbca5320 android-build apa26 #1
Any sugestion ?
I mean and idea about where I can download a FRG83D version suitable for my phone ?
If you just want stock with very little tweaks, may i suggest Geo's Rom. It's basically the latest stock rom w/ superuser, busybox, trackball alert etc. Runs amazing too =)
As for breaking any netiquette, you're suppose to post this in the questions forum not the general. Have fun with your phone.
worked!
Thanks Mokurex!
It worked.
It's unbelievable.
I spent three nights in search of an answer, and then you solved it in few seconds.
I'm new to Android, and I must confess that I'm quite disoriented.
There hare hundred of versions, produced by individuals, companies, etc ... The one I used, I mean the one you suggested me, seems to be the fruit of an individual's work in the US.
It's ok to me, sounds and works good.
But It's not the original one, I mean the one released by ... Google ? or ... what ?
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1, the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
I understand that we can rely of forums and on kind people like you, but having some clear cut guidelines would be very useful.
... and looking at the future ... I guess I'll have the same problems when I'll have to update to Gingerbread.
I's very frustrating to search the web for a suitable ROM for your phone ...
stefanopelloni said:
[snip]
But It's not the original one, I mean the one released by ... Google ? or ... what ?
Click to expand...
Click to collapse
No, it's not the original. That one is deodexed, so any future OTA updates will not work (as Google's stock ROMs and updates and not de-odexed). You will have to wait until someone repacks the update, then apply it.
stefanopelloni said:
[snip]
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1,
Click to expand...
Click to collapse
Did you read the wiki? There are lots of posts/threads/guides available.
stefanopelloni said:
[snip]
the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
Click to expand...
Click to collapse
What are you trying to say? Phones running a rooted, but otherwise stock ROM will certainly received the OTA updates. Now if you use a non-stock ROM, you may or may not receive the OTA update. But whether you receive it or not, you will not be able to apply it as is, until someone repacks it (unless you are using the stock ROM, rooted or not).
I believe you have to use the stock recovery as well if you wanted to update via OTA.
If you want to get Gingerbread by way of OTA, then revert to stock rom and recovery. Everything you need is in the sticked thread in the development section.
Mokurex said:
I believe you have to use the stock recovery as well if you wanted to update via OTA.
[snip]
Click to expand...
Click to collapse
No, you do not. You just need a newer version of Amon_RA (1.9+) or CWM.
Thank you for the correction.
Efrant, Mokurex,
perhaps it's my problem.
My original plan was to restore my phone is a status capable of receiving OTA updates. Considering that I'm not an IT expert it would be easier for me ho have such a phone.
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Mokurex helped me a lot (actually, solved my problem by now) suggesting that version of the ROM (I mean Geo's one) but it's the fruit of a work of an individual. I'm very grateful to him as well, but who knows about the future. Will Geo provide a similar version of Gingerbread as well ? Because without him I can't upgrade.
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Geo has been quick to update his rom to the newest version. To upgrade to gingerbread, i'd assume that it would be like flashing any other custom rom, but there might be a bit more steps involved.
If you want completely stock, no root whatsoever, go here.
stefanopelloni said:
[snip]
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Click to expand...
Click to collapse
I said it before, and I'll say it again: rooting has no bearing on the phone's ability to receive and install OTA updates -- what matters is which ROM you have. I rooted my phone when I bought it, and it had Eclair on it. I have received EVERY OTA update without any problem.
stefanopelloni said:
[snip]
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Click to expand...
Click to collapse
That is probably because you were not using a stock ROM...
stefanopelloni said:
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Click to expand...
Click to collapse
If you want a stock ROM, you can go here: http://developer.htc.com and download a Nexus One image to your sdcard, rename it to PASSIMG.zip and boot the phone into bootloader (by holding the trackball and powering up the phone). It should automatically detect the file and allow you to flash it.
Files from the site are official. If you get them from anywhere else, you can't really know what's been modified.
Dear Efrant,
if you were a girl, and in Italy, I would probably kiss you.
Now I have a bright-clear picture of the situation.
During the next holiday, I'll try and flash a stock version of the OS and then try the OTA update.
By now, the version mokurex suggested me work brilliantly and after so many nights wasted in a desperate search of an answer my myself i'm going to have a break.
... but thanks a lot. thanks indeed !!!
Sorry to disturb you again Eftant.
The fact is that today decided eventually to follow your step, but encountered another unexpected problem.
downolaed the original HTC rom - done
renamed it passimg.zip - done
turned on the N1 pressing trackball - done
expected detection of PASSIMG.zip - done
opening passimg.zip - done
checking passimg.zip - done
and then .. nothing
once the N1 load the passimg.zip file (i notice it from a loading bar on the upper right conder of the phone) it just allow me to
1)run bootloader agan
2) lock sim
3) restore something ...
... and that !
No possibility to "flash" rom as you wrote.
Did I miss anything ?
I see from the web that a lot of people bring back the N1 to the stock image using SDK from PC (MAC in my case) but the steps are not so clear considering the fact that I'm not that comfortable with the shell and the Android SDK is not intuitive (... to me).
Thanks in any case for your attention!
Try wiping your device then download the FRF91 image from the same site, rename it to PASSIMG.zip and save it to the root of your sdcard. Put your sdcard back into your device, and boot into the bootloader (by holding down the trackball as you push the power button). Once it flashes, wait for the OTA to FRG83G. Some users have said that the later images don't work using, particularly if you have updated to the 0.35 version of the bootloader.
Hey guys,
If you're having trouble with the new 2.2.2 update (getting stuck at 20%, seeing a triangle with an exclamation point, etc.) I'll be glad to help you guys.
I had the issue myself, but now I fixed it and am running 2.2.2 thanks to NFHimself.
He was the one who linked me all of the code, so creds goes to him, but I'll be putting up a step-by-step guide later tonight on how to update. Be patient! It will work.
Pm me and I will link you the thread I make later, or just check atrix general and android development later tonight/tommorow.
Cheers Canadian users! Dont have fear, you can update!
I got the same issue. The help will be appreciated. Keep us posted.
Sweet..I love step by step guides. I'll be keeping my eyes open for this!
Will you also be including a way for users with the French SBF to install this update?
IrshaadH said:
Will you also be including a way for users with the French SBF to install this update?
Click to expand...
Click to collapse
I would immagine that the process would be the same if I have rooted and flahsed the SBF from the OLYEM 2.1.1 SBF from here... ?:
http://forum.xda-developers.com/showthread.php?t=1070076
The guide will only be for bell firmware. If you're running an international firmware its much more complex, and I never swapped to an international firmware, so I can't say how to do it. However, NFhimself managed to go from the french SBF to bell 2.2.2 and bell radio. Not sure how exactly, he's a master with ADB and code. He's the one who has made the bell deodex files, as well as many bell atrix mods. Contact him if you need help going from french sbf to bell, since he went through the process. However, know you'll need pretty extensive programming/code knowledge.
The guide will be up asap, im studying for exams / beginning to write it right now.
To clarify: the guide will show all bell users who are on 0.37.4 how to update who have modified system files (ie. webtop hack, deodexed, etc.) to bell android 2.2.2. A clean update as well, not some weird glitch of an update.
OK, after reading a bunch of posts today, I'm dizzy as h3ll, and very confused.
We have two updates that came out OTA in the past couple of days.
1.139.04_4.010.40_COM_GEN1
And then we have
1.141.07_4.010.13_COM_GEN2
I bought my Tablet at Walmart in Watertown, NY, and it was a GEN1 with HC 3.01 on it.
Now some are saying that Acer switched over to GEN2 for US tablets as of the 3.1 update. (I'm not naming names).
I've run multiple custom ROMs on my tablet, and recently went back to see how stable the Acer releases have been. I downloaded both of the files listed above, (actually 11 GEN2 then OTA update to 13).
One person stated that the GEN1 was an Australian release, and that the GEN 2 was the US release. I can confirm what someone else said, that they both have GPS.conf files for north America, not Europe, nor Australia. Now I've seen many custom ROMS with different GPS.conf files in them ie: Europe, North America, etc.
Here's my question, how can we know for certain #1 which update is indeed for which country, as they're both seemingly configured for use in North America, unless Acer is really messing things up and issuing updates for Australia with the GPS configured for north America, and it certainly wouldn't surprise me.
And #2, which update is the newest, as someone else stated that the prefix with the highest number is the latest version, and yet another said it was the one with the higher end number is the latest!
If someone knows the real answer to these two questions, please stand up!
Otherwise it's going to get very confusing when trying to give advice to others asking questions about updates if they don't like waiting on Acer to get their act together.
TIA
XBoxD00D said:
OK, after reading a bunch of posts today, I'm dizzy as h3ll, and very confused.
We have two updates that came out OTA in the past couple of days.
1.139.04_4.010.40_COM_GEN1
And then we have
1.141.07_4.010.13_COM_GEN2
I bought my Tablet at Walmart in Watertown, NY, and it was a GEN1 with HC 3.01 on it.
Now some are saying that Acer switched over to GEN2 for US tablets as of the 3.1 update. (I'm not naming names).
I've run multiple custom ROMs on my tablet, and recently went back to see how stable the Acer releases have been. I downloaded both of the files listed above, (actually 11 GEN2 then OTA update to 13).
One person stated that the GEN1 was an Australian release, and that the GEN 2 was the US release. I can confirm what someone else said, that they both have GPS.conf files for north America, not Europe, nor Australia. Now I've seen many custom ROMS with different GPS.conf files in them ie: Europe, North America, etc.
Here's my question, how can we know for certain #1 which update is indeed for which country, as they're both seemingly configured for use in North America, unless Acer is really messing things up and issuing updates for Australia with the GPS configured for north America, and it certainly wouldn't surprise me.
And #2, which update is the newest, as someone else stated that the prefix with the highest number is the latest version, and yet another said it was the one with the higher end number is the latest!
If someone knows the real answer to these two questions, please stand up!
Otherwise it's going to get very confusing when trying to give advice to others asking questions about updates if they don't like waiting on Acer to get their act together.
TIA
Click to expand...
Click to collapse
Wow no answers to this post. Especially with everyone knowing everything in other threads.....amazing!
Here we go...This is from Acer's patch documents and best shows the current separate code trains...
A. Countries: UK/France/Italy/Spain
- Affected OS versions:
Acer_A500_4.010.22_COM_GEN1
Acer_A500_4.010.30_COM_GEN1
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.38_COM_GEN1
Acer_A500_4.010.38_7.006.01_COM_GEN1 (3.2)
B. Country: USA
- Affected OS versions:
Acer_A500_4.010.07_COM_GEN2
Acer_A500_4.010.08_COM_GEN2
Acer_A500_4.010.09_COM_GEN2
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.10_COM_GEN2
Acer_A500_4.010.11_COM_GEN2
Acer_A500_4.010.13_COM_GEN2 NEW
C. Countries: Singapore/Malaysia/Thailand/Philippines/India/Vietnam/
Indonesia/Australia/New Zealand
- Affected OS versions:
Acer_A500_4.010.12_COM_GEN1
Acer_A500_4.010.24_COM_GEN1
- After installing the update, you are advised update your tablet’s operating system to:
Acer_A500_4.010.40_COM_GEN1
Acer_A500_4.010.40_7.006.03_COM_GEN1 (3.2)
D. Countries: Taiwan/Hong Kong
- Affected OS version:
Acer_A500_4.010.23_COM_GEN1
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.39_COM_GEN1
Acer_A500_4.010.41_COM_GEN1
Acer_A500_4.010.41_7.006.01_COM_GEN1
I'm trying to sort through them to perhaps find/explain some differences.... other than the wifi driver (different countries allow different channels).
The one thing I can tell you is that no matter which rom i've looked at, all of the roms have the following lines in build.prop..
ro.product.locale.language=en
ro.product.locale.region=US
That said, we can add LAZY to the description of ACER. The thing that makes this most murky is the fact the people like us are more inclined to find instant gratification. That is, we download the newest version of the rom (or so we think) rather than the newest regional version. If you look at the above listings and you are on one of the lower versions for any of the above regions, looking for the OTA on the tablet itself will lead you through the upgrade paths listed for each region.
In all honesty we should have a mod sticky a thread for this so all inbound noobs can see it and avoid some grief.
dottat said:
In all honesty we should have a mod sticky a thread for this so all inbound noobs can see it and avoid some grief.
Click to expand...
Click to collapse
I agree! It's tough enough as it is helping ppl with the current naming process by Acer, or lack thereof!
Should, could, would, good luck!
Moving to Q&A.
PS: Every Q? thread should be posted in Q&A.
Of course the naming convention is only confusing if you're going off the rails with your tab - those of us who just leave them stock and install OTA's don't particularly care or pay attention to the update names.
Buy tablet > use tablet > get incremental > use tablet > get 3.1 > use tablet > get incremental > use tablet...
I'm waiting until the life cycle on this puppy nears its end before I do any ROM'ming. I'm a little paranoid that way but mostly I'm happy with vanilla. I also get confused by all the different steps - update, backup, clear this, clear that, install this, then update with that... I know, it can't be that complicated but I'm easily ditractac....
Oh look, a butterfly!
...
As I was saying, when you spread the peanut butter over the toast you could have added the honey first, thereby eliminating the danger or bread-breakage and...
gammaRascal said:
Of course the naming convention is only confusing if you're going off the rails with your tab - those of us who just leave them stock and install OTA's don't particularly care or pay attention to the update names.
Buy tablet > use tablet > get incremental > use tablet > get 3.1 > use tablet > get incremental > use tablet...
I'm waiting until the life cycle on this puppy nears its end before I do any ROM'ming. I'm a little paranoid that way but mostly I'm happy with vanilla. I also get confused by all the different steps - update, backup, clear this, clear that, install this, then update with that... I know, it can't be that complicated but I'm easily ditractac....
Oh look, a butterfly!
...
As I was saying, when you spread the peanut butter over the toast you could have added the honey first, thereby eliminating the danger or bread-breakage and...
Click to expand...
Click to collapse
Yeah bro, you best stick to OTA, you don't want to get too confused, and overtax yourself lol
Now... if we could get custom rom devs to make a couple different versions we'd be in business too...
Please tell me where to get the kernel module tun.ko 2.6.36.3Hoeyillian-3.4 +
shurpa said:
Please tell me where to get the kernel module tun.ko 2.6.36.3Hoeyillian-3.4 +
Click to expand...
Click to collapse
I wouldn't try to get that as a standalone file unless you *really* know what you are doing, like an experienced linux sysadmin/developer. The simplest thing to do would be to just install the latest HoneyVillain kernel, currently at 3.6.
Frankly, I'd like to see something (preferably from Acer) about what each update actually provides us PRIOR to accepting the OTA. Heck, I can't even find that information when upgrading custom ROMs from like v3.2 to v3.2.1. I'm the type of person who always waited to see how much (for example) SP3 would break Windows XP before installing it myself.
are these ics or hc if they are ics check out my article on how to unbrick your tablet(also how to manually update to ics) PS: if you have already upgraded to ics via custom rom or acer you probably wont be able to go back to HC
http://forum.xda-developers.com/showthread.php?t=1699277
using custom rom is more simple.
Advice for interested Newbies for updating
gammaRascal said:
Of course the naming convention is only confusing if you're going off the rails with your tab - those of us who just leave them stock and install OTA's don't particularly care or pay attention to the update names.
Buy tablet > use tablet > get incremental > use tablet > get 3.1 > use tablet > get incremental > use tablet...
I'm waiting until the life cycle on this puppy nears its end before I do any ROM'ming. I'm a little paranoid that way but mostly I'm happy with vanilla. I also get confused by all the different steps - update, backup, clear this, clear that, install this, then update with that... I know, it can't be that complicated but I'm easily ditractac....
Oh look, a butterfly!
.....
Click to expand...
Click to collapse
Pretty Butterflies.
Seriously, I took the same tact with you use stock...use stock..., however, I broke down about a month ago, after installing android 4.2 on my wife's HP Playbook (the dead Palm version...)
I got jealous, so used afterOTA to install a new recovery ROM, and root the tablet (also used blackthunder's ap500apx flashing tool), and between the two of them got jb (4.1.2 up and running very smoothly). Now that I installed the skrillex clockwork mod 9.x I now have a great recovery tool, and just installed
4,2.2 on my tablet, with less then 30 minutes to take care of it.
updating rules:
a) read the ENTIRE thread (use multiple tabs.
a1) use a new window for each new topic or sw you investigate.
a2) download all the sw to ONE folder so you can find it.
b) READ the ENTIRE thread (oh, did I say that already?... I mean REALLY read EVERY thread to the END!!
b1) open the first page. open the last page in a new tab, or work your way backwards. yes, 42 pages of updated discussion is difficult, but so is
repairing a bricked tablet.
anyway that's my 25cents worth.
good luck
need to reinstall original os A500
XBoxD00D said:
OK, after reading a bunch of posts today, I'm dizzy as h3ll, and very confused.
It was during an update (and my forgetting pattern) when my A500 failed. I am also dizzy from all this and Acer isn't any help AT ALL. Just added insult to injury as far as I'm concerned. One has to jump hoops just to find a contact number or email.
So, vent over, does anyone have the original OS for the A500 that I can easily (with instructions) get my tablet up and going with again? I did learn that when using the paperclip method, one has to release the power switch and repress again. Just looking for some assistance yet once again. Thanks - if there were a pill for this, I'd take it.
Click to expand...
Click to collapse
ivibre said:
OK, after reading a bunch of posts today, I'm dizzy as h3ll, and very confused.
It was during an update (and my forgetting pattern) when my A500 failed. I am also dizzy from all this and Acer isn't any help AT ALL. Just added insult to injury as far as I'm concerned. One has to jump hoops just to find a contact number or email.
So, vent over, does anyone have the original OS for the A500 that I can easily (with instructions) get my tablet up and going with again? I did learn that when using the paperclip method, one has to release the power switch and repress again. Just looking for some assistance yet once again. Thanks - if there were a pill for this, I'd take it.
Click to expand...
Click to collapse
I'm having the same problem and really will do anything to get it working again. You can use timmy dean's rollback tool, if you can get the 7z open. Neither lubuntu nor Windows XP will open it. So far I flashed a V8 bootloader, but I can't use blackthunder's tool for some stupid reason, and when I contacted Acer (more like called them out on Facebook with a rant for thousands of people to see) they said they'd fix it under warranty conditions even though mine ran out.
They then proceeded to tell me when I went to double check that the case would be valid before I sent it to them, they said it expired and that I would have to pay $160 just to send it to them and not including parts. About a year before it stopped working, I sent it in to get the light board fixed (it was broken when I woke up one day) and I never opened the back of before. Three days ago I opened the back only to see that a cord was unplugged (promptly plugged it back in) and that multiple screws were missing. I nearly "contacted" them again, but decided to continue my search for a solution on here.
As I stated in the title. Anyone know how long the wait may be before those of us with unlocked bootloaders and rooted Xplays are able to get this in a ftf or update.zip format to flash manually? I am liking the 720p camera and of course the auto brightness option.
Or if someone knows if its a pain in the ass to create one of the above? I am sure that in order for any of this to happen someone would have to gain root access and then flash a recovery to do a complete backup, then piece it together and or convert it to one of the above formats.
Are you sure 2.3.4 is out for Verizon?
2.3.3 came out like 5 days ago.....
sorry, your right. I meant 2.3.3. By the way, would it be possible to flash a 2.3.4 ROM from the UK and then just flash the CDMA files from Frasertags ROM?
Do we know what the changelog is or the Verizon update? I cannot find it anywhere.....
Also, I now its the wrong thread but if I relock my phones bootloader and relfash stock ROM so I am unrooted, and I flashed the new 2.3.3 ROM, if I wanted to unlock the bootloader then would it be the same key I used to unlock the first time?
jgregoryj1 said:
sorry, your right. I meant 2.3.3. By the way, would it be possible to flash a 2.3.4 ROM from the UK and then just flash the CDMA files from Frasertags ROM?
Do we know what the changelog is or the Verizon update? I cannot find it anywhere.....
Also, I now its the wrong thread but if I relock my phones bootloader and relfash stock ROM so I am unrooted, and I flashed the new 2.3.3 ROM, if I wanted to unlock the bootloader then would it be the same key I used to unlock the first time?
Click to expand...
Click to collapse
Sorry I run my phone stock not sure if any of that will work.
As for the changes, there is no changelog but there is another thread I think in Q&A where everyone has been documenting changes. 720P video recording is not one of them.
The major ones: better autobrightness and a way to disable it and Media Server (awesome feature, stream stuff from your phone wirelessly to any DLNA device).
Thanks Rogue, I found the thread about the changelog stuff..... where people are posting there findings. The 720p is from 2.3.4.
To answer earlier questions: If you re-lock your bootloader you _SHOULD_ be able to safely apply the OTA (or a flash file) and then re-unlock using the same code. However, I would probably try to do it via SEUS instead of the OTA. That way you can have the files ready just in case you need to unbrick and re-do it. There are unbrick from bad OTA threads around in case you booger the thing.
I wonder if somebody who hasn't unlocked could use SEUS (SonyEricsson Updater Service software) and download a copy of the flash and post it up for us. I imagine the Devs would like to have it, as well as the general unlocked community. I saw what looked like a link to a .IMG file over in the dev section that somebody was claiming was the R800x 2.3.3 (the new OTA) but I haven't verified it yet.
Unrooted my tab and trying to get it back to the latest official version, but I'm having loads of trouble. Please help. Thanks!
My model number is A500, Android version is 3.0.1, kernel version is 2.6.36.3-00001-g44a8bac and build number is Acer_A500_1.145.01_COM_GEN2
This is the tab that best buy had on sale a few weeks/months on sale. Only 8GB of on board storage.
I have found threads with official updates, but don't know which is safe to install. They are all the same version but have different build numbers so I don't know which build number corresponds with my tab
I think I know the answer to this already, but can I jump from 3.0.1 to 3.2.1?
Anyways please help. I do appreciate it.
Thanks!
EDIT: 99 views and no replys? Do you guys not know the answer or are just being jerky? This is seriously my first post let alone question on the acer threads. I usually get things pretty easily, but I am having trouble on this one so it's not like I'm being lazy or asking a stupid question. Can someone help either by providing some answers or let me they don't know how to fix this??
Thanks
EDIT 2: Close mods
Not sure if you're still with us -
interested in knowing why you have not rec'd any OTA before now -unless you've been rooted from the start like i was when i got mine!!!
you also have to be stock, as in factory stock! the update checks a whole lotta stuff before it will install . If the system doesnt stack up the update will fail. So if you have deleted or frozen bloatware apps they will need to be restored, along with modded build props etc. factory data reset and full wipe fixes that problem, but Most people want to keep their data if they can and isn't an option. The update itself should leave everything in place. Mine did.
u need a Gen_2 build. I'm not familiar with your build number or upgrade path for 1.145, but you should receive an OTA for 3.1, 3.2 and the latest 2 for 3.2.1.
if u just wanna install one of the updated custom stock roms with root or cwm, you should be fine with any build and yes you can go straight to 3.2.1 from 3.0.1, but no OTA with these roms
ACis0014 said:
Unrooted my tab and trying to get it back to the latest official version, but I'm having loads of trouble. Please help. Thanks!
My model number is A500, Android version is 3.0.1, kernel version is 2.6.36.3-00001-g44a8bac and build number is Acer_A500_1.145.01_COM_GEN2
This is the tab that best buy had on sale a few weeks/months on sale. Only 8GB of on board storage.
I have found threads with official updates, but don't know which is safe to install. They are all the same version but have different build numbers so I don't know which build number corresponds with my tab
I think I know the answer to this already, but can I jump from 3.0.1 to 3.2.1?
Anyways please help. I do appreciate it.
Thanks!
EDIT: 99 views and no replys? Do you guys not know the answer or are just being jerky? This is seriously my first post let alone question on the acer threads. I usually get things pretty easily, but I am having trouble on this one so it's not like I'm being lazy or asking a stupid question. Can someone help either by providing some answers or let me they don't know how to fix this??
Thanks
EDIT 2: Close mods
Click to expand...
Click to collapse
This is a known issue and too many reasons to list. But, basically you are not 100% or it thinks that (checksums different) etc.
So, just flash directly to 3.2.1 GEN2
Mods please close. I was able to fix the issue
I was rooted and had to flash to 3.0.1 or 3.1 before unrooting with the iconia apk. Then I used the acer recovery tool to flash stock recovery. But after flashing stock recovery and unrooting I couldn't get any OTA updates. I re-read some the posts and manually updated to 3.2 after decrypting the zip. After updating I checked for new OTA updates and sure enough found both. Now I'm back to stock 3.2.1. Patiently waiting for ICS
Glad you got it working.