Database Users

[GUIDE][ROOT][UNIVERSAL] FORCE INSTALLING STOCK OTA UPDATES WITH SToCK RECOVERY

Since lollipop there is no manual update option in huawei updater and even the huawei stock recovery has no or less interface which has no adb sideload option. This became a crunch to flash the update which your friend got and which u dont.
This Method is Universal for all huawei devices
In order to apply ota update using this method , root access is a major requirement so be sure your device is rooted.
If u had twrp recovery , at first flash SuperSu package to root your device (Try systemless root only) .
After successfull root ,flash stock recovery from twrp and reboot system.
Step 1:
In my case b370 is the last ota i found for kiw-l22 which vsriram92 posted here . Thanks to him for posting the update before 99% users got their update :good:
Download the relevant update package (ota) which you need a relevant base package to install it on . Ex: b360 as base for b370 update
step 2:
just remember the path where u downloaded the package . Install Flashify from playstore or From Here
Select Zip file which is the third option in flashify .
step 3 :
Navigate to the path where u downloaded ota package select the update.zip (ota package).
flashify starts downloading the package to its path asks you for root access .
Grand Su permissions , Select Cwm recovery if flashify asks as the next option.
Now the phone reboots to recovery and starts flashing.
After the ota update , your device will be unrooted . so take a backup of your stock recovery by following below guide.
Enable Usb debugging and connect ur phone to pc.
navigate to adb folder and place twrp.img or recovery.img in adb folder ,open command window from the same folder and type
Code:
adb reboot bootloader
Now type
Code:
fastboot boot recovery.img
or what_ever_its_name.img
now it temporarily boots twrp , take a backup of your stock recovery and then flash twrp for permanent install and then reroot ur device.
Happy flashing :laugh::good:​

it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified

rbtrai said:
it gets zip signature verification failed....the method is similar to installing the zip file directly from the recovery but that doesn't work unless zip signature is verified
Click to expand...
Click to collapse
You might have installed a zip which is not stock ota update . i haven't posted this without trying . I installed b370 with this method and made this live here .

i downloaded from the link provided above which vsriram92 posted...

rbtrai said:
i downloaded from the link provided above which vsriram92 posted...
Click to expand...
Click to collapse
Were you in b360 before doing this ?

Thanks again Gopi. Another great contribution.

vsriram92 said:
Were you in b360 before doing this ?
Click to expand...
Click to collapse
yes ofcourse

This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option

Ajith san said:
This only for rooted phone ?
I'm having honor 4x unroot and I don't know how to install the ota file. Is there any way for upgrading a phone without root option and in my phone there is no local update option
Click to expand...
Click to collapse
Nope. It was there in EMUI 3 previously. Now, we can't unless it has only update.app.

so b370 is only for the ones who gave root access to their phones?

Like your contribution. Perfectly updated to B370.

rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
great

Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?

Zacki06 said:
Hello together, I tried flashing the B360 update for my L21 with this method but unfortunately I did not succeed. I followed every step but when flashify reboots to the stock recovery nothing happens. Just nothing.
I used the file for the L21 that I linked to in this post.
Any suggestions how to get it to work?
Click to expand...
Click to collapse
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...

ShadySquirrel said:
Are you on B350D0003 or some earlier firmware? I'm on stock B350, just rooted with Magisk+phh's superuser, and it doesn't want to flash that big file at all; tried flashing OTA update (200MB file) and it failed at 80%, causing a damn bootloop. Gah, I thought my old phone was pain in the ass...
Click to expand...
Click to collapse
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.

