Related
So, just like others I have been itching to install the Nougat beta and boy what a ride I had. I used the Charles method and installed the beta successfully. While install was great, the software was not. I had several things missing and It did not go well.
First and foremost, beta is ONLY for FRD-L04 models which is the US 32GB single sim version and NOT for the FRD-L14 64GB models. The beta build really screwed up my phone and I had to downgrade to official MM build. The software doesn't really tell there is a mismatch in the model as technically they are the same specs except for the storage.
To downgrade, I read this thread and then downloaded and restored from the image from the Honor 8 downloads page. Restored to MM successfully but guess what, my model number showed FRD-L04 and not FRD-L14. This was a problem. Why? Well, it turns out when you set up Android Pay, it clearly tells that I am running a custom ROM. While all day to day function work right, you are still running a custom rom as you are not running the software for FRD-L14.
Honor 8 site does not have the restore image in their downloads page. I called their support and they acknowledged that the restore image available is not for FRD-L14. They are working on it to see why they don't have this image available for download.
So, how do you restore?
Thanks to this thread, I was able to get the full image. Below are the links:
1. update.zip
2. update_data_full_hw_usa.zip (only if you need the bloat)
Download those and flash them from SD card as described in this thread. That will get you the MM build. Below is the build number you should be if you are in MM:
- FRD-L14C567B162
Hope tha helps.
@digitalbreak
Although your post is very informative your missing some key elements.
Where is your Rollback Update.app zip ?
The correct way to restore MM from Nougat is to flash rollback and then your last full update.zip (B162 ?)
you could try the one for the L04 here >> http://download-c.huawei.com/download/downloadCenter?downloadId=92098&version=360320&siteCode=us
the link you posted to FRD-L04, Android 6.0, EMUI 4.1, C567B122 is useless and just makes it confusing
Also flashing the update_data_full_hw_usa.zip is how you update the /cust partition
that's where your Local.prop is stored and that's where your phone gets the information displayed in the Settings / About screens.
So if you had not previously changed the /cust their would be no need to flash it again after the Full update.app is flashed.
You would be able to tell this if your Settings/About screens are wrong after the flash.
Also you state that using the Charles method did not go well ? That's really not possible, because this method downloads the files directly from Huawei servers
and the update is the same as if the OTA were pushed to your phone. Only real way to mess that up is to input the wrong response in Charles App and download the wrong update. If you had linked the correct FRD-L14C567B360 file in Charles you would have had no problems.
Bottom line
If your on Nougat Beta and you want to return to MM
you simply dload flash the Rollback and then the Full B162
and you should be back to stock. If Settings / About is incorrect
dload flash the update.app inside the update_data_full_hw_usa.zip
And just for reference here are all the files available for you phone >> http://hwmt.ru/oth/HWFF/info/view.php?find_model=frd-L14
And to get the correct update_data_full_hw_usa.zip for each version
just edit the update.zip download link
Code:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v72029/f1/full/update.zip
to http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v72029/f1/full/[COLOR="Red"]hw/usa/update_data_full_hw_usa.zip[/COLOR]
The correct way to restore MM from Nougat is to flash rollback and then your last full update.zip (B162 ?)
you could try the one for the L04 here >> http://download-c.huawei.com/downloa...20&siteCode=us
Click to expand...
Click to collapse
Unfortunately that doesn't help for FRD-L14, at least for me as it didnt succeed. I tried the included manual step by step but it did not restore to MM.
Also flashing the update_data_full_hw_usa.zip is how you update the /cust partition
that's where your Local.prop is stored and that's where your phone gets the information displayed in the Settings / About screens.
So if you had not previously changed the /cust their would be no need to flash it again after the Full update.app is flashed.
You would be able to tell this if your Settings/About screens are wrong after the flash.
Click to expand...
Click to collapse
If I am not wrong, when you use Charles method and download the update, it applies those and hence since I had pulled L04 update into my L14, the /cust was changed by the OTA.
Also you state that using the Charles method did not go well ? That's really not possible, because this method downloads the files directly from Huawei servers
Click to expand...
Click to collapse
In the sense that I had pulled the update for the wrong model. It was hard to find that the beta program was only for FRD-L04 and not for FRD-L14. And that thread is so long it is difficult to even guess that if you are a newcomer.
If your on Nougat Beta and you want to return to MM
you simply dload flash the Rollback and then the Full B162
and you should be back to stock. If Settings / About is incorrect
dload flash the update.app inside the update_data_full_hw_usa.zip
Click to expand...
Click to collapse
In theory yes and works well for FRD-L04. I couldnt find the builds in Honor's web site for FRD-L14. Getting to know the servers from other methods is OK, but thats not how most customers do. We geeks do that
digitalbreak said:
Unfortunately that doesn't help for FRD-L14, at least for me as it didnt succeed. I tried the included manual step by step but it did not restore to MM.
If I am not wrong, when you use Charles method and download the update, it applies those and hence since I had pulled L04 update into my L14, the /cust was changed by the OTA.
In the sense that I had pulled the update for the wrong model. It was hard to find that the beta program was only for FRD-L04 and not for FRD-L14. And that thread is so long it is difficult to even guess that if you are a newcomer.
In theory yes and works well for FRD-L04. I couldnt find the builds in Honor's web site for FRD-L14. Getting to know the servers from other methods is OK, but thats not how most customers do. We geeks do that
Click to expand...
Click to collapse
I can do the rollback but I just realized that I have the 64GB version which is the FRD-L14
http://www.phonemore.com/huawei-honor-8/models/629
I'm not sure if there is a FRD-L14(64GB) variant of the MM firmware available anywhere. If so, I'm not aware of the link of the site to find it. Secondly, if I do install the FRD-L04(32GB) variant of the MM firmware would that create problems for the phone in upgrading and later trying to root and install custom ROM etc.
Much Thanks
Installing the FDR-L04 image on FDR-L14 will tell Google that you are using an unidentified or a custom ROM version. That will limit certain services/apps like for example Android Pay and even sometimes updater to work. Android Pay certainly didn't work for me. Some say its just a file that contains the hardware info that needs to change while the rest are the same, but I have had no luck with that approach.
digitalbreak said:
Installing the FDR-L04 image on FDR-L14 will tell Google that you are using an unidentified or a custom ROM version. That will limit certain services/apps like for example Android Pay and even sometimes updater to work. Android Pay certainly didn't work for me. Some say its just a file that contains the hardware info that needs to change while the rest are the same, but I have had no luck with that approach.
Click to expand...
Click to collapse
When you rolled back your L14, do you have service like Android Pay? I really want to roll-back since Nougat/EMUI5 have been terrible on battery life. Is it "legitimately" L14 with the 64GB storage?
digitalbreak said:
So, just like others I have been itching to install the Nougat beta and boy what a ride I had. I used the Charles method and installed the beta successfully. While install was great, the software was not. I had several things missing and It did not go well.
First and foremost, beta is ONLY for FRD-L04 models which is the US 32GB single sim version and NOT for the FRD-L14 64GB models. The beta build really screwed up my phone and I had to downgrade to official MM build. The software doesn't really tell there is a mismatch in the model as technically they are the same specs except for the storage.
To downgrade, I read this thread and then downloaded and restored from the image from the Honor 8 downloads page. Restored to MM successfully but guess what, my model number showed FRD-L04 and not FRD-L14. This was a problem. Why? Well, it turns out when you set up Android Pay, it clearly tells that I am running a custom ROM. While all day to day function work right, you are still running a custom rom as you are not running the software for FRD-L14.
Honor 8 site does not have the restore image in their downloads page. I called their support and they acknowledged that the restore image available is not for FRD-L14. They are working on it to see why they don't have this image available for download.
So, how do you restore?
Thanks to this thread, I was able to get the full image. Below are the links:
1. update.zip
2. update_data_full_hw_usa.zip (only if you need the bloat)
Download those and flash them from SD card as described in this thread. That will get you the MM build. Below is the build number you should be if you are in MM:
- FRD-L14C567B162
Hope tha helps.
Click to expand...
Click to collapse
I just tried this method to get back to MM from N B360. Unfortunately the software always failed with the error: "Software install failed! Incompatibility with current version. Please download the correct update package!" I downloaded the file from your link and confirmed the MD5 hash is correct. Did I miss something? I am currently running the OFFICIAL Nougat B360 on FRD-L14. Thank you.
KevinN206 said:
I just tried this method to get back to MM from N B360. Unfortunately the software always failed with the error: "Software install failed! Incompatibility with current version. Please download the correct update package!" I downloaded the file from your link and confirmed the MD5 hash is correct. Did I miss something? I am currently running the OFFICIAL Nougat B360 on FRD-L14. Thank you.
Click to expand...
Click to collapse
Did you install the rollback image first from the Honor site? Not the full one, just the rollback package. Once you install that, then you can install the full package.
digitalbreak said:
Did you install the rollback image first from the Honor site? Not the full one, just the rollback package. Once you install that, then you can install the full package.
Click to expand...
Click to collapse
Are you talking about the rollback package here? Is this the same rollback for the L14? The description says it's for L04. http://www.hihonor.com/us/support/details/index.html?DOC_ID=92098
How do I flash this rollback image and in what order compared to UPDATE.APP?
I will research into this more when I get home from work tonight. Thank you!
KevinN206 said:
Are you talking about the rollback package here? Is this the same rollback for the L14? The description says it's for L04. http://www.hihonor.com/us/support/details/index.html?DOC_ID=92098
How do I flash this rollback image and in what order compared to UPDATE.APP?
I will research into this more when I get home from work tonight. Thank you!
Click to expand...
Click to collapse
I had an issue with this yesterday too.
If you still have access to TWRP, try deleting the data partition too. I think that sets it to a test mode than you can then downgrade.
From there I used the dload method to flash the rollback package, and then I flashed a full MM package.
I really wish Huawei would release a damn full Nougat image so we didn't have to do this each time (unless you really want to go back to MM)
SolarisSixth said:
I had an issue with this yesterday too.
If you still have access to TWRP, try deleting the data partition too. I think that sets it to a test mode than you can then downgrade.
From there I used the dload method to flash the rollback package, and then I flashed a full MM package.
I really wish Huawei would release a damn full Nougat image so we didn't have to do this each time (unless you really want to go back to MM)
Click to expand...
Click to collapse
I downloaded the rollback image except the instruction mentions L04. Is okay to install this rollback image on the L14 with 64GB? My phone was never part of Nougat beta and I don't have root. Never installed TWRP.
I just want to go back to MM because Nougat on my L14 has been a disaster on battery life. It also caused my audio to skip especially spotify when stream to bluetooth and I try to use the Internet.
KevinN206 said:
I downloaded the rollback image except the instruction mentions L04. Is okay to install this rollback image on the L14 with 64GB?
Click to expand...
Click to collapse
Yup. Like I said, same issue. I have the L14 and that package is only for the L04.
I flashed it and seemed ok. Although I still think that wiping the data partition maybe had something to do with it.
Good luck either way!
I want to downgrade myself but don't want to mess up my phone. Huawei is really stupid of just putting the downgrade package only for the 32gb version of the phone.
Rollback image is Ok but don't download the full image as that is the one tied to L04.
I chatted with Honor support twice to give us a L14 image and they haven't done it yet. I would really ask you guys to do the same if you can as that will put pressure on them.
digitalbreak said:
Rollback image is Ok but don't download the full image as that is the one tied to L04.
I chatted with Honor support twice to give us a L14 image and they haven't done it yet. I would really ask you guys to do the same if you can as that will put pressure on them.
Click to expand...
Click to collapse
I have good news. The rollback image for L04 worked fine on my L14. After flashing that, I was able to install the actual update from your link. My phone is still identified as L14 and the 64GB is intact. My Android Pay is fully functional. Thank you very much.
Glad it worked for you!
frommars6 said:
I want to downgrade myself but don't want to mess up my phone. Huawei is really stupid of just putting the downgrade package only for the 32gb version of the phone.
Click to expand...
Click to collapse
I have the L14 64GB version and the downgrade was actually flawless. You will need to download the main update file per OP and also download the rollback image for the L04 from my prior post. It's a compressed RAR file so you can use 7zip to decompress. Ignore the instruction inside the file. My rollback went without a hitch but my phone is not rooted and no TWRP installed. Everything is stock so YMMV.
Create a folder "dload" in your micro SD card and copy in the UPDATE.APP from the rollback image. This file is about 67 MB.
Turn-off the phone.
Press Vol+, Vol-, and Power Button simultaneously until it turns on. Keep them all pressed until you see the update screen. You can release the buttons when you see them. The rollback image takes about 30-60 seconds to complete. The phone will reboot when completed.
The phone will restart back into Android. Turn-off the phone and remove the micro SD card.
Delete UPDATE.APP rollback image (67 MB) from folder dload.
Copy the UPDATE.APP file from the L14 image into dload. The file is about 3 GB after decompression.
Re-insert micro SD into phone and restart per step # 3.
The update screen will appear and it'll start to install the L14 image.
I believe it'll auto restart after completion (don't remember). The entire process should take 5-10 minutes.
Congratulations!!! Now you are back to MM.
KevinN206 said:
I have the L14 64GB version and the downgrade was actually flawless. You will need to download the main update file per OP and also download the rollback image for the L04 from my prior post. It's a compressed RAR file so you can use 7zip to decompress. Ignore the instruction inside the file. My rollback went without a hitch but my phone is not rooted and no TWRP installed. Everything is stock so YMMV.
Create a folder "dload" in your micro SD card and copy in the UPDATE.APP from the rollback image. This file is about 67 MB.
Turn-off the phone.
Press Vol+, Vol-, and Power Button simultaneously until it turns on. Keep them all pressed until you see the update screen. You can release the buttons when you see them. The rollback image takes about 30-60 seconds to complete. The phone will reboot when completed.
The phone will restart back into Android. Turn-off the phone and remove the micro SD card.
Delete UPDATE.APP rollback image (67 MB) from folder dload.
Copy the UPDATE.APP file from the L14 image into dload. The file is about 3 GB after decompression.
Re-insert micro SD into phone and restart per step # 3.
The update screen will appear and it'll start to install the L14 image.
I believe it'll auto restart after completion (don't remember). The entire process should take 5-10 minutes.
Congratulations!!! Now you are back to MM.
Click to expand...
Click to collapse
I did follow your steps, but my keyboard has now vanished when the set up screen appears. It only shows google voice and I'm having trouble setting up my phone. Has anyone had the same problem. What can I do to get my keyboard back?
Note: my phone is unrooted. Not sure if that makes a difference
KevinN206 said:
I have the L14 64GB version and the downgrade was actually flawless. You will need to download the main update file per OP and also download the rollback image for the L04 from my prior post. It's a compressed RAR file so you can use 7zip to decompress. Ignore the instruction inside the file. My rollback went without a hitch but my phone is not rooted and no TWRP installed. Everything is stock so YMMV.
Create a folder "dload" in your micro SD card and copy in the UPDATE.APP from the rollback image. This file is about 67 MB.
Turn-off the phone.
Press Vol+, Vol-, and Power Button simultaneously until it turns on. Keep them all pressed until you see the update screen. You can release the buttons when you see them. The rollback image takes about 30-60 seconds to complete. The phone will reboot when completed.
The phone will restart back into Android. Turn-off the phone and remove the micro SD card.
Delete UPDATE.APP rollback image (67 MB) from folder dload.
Copy the UPDATE.APP file from the L14 image into dload. The file is about 3 GB after decompression.
Re-insert micro SD into phone and restart per step # 3.
The update screen will appear and it'll start to install the L14 image.
I believe it'll auto restart after completion (don't remember). The entire process should take 5-10 minutes.
Congratulations!!! Now you are back to MM.
Click to expand...
Click to collapse
Sorry to bring this thread up again... I just followed this and got to B162 (L04), but my device is L14.
How can I start updating towards B385 for L14?
Anyone have any step by step instructions?
coolest35 said:
Sorry to bring this thread up again... I just followed this and got to B162 (L04), but my device is L14.
How can I start updating towards B385 for L14?
Anyone have any step by step instructions?
Click to expand...
Click to collapse
You need to make sure that the full update image (3GB) is already for the L14 version and not the L04.
In the second post in this thread there is a link to all the current L14 packages. In the list locate the one that has the version B162 and download it. Extract the UPDATE.APP and use that as the MM package for your specific phone.
Just FYI, the rollback image is branded for L04, however at that point it's only preparing the phone to allow to receive a update package that is of lower version than what you currently have (going from N back to MM). So even though you have the 64GB L14 version the roll back image will work regardless.
Once you are back to MM and your device is recognized as L14 once again, it should start taking OTA updates. This will get you back to stock N.
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
[SOLVED] Hi i was on l-31c432b381 firmware with emui 5.0 and android 7.0, i have unlocked the bootloader for install magisk 12.0 and have root permissions, after months i saw an update for my phone (b389) so i tried to upgrade but i had twrp so error 1 or 7, i flashed the stock recovery, redowload the update and the install failed at 5%, so i tried to unistall magisk before update, but nothing it wont update, after few tries the upgrader says that the update now is not 300mb but is full and is 2gigs, so i think is the time.. but no. so i tried to force the update with 3 buttons recovery dload method but it doesn't work at all 5% at every try. so i searched for support and i found that the ota connot be installed on unlocked devices, so i tried to relock my bootloader with oem relock and the unlock number but it says root type is risk... so i can't even relock my bootloader.. other says that i have to install to relock or can relock... but is b381 the stock? or they instend the mm version? i don't remember what version p9 lite ships. i tried to flash imgs through fastboot but even if i flash system and boot of the b389 the system boot and the info are of the b381, unisatlling app system crash, so i restored my previous backup made through twrp recovery, i immidiatly noticed that the huawei boot animations was gone and was an android stock animation. i thinked it was fine and all was working properly, i give up o upgrade and i was fine but sad. after few hours i tried to make a paper copy with my printer that have nfc but my phone keep shows and hide nfc symbol like on off on off on off over and over even after reboot, after a call i understand that the audio doesn't was working, every type of audio not work even the mic. i don't see any other problems but without sounds is unusable as a phone or mulimedia things... sorry for bad english please HELP i tried all i founded ...
Franseven said:
Hi i was on l-31c432b381 firmware with emui 5.0 and android 7.0, i have unlocked the bootloader for install magisk 12.0 and have root permissions, after months i saw an update for my phone (b389) so i tried to upgrade but i had twrp so error 1 or 7, i flashed the stock recovery, redowload the update and the install failed at 5%, so i tried to unistall magisk before update, but nothing it wont update, after few tries the upgrader says that the update now is not 300mb but is full and is 2gigs, so i think is the time.. but no. so i tried to force the update with 3 buttons recovery dload method but it doesn't work at all 5% at every try. so i searched for support and i found that the ota connot be installed on unlocked devices, so i tried to relock my bootloader with oem relock and the unlock number but it says root type is risk... so i can't even relock my bootloader.. other says that i have to install to relock or can relock... but is b381 the stock? or they instend the mm version? i don't remember what version p9 lite ships. i tried to flash imgs through fastboot but even if i flash system and boot of the b389 the system boot and the info are of the b381, unisatlling app system crash, so i restored my previous backup made through twrp recovery, i immidiatly noticed that the huawei boot animations was gone and was an android stock animation. i thinked it was fine and all was working properly, i give up o upgrade and i was fine but sad. after few hours i tried to make a paper copy with my printer that have nfc but my phone keep shows and hide nfc symbol like on off on off on off over and over even after reboot, after a call i understand that the audio doesn't was working, every type of audio not work even the mic. i don't see any other problems but without sounds is unusable as a phone or mulimedia things... sorry for bad english please HELP i tried all i founded ...
Click to expand...
Click to collapse
Hi, my english is bad too , B389 is an OTA update, its impossible upgrade via fstboot or via TWRP (error 7). IMO the right way to fix your problems - downgrade to MM , then back to Nougat etc. (remove pattern Lock , Fingerprint lock, root etc. before installing downgrade). It will erase all your phone data!!!
Download official rollback package for your VNS-L31C432
http://download-c1.huawei.com/download/downloadCenter?downloadId=93789&version=373429&siteCode=sk
and download MM firmware VNS-L31C432B161 (Single SIM)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66022/f1/full/update.zip
1) Create a new folder dload in root directory of SD card (root directory : it means dont put it in any folder .) Now unpack the rollback package and copy its contents “UPDATE.APP” to the “dload” folder. Use the 3 button combo installation. After your firmware version should now be on “B300” or "test-keys".
2) Remove from dload folder rollback package, extract the ZIP file with MM firmware to the dload folder and use 3 combo button installation.
Or you can use this method : on your phone launch the phone dialer app and dial *#*#2846579#*#*. Next, select Project Menu – > Software upgrade – > SDcard upgrade – > and confirm the flashing process that is about to be initiated.
Good luck!
bozka1 said:
Hi, my english is bad too , B389 is an OTA update, its impossible upgrade via fstboot or via TWRP (error 7). IMO the right way to fix your problems - downgrade to MM , then back to Nougat etc. (remove pattern Lock , Fingerprint lock, root etc. before installing downgrade). It will erase all your phone data!!!
Download official rollback package for your VNS-L31C432
http://download-c1.huawei.com/download/downloadCenter?downloadId=93789&version=373429&siteCode=sk
and download MM firmware VNS-L31C432B161 (Single SIM)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v66022/f1/full/update.zip
1) Create a new folder dload in root directory of SD card (root directory : it means dont put it in any folder .) Now unpack the rollback package and copy its contents “UPDATE.APP” to the “dload” folder. Use the 3 button combo installation. After your firmware version should now be on “B300” or "test-keys".
2) Remove from dload folder rollback package, extract the ZIP file with MM firmware to the dload folder and use 3 combo button installation.
Or you can use this method : on your phone launch the phone dialer app and dial *#*#2846579#*#*. Next, select Project Menu – > Software upgrade – > SDcard upgrade – > and confirm the flashing process that is about to be initiated.
Good luck!
Click to expand...
Click to collapse
Ok i'm posting in real time now. i'm copy update.app in dload folder (rollback)
it have completed ... wow
same android boot animation, the version says is nrd90m test keys (still no audio)
now i'm copying full mm firmware
its installing 40% i'm loving you.. 50% 60% 70%80%90% SUCCESS
user reset... OK
huawei boot animation with audio!!!!!!!!!!!!!!! and there is not unlocked text like (......can't be trusted...)
ok wifi connected skip.skip skip.... start
song... AUDIO WORKING
recording, its working, nfc ok
i'm on b161 and it shows update, now, can i update to the latest version?
THANK YOU SO MUCH
Franseven said:
Ok i'm posting in real time now. i'm copy update.app in dload folder (rollback)
it have completed ... wow
same android boot animation, the version says is nrd90m test keys (still no audio)
now i'm copying full mm firmware
its installing 40% i'm loving you.. 50% 60% 70%80%90% SUCCESS
user reset... OK
huawei boot animation with audio!!!!!!!!!!!!!!! and there is not unlocked text like (......can't be trusted...)
ok wifi connected skip.skip skip.... start
song... AUDIO WORKING
recording, its working, nfc ok
i'm on b161 and it shows update, now, can i update to the latest version?
THANK YOU SO MUCH
Click to expand...
Click to collapse
Yes, you can. Via OTA, or you can use TWRP (Meticulus 3.0.2.0 only ! ) and flash both .zip files. You must download two files:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v80474/f1/full/update.zip
and
http://update.hicloud.com:8180/TDS/...-L11_hw_eu/update_data_full_VNS-L11_hw_eu.zip.
In TWRP set Install, then select memmory SD card, and klick on
update.zip, confirm installation. After, STAY in TWRP, go back to Install, find file ...hw_eu....zip , confirm installation. Then select rebot system. Done!
bozka1 said:
Yes, you can. Via OTA, or you can use TWRP (Meticulus 3.0.2.0 only ! ) and flash both .zip files. You must download two files:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v80474/f1/full/update.zip
and
http://update.hicloud.com:8180/TDS/...-L11_hw_eu/update_data_full_VNS-L11_hw_eu.zip.
In TWRP set Install, then select memmory SD card, and klick on
update.zip, confirm installation. After, STAY in TWRP, go back to Install, find file ...hw_eu....zip , confirm installation. Then select rebot system. Done!
Click to expand...
Click to collapse
i've done b371 thrugh updater now it doesn't show newer versions but i'm using b389 dload and it should go ok right? (full b389 update.app)
Franseven said:
i've done b371 thrugh updater now it doesn't show newer versions but i'm using b389 dload and it should go ok right? (full b389 update.app)
Click to expand...
Click to collapse
Try it, but I think, you will get a message "not compatible" . Via dload its impossible, IMO use rather Huawei firmware finder or wait for OTA update.
bozka1 said:
Try it, but I think, you will get a message "not compatible" . Via dload its impossible, IMO use rather Huawei firmware finder or wait for OTA update.
Click to expand...
Click to collapse
yes it failed with b389 dload full
i'm on b371, i've to download and flash manually the b381 and after b389? where i can find otas?
Franseven said:
yes it failed with b389 dload full
i'm on b371, i've to download and flash manually the b381 and after b389? where i can find otas?
Click to expand...
Click to collapse
If I said, it's impossible manually update to 381 or 389 using OTA firmware, trust me . Try Firmware finder. GL!
bozka1 said:
If I said, it's impossible manually update to 381 or 389 using OTA firmware, trust me . Try Firmware finder. GL!
Click to expand...
Click to collapse
i tried full ota (firmware finder) flashes from twrp but gives error 7
e:unknown command [errno]
update_huawei_pkg_from_ota_zip: failed
Franseven said:
i tried full ota (firmware finder) flashes from twrp but gives error 7
e:unknown command [errno]
update_huawei_pkg_from_ota_zip: failed
Click to expand...
Click to collapse
https://m.youtube.com/watch?v=s5hHTZ4LGMM
bozka1 said:
https://m.youtube.com/watch?v=s5hHTZ4LGMM
Click to expand...
Click to collapse
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Franseven said:
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Click to expand...
Click to collapse
FF works with proxy fine, but you must first download and install Firmware finder proxy apk. On Nougat use TWRP 3.1.0-2.
---------- Post added at 21:03 ---------- Previous post was at 20:59 ----------
Franseven said:
it worked with the dns method not the proxy (was keeping redownload infinite patch over 4gigs tot crazy)
i'm now back at b381 with sound but without my data, i'm trying to reach b389 and over, can i restore through twrp only data partition without a hitch?
in b389 emui is 5.0.1 if i remember right. its data compatible? are the data the cause of no sound? thanks
ALL WORKED FINE , ALL SOLVED. currently b391 (latest) emui 5.0.1 and all my data, super happy thank you
2EDIT: nfc chip still not work, when selected emui crash. minor problem..
note: twrp by (that you said) didn't work in emui 5+ i'm using newer revolution based one twrp 3.03
Click to expand...
Click to collapse
FF works with proxy , but you must download and install Firmware finder proxy apk. On Nougat use TWRP 3.1.0-2.
OMG, sorry !
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
..
Hey everyone! i want to roll back to oreo since it has support for my language.
How can i do so? i use the a2017u
i just download the b35 nougat package and flash it trough recovery?
thanks a lot!
Igorperrotta said:
Hey everyone! i want to roll back to oreo since it has support for my language.
How can i do so? i use the a2017u
i just download the b35 nougat package and flash it trough recovery?
thanks a lot!
Click to expand...
Click to collapse
roll back to Oreo? What are you running right now then?
If you mean roll back to Nougat then yeah, just download the official b35 package, get the update.zip from inside the zip, and put it in the root of the internal storage, then go to Updates and it should appear
If it doesn't put it in an SD card and install it from the recovery
Also, G Oreo probably has support for your language, if you want to stay on stock+ firmware just flash oreo B03 from the G, but remember to flash the U modem
Choose an username... said:
roll back to Oreo? What are you running right now then?
If you mean roll back to Nougat then yeah, just download the official b35 package, get the update.zip from inside the zip, and put it in the root of the internal storage, then go to Updates and it should appear
If it doesn't put it in an SD card and install it from the recovery
Also, G Oreo probably has support for your language, if you want to stay on stock+ firmware just flash oreo B03 from the G, but remember to flash the U modem
Click to expand...
Click to collapse
Hey, I'm having the same problem when I try to roll back from Oreo. I tried putting the update.zip in both internat and external storage but the updates just fails, even from recovery.
bieljacintho said:
Hey, I'm having the same problem when I try to roll back from Oreo. I tried putting the update.zip in both internat and external storage but the updates just fails, even from recovery.
Click to expand...
Click to collapse
Try enabling USB debugging, I don't recall if it was needed or not for the recovery update but it might be. If it fails you'll have to go EDL Tool, simply get it from the ROMs, kernels, development section and also download the B35 EDL package from there. Flash the package and you're done.