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
Related
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 All,
I am at the end of my rope with trying to fix my phone. The back story is I successfully rooted my Mate 10 Pro using TWRP and Magisk from a guide I found here. I didn't even want to root this phone until I saw a cool video on mirroring your rooted phone with Android Auto. When that didn't end up working I decided to unroot my phone and return it to factory condition. Unfortunately when I did this my phone would not boot into stock and I lost TWRP of course so it will now only boot into Erecovery and fails to download the update package. I have since paid for FunkyHuawei and also DC-Phoenix. My bootloader is unlocked but the FPR is locked and I was able to flash firmware files using DC-Phoenix. However, it still will not boot up without wanting to go through eRecovery first. I can't find 8.0.0.119 firmaware so I tried 8.0.0.112. Maybe I need to try 8.0.0.110 or another one? It doesn't seam to me that should matter... I also cannot create a DNS because I have stupid Comcast internet and my router doesn't have that option. Am I screwed!?
androidstereoman said:
Hello All,
I am at the end of my rope with trying to fix my phone. The back story is I successfully rooted my Mate 10 Pro using TWRP and Magisk from a guide I found here. I didn't even want to root this phone until I saw a cool video on mirroring your rooted phone with Android Auto. When that didn't end up working I decided to unroot my phone and return it to factory condition. Unfortunately when I did this my phone would not boot into stock and I lost TWRP of course so it will now only boot into Erecovery and fails to download the update package. I have since paid for FunkyHuawei and also DC-Phoenix. My bootloader is unlocked but the FPR is locked and I was able to flash firmware files using DC-Phoenix. However, it still will not boot up without wanting to go through eRecovery first. I can't find 8.0.0.119 firmaware so I tried 8.0.0.112. Maybe I need to try 8.0.0.110 or another one? It doesn't seam to me that should matter... I also cannot create a DNS because I have stupid Comcast internet and my router doesn't have that option. Am I screwed!?
Click to expand...
Click to collapse
So you successfully flashed a full firmware with DC-Phoenix but still doesn't boot? Which version did you flashed and which version were you on.
Also, which method did you used with Phoenix, fastboot with your own firmware?
Tried a factory reset after flashing with Phoenix.
I'm asking all this questions because if Phoenix flashed everything successfully, then it should've worked.
Pretoriano80 said:
So you successfully flashed a full firmware with DC-Phoenix but still doesn't boot? Which version did you flashed and which version were you on.
Also, which method did you used with Phoenix, fastboot with your own firmware?
Tried a factory reset after flashing with Phoenix.
I'm asking all this questions because if Phoenix flashed everything successfully, then it should've worked.
Click to expand...
Click to collapse
I was on BLA-A09 8.0.0.119 before I bricked it. I could not find that version so I flashed it with the closest one I could find, BLA-A09 8.0.0.112. I used DC-Phoenix and opened the Update.APP and flashed in fastboot. I tried a factory reset after flashing and the phone still boots into eRecovery and fails to download the package.
androidstereoman said:
I was on BLA-A09 8.0.0.119 before I bricked it. I could not find that version so I flashed it with the closest one I could find, BLA-A09 8.0.0.112. I used DC-Phoenix and opened the Update.APP and flashed in fastboot. I tried a factory reset after flashing and the phone still boots into eRecovery and fails to download the package.
Click to expand...
Click to collapse
***UPDATE*** I got home and tried flashing BLA-A09 8.0.0.110 using DC-Phoenix and then factory reset the phone after and it worked! I was then able to update to BLA-A09 8.0.0.125 using HiSuite. Success!
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...
I was trying to install a custom rom and was not aware that you can only unlock the bootloader by paying, which is fine but I can't afford it at the moment but by then I downgraded my rom.
I returned to version 9 on my phone OS and was hoping to get updates afterwards through official updates as I was restoring back to stock but I made a mistake and downloaded and installed ANE-LGRP2-OVS 9.1.0.200 which was not the correct one.
I have tried a few roms, copied to SD card in the dload folder but no matter what I try it keeps failing. No matter what I try downgrades and upgrades won't work anymore.
It seems similar to this: https://forum.xda-developers.com/t/downgrade-ane-lx3-ane-lgrp2-ovs-pie-to-oreo.3944399/
Everything does seem to work fine on my phone except the update system and google pay is not happy and not enabling contactless (which I use all the time)
Is there anything I can do to fix my dumbness
How does the dload method fail? Or is it successful in installing a different firmware yet the official update service is still broken?
Have you tried the forced dload method and did a factory reset/wipe data immediately after installation in recovery?
lemon567 said:
How does the dload method fail?
Click to expand...
Click to collapse
for several reasons .
In this specific case it is due to installing the wrong FW (ANE-LGRP2-OVS ). With this build number it is impossible to install another full stock FW or update system via OTA.
I totally forget to mention on here that I solved it. I managed to get hold of a version 8 stock rom and installed it to the SD card, then it was happy to update itself from there all the way up to current version.
I don't know why it worked at that point as I'm pretty sure I tried that same thing several times before but sometimes there are things I cannot explain, it just randomly worked all of a sudden