Zacki06 said:
I'm on B350D003. After I tried the OTA instead of the full package I came across the same problem with the stock recovery, but when flashing it from TWRP it did flash it, but exited with an error.
No bootloop but as a file was missing for the full update process wifi (and probably bluetooth) are not working.
If you are interrested to solve it, have a look here. It looks like there is a way to fix the problem and we are currently investigating.
Click to expand...
Click to collapse
TBH, I'm on a verge to start building LOS or PAC/Slim/whatever is properly maintained and fast for my own needs and ditch EMUI completely....
I'm searching for other firmwares now via FirmwareFinder, there is a probability that one is a leaked test or something like that, because it simply doesn't want to flash. If I find out something, I'll continue on thread you've linked, to avoid flooding this one.

Hi. Thanks for your guide.
I need to update my phone with several ota updates. I just need to repeat this guide's procedure until updated to the last ota or there is a better way to do that?

Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
rajibie said:
Like your contribution. Perfectly updated to B370.
Click to expand...
Click to collapse
How to update step by step.. Mention it plz

Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just because you can't do it, that doesn't mean it's fake.

Tapan Patel said:
Can't update.. Its fake i think.. I m still in B360
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
How to update step by step.. Mention it plz
Click to expand...
Click to collapse
Just follow the procedure and you will be done

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue

EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29

Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.

lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.

First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.

WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.

Only use ota if you don't want twrp/root anymore.

Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2

H901 T-Mobile Nougat v30b TWRP flashable update.zip

