My Experience Upgrade to ICS - Acer_AV041_A100_1.017.00_PA_CA - Acer Iconia Tab A100

I'm posting this because I didn't see anybody with this build yet...
Okay, so here is my story, like most of you, I was pretty frustrated that my stock build wasn't getting ICS, I was running 2.007.04_EMEA_GB. First off I wasn't sure if the EMEA_GB version is designed for Canada (since I bought my A100 off of someone from Craigslist). I took many backups of my system by using the DD commands before trying the leaked versions of ICS that were posted by Vache, starting in March. When 14 was out, I loaded it up but really didn't think it was the "official" firmware, as there were still a few lingering issues with the ICS build, so I went back to HC (using the Gen2 HC full update package) rooted it, then and reimaged all of the partitions with the old DD images I kept from the original firmware that shipped with my device.
ICS was supposed to have been released yesterday, and I had in my mind from March that I was going to have ICS from Acer as my birthday present... and Today is my birthday (haha) so I had to make it happen! I didn't want that v14 on there, and I had read in a different thread that an A100 actually had a build 15 on it, which sort of verified hypothesis that v14 might not be the official firmware, so I went ahead and flashed the original GEN1 stock Honeycomb rom, Acer_A100_1.014.08_COM_GEN1 : http://vache-android.com/v1/download.php?fileID=109 .
Once that was flashed, (with a data reset) I immediatley tried to run an update check but it told me that the device was up to date (haha what a lie). Since this was about 2am and I was supposed to be sleeping, I let it sit for about an hour before trying the update check again. The device had 4 updates in total, after the second update, it changed to a PA_CA release, then before the 4th update came in, the update wizard warned me that Kobo and Adobe Flash wasn't part of the system, but could be downloaded. I figured this was the ICS update, and I wasn't wrong. Once everything was done updating (at about 3:30, the Acer update servers were really fast at that point LOL) I checked the system version and found that I was on v17_PA_CA. Attached is my screenshot.
After running this version for ~8 hours, I havent had any freezing, menu transitions are very smooth, no touchscreen bugs yet either. This build feels like it is a perfect match for my hardware. Also, it looks like the battery life is better, but only time will tell on it.
I have attached a screenshot of the build that I'm on as well, just in case anyone has any questions. It's really possible that since I used the original firmware that it checked in to the acer servers as a new device and it should send me all the updates in one shot.

danifunker said:
I'm posting this because I didn't see anybody with this build yet...
Okay, so here is my story, like most of you, I was pretty frustrated that my stock build wasn't getting ICS, I was running 2.007.04_EMEA_GB. First off I wasn't sure if the EMEA_GB version is designed for Canada (since I bought my A100 off of someone from Craigslist). I took many backups of my system by using the DD commands before trying the leaked versions of ICS that were posted by Vache, starting in March. When 14 was out, I loaded it up but really didn't think it was the "official" firmware, as there were still a few lingering issues with the ICS build, so I went back to HC (using the Gen2 HC full update package) rooted it, then and reimaged all of the partitions with the old DD images I kept from the original firmware that shipped with my device.
ICS was supposed to have been released yesterday, and I had in my mind from March that I was going to have ICS from Acer as my birthday present... and Today is my birthday (haha) so I had to make it happen! I didn't want that v14 on there, and I had read in a different thread that an A100 actually had a build 15 on it, which sort of verified hypothesis that v14 might not be the official firmware, so I went ahead and flashed the original GEN1 stock Honeycomb rom, Acer_A100_1.014.08_COM_GEN1 : http://vache-android.com/v1/download.php?fileID=109 .
Once that was flashed, (with a data reset) I immediatley tried to run an update check but it told me that the device was up to date (haha what a lie). Since this was about 2am and I was supposed to be sleeping, I let it sit for about an hour before trying the update check again. The device had 4 updates in total, after the second update, it changed to a PA_CA release, then before the 4th update came in, the update wizard warned me that Kobo and Adobe Flash wasn't part of the system, but could be downloaded. I figured this was the ICS update, and I wasn't wrong. Once everything was done updating (at about 3:30, the Acer update servers were really fast at that point LOL) I checked the system version and found that I was on v17_PA_CA. Attached is my screenshot.
After running this version for ~8 hours, I havent had any freezing, menu transitions are very smooth, no touchscreen bugs yet either. This build feels like it is a perfect match for my hardware. Also, it looks like the battery life is better, but only time will tell on it.
I have attached a screenshot of the build that I'm on as well, just in case anyone has any questions. It's really possible that since I used the original firmware that it checked in to the acer servers as a new device and it should send me all the updates in one shot.
Click to expand...
Click to collapse
cool beans...im on pa_ca as well...but sticking on HC for now to crack the darn sbk.
they must be planning future updates as your image version still looks like it could be a release candidate. :-D
glad to hear theres several builds being pushed tho!
Sent from my SGH-I897 using xda premium

