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.
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.
Hey everyone,
Just wanted to ask a quick question regarding the firmware
I got my UK unlocked S5 last week and as soon as I set it up, an update came through, which is 100mb, the note regarding say "Improved performance", the update download, but I haven't installed it yet. Mainly because of a bad experience I had after updating my S3. I haven't come across any bugs since I've been using it, and I'm concerned that if I update, the battery will drain quicker, or perhaps cause an error in the recovery mode(these things happened to my S3 after updating to 4.3). So 2 main questions.
1. Has anyone here downloaded this 100mb software update their S5? If so, what differences did you notice?
2. Suppose I updated and wasn't happy with the new changes? Would it be possible to go back to the original firmware version that my phone came with when I took it out of the box, *without rooting my S5?
Hope some people on here can shed some light on these questions.
Thank you in advance*
1. It's just a system update. The phone is new there are bound to be updates as issues are ironed out
2. You can odin any firmware whenever you want
Sent from my SM-G900F using Tapatalk
MasterfulNinja said:
Has anyone here downloaded this 100mb software update their S5? If so, what differences did you notice?
Click to expand...
Click to collapse
Your instincts are dead on. Updates may fix bugs or add a desireable feature. But just as often they introduce new bugs, break root or disable root exploits, break a few apps and add noxious DRM frameworks like the Knox qfuse warranty bit. They can seriously mess up a custom ROM and may depreciate features like MSC or car dock that may be important to you personally.
Updates cannot always be reverted. Try downgrading your Kitkat baseband to Jellybean and see what happens. Or try removing the Knox security bit after you take the update that introduced it. I disable automatic updates and wait to hear what early adopters find before upgrading.
Unfortunately you didn't tell us the all important version of your update. Or even tell us what your current firmware version and carrier are. Your update might be similar to the recent ATT /Verizon OTA adding the mixed blessing of reactivation lock. That is causing bootloops for some people with custom kermels. 4.4.3 is mostly bug fixes, with a few UI tweaks. And I believe 4.4.4 took aim at closing yet another open-SSL exploit and reverting some of the new 4.4.3 bugs.
No matter what an update intends to do, a few new bugs and unexpected conflicts usually turn up. A quick Google finds reports like this:
International Business Times said:
Issues Spotted for the Android 4.4.3 Kitkat
The Android 4.4.3 Kitkat system update is pretty much all about improving performances, strengthening stability and fixing a couple of bugs. However, it reels in a couple of issues experienced by users of Nexus devices that have already been upgraded to the latest update.
According to IT Pro, some of these issues include wi-fi problems, crashes and reboots and bugs found in apps. Google has not yet given any statement about how to deal with these issues nor has there been any word if these issues are only experienced by a handful.
Click to expand...
Click to collapse
.
.
fffft said:
Your instincts are dead on. Updates may fix bugs or add a desireable feature. But just as often they introduce new bugs, break root or disable root exploits, break a few apps and add noxious DRM frameworks like the Knox qfuse warranty bit. They can seriously mess up a custom ROM and may depreciate features like MSC or car dock that may be important to you personally.
Updates cannot always be reverted. Try downgrading your Kitkat baseband to Jellybean and see what happens. Or try removing the Knox security bit after you take the update that introduced it. I disable automatic updates and wait to hear what early adopters find before upgrading.
Unfortunately you didn't tell us the all important version of your update. Or even tell us what your current firmware version and carrier are. Your update might be similar to the recent ATT /Verizon OTA adding the mixed blessing of reactivation lock. That is causing bootloops for some people with custom kermels. 4.4.3 is mostly bug fixes, with a few UI tweaks. And I believe 4.4.4 took aim at closing yet another open-SSL exploit and reverting some of the new 4.4.3 bugs.
No matter what an update intends to do, a few new bugs and unexpected conflicts usually turn up. A quick Google finds reports like this:
.
.
Click to expand...
Click to collapse
Thank you very much for your detailed answers! That's exactly it! And I know from experience that updating firmware can cause a negative affect to the phone's performance. My iPhone 4S is still on iOS 5.1 but runs perfectly, while friends who updated their 4S to 7.1 experience freezes and heavy lag. Maybe companies do this deliberately, so people get frustrated and end up having to get the latest, more powerful model so the OS to run smoothly?
I do exactly the same, I always wait to see what people about an update before updating. The only difficulty with Android updates is that there seem to be so many different versions of updates. For example, when I researched the 100mb one for the S5,* various sites mentioned it, but others say the size of the update was 30mb, which were called "improved performance" I also heard about updates not always being able to be reverted to the previous version,* and also about Knox. So, you can see why I'm hesitant to update.
I know quite a bit about using Android, but have very limited knowledge regarding rooting and custom roms and so on. Also, after reading that rooting a phone incorrectly can turn it into a brick, I'm happy to just leave it as it is. I've attached a photo which shows my current firmware version, as well as other information. Also, as my S5 is unlocked, the only updates I'll receive will be from Samsung. I asked my carrier (T-Mobile UK) and that's what they told me. Only phones from bought from them include added apps that they put on, and I think they may also be able to tweak the updates received, by adding their own features.
Some more questions for you;
1. Do you recommend a factory reset after each software update?(I had to factory reset my S3 to stop the battery draining issue that 4.3 caused. But was wondering if it's best to factory reset after each and every update on Android devices)
2. I know you said that sometimes reverting back to a previous firmware isn't always possible, but can't using Odin with the correct firmware version work? Like Goldie mentioned in the above reply. And does changing the firmware via Odin require rooting the phone?
MasterfulNinja said:
Thank you very much for your detailed answers! That's exactly it! And I know from experience that updating firmware can cause a negative affect to the phone's performance. My iPhone 4S is still on iOS 5.1 but runs perfectly, while friends who updated their 4S to 7.1 experience freezes and heavy lag. Maybe companies do this deliberately, so people get frustrated and end up having to get the latest, more powerful model so the OS to run smoothly?
I do exactly the same, I always wait to see what people about an update before updating. The only difficulty with Android updates is that there seem to be so many different versions of updates. For example, when I researched the 100mb one for the S5,* various sites mentioned it, but others say the size of the update was 30mb, which were called "improved performance" I also heard about updates not always being able to be reverted to the previous version,* and also about Knox. So, you can see why I'm hesitant to update.
I know quite a bit about using Android, but have very limited knowledge regarding rooting and custom roms and so on. Also, after reading that rooting a phone incorrectly can turn it into a brick, I'm happy to just leave it as it is. I've attached a photo which shows my current firmware version, as well as other information. Also, as my S5 is unlocked, the only updates I'll receive will be from Samsung. I asked my carrier (T-Mobile UK) and that's what they told me. Only phones from bought from them include added apps that they put on, and I think they may also be able to tweak the updates received, by adding their own features.
Some more questions for you;
1. Do you recommend a factory reset after each software update?(I had to factory reset my S3 to stop the battery draining issue that 4.3 caused. But was wondering if it's best to factory reset after each and every update on Android devices)
2. I know you said that sometimes reverting back to a previous firmware isn't always possible, but can't using Odin with the correct firmware version work? Like Goldie mentioned in the above reply. And does changing the firmware via Odin require rooting the phone?
Click to expand...
Click to collapse
1. Yes, a data factory reset after a update/flash a rom is remmended and gives best performance and stability;
2. I haven`t tried flashing a older rom itself but it should be possible i guess as this is not dowgrading like from 4.4.2 to 4.3. You could try it and if it fails there`s no harm done as you can flash your current rom back.
3. Installing a update or flash a rom usualy will kill root, though superSU Pro offers a survival mode to keep root after a update. You can also flash a rom with Mobile Odin Pro and enable everroot and the 2 other options so you will not loose root.
@MasterfulNinja
I don't automatically accept updates. Someone more impulsive, or indifferent can be the guinea pig. That approach is effective in avoiding some unpleasant firmware surprises. Often an older firmware version runs smoother and is more stable as in your IOS 5 vs 7 example. Running an older firmware means that you may have unpatched security vulnerabilities but in practice this usually isn't a great or unmanageable problem. It is a point to keep in mind though.
Rooting isn't nearly as dangerous as many people think it is. Someone who can follow directions and avoid flashing firmware from a completely different device will rarely brick a phone. And even if you did, you can usually recover from the mishap. I mention this because one of the best ways to maintain a stable phone OS is to install a decent custom ROM (which typically requires root). And then most of the heavy lifting is done by the developer who has already removed bloat, restrictions and other objectionable pieces. And monitors and releases tailored and usually stable updates for those using his ROM.
Android updates vary in size because they are screened by carriers, each deciding what update components and /or custom bits goes into their version of the update. More restrictive Apple manages all IOS updates centrally from their California servers i.e. they don't relinquish direct control to carriers. Still it isn't hard to find articles giving a good summary of what issues android firmware updates are addressing.
Some people believe that you should accept every update and as soon as it becomes available. I don't see a compelling need to update unless you are trying to resolve a current bug or are enticed by a specific new feature. I don't recommend a factory reset after each update. I do recommend that you clear the system cache from recovery mode though. A factory reset usually won't benefit you but it is time consuming to reinstall and reconfigure your phone.
Having said that, if you have a specific issue, such as the 4.3 battery drain then you have a rationale for doing so. But I have to say that I experienced the same S3 issue and clearing the cache was sufficient to stabilize the phone for me. Some phones will develop corruption or configuration conflicts over time, especially if you install a lot of apps. Or if you have a specific app that makes a mess of your file system. With that in mind, I do do a factory reset about once a year to clean up the phone, the same as I would do for a laptop OS. But I don't see a reason to do it after every update.
Odin is a Samsung product, complete with DRM. So no, you cannot flash anything with Odin. You can flash most stock firmware and in particular Odin will look for OEM signatures if you try to change the bootloader or modem. In the case of downgrading, it is the Knox qfuse on your phone that will cause the Odin flash to fail. If you try to downgrade you end up with a partial flash which can soft brick your phone and trip the Knox flag.
.
I've been working at this non-stop for the past week, and I've finally found a way. I am not able to flash a European ROM on the Chinese Mate 9.
I came very close to bricking my device, so I'm currently making sure of the method. Here is what it looks like:
http://imgur.com/a/1ONOF
(I am long-pressing the home button to show it's fully google-ized, in both pictures, but I took my hand out of the picture for paranoia purposes)
So, how is it done? Through eRecovery. I will release the full method once I have tested it enough for public consumption, because I don't want people bricking their devices.
How does it work? It's... interesting.
The version showing up on the phone is the last Chinese firmware which was installed. It doesn't update to show what version it is. In the imgur picture, for instance, it says B109SP01, but it's actually B115 running on it. The phone still thinks it's a Chinese phone, so if you try to get an OTA, you'll probably be getting a Chinese OTA which will not work correctly. So in that sense, it's a bastardized version, and OTAs/updates will not work normally -- You'll have to flash them through a different method.
The positive side is, Google works. Completely. It comes installed out of the gate with account sync, and so on. Other than being Google-fied, some other differences include the permissions menu, the keyboard (SwiftKey is default), and a few other things here and there. The default theme looks strange, and I think it has to do with the cust partition not matching the actual model. This is something I'm currently looking into before release. I'm also looking into using version B122 (or newer if it becomes available) instead of 115.
I'm sure many of you want to get your hands on the European firmware and the method to install it. If you're interested in testing despite one-day-old pre-beta status, shoot me a PM, and I'll try to get you hooked up. In the future, because this method will require a lot of data transfer, I'm considering charging some money to people who download it, and setting up a proper server.
Anyway, for now, know that it's possible, and if you want to do it right away, get in touch with me and I'll try to help!
Update: I have now verified that it's possible to go back to the Chinese ROM. I should have something for those who contacted me wanting to test tomorrow. Since this is a LOT of work, priority will be given to those willing to make a donation.
Although I don't have a Chinese M9 I appreciate your efforts as this opens up the way to flashing other stock and maybe even custom ROM's. Well done!
blackspp said:
Although I don't have a Chinese M9 I appreciate your efforts as this opens up the way to flashing other stock and maybe even custom ROM's. Well done!
Click to expand...
Click to collapse
Unfortunately, I think that custom ROMs will not work with this method, because they're not signed by Huawei.
Wow, That's great news.
I really appreciate your efforts.
I think that you can get a little bit of money in return for your efforts.
I would like to participate in this plan.
Please notify me when the procedure is completed.
Thanks again!
So, here's where we are at right now:
We can flash the system partition of a European firmware, no problem. There's seemingly no issue there.
Where we get the issue is when we look at the cust partition. Because we can't change the actual region of the phone from all/cn to hw/eu, for example, the cust partition has issues. What I mean by issues is, you don't get any of the default themes, various software might be missing features, and so on. Your phone's model number also appears to change from MHA-AL00 to M300-AL00 if you flash the non-Chinese cust partition. When this happens, things go crazy, and you cannot see a proper version number, build number, or model number.
I am looking into making a 'bastardized' version of something to flash, using a Chinese cust partition with an international system rom. Theoretically, this could fix the issues to an extent. It will, however, probably give you a warning upon boot-up that the system has been tampered with, and so on. I will have more information later tonight, Japan time, when I get a chance to work on it some more.
The programs which go missing on a flash of the European firmware are the following:
AutoInStallAPKFromMcc HPLegacyPlugin HwPhoneService PlayGames
Books HwCloudDrive_Local LatinImeGoogle PlusOne
ChromeHomePage HwID Newsstand PredefinedEapSim
GameBoxGlobal HwOUC OMACP talkback
Appmanager HwBetaClub Instagram_Stub Todoist
Booking HwHealthPlatform_OVE Installer Todoist_ntp
DisableTodoistReceiver HwLogUploadService NewsRepublic Twitter
Facebook_Stub HwOUCBeta ProjectMenuAct WPS
Along with all the included themes, and the auto-installer which mounts via USB when you plug the phone in.
Obviously, some of these files are more important than others. All of the things really vital to being able to use the phone can likely be loaded via a Chinese cust partition, but the versions are probably different from the european versions.
Update:
I've obtained a server and am currently setting things up to bring this to the public. The first stage will be a private test. I'm still willing to take some testers who are willing to put their phones in the line of fire! I don't think the private test will launch today, because a new International B126 ROM just came out, so I'm going to base my work off of that for now.
After all the kinks are worked out, I will develop some kind of system for the general public to use. Eventually, this system will be one where you configure your DNS to my server, log into a website, choose what firmware you want to flash, then use eRecovery and that firmware will flash to your phone. I will have to customize all of the international firmware to work perfectly on Chinese devices, and I've yet to do that, but will be working on it. If there's a need, I can expand this system to other Huawei phones. It's exciting times for Mate 9 owners.
Hi duraraa
I have just received my 128g mate 9 in France. I will be happy tomake a donation and participate to the test. Please let me know.
v.kuo said:
Hi duraraa
I have just received my 128g mate 9 in France. I will be happy tomake a donation and participate to the test. Please let me know.
Click to expand...
Click to collapse
Sure, thank you for your interest. In the meantime, if you are currently on a version like B115 or higher, please downgrade to B106 / B109SP01 so you are familiar with the process.
Update: Now that we can install Google framework on the Chinese latest firmware, I have decided to cancel this project for now. I may keep a server alive to upload to unsupported/beta firmwares, but trying to get the European firmware working well on the Chinese Mate 9 is no longer a priority.
Which version of the firmware Duraraa ?
duraaraa said:
Update: Now that we can install Google framework on the Chinese latest firmware, I have decided to cancel this project for now. I may keep a server alive to upload to unsupported/beta firmwares, but trying to get the European firmware working well on the Chinese Mate 9 is no longer a priority.
Click to expand...
Click to collapse
Hi Duraaraa.
i might have missed something... how to put the framework on? Thanks so much - looking soo much forward to have Google on my AL00 phone.
weiaoli said:
Hi Duraaraa.
i might have missed something... how to put the framework on? Thanks so much - looking soo much forward to have Google on my AL00 phone.
Click to expand...
Click to collapse
Just search for GMS in the HiApp store. Huawei released a google framework installer.
But the app twin functionality in Chinese handset only allows QQ and wechat. Please continue with finding out how we can install European Rom on Chinese handset so we can have twin app functionality for whatsapp.
ewijaya74 said:
But the app twin functionality in Chinese handset only allows QQ and wechat. Please continue with finding out how we can install European Rom on Chinese handset so we can have twin app functionality for whatsapp.
Click to expand...
Click to collapse
If I flash the European rom on the Chinese handset, it's still QQ and wechat. Strange, eh?
Yes very strange....But there must be a way to fix this right?
Mate 9 from Taiwan
Hi everyone, keeping an eye on the market I found a very tempting offer on the 64GB version - HUAWEI Mate 9 64GB 4G Dual Sim SIM FREE/ UNLOCKED .
Now, my knowledge of ROM flashing is "level: what is a ROM?", but I am reading lots on the subject , but a couple of months ago I bought a P9 for my wife, chinese Al00 version, no problems to install Google Play but still many things are in chinese, the language correction for english or other EU languages sucks. That is why I decided not to go for Chinese versions unless there were exaustive guides on how to flash the mobile to an international or better european ROM.
Said all that, I wonder if anyone has found an easy way to solve the above mentioned issues - I assume everyone with a chinese version will have similar problems - and if you solved them otherwise.
Thanks for any information you might provide, and sorry if I missed key info to have this question properly addressed, but I will be happy to add it if asked.
Cheers,
Daniele
Newb here. Live in the US, just got a Mediapad M3 with version BTV-DL09C433B001 ( EMUI 4.2.3 and Android 6 ). The sim from my iPad works great and I can make and receive calls. Everything seems to work ok.
Like anyone I want the latest Android and EMUI. Is it worth it? should I bother? I am an actual embedded developer, so this stuff isn't way out of my league, I just don't know exactly what to do for this device on this platform.
I found FF and it show a lot of images that I can apply. I guess C433 means spcseas region. I heard that C233 installs Chinese and that may be the latest but comes with limits like no Google. I have three questions:
1) can I install an image for a different region (Cxx) without breaking everything,
2) can I install a fullOTA image rather than tediously stepping up image by image, and
3) which region (Cxx) should I go with to continue to work in the US?
Thanks in advance if you bother to have answers
wonderlamb said:
Newb here. Live in the US, just got a Mediapad M3 with version BTV-DL09C433B001 ( EMUI 4.2.3 and Android 6 ). The sim from my iPad works great and I can make and receive calls. Everything seems to work ok.
Like anyone I want the latest Android and EMUI. Is it worth it? should I bother? I am an actual embedded developer, so this stuff isn't way out of my league, I just don't know exactly what to do for this device on this platform.
I found FF and it show a lot of images that I can apply. I guess C433 means spcseas region. I heard that C233 installs Chinese and that may be the latest but comes with limits like no Google. I have three questions:
1) can I install an image for a different region (Cxx) without breaking everything,
2) can I install a fullOTA image rather than tediously stepping up image by image, and
3) which region (Cxx) should I go with to continue to work in the US?
Thanks in advance if you bother to have answers
Click to expand...
Click to collapse
I have the same Model with the same question. Were you ever able to get updated to Nougat?
You may need to change your region oeminfo partition before flashing another regions firmware. If you dont certain things might or might not work properly.
Any help on my ME us edition BTV-DL09C433B001 would be much appreciated.
I also have the M3 Btv-dl09c433b001 version.
It appears this version is not getting any support from Hauwai. I am still on Android 6.
Does anyone have a way to update my version to 7.0?
I did try to download and install BTV-DL09C199B350 on to my M3 but it didn't work. Thank you for taking the time to read this post.
I would read this thread on how I upgraded to 7.0.
https://forums.androidcentral.com/huawei-mediapad-m3/851348-latest-u-s-build.html#post6102181