If you have already upgraded to Nougat using the manual method I posted, you don't need to flash this. If you do, you will get all the bloat back (again), and have to flash your su bin (again), but it isn't going to break your phone.
This is for the H901. Make SURE you have an ACTUAL H901, and not one of the half / half H901 / F600 phones.
If you are still on MM (any version), NOT LP, then you can use this to upgrade (or clean install -- just do a wipe) to Android 7.0 Nougat. This is from the official KDZ that was released on July 18th.
When you flash this, all the carrier bloat / LG bloat / crap / garbage, will come back. You will also lose root until you flash the su bin of your choice. That is the point of this, you WON'T lose TWRP, so you can still root...
Any questions, don't hesitate to ask.
Lastly, when I have time, I will be releasing a version that is already debloated...
Download v30b_update.zip
SHA1: 4ae9338b9301f4b56437ec761b678c8706c90bc7
If you want the FULL Nougat experience -- that is ALL of the v30b firmware except the stock recovery (we don't want to lose TWRP do we?), then flash this as well.
If you flash this, then you might as well delete all of your MM backups that you made with TWRP because you can no longer restore to MM using your backups (you can flash back to MM -- just not with the backups).
If you choose to ignore this, and decide to restore a MM backup, you will brick your phone.
Download full_nougat.zip
SHA1: b1ac20a6eaccf2dfbd22c09886ddcd03ab638ec3
Known working (tested by me) SU binary: download SuperSU 2.82.
SHA1: d980effb25a8f23bc944d6b1015923f310038031
It has also been confirmed by multiple users that Magisk 12+ works, but I have not confirmed that myself.
This will not wipe ANY of your data / apps / or anything else you may have on your phone. That is why it is an UPGRADE and not a CLEAN install
If you want to do a clean install, just do a full wipe, and then flash.
If you downloaded any of my failed attempts (really -- a typo in a ui_print line?!?!?), and don't want to download the whole zip again, you can download this zip. It is the META-INF directory. You will need to unzip the broken v30b_update.zip, and then extract this over top of the META-INF dir, and then zip it back up.
Make sure you use recursion, and make sure you unzip it on TOP of the META-INF dir, not inside it -- or you will end up with META-INF/META-INF/com/google/android. Won't break your phone, but won't flash either.
-- Brian

Thank you so much man you just made my day...
it will be nice if you can share the recommended SU zip...

Any of the current SUs will work. I am using SuperSU 2.82 (hell, there may be a newer version, but it works, so I don't bother), but I know that Magisk will work as well.
-- Brian

seems that my TWRP has a problem
during update it says "could not find 'META-INF/com/google/android/update-binary' in the zip file"
any help :/?

having the same problem too bad for me !!
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
Just opened the zip file and notices META-INF folder is empty there are suppose to be some files in there which helps flash a file...

Weird. I just unzipped it, and it is there. I grabbed the update-binary from one of my LG G4 trees. It shouldn't matter, but I will replace the update-binary, and re-upload.
Sorry about that guys. Unfortunately I can't test this, well I could, but I really don't want to debloat my phone again
It is a SUPER simple script though...
-- Brian

Well THERES the problem. I uploaded the bad copy. I zipped without recursion the first time. Thought I nuked that copy. I am uploading the proper version now -- ya know -- with an ACTUAL META-INF dir
-- Brian

JiggyTox said:
seems that my TWRP has a problem
during update it says "could not find 'META-INF/com/google/android/update-binary' in the zip file"
any help :/?
Click to expand...
Click to collapse
runningnak3d said:
Weird. I just unzipped it, and it is there. I grabbed the update-binary from one of my LG G4 trees. It shouldn't matter, but I will replace the update-binary, and re-upload.
Sorry about that guys. Unfortunately I can't test this, well I could, but I really don't want to debloat my phone again
It is a SUPER simple script though...
-- Brian
Click to expand...
Click to collapse
if you can only share meta-inf folder, I think it will work if you just copy files into the zip. that'll be awesome!!

OK -- I replaced the update.zip with the proper version, and I added the META-INF zip if you downloaded the bad one and don't want to redownload the whole thing.
-- Brian

Thanks a ton for the work you do helping keep this device alive.
I couldn't wait so I went ahead and unzipped the original update.zip and did the other method of pushing the three images via adb, and it works perfectly! thanks a lot again!

idk
i'm getting an error 6 when trying to flash. i did some research and they say it may be a line of code written somewhere wrong.

runningnak3d said:
OK -- I replaced the update.zip with the proper version, and I added the META-INF zip if you downloaded the bad one and don't want to redownload the whole thing.
-- Brian
Click to expand...
Click to collapse
thanks man :highfive:

DroxOh said:
i'm getting an error 6 when trying to flash. i did some research and they say it may be a line of code written somewhere wrong.
Click to expand...
Click to collapse
Getting the same error as well

Well, what the crap. Edify script is ... or should I say WAS, one of the simplest things in the world. Now that I am off work and don't need my phone, I can actually test this before I post an updated zip.
The only thing I can guess is that the v10 doesn't let you flash from the zip itself, so I am going to extract the files to /tmp and then flash them.....
I will post an update as soon as I have this working. This has never been an issue before.....
-- Brian

Thanks Bro. But, I want to turn off big cores Lg v10 H901 Android 7.0. You can create file off core.zip? Plz....

Help me! when i try to flash it, i get the next msg: Updater process ended with ERROR: 6
---------- Post added at 04:35 AM ---------- Previous post was at 04:23 AM ----------
Tell me something, if i update with LG Bridge.... i will lose the TWRP or Just the root ? I net to update to nougat now :/

You will lose both. I did before I found this thread.
Sent from my LG-H901 using Tapatalk

My H901 was updated to 30L directly via LG Bridge. Can I roll it back to 20L to flash TWRP recovery? I will attempt to kdz via LGup but I wonder if it work or bricks my phone

Ash.... i hope that we can get a solution to make the zip works....

huy chuong said:
My H901 was updated to 30L directly via LG Bridge. Can I roll it back to 20L to flash TWRP recovery? I will attempt to kdz via LGup but I wonder if it work or bricks my phone
Click to expand...
Click to collapse
As far as I know you cannot rollback to MM from Nougat. Just have to wait and see if someone is able to create a rooted and debloated kdz or .tot Nougat Rom for our H901. I tried to use Dirtycow method to root but the fastboot commands do not work.
Sent from my LG-H901 using Tapatalk

Lineage 15 - Vendor Image Mismatch

So this appeared today after updating my Lineage OS. I'm not that deep into custom Android stuff so i have no clue what to do regarding this, could anyone direct me please?
To be specific i'm getting this message:
A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches OPM2.171019.029.A1
Click to expand...
Click to collapse
I only have the OK option and after pressing it is seems the phone works normally yet I still want to resolve this.

@niirb Each months security update will come with a different vendor. So if your on the latest update of your ROM more then likely June's. You can always extract Google's firmware to get it. But usaully it gets posted somewhere in the ROMs thread. I use this site always gets updated . Flash the vendor in either fastboot or with twrp just select zip button to change to image so you can see the file in your downloads .

Exodusche said:
@niirb Each months security update will come with a different vendor. So if your on the latest update of your ROM more then likely June's. You can always extract Google's firmware to get it. But usaully it gets posted somewhere in the ROMs thread. I use this site always gets updated . Flash the vendor in either fastboot or with twrp just select zip button to change to image so you can see the file in your downloads .
Click to expand...
Click to collapse
Thank you! So this is common and I should do this once every month or did something screw up in my update and is this just the exception?

niirb said:
Thank you! So this is common and I should do this once every month or did something screw up in my update and is this just the exception?
Click to expand...
Click to collapse
You didn't break anything. This is completely normal since the LineageOS update doesn't update the vendor image.

Anyone have issue updating to June vendor img? I updated radio bootloader vendor via fastboot said it was installed but didn't tried TWRP same result says it installed but to no avail any suggestions thank you.

Glock45 said:
Anyone have issue updating to June vendor img? I updated radio bootloader vendor via fastboot said it was installed but didn't tried TWRP same result says it installed but to no avail any suggestions thank you.
Click to expand...
Click to collapse
What are you showing as wrong in the picture? Are you getting error on boot up?

Exodusche said:
What are you showing as wrong in the picture? Are you getting error on boot up?[/QUOTE Couldn't update to Build OPM6 was getting mismatch till last update but everything functioning properly
Click to expand...
Click to collapse

Glock45 said:
What are you showing as wrong in the picture? Are you getting error on boot up?[/QUOTE Couldn't update to Build OPM6 was getting mismatch till last update but everything functioning properly
Click to expand...
Click to collapse
Try this page has all the vendors. You can flash in TWRP just to get a match

Exodusche said:
Try this page has all the vendors. You can flash in TWRP just to get a match
Click to expand...
Click to collapse
Thanks I've noticed these are large so I have to extract the vendor img from the dwnld correct?

Glock45 said:
Thanks I've noticed these are large so I have to extract the vendor img from the dwnld correct?
Click to expand...
Click to collapse
No extraction they are large just download the desired vendor/s and flash.

Exodusche said:
No extraction they are large just download the desired vendor/s and flash.
Click to expand...
Click to collapse
Dwnld the opm6 flashed in TWRP still showing opm2 oh well everything is functioning so guess I'll have to leave it! Thanks for the link/help

Glock45 said:
Dwnld the opm6 flashed in TWRP still showing opm2 oh well everything is functioning so guess I'll have to leave it! Thanks for the link/help
Click to expand...
Click to collapse
Oh I get it now yeah the developer didn't change the title to represent the next month's update that's all. General rule of thumb after a week into the month updates should have the corresponding security update.

i am having the same issue, downloaded the vendor file and moved it to twrp. when i click twrp install i can not find the file, i moved the file a second time to twrp and it asked if i want to replace it, so it must be in there somewhere. i searched the files but did not find it. any idea where it is located? thanks
edit: i downloaded the vendor file directly on the phone. the file manager shows it in the phone dl file. when i open twrp/install/download it is empty?

i run sideload and get "zip file is corrupt!" this is in linux.
[email protected]:~/Desktop$ adb start-server
[email protected]:~/Desktop$ adb sideload vendor-angler-OPM6.171019.030.B1.img
Total xfer: 0.00x

dr1445 said:
i am having the same issue, downloaded the vendor file and moved it to twrp. when i click twrp install i can not find the file, i moved the file a second time to twrp and it asked if i want to replace it, so it must be in there somewhere. i searched the files but did not find it. any idea where it is located? thanks
edit: i downloaded the vendor file directly on the phone. the file manager shows it in the phone dl file. when i open twrp/install/download it is empty?
Click to expand...
Click to collapse
When you're downloading the file in the phone, it should be in /sdcard/download/ folder
But when you're navigating on TWRP, seems you're in /sdcard/twrp/install/download folder. Just go up from TWRP and see if you can see that download folder.

updating failed

So, I just rooted my Huawei P Smart, the 136 update shows up, it does all the install steps, reboots and then says it failed. Do O need to do something on the twrp boot?

Download the full firmware, we lose the option to just update via normal update and we can update with a full system update

airb05 said:
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
Click to expand...
Click to collapse
Just did that, 2 GB download, tries to install, reboots, goes to twrp, then I reboot to normal system and still says update failed.

Pretty sure you'll need stock recovery to update the "normal" way.

callmeWhiskers said:
Pretty sure you'll need stock recovery to update the "normal" way.
Click to expand...
Click to collapse
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL

siivet said:
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
Click to expand...
Click to collapse
I'm not an expert - I always use HuRUpdater to update. It just requires you to download the (exact) right files, renaming them correctly and (like rooting with Magisk) just simply flashing a single .zip in recovery. In case you try it out, remember rule#1: Always make sure you have a (nandroid)backup.
Here are the relevant lines from my "Huawei-related-findings" text file:
#update
"Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
• HUAWEI stock recovery installed
• unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install)."
Click to expand...
Click to collapse
#source XDA
 @st_voss (u=1065667)
https://forum.xda-developers.com/showpost.php?p=73011427&postcount=2
#update
“It's recommended to use a proper custom recovery (with running oeminfo_nvm_server service) like for example*my version of TWRP.
How to use:
Warning: Make sure you know what you are doing and do not flash firmware from other devices.
1. Download firmware files (for official firmware use Huawei Firmware Finder).
2. Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
◦ update.zip (use FullOTA file)
◦ update_all_hw.zip
◦ update_data_public.zip
3. Optional: Put recovery.img in same folder if you want to keep custom recovery.
4. Put HuRUpdater zip in same folder.
 5. Select*only HuRUpdater*to flash in custom recovery.
6. Follow instructions on screen. Flashing can take multiple minutes.
Problems:
• If firmware includes factory reset
◦ Factory reset is not supported by custom recovery. Therefore HuRUpdater will flash stock recovery before launching factory reset. After flashing firmware and doing factory reset, you need to flash recovery manually.”
Click to expand...
Click to collapse
#source XDA
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
#notes HuRUpdater_0.4.zip working

Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip

siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Yes, I'm im the same boat - I guess you also get the "can't have connection" error using the FF app. During the last weeks they had troubles with their service regarding hackers and moving to a new server (according to their telegram group), which have been fixed ("all services working normally now"), and many can use it again - for whatever reason some still can't connect. I tried reinstalling the app, using proxies from different countries - still doesn't let me connect.
But their web interface is working: https://pro-teammt.ru/firmware-database/ though you can't check iirc, if the firmware has been approved for your IMEI.
According to this post:
sun75 said:
It's online now! I suggest you to download the "2018.08.30" .158 "2379" release, if you have a FIG-LX1, L31 board phone.
Click to expand...
Click to collapse
You apparently can download this release (2379) if you own this device/board- though the last time I updated mine (.148) I used the 2079 (154226) one despite owning the exact same device. I'm slightly confused about this
I didn't try the above mentioned update myself.

siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Try installing an older version of the Firmware Finder app - I switched from (current) v9.0 to v8.9 and it works now
https://apkpure.com/firmware-finder...efinder/download/86-APK?from=versions/version

..