Hi,
my version of Android doesn't want to update. I get no OTA updates. I tried to install these two updates manually (using dload folder):
[BETA][6.0][EMUI4.0] PLK-L01 B312(WEU) [OTA FULL UPDATE B140]
[STB][5.0][EMUI3.1] PLK-L01 B130(WEU) [OTA UPDATE B121]
On screens the updates seems working fine (it goes till 100% and says upgrade was successful), but after reboot the version is still the same.
Any idea please?
Thank you,
Sebastien.
sebastien_be said:
Hi,
my version of Android doesn't want to update. I get no OTA updates. I tried to install these two updates manually (using dload folder):
[BETA][6.0][EMUI4.0] PLK-L01 B312(WEU) [OTA FULL UPDATE B140]
[STB][5.0][EMUI3.1] PLK-L01 B130(WEU) [OTA UPDATE B121]
On screens the updates seems working fine (it goes till 100% and says upgrade was successful), but after reboot the version is still the same.
Any idea please?
Thank you,
Sebastien.
Click to expand...
Click to collapse
Enter in Hicare and try to request the update.
I actually did not understand much what you want but if you want to install MM, just install B330b manually.
Related
Google just released Factory Image 5.0.2 (LRX22G) for Nexus 10. (and 7 Wifi(2013))
https://developers.google.com/android/nexus/images
I noticed that as well. Any reason why it's not alerting me to update? I can always d/l the link, but that does a full wipe and don't really feel like setting things back up again.
Any reason why it's not doing the update on it's own?
tclarkey said:
Any reason why it's not doing the update on it's own?
Click to expand...
Click to collapse
Google does staged rollouts with OTA of new Android versions, so at first only 1% of devices receives the new update (source: Droid-Life).
As soon as someone gets the OTA url and publishes it, it will appear on this thread and you can sideload it without having to do a factory reset. Alternatively, you could apply the Factory Image without the "-w" flag, but that's a little more risky (although with the minor update from 5.0.1 to 5.0.2 it should be fine, I did it on my Nexus 5 from 5.0 to 5.0.1 and it runs fine).
BorgKing said:
Google does staged rollouts with OTA of new Android versions, so at first only 1% of devices receives the new update (source: Droid-Life).
As soon as someone gets the OTA url and publishes it, it will appear on this thread and you can sideload it without having to do a factory reset. Alternatively, you could apply the Factory Image without the "-w" flag, but that's a little more risky (although with the minor update from 5.0.1 to 5.0.2 it should be fine, I did it on my Nexus 5 from 5.0 to 5.0.1 and it runs fine).
Click to expand...
Click to collapse
Or alternatively unpack and flash only system.img, that will preserve your data.
is that fixed?
http://forum.xda-developers.com/nexus-10/help/android-5-0-sound-problem-charging-t2939672
perfect_ said:
is that fixed?
http://forum.xda-developers.com/nexus-10/help/android-5-0-sound-problem-charging-t2939672
Click to expand...
Click to collapse
No
Just checked and received a ota update on mine for the January security update and few fixes. Anyone else get it?
Just got it, it was fast update, rebooted and everything is okay
Quick question; I have the KIW-L24 model with TWRP and root by SuperSU, on a stock ROM though. I received the notification for the quick OTA update, but I'm worried it might brick my phone. Is it safe for me to download and uninstall it like the system suggests me to?
It sure took them long enough for this but I also got it updated only yesterday after reverting back to Stock via the UPDATE.APP in Dload folder method and pressing all 3 side buttons and letting it do it's thing.
It actually seems the Honor 5X runs better now but am not exactly sure what changed that yet.
Update.app got installed!
RE: I know this is old but...
GrimReaper24 said:
Just checked and received a ota update on mine for the January security update and few fixes. Anyone else get it?
Click to expand...
Click to collapse
Can you share the file, I am on l24 EMUI 4.0 MM 6.0.1 but no ota received.
I installed RROS on my honor 9 (STF-L09C432 from 3 UK) a few weeks ago, however due to many issues with it I decided to go back to EMUI. I eventually managed this using the rebrand guide, but just flashing without rebrand. I flashed B120 firmware as many people said this is the only rom where the torch and capacitive keys work if you are flashing from a non-EMUI OS.
The flash went perfectly and everything works, except I cannot OTA, software update is listing me as being on the latest firmware, but I know it isnt from firmware finder. If I try to upgrade via firmware finder, it all works till the phone restarts, then the recovery just throws an error, and says it can't be installed.
Fastboot says FRP and bootloader are unlocked onscreen however trying to flash anything, or run the rebrand script on a newer firmware just gets command not allowed. I suspect I need to try unlocking the bootloader again, however I don't want to factory reset, as while I can backup app data with huawei backup I preferably need as little downtime as possible
Although the phone passes safety net, I get a error message saying device can't be verified on boot, and huawei apps warn my my phone is insecure.
Does anyone have any other ideas to get it to update, as especially as oreo is rolling out I would like OTA to work?
killmeplease69 said:
I eventually managed this using the rebrand guide, but just flashing without rebrand. I flashed B120 firmware (...) If I try to upgrade via firmware finder, it all works till the phone restarts, then the recovery just throws an error, and says it can't be installed.
Click to expand...
Click to collapse
From C432B120 without ota working I've be able to update straight to 'B183 full ota approved by imei' with Firmware Finder.
I then normal updated with ota from C432B183 to B360.
Tough, it was just a downgrade I did to get back to B120, not a rebrand.
After the downgrade my phone and frp status were both locked.
I think I unlocked them again only once on B183 and thet stay that way after updated to B360. Flash and capacitives button are still working.
oslo83 said:
From C432B120 without ota working I've be able to update straight to 'B183 full ota approved by imei' with Firmware Finder.
I then normal updated with ota from C432B183 to B360.
Tough, it was just a downgrade I did to get back to B120, not a rebrand.
After the downgrade my phone and frp status were both locked.
I think I unlocked them again only once on B183 and thet stay that way after updated to B360. Flash and capacitives button are still working.
Click to expand...
Click to collapse
Thank you, I'm now running B183, I was trying to upgrade one by one by OTA in firmware finder because my internet is appallingly slow, but doing a full B183 flash worked. Just waiting for approved B360 now
Hello!
I have updated to pie .161 using the erecovery method via FF. Now if i use the erecovery normally on my phone it just say "Getting package info failed".
This isnt normalt right? There should always be a possibility to restore my phone via this erecovery right? Whats going on?
Have I messed up my phone now?
Cloudstrife said:
Have I messed up my phone now?
Click to expand...
Click to collapse
Erecovery can not mess up your phone.
Erecovery can only recover to the latest available firmware. I guess one reason why you used erecovery is because you have not received the official ota yet. Obviously it cannot recover to Emui 8 easily and emui9 is not officially pushed to your device yet. Result: erecovery cannot find a firmware to recover yet. Though it should be able to discover the 161 build later. It should be the point of time when you would have received the official ota if you had not upgraded yet manually.
The irony :laugh:
Cloudstrife said:
Hello!
I have updated to pie .161 using the erecovery method via FF. Now if i use the erecovery normally on my phone it just say "Getting package info failed".
This isnt normalt right? There should always be a possibility to restore my phone via this erecovery right? Whats going on?
Have I messed up my phone now?
Click to expand...
Click to collapse
The very same thing happened with me when i update my phone through FunkyHuawei. Erecovery stopped working. Then i roll back to Oreo and then install OTA update. Everhthing is working perfectly fine again. Always use the offcial method.
Same thing happened to me but I used the hicare method so it should be official ota but still broke kt
eyeb said:
Same thing happened to me but I used the hicare method so it should be official ota but still broke kt
Click to expand...
Click to collapse
You cannot break the phone by using either FF or erecovery (if your phone is (re)locked and you install approved firmware). That is a fact.
Erecovery is like official OTA. If the firmware is faulty not approved or otherwise not meant to be installed it will only download but fail to verify and install.
It has been reported by fh though that a factory reset on emui 9 beta builds stopped erecovery from working. That is why they came up with the hisuite method for downgrading/updating on emui9.
0alfred0 said:
You cannot break the phone by using either FF or erecovery (if your phone is (re)locked and you install approved firmware). That is a fact.
Erecovery is like official OTA. If the firmware is faulty not approved or otherwise not meant to be installed it will only download but fail to verify and install.
It has been reported by fh though that a factory reset on emui 9 beta builds stopped erecovery from working. That is why they came up with the hisuite method for downgrading/updating on emui9.
Click to expand...
Click to collapse
I downgraded using hisuite, :/ guess I'm back on android 8, but I don't mind so much since I didn't like android 9 that much. I didn't see any improvements overall so going back to 8 was something I thought about before. Now I have a reason to fix this erecovery thing
Found this interesting, after downgrade to 8, I kept the wireless projection function from Android 9 after I restored the backup.
Edit NVM it was the mirrorcasting
Hi,
I have a Mate 10 ALP-L29 8.0.0.132 (C636), unlocked bootloader, rooted with magisk. I would like to update the phone to Android 9.
After reading lots of posts, I think following procedure may give what I want.
0. downloading current stock firmware from here:
https://pro-teammt.ru/en/online-firmware-database/?firmware_model=alp-l29c636b132&firmware_page=0
1. downloading Android 9 official stock firmware from here:
https://pro-teammt.ru/en/online-fir..._model=ALP-L29C636E2R1P12B159&firmware_page=0
2. flashing back stock RAMDISK.img and RECOVERY_RAMDIS.img from stock 8.0.0.132 firmware
https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
3. Simply waiting for OTA or Using SD card method to update Mate 10 to Android 9.
see: https://huaweiadvices.com/flash-stock-firmware-huawei-honor-phones/
I would appreciate it if someone answer/confirm my following questions:
Will the procedure work?
Is step 2 really necessary?
Will my user data be erased? I don't really mind if I have to re-install my apps.
root will be lost after updating. Is it right?
Thanks.
zagzzig said:
Hi,
I have a Mate 10 ALP-L29 8.0.0.132 (C636), unlocked bootloader, rooted with magisk. I would like to update the phone to Android 9.
After reading lots of posts, I think following procedure may give what I want.
0. downloading current stock firmware from here:
https://pro-teammt.ru/en/online-firmware-database/?firmware_model=alp-l29c636b132&firmware_page=0
1. downloading Android 9 official stock firmware from here:
https://pro-teammt.ru/en/online-fir..._model=ALP-L29C636E2R1P12B159&firmware_page=0
2. flashing back stock RAMDISK.img and RECOVERY_RAMDIS.img from stock 8.0.0.132 firmware
https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
3. Simply waiting for OTA or Using SD card method to update Mate 10 to Android 9.
see: https://huaweiadvices.com/flash-stock-firmware-huawei-honor-phones/
I would appreciate it if someone answer/confirm my following questions:
Will the procedure work?
Is step 2 really necessary?
Will my user data be erased? I don't really mind if I have to re-install my apps.
root will be lost after updating. Is it right?
Thanks.
Click to expand...
Click to collapse
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Pretoriano80 said:
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Click to expand...
Click to collapse
Hi Pretoriano80,
Thanks for your reply. cheers.
Pretoriano80 said:
With EMUI 8 i think that flashing the stock ramdisk would be enough, but it won't hurt flashing the recovery_ramdisk too (in case you have twrp installed).
After that you should receive several OTAs, i don't think it will update directly to EMUI 9.
In case you don't receive any OTA, try with Hisuite on PC.
P. S. Installing the official OTAs is the safest way.
Click to expand...
Click to collapse
Just to update my progress so far.
above procedure worked
all my date remain unchanged.
I lost my root.
however, I got EMUI 9 though OTA!. I kept getting OTA updates after flashed back stock RAMDISK.img and RECOVERY_RAMDIS.img. Here is the list of OTA update I have got.
OTA 8.0.0.143 1.08G, Google Security path Aug, Sept, Oct.
OTA 9.0.0.159 3.88G, ALP-L29 9.0.0.159(C636E2R1P12).
OTA 9.0.0.159(C636E2R1P12patch01), a small 3.8M update on NFC
OTA 9.1.0.300(C636E2R1P12), 3.83G EROFS and GPU turbo 3.0; Security path July 2019
OTA 9.1.0.321(C636E5R1P13), 4.01G Security path Oct 2019
PS. I am in Australia.
I heard the good news that EMUI 10 has been rolled out :fingers-crossed:. Let's just wait...