Hello everybody,
My phone has had various problems lately and I thought that reverting to factory settings and then installing an official OTA update was a good idea.
I did a factory reset from the settings and unrooted the phone with Super SU, but it keeps telling me that the phone has been modified. I figured out I should flash a stock firmware through ODIN, but which one should I pick? I currently have I8190XXAMA4, which seems to be an Iranian firmware (WTF? I bought this phone in Italy!). The latest Italian firmware ends with ANI4, can I flash that one? Will it allow me to update OTA after that?
Related
Guys,
I flashed my Note with a HK Original Samsung ROM (N7000ZSKK1, obtained at the development section).
When I bought it in Shanghai, it had a modified version of the original firmware with lots of china apps that meddle with what I want to do, and since it had superuser on there I knew it was flashed. probably from a China issue version that doesn't have google apps
All seems fine after flashing the original HK version, except for one thing: I get software update notifications, and when I try to install them, I get an installation failure notification. I thought that if a phone had a correct ROM installed, it would be able to receive OTA updates? I was hoping to get Samsung's ICS update officially (rather than performing ROM flashes each time an update comes along...).
I used Mobile Odin to flash the firmware. Without checking (e.g. by installing titanium backup) I don't know if it is still rooted or not. Prior to flashing it the unit was actually not rooted (the chinese unrooted it after flashing the custom HK ROM I think), and it had the same issue wrt not being able to install OTA updates.
Any idea why I cannot install OTA updates?
Alternatively, what's the easiest solution to keep my phone up to date with samsung's latest and greatest?
ksporry said:
Guys,
I flashed my Note with a HK Original Samsung ROM (N7000ZSKK1, obtained at the development section).
When I bought it in Shanghai, it had a modified version of the original firmware with lots of china apps that meddle with what I want to do, and since it had superuser on there I knew it was flashed. probably from a China issue version that doesn't have google apps
All seems fine after flashing the original HK version, except for one thing: I get software update notifications, and when I try to install them, I get an installation failure notification. I thought that if a phone had a correct ROM installed, it would be able to receive OTA updates? I was hoping to get Samsung's ICS update officially (rather than performing ROM flashes each time an update comes along...).
I used Mobile Odin to flash the firmware. Without checking (e.g. by installing titanium backup) I don't know if it is still rooted or not. Prior to flashing it the unit was actually not rooted (the chinese unrooted it after flashing the custom HK ROM I think), and it had the same issue wrt not being able to install OTA updates.
Any idea why I cannot install OTA updates?
Alternatively, what's the easiest solution to keep my phone up to date with samsung's latest and greatest?
Click to expand...
Click to collapse
Sometimes OTA updates get fail. Try with Samsung Kies.
Tried that, but it gives the message "Your device does not support software upgrading via Kies". It states for current firmware version: PDA:KK1 / PHONE:KJ6 / CSC: (TGY)
SHould I be installing a different firmware?
Ok so I just received the OTA here in the UK. I downloaded it and when I finally did it wouldn't work. It said I needed a "victara" version and that I have a cm_victara version. That's because I have a custom recovery right?
So I installed multi-tool to restore my phone to stock and also installed the stock recovery. Full wipe and all. I then proceeded to install the OTA again but no luck it said that it had a problem.
Any ideas guys?
So far after using multi tool my phone is KXE21.187-42 and the system version is "21.21.42.victara_tmo.tmo.enUS retgb"
Now when I actually download the OTA the version it's downloading is the ".US" version.
Would really appreciate the help guys, been stuck on this for a whole day now. Also wiped my phone repeatedly lo
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
cowboyv said:
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
Click to expand...
Click to collapse
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Revontheus said:
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Click to expand...
Click to collapse
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
cowboyv said:
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
Click to expand...
Click to collapse
You can always download GAPPS manually, and flash it via Recovery if you think the Google Play Services that comes with your FW is bugged
Hi.
I'm just wondering if anybody can help me please?
I have a UK Huawei P9 EVA-L09 with Marshmallow currently on it (B166) build I think. It is unlocked and has TWRP 3.0.2.0 Recovery installed on it.
I would like to upgrade to Nougat 7.0 and EMUI 5.0, but most of my attempts have failed and I have had to use the rollback method to get back to Marshmallow.
I have tried to do it by flashing an Update.zip and subsequent EU_Apps package.zip through TWRP to no avail.
I have also tried the 'Dload' folder method, also to no avail. The closest I've gotten is to build no B378, but it shows up as NRD90M Test-Keys on the Build No in the phone settings instead and all apps such as camera, NFC, Bluetooth are missing / not working etc. Trying to then flash the EU_Apps package through 'Dload' method doesn't alleviate the problem of missing apps.
Does anybody have any tips for what I could try to get it onto a working Nougat build with apps please?
Also, if anybody has any links to any relevant firmware etc, then that would be very helpful too.
I'm pulling my hair our trying to get this to work. Surely it's can't be that hard can it??
Many thanks, Bill.
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
chris5s said:
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
When I tried to flash .Zips through TWRP it kept coming up with errors and didn't flash them (something about being umnable to mount /System).
I was on EE UK, but found a method yesterday for debranding my phone and setting it to C432. I also managed to successfully flash C432B182 firmware on it.
I have since attempted to flash Nougat B360 using the 'Dload' method and now my phone keeps asking me to enter my password to decrypt storage. Multiple attempts to reset my phone and wipe cache partitian don't seem to be working. Do you have any idea how I can get around this?
It's so hard and it's so annoying how other people seem to be getting it right and mine is proving to be a swine. Makes me want to get rid of it to be honest and get something easier.
Thanks again, Bill.
I'm concerned that this may be bricked right now. No amount of using eRecovery to reset the phone will stop it from going onto the dreaded 'enter password to decrypt storage' screen! I will see if I can re flash it using Fastboot, but I'm a bit concerned right now...
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
tmohammad said:
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
Click to expand...
Click to collapse
Probably advisable unless you absolutely know what you're doing and don't mind taking the risk. I'm a bit annoyed with Huawei and my carrier, they are always so slow with providing updates and Hmui 5.0 is only what Hmui 4.0 should have been in the first place. I'm done with these manufacturer's stupid over bloated overlays and will be going to an official Google phone in future!
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
chris5s said:
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
Click to expand...
Click to collapse
Hi again all.
Success! I finally managed to crack it.
I downloaded MM Firmware version C432B136 and used Huawei Extractor to extract the Boot.img, Recovery.img and System.img files and was able to boot into Fastboot mode fortunately. I used a Command Prompt to unlock the Bootloader again and flashed each .img file in line.
The phone booted up into the B136 firmware and I was then able to update OTA to B166, but not B182 strangely. So I downloaded a B182 version firmware and placed it in the 'dload' folder of the phone's S.D Card, before forcibly flashing it by holding volume up, volume down and the power button on boot up.
I subsequently used the below link, which showed me how to use Huawei Updater and HiSuite to update to B361 firmware.
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Once on Nougat B361 firmware, my phone's update setting prompted me to update to the latest B378 firmware OTA.
Finally, to achieve Root status I followed the below guide and am now running root with SuperUser and BusyBox installed. I'm happy to report that both Nougat 7.0 and HMUI 5.0 are running smoothly on my phone and all features are working (i.e. Bluetooth, Camera and NFC) and performance and battery life are all noticeably better than ever.
https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
Be aware that my phone is EVA-L09, so I followed all guides and downloaded all firmware that related to my specific phone model.
Phew! Thanks for all of your help and good luck to those who are attempting to get this working.
Bill.
Hi all,
I have a PRA-LX1 that had a Vodafone customization. The suddendly it just factory resetted itself (I SWEAR, I had it in my pocket) only to find it with a NRD90M firmware. Sick of this customization, I unlocked the bootloader and flashed a C432 oeminfo. I then tried to flash PRA-LX1C432B212 downloaded via FirmwareFinder, but went in bootloop. Well, no panic: fired up eRecovery, it installs PRA-LX1C432B170. I installed it and after the factory reset I now have a working phone. My only question is: is B170 really the latest available version I can get via OTA? I'd like not to lose the OTA feature so I don't have to rely on Firmware Finder to get updates every time... is there anything I can do?
A slightly related question: one thing I tried is to download B212 with FirmwareFinder. I managed to use the in-app proxy and actually found an update, but once it downloaded it didn't apply because of some failed verification (I don't have the phone with me now, but it was something AFTER the integrity check, so it's not something related to the download. I also verified the availability of B212 in FF by clicking the "Check Firmware Access" button and it's actually not available, like any other version I tried. Does this mean I won't get any OTA in the future?
Here is a discussion, probably related to your problem. Are you using TWRP Recovery when installing the OTA update or the stock recovery?
I read somewhere that Huawei OTA updates won't install on custom recoveries.