I was on 3.2.1 COM_GEN2, and couldn't upgrade, so went back to 3.2 GEN1 from there going a similar path as you did: 4 updates, and the last being PA_CA. I that time I though "almost there", but found I no longer have spanish language as an option
My first impression: ICS is faster and better looking. But,
Do you know where can I download a language patch to it?

on a side note...fellow rogers user...you jumpin on the one x ?? i just ordered mine

rising power said:
I was on 3.2.1 COM_GEN2, and couldn't upgrade, so went back to 3.2 GEN1 from there going a similar path as you did: 4 updates, and the last being PA_CA. I that time I though "almost there", but found I no longer have spanish language as an option
My first impression: ICS is faster and better looking. But,
Do you know where can I download a language patch to it?
Click to expand...
Click to collapse
I've the same problem, not italian language and "PA_CA" Build.. WHY ??

i have Acer A100 in Russian
and yesterday it updated to 4.0.3
i lost my language in OS and apps
version PA_CA too
((((((((((

ptesmoke said:
on a side note...fellow rogers user...you jumpin on the one x ?? i just ordered mine
Click to expand...
Click to collapse
Hehe cool, when it comes to phones, I need a keyboard, so I actually picked up a bell Moto xt860 and unlocked it. I might be stuck with this one for a while since I hear keyboard android phones don't sell as well as blackberries up here. We will see what happens to RIM...
My other goal is not to sign another contract again, and I have a really sweet deal with Rogers now also...
Sent from my XT860 running ICS

devitos said:
i have Acer A100 in Russian
and yesterday it updated to 4.0.3
i lost my language in OS and apps
version PA_CA too
((((((((((
Click to expand...
Click to collapse
It really looks like PA_CA is geared towards Canada, with only English, French and Chineese (simplified and traditional). I don't know another way of pulling another language, unless you can grab them from the WW 014 package somehow... let me look at it
Sent from my XT860 running ICS

I am very interested - how Canada firmware got in Russia)))
acer have a bug in service

Isn't possible flash directly Acer_A100_AV041_1.014.00_COM_GEN1 ? (to gets languages)

This is the third post today I have read someone say that the build 14 is not official. I have myself and numerous other people received this update OTA from Acer. Unless Acer is beta testing on our devices, you can't call it anything but official. It is the exact same rom ZN posted.

devitos said:
I am very interested - how Canada firmware got in Russia)))
acer have a bug in service
Click to expand...
Click to collapse
I've just buyed my own one here in spain and it comes with the PA_CA firmware as well

Related

Read this about the new february 27 ROM

If you like me have just upgraded to the 2.03 rom released in January and now HTC released a new rom with exactly the same changelog it may not be worth all the hassle with reinstalling / configuring all your stuff once again already.
I was pissed at HTC since they couldn't tell us what they changed since they told us to REAPPLY this update if we had installed it prior to february 27. So today I sent them this email:
Latest ROM update for HTC Touch Diamond. It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? We are many people who don't wanna go trough all the hassle again. Why can't you just tell us what you fixed so we can decide for ourselves if it's necessary. The january ROM works just fine. Yours sincerely, ******.
And I just got an answer from them that I can't post here since it came with a confidentialy note. But I can tell you in short that they explained that there are lots of things and bugs for different time made devices and changes and that is why they can't say what is changed in the february 27 rom.
They also told me not to reapply the update if my device is working fine, there is no need to.
So you can without any worries stick with the january update for now if you don't experience any issues or don't feel like installing all your stuff from scratch
owziee said:
If you like me have just upgraded to the 2.03 rom released in January and now HTC released a new rom with exactly the same changelog it may not be worth all the hassle with reinstalling / configuring all your stuff once again already.
I was pissed at HTC since they couldn't tell us what they changed since they told us to REAPPLY this update if we had installed it prior to february 27. So today I sent them this email:
Latest ROM update for HTC Touch Diamond. It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? We are many people who don't wanna go trough all the hassle again. Why can't you just tell us what you fixed so we can decide for ourselves if it's necessary. The january ROM works just fine. Yours sincerely, ******.
And I just got an answer from them that I can't post here since it came with a confidentialy note. But I can tell you in short that they explained that there are lots of things and bugs for different time made devices and changes and that is why they can't say what is changed in the february 27 rom.
They also told me not to reapply the update if my device is working fine, there is no need to.
So you can without any worries stick with the january update for now if you don't experience any issues or don't feel like installing all your stuff from scratch
Click to expand...
Click to collapse
I have to soft-reset my device everytime during an installation, then run the install again. The x-button doesn't work properly (turned "close programs using x" on). Never had to use the red soft-reset button as often as with this ROM (crashes easily). Plus it's much slower than my previous official ROM.
I think this ROM update is for people like me...
Well maybe... I don't experience any of the problems you mentioned.
owziee said:
...It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? ...
Click to expand...
Click to collapse
are u suggesting that htc should stop releasing updates for diamond?! dude, why using stock rom's, what's the fun in it anyway!?
No no, absolutely not!!!
But HTC released this rom (february 27) with the same changelog as the 2.03 rom they released in january and I've just gone trough reinstalling everything so the idea of installing virtually the same rom once again gave me a headache.
HTC urged us to reapply the update if we installed it before february 27 and I really needed to know why so I had to send them the email.
Of course I would be very happy to see new rom upgrades in the future as long as there are changes / fixes worth mentioning (They didn't even mention any fixes this time since they just posted the same changelog all over and it was only 1 month between the updates).
ROM info...
What's more... take a look at the version numbers:
January's ROM: v2.03.405.2
February's ROM: v2.03.405.3
When a version number change isn't even a point (i.e. the '.03' in the above example), believe me, not a lot has changed. But this is worse than that, a change from .03 to .04 would probably mean just correcting a spelling mistake... this change is so far down the points, it doesn't even make it past the 'what's the POINT' stage with me (get it... what's the POINT!!) - OK, rubbish joke
Maybe the newer ROM fixes problems that only appear under special constellations.
For my part it fixed a problem i had:
Sometimes TouchFlo 3D diddn't start correctly after a softreset (from Sprite Backup),
device kept powered on until battery was empty.
They don't list a newer changelog for this ROM, but i find it strange that the Jannuary
version is no more available on the website.
But i agree, if the Jannuary version runs fine absolutely no need to upgrade.

New Asian Firmware ZUJP2

Another Asian firmware that runs nice. The build date 2010-09-08. Its branded with Taiwan Telecom Apps, just like ZUJP1.This firmware is that is read and write, this is the first september firmware i found that are. Try if you like
Download link:http://www.multiupload.com/FBLCZHQNYY
Its with root files (kernels, update.zip,PIT, Odin, firmware)
Nice to see some new FW, thanks
is it a froyo build??
racerboy3801 said:
is it a froyo build??
Click to expand...
Click to collapse
No.. seems its Eclair..
September firmware?! - that's good.
JPK has a 19th sept build date...
new_bember said:
No.. seems its Eclair..
Click to expand...
Click to collapse
No, its Froyo
new_bember said:
No.. seems its Eclair..
Click to expand...
Click to collapse
No. I saw the Froyo like rooting method inside (flashing back the original kernel etc.). This is a Froyo build.
Has anyone (else) tested it?
Honestly i am disapointed in voodoovkernel jm 8 plus lagfix plus OCLF 2 on top. Quadrant is skyrocketing, inside apps it eorks well, but everything else in beteeen takes much longer to load, lot of black screens inbeteeen apps. I am willing to try something new, or maybe i ll just get back to stock.
Sent from my GT-I9000 using Tapatalk
I suspect this is a branded or at least customised build off the release Froyo branch, which I suspect is the JPH / JP4 branch.
JPK is newer because it is a leak from the Froyo trunk.
My feeling is that what we're seeing now, and what will form the "official" releases, are optimised JPH /JP4 builds. They may be better / faster than JPK but as they're based on an earlier branch, their build dates won't be as new as JPK.
Rawat said:
JPK has a 19th sept build date...
Click to expand...
Click to collapse
ZUJP2 is 06 September build date which is older than JPK.
stuclark said:
I suspect this is a branded or at least customised build off the release Froyo branch, which I suspect is the JPH / JP4 branch.
JPK is newer because it is a leak from the Froyo trunk.
My feeling is that what we're seeing now, and what will form the "official" releases, are optimised JPH /JP4 builds. They may be better / faster than JPK but as they're based on an earlier branch, their build dates won't be as new as JPK.
Click to expand...
Click to collapse
If they're not recompiling anything (keeping the build date same) then what exactly are they optimizing? They can't even recompile the kernel without build dates changing.
I think all they do is test and custom apps/branding. For now everything is speculation and guesswork.
I think I will wait for official Froyo or flash it out of boredom.
man firmware release had really dried up lately
Why would they waste anymore time on Eclair builds if Froyo is a soon to be release.
We should be glad they have switched tactics to concentrate on Froyo which could mean a definate release by months end.
Question is, will it be released in all countries at the same time or specific countries first.
So, has anyone tried it?
just flashed..
first impressions good..
1. booted up in chinese language
2.contacts showing all alphabets in the side search
3. quite fast like dxjp1
4. comes pre installed with some bloatwareapps like hamiapps, hami... hami.. dont know what these are..
5. seems to me as being very close to an official build.
aswinm16 said:
just flashed..
first impressions good..
1. booted up in chinese language
2.contacts showing all alphabets in the side search
3. quite fast like dxjp1
4. comes pre installed with some bloatwareapps like hamiapps, hami... hami.. dont know what these are..
5. seems to me as being very close to an official build.
Click to expand...
Click to collapse
How is browser performance? Loading times, panning around etc.
its ok..not perfect..i went back to dxjp1..too much bloatware slowing up the phone..
anyone know if this uses hsupa?
This ROM seems to be de-odexed.
It starts in Chinese. You have to manually switch it to English.
Includes the Chinese keyboard.
If you don't want those carrier custom apps, just don't flash the CSC file. I didn't need to repartition (mine is the 803 pit) and it worked just flashing the PDA and MODEM sections.
TIP: When you are rooting, you don't have to "pull the battery out" after the first kernel flash. You can just press and hold the power button for around 20 seconds and the phone will shut down.

ROM updates for Samsung Taylor SGH-i707?

So I'm wondering about this phone a friend offered to sell to me. It's a Samsung Taylor developer phone, so I have no idea which forum this goes into.
Will I be able to get software updates to the phone at all? Because right now the phone comes with the prototype ROM, so it can't record 720P. The camera is crap, some things like Facebook and Twitter don't work all the way. The marketplace isn't there. Its not stolen property because he is an independent developer and he says the phone served its purpose and he moved on to actual Win7 phones.
Any opinions? I asked my friend and he says he never tried looking for updated ROMs and he stopped using them after he got a focus.
untrueparadox said:
So I'm wondering about this phone a friend offered to sell to me. It's a Samsung Taylor developer phone, so I have no idea which forum this goes into.
Will I be able to get software updates to the phone at all? Because right now the phone comes with the prototype ROM, so it can't record 720P. The camera is crap, some things like Facebook and Twitter don't work all the way. The marketplace isn't there. Its not stolen property because he is an independent developer and he says the phone served its purpose and he moved on to actual Win7 phones.
Any opinions? I asked my friend and he says he never tried looking for updated ROMs and he stopped using them after he got a focus.
Click to expand...
Click to collapse
connect it to zune and look for updates , there are beta updates for that phone (actually with a higher build number and copy/past) so I would say yes there are updates for .
I have a German Vodafone Optimus 7 that was used a couple of months by a software developer. I don't think it's running the latest (stable) build of WP7 however. When I check for updates with Zune it says that I'm up to date and the current version is: 7.0 (6536). Is this the latest version that every WP7 device is running? And if not, how come that my device doesn't get any updates?
Btw, Marketplace etc. just work fine on the device.
renegadEEE said:
I have a German Vodafone Optimus 7 that was used a couple of months by a software developer. I don't think it's running the latest (stable) build of WP7 however. When I check for updates with Zune it says that I'm up to date and the current version is: 7.0 (6536). Is this the latest version that every WP7 device is running? And if not, how come that my device doesn't get any updates?
Btw, Marketplace etc. just work fine on the device.
Click to expand...
Click to collapse
that is not a developer phone but a pre release , only the Samsung Taylor is a developer phone (and get beta updates )
you have to wait for the official update in 2011.
ceesheim said:
that is not a developer phone but a pre release , only the Samsung Taylor is a developer phone (and get beta updates )
you have to wait for the official update in 2011.
Click to expand...
Click to collapse
The LG Panther was a developer phone too I believe. Thanks for your reply, I'll be waiting for the january update just lik everyone else then
renegadEEE said:
The LG Panther was a developer phone too I believe. Thanks for your reply, I'll be waiting for the january update just lik everyone else then
Click to expand...
Click to collapse
thanks , didn't know of the LG Panther .
ps, the latest official build is 7004.
In theory, the Taylor and Panther have updates to build 7003/7004, and they are available on the net (or if you ask the right friendly WP7 dev).
If you plug the device in to Zune, it should search for an update to 7003, though that might not happen.
73XX and above do also exist for the Taylor/Panther, but they're a lot harder to come by, and won't be coming out via Zune any time soon.
In theory, a dev device running 7003 will be able to do anything a release device running the same build (they wouldn't be much use as developer phones if they behaved differently) so I think updating the device should fix the issues you've got, though it'll never do 720p video, and the camera is terrible!
i dont think my friend's is even running the release. the market doesnt work and the live integration is blank. so if i have him get the update, basically i can upgrade it? awesome.
untrueparadox said:
i dont think my friend's is even running the release. the market doesnt work and the live integration is blank. so if i have him get the update, basically i can upgrade it? awesome.
Click to expand...
Click to collapse
That sounds like an older build then, those are both working on the Taylor/Panther I've got.
Let me know if you need help finding an update.
I don´t know why but I have ROM 7006 installed on my Samsung Taylor, so diff packages from 7004 to 7008 won´t work. Asked lots of devs and MSFTies an no one seems to have ROM 7004 for the Taylor.
Any help?
Follow this guide to get Mango running on the Samsung Taylor: http://www.rudigrobler.net/blog/2011/9/28/installing-mango-on-your-samsung-taylor.html
Leapo said:
Follow this guide to get Mango running on the Samsung Taylor: http://www.rudigrobler.net/blog/2011/9/28/installing-mango-on-your-samsung-taylor.html
Click to expand...
Click to collapse
Update is possible from rev. 7004 only, not from 7003 or 7006 (never heard about that revision).
sensboston said:
Update is possible from rev. 7004 only, not from 7003 or 7006 (never heard about that revision).
Click to expand...
Click to collapse
So you personally tried it the above process, and it failed?
Leapo said:
So you personally tried it the above process, and it failed?
Click to expand...
Click to collapse
I've tried from 7003 and failed.
I tried it with ROM 7006 and it also failed.
At what point is it failing?
Are you absolutely sure you're using the correct "ChevronWP7.Updater"?
The download link was pulled some time ago, so if you downloaded anything off of Chris's blog, it was the wrong updater.
Edit: I would post a link to the correct one, but all the mirrors were on megaupload...which is now gone
Leapo said:
Are you absolutely sure you're using the correct "ChevronWP7.Updater"?
Click to expand...
Click to collapse
Actually, I'm not sure about Rudi Grobler's post. No proof screenshots (even photoshopped!), nothing at all but just words...
Second, search for deleted comments to his article: http://www.rudigrobler.net/display/Search?moduleId=12353177&searchQuery=Samsung+Taylor
The first said (but he left all comments without reply!):
Comment On: Installing Mango on your Samsung Taylor
Journal Entry Comment by r2d2rigo on September 29, 2011
How did you get your Taylor to 7004 in the first place?
Click to expand...
Click to collapse
So, it may be fake... I received Sammy Taylor at August, 2010 and installed all updates MS sent to registered developers/partners but never heard about Taylor on 7004.
In my case, it fails when applying the diff packages, since they are all 7004-7008, adn my rom is 7006.
I have try to find info about the links to 7006-7008 packages with no success so far.

You are using an illegal copy of our ROM, Venom is pissed!!

or at least it seems like it.
i downloaded the port over version the other day before all the "close this thread now" stuff. And i have loved it so far.
But, i just got a notification on my phone that said there was an update available, out of curiousity as to it being verizon or venom, i clicked download and it said the following.
"You using illegal copy of our ROM, to fix it apply update" and so forth and so on.
My question is the Venom rom now ready and they are just sending out an update to get up to their specs or is this update going to kill my phone. I have no problem taking this rom off and putting something on if this update was designed to kill the old version, just want to get some answers before i go in any directs.
was just struck off guard today with this development...
thanks,......
jhollon said:
or at least it seems like it.
i downloaded the port over version the other day before all the "close this thread now" stuff. And i have loved it so far.
But, i just got a notification on my phone that said there was an update available, out of curiousity as to it being verizon or venom, i clicked download and it said the following.
"You using illegal copy of our ROM, to fix it apply update" and so forth and so on.
My question is the Venom rom now ready and they are just sending out an update to get up to their specs or is this update going to kill my phone. I have no problem taking this rom off and putting something on if this update was designed to kill the old version, just want to get some answers before i go in any directs.
was just struck off guard today with this development...
thanks,......
Click to expand...
Click to collapse
i don't think anybody would side with venom if they released an update that killed somebody's phone over a ported rom.
wiredout46 said:
i don't think anybody would side with venom if they released an update that killed somebody's phone over a ported rom.
Click to expand...
Click to collapse
i agree, i was just trying to find out if anyone else had seen this and did the update to see what gives.
UPDATE: i tried to install the update and it fails every single time. not sure what it is supposed to do, but it fails. just thought i would shoot the update to everyone. i am fairly certain that i am not the only one.
thanks,
see if the ROM that we are using was ported from got an update.. since it's a port, it's likely the update is for sprint...
thought that is what it might be, but the "illegal" ROM part made me wonder a bit more than usual..
http://forum.xda-developers.com/showpost.php?p=47380724&postcount=213
turge had asked members of the verizon one community to supply fixes to enable verizon to work properly with the intl venom rom
this wasnt meant to have people fix up the rom for verizon and release it.....when its meant to be released to the public, it will be
our server cant distinguish between actual kang roms (ie chinese ones which are so prevalent) and ports that are being worked on....my advice is to not use a venom rom on your verizon one until turge or jan release it via an official thread
it wouldnt be an update from verizon as its not a verizon based rom with verizon ota files in it
nitsuj17 said:
http://forum.xda-developers.com/showpost.php?p=47380724&postcount=213
turge had asked members of the verizon one community to supply fixes to enable verizon to work properly with the intl venom rom
this wasnt meant to have people fix up the rom for verizon and release it.....when its meant to be released to the public, it will be
our server cant distinguish between actual kang roms (ie chinese ones which are so prevalent) and ports that are being worked on....my advice is to not use a venom rom on your verizon one until turge or jan release it via an official thread
it wouldnt be an update from verizon as its not a verizon based rom with verizon ota files in it
Click to expand...
Click to collapse
Perfectly said, Sir.

L24 update News 30/04

Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
blasbenoit said:
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
Click to expand...
Click to collapse
Update has landed. Found links on teammt site few moments ago.
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v133897/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...BND-L24_hw_usa/update_full_BND-L24_hw_usa.zip
http://update.hicloud.com:8180/TDS/...97/f1/full/public/update_data_full_public.zip
MD5 verified numbers ( from my working downloads)
Code:
e75a21769f049430840ea900b11600c4 c:\android\honor_7x\l24-oreo\update.zip
73414b5383e5fb3391e77a13c17dca53 c:\android\honor_7x\l24-oreo\update_data_full_public.zip
122f0e91d77fba6e399300926d1ef289 c:\android\honor_7x\l24-oreo\update_full_bnd-l24_hw_usa.zip
So can I just flash those update files with TWRP and be good to go?
I don't know if that's the stable or not, I've had that version for over a week now.
My update says C567?
I used the teammt firmware finder and, clicking on "Check Firmware Access" get "The firmware is not approved for installation."
This, I believe, means that it's not official.
We can expect the OTA to be pushed in stages, just like the beta, but, hopefully, it'll be complete by end of day this time.
johncro13 said:
I used the teammt firmware finder and, clicking on "Check Firmware Access" get "The firmware is not approved for installation."
This, I believe, means that it's not official.
We can expect the OTA to be pushed in stages, just like the beta, but, hopefully, it'll be complete by end of day this time.
Click to expand...
Click to collapse
Why would it be available if it's not official? I don't get that lol. The app is a little funky.
How long did the staged release of the beta take? Can we expect the update within hours, days, or weeks do you all think?
mparma13 said:
How long did the staged release of the beta take? Can we expect the update within hours, days, or weeks do you all think?
Click to expand...
Click to collapse
I'd say weeks, but that is just a hunch based on my experience with the rollout of the previous two patches... Once again, it would have been nice when Honor USA announced it that they didn't just say "Coming April 30" but instead were a bit more honest about how the release was being pushed out.
They shoyld have said that it will be around a certain week or something cause the frustrating lag is killing me badly and i even have a Oneplus 5t...but still is the worst lag i have seen in since 2013
I think the released update file are for update from oreo beta to oreo stable.
My first attempt to manually flash the update failed to flash the data files, only did the system update. It left me with odd build number and missing the new face-unlock feature.
I installed a second time , from the half installed oreo , and this time it completed fully. Also changed install script to use original file names instead of shortened names.
If anyone does this also please note that you will need to use the oreo flash update section as you will already be on oreo .
mrmazak said:
I think the released update file are for update from oreo beta to oreo stable.
My first attempt to manually flash the update failed to flash the data files, only did the system update. It left me with odd build number and missing the new face-unlock feature.
I installed a second time , from the half installed oreo , and this time it completed fully. Also changed install script to use original file names instead of shortened names.
If anyone does this also please note that you will need to use the oreo flash update section as you will already be on oreo .
Click to expand...
Click to collapse
How did you install it?
allrockedout said:
How did you install it?
Click to expand...
Click to collapse
I used the update oreo section from my guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
It was not 100% working. I am not sure if it was the shortened update-file names or because the update files are for beta update.
The update fails at about 70-80% --during the data_update and hw_update-- and then I needed to do factory reset.
After booting into half updated oreo I updated again using same guide, but used the flash update section for oreo.
And I modified the updater-binary to use the full name of updates instead of the shortened names.
Might be able to use full names on nougat update section too, but I was already in oreo, so could not test.
mrmazak said:
I used the update oreo section from my guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
It was not 100% working. I am not sure if it was the shortened update-file names or because the update files are for beta update.
The update fails at about 70-80% --during the data_update and hw_update-- and then I needed to do factory reset.
After booting into half updated oreo I updated again using same guide, but used the flash update section for oreo.
And I modified the updater-binary to use the full name of updates instead of the shortened names.
Might be able to use full names on nougat update section too, but I was already in oreo, so could not test.
Click to expand...
Click to collapse
Ok thanks I'm on stock bootloader still locked I'll just wait for official update
yeah....
blasbenoit said:
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
Click to expand...
Click to collapse
Looks like they crapped the bed on the update....
East coast here and so far just crickets.
I'm not worried about it because my 7x is fast and solid so far. Loving this phone since I bought it in January.
It just sucks that there's all this hype about the Oreo release coming Monday and you get all excited and ... Then you fell frustrated
pcaseiro said:
East coast here and so far just crickets.
I'm not worried about it because my 7x is fast and solid so far. Loving this phone since I bought it in January.
It just sucks that there's all this the about the Oreo release coming Monday and you get all excited and ... Then you fell frustrated
Click to expand...
Click to collapse
Well some group is getting it(probably beta testers), because it is on firmware finder
China has a holiday right now. I think they come back to work on the 2nd maybe that's why no update. Im guessing I have no idea.
allrockedout said:
China has a holiday right now. I think they come back to work on the 2nd maybe that's why no update. Im guessing I have no idea.
Click to expand...
Click to collapse
Then why would they be so set on the 1st, shouldn't they have said the 2nd? Lol
Anyone receive official update yet?

Categories

Resources