Database Users

[Q] 2.3.5 update

Alright, so I'm quite cautious before I proceed with the update but I've been hearing mixed results with the 2.3.5 update. I pretty much have the update ready to go in the ext SD card.
I was wondering since my phone is fairly new and stock, have the problems experienced by users who updated to 2.3.5 (such as null IMEI and touch screen issues) only affected those who have rooted and are running different roms? or could it affect me if I do an update to 2.3.5?
As for null IMEI, what significant impact would it have on my phone?
I'm really keen to go on Gingerbread as there doesn't seem to be any OTA updates to 2.3.5 here in NZ...
Current Android Version: U8800 V100R001C00B136
Cheers

I have been upgrading from stock 2.2 and did not have any problems at all. All went smooth and everything is working as it should. I am using 2.3 beta 1 update, because it has unlocked bootloader, otherwise it is preety much the same as final 2.3 release.

oh, do the problems people experience persist in beta 1? or over the official one?

Like I said, I did not have any problems with it and I had stock phone just like you (no costum rom, no costum partition). I know people have reported many problems with these updates but it works for me. If someone has different experience please post it and write in what state your phone was before update ( costum rom, partition, etc...)!

when I got my brand-new phone from the store, it was 2.2 but rooted (!) and no g-apps.
The update to 2.3 was no problem and everything works fine.
no root any more, but I don´t need it anyways.

Wurstwa55er said:
when I got my brand-new phone from the store, it was 2.2 but rooted (!) and no g-apps.
The update to 2.3 was no problem and everything works fine.
no root any more, but I don´t need it anyways.
Click to expand...
Click to collapse
did you update to the beta builds or the 'original' build? I guess I won't have to back up if its only a rare minority experiencing these faults.

Stephen289 said:
I was wondering since my phone is fairly new and stock, have the problems experienced by users who updated to 2.3.5 (such as null IMEI and touch screen issues) only affected those who have rooted and are running different roms? or could it affect me if I do an update to 2.3.5?
Click to expand...
Click to collapse
I have a U8800Pro so I can't offer you an answer as to whether you should upgrade, but all I can say is:
If your phone is rooted, use http://forum.xda-developers.com/showthread.php?t=1325036 to back up your IMEI. It's worth it anyway, even if you don't plan to upgrade
From what I've read, touchscreen issues seem to be occuring for those with Atmel screens (and there's a report of an Atmel screen going bad on its own anyway), not those with Synaptics ones. This is what I've gleaned by reading U8800 threads; again, I have a U8800Pro (which all come with Synaptics screens). You can use the tool Elixir from the Market or dial #*#2846579#*#* and navigate through the menus to find out what touchscreen you have

[Q] 2.3.6?...Am I totally ****ed?

Right.
So, these days I had problems with my phone and have been forced to flash a new .sbf on my Defy+.
Now, my main question is: What are the main issues with 2.3.6? As far as I read there weren't issues with some .sbfs. (and there weren't any reported with my .sbf.)

Had read about issues like random reboots and inconsistent Wi-Fi connectivity on 2.3.6. Though i had issues of random reboots only, Wi-Fi was fine on my defy+, when i was on 2.3.6 firmware version ending with 1321.

andr0idfreak said:
Had read about issues like random reboots and inconsistent Wi-Fi connectivity on 2.3.6. Though i had issues of random reboots only, Wi-Fi was fine on my defy+, when i was on 2.3.6 firmware version ending with 1321.
Click to expand...
Click to collapse
what can i do if i have these probelms?is there any way of solving this??

The best you can do, if you want to stick to stock ROM, is to upgrade to the latest version available i.e. 231x. Keep in mind that it has BL7 and it's a bit difficult to root.
The other option is to switch to CM7. I would recommend CM7 builds by FuZZ_. I never had any problems after switching to Cyanogenmod.

Moto G KitKat OTA - Canada - Koodo

