here it is
https://www.youtube.com/watch?v=gNoaWG0vylg
Nothing special, show how can i install it when its not approved
Even if firmware is approved for installation, it is not immediately shown if you check the normal way for updates. That seems to be the only advantage of Firmware Finder. At least this was the case when upgrading to Oreo. The update was shown for 2 weeks in Firmware Finder but not yet approved. Yesterday checked the normal way, no updates, checked in Firmware Finder again and checked if it was approved for installation, which was the case. So I used FF to download and install.
Related
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
Guys i have a problem.
I found approved firmware for my 8.4 LTE version version .123
Right now im on .122
I tap the DNS update, it shows in updater, then i turn off DNS so it can verify and install, it reboots and then fails at around 20%
Am i doing anything wrong?
Thanks
wait for the ota to be pushed by huawei and don't mess around with the firmware finder. At least that's what I'd do
It's an incremental OTA or a full one?
Incremental
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
I just purchased a used AT&T SM-G965U. My carrier is Google Fi. It's running Android 8.0 and Samsung Experience 9.0. Build number is G965USQU3BRK1. Last security patch was November 1, 2018. When I try to update OTA or with Smart Switch both claim my phone is up to date.
I started looking into how I might manually update the phone and found some instructional pages for updating via ODIN, but was not able to find the correct firmware to update to Pie using that method. I did however find a thread on the XDA forums with a download link for an SM-G965U Pie build. Someone posted in that thread that it is possible to update the phone with a micro SD in recovery mode. Even with that being the case the firmware.science page linked in the thread specifically says that the firmware will update my phone from version G965USQS3BRK2 to version G965USQU3CSAB. This seems like a problem since my phone is running G965USQU3BRK1 which I assume is an older build based on the BRK1 designation. Will this update method even work with my phone? Do I need to update to BRK2 before I use the firmware linked in the thread? If so is the BRK2 firmware available for download anywhere? Or failing that is there an ODIN firmware update available?
Update: I tried updating via micro SD in recovery mode using a firmware update downloaded from firmware.science that is supposed to update my SM-G965U from version G965USQU3BRK1
to version G965USQU3CSA5. The update was aborted due to "unexpected contents". I transcribed the error at the bottom of this post. Not sure what else I can do if I can't find an ODIN firmware. If I used the modifed ODIN to flash my phone with U1 firmware would that enable updates through normal (OTA/Smart Switch) channels?
E3005: "EMMC://dev/block/bootdevice/by-name/modem:83300864:2d921fc2a30290a4f894ef4e5528ab83263913ec:84005376: 12c0577b202561c4a0732793bdbaf3a04eca67f0" has unexpected contents.
E:Error in /sideload/package.zip (Status 7)
Installation Aborted.#1
Update 2: I managed to find the ODIN firmware update files and successfully flashed my phone with a Pie build. Disregard this post.
I'm having the identical problem, only with Verizon SM-G965U. Android 8.0.0, last security update Nov 2018. Can someone guide me to the solution?
Thanks
DIncLover said:
I'm having the identical problem, only with Verizon SM-G965U. Android 8.0.0, last security update Nov 2018. Can someone guide me to the solution?
Thanks
Click to expand...
Click to collapse
What firmware are you currently on?
I've done a bit of research since I first posted this and think I know what's going on. This phone was supposedly new, unlocked. Then I found out SM-G965U is actually locked. It booted up with Verizon logo and worked on Verizon network, so I was ok with that. When I checked the firmware version, it was ....BRK1 (I don't have the phone in front of me), which I looked up to be Sprint firmware! This would explain why it doesn't get updates on Verizon's network, wouldn't it? How this came to be, I don't know, but I think I can proceed by getting a later Oreo or maybe Pie version for VZW and flashing it with Odin.
Comments, if any, are welcome.
If memory serves correctly if your firmware is a certain amount of revisions behind what is currently released then the OTA update and samsung switch will say your firmware is up to date. Even though it obviously is not up to date, it has something to do with how far behind in updates the phone is.
In which case you should be able to update your phone using the patched ODIN and the firmware files found on sammobile or via samfirm app. Thee files from sammobile or samfirm are not ones you can flash via SD card in the recovery menu, the OTA files and what are offered on sammobile or samfirm app (and from here unless otherwise specified) are two different things.
I would note that you might have to factory data reset your phone after flashing the new firmware. It's one possible result of flashing a newer firmware to a phone that has an older firmware like that installed.
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...