Folks,
I got an OTA update for the moto g. I'm on the Koodo network.
I downloaded the OTA update. Got the file from /cache.
Interesting the zip file i got has the name:
Blur_Version.173.44.9.falcon_umts.Telus.en.CA.zip
The OTA installer is telling me: 173.44.30.en.CA
The release notes had stated (can't find it now) that it has a fix for the OTG support and radio fixes like the UK and DE updates, PLUS a fix for Telus/Koodo customers that couldn't end their calls correctly.
Anyway i can't apply/update as i'm currently rooted. What are my options?
Be gentle, its my first android device.
------------------------------------------------------------------------------------------------------

Vector_Calculus said:
Folks,
I got an OTA update for the moto g. I'm on the Koodo network.
I downloaded the OTA update. Got the file from /cache.
Interesting the zip file i got has the name:
Blur_Version.173.44.9.falcon_umts.Telus.en.CA.zip
The OTA installer is telling me: 173.44.30.en.CA
The release notes had stated (can't find it now) that it has a fix for the OTG support and radio fixes like the UK and DE updates, PLUS a fix for Telus/Koodo customers that couldn't end their calls correctly.
Anyway i can't apply/update as i'm currently rooted. What are my options?
Be gentle, its my first android device.
------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
I just updated although I'm rooted but Im using the original ROM
See this thread too: http://forum.xda-developers.com/showthread.php?t=2648590&page=13

you have to unroot
You can unroot quite easily and apply the OTA then root again.
You shouldn't loose anything: download the original ROM you are currently running (the telus 4.3) and extract the 3 parts of the system image, then flash them using fastboot.
Let me know if that's not clear enough, I'll find the Step by step instructions for you.

Just an update on the Koodo/telus patch (8.5mb)
I was originally running at 4.4.2 but after backup critical files i jumped in and rooted to get the fixed the update provided.
It worked! No issues. Root was preserved after the update.
My phone prior to update was at 4.4.2 (173.44.9) and after the update it went to 4.4.2 (173.44.30). Don't know why its not called 174.xxx like the other countries. It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
The fixes included:
"Fixed an issue which caused temporary cellular network loss for small number of moto G customers.
-Fixed wallpaper cropping issue
-Resolved USB OTG support issue with USB Drives
-Fixed low call volume by some users
-Fixed an issue with ending calls originated from a moto G on Telus/Koodo.
I actually the last item happened to me as both my wife and I have the motog and are on the same network.

Vector_Calculus said:
It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
Click to expand...
Click to collapse
Yes, the naming scheme is quite confusing, but despite the fact that my German version is 176, US version is 174 and yours is 173 after updates, obviously they got exactly the same patches as you listed. No worries.

Vector_Calculus said:
Just an update on the Koodo/telus patch (8.5mb)
I was originally running at 4.4.2 but after backup critical files i jumped in and rooted to get the fixed the update provided.
It worked! No issues. Root was preserved after the update.
My phone prior to update was at 4.4.2 (173.44.9) and after the update it went to 4.4.2 (173.44.30). Don't know why its not called 174.xxx like the other countries. It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
The fixes included:
"Fixed an issue which caused temporary cellular network loss for small number of moto G customers.
-Fixed wallpaper cropping issue
-Resolved USB OTG support issue with USB Drives
-Fixed low call volume by some users
-Fixed an issue with ending calls originated from a moto G on Telus/Koodo.
I actually the last item happened to me as both my wife and I have the motog and are on the same network.
Click to expand...
Click to collapse
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.

xda127 said:
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
Click to expand...
Click to collapse
Battery drain is about the same as before. Maybe a factory data reset may help. I don't know if you lose root if you go this route..

xda127 said:
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
Click to expand...
Click to collapse
There is a camera bug on 4.4.2 that keeps the phone running after exiting the app. A fix is o the way...

[Q] Some Questions About Software Update

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.
.

Problems with last update Flyme 6.0.1.0A meizu pro 5

Hi there
With the last update, my pro 5 went nuts. Stopped ringging when people calls me and became very difficult to access my contacts. Also the battery drains a lot faster.
I have a chinese version Flyme 6.0.1.0A installed and the baseband version is S333_M86_20160406_CHNOPEN_MZ036.
I would like to change to the Global version but while searching I get confused (new at these things). Can you help me showing a safe way for me to change A version to G version?
Thanks
Joao

Have you tried a clean install? In order to do so wipe your data while flashing the firmware.
My phone went crazy two times after an update and both times a clean install solved the problems.
Dont forget to backup your data