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
Related
Owners of the factory-unlocked, dual SIM Snapdragon variant labelled as 'a5_dug' in the bootloader mode, will be pleased to know that the update is now available from your stock Lollipop ROM.
Before you begin
Preparation
If you are not using the official update tool, and wish to use OTA files uploaded here, reboot your phone in to its bootloader, and ensure that a5_dug is displayed. This update may not apply to other models, regardless of whether they are dual SIM or not. It most certainly will not apply to the 816G model which uses a MediaTek chipset.
You must ensure that you have 2GB free on the internal eMMC storage before continuing if you wish to update using the stock update tool. The update tool does not download to the microSD card.
The update does not update, unfortunately, the HTC Sense user interface. It uses the same Sense version as Lollipop did, with some minor changes.
Update contents, simplified
Android 6.0.0
HTC Sense 6.0
Additional Google features
Installation
For phones running a stock ROM earlier than Lollipop 5.0.2
Please update your phone to 5.0.2 and proceed to follow the instructions below if you wish to update through the official update tool.
For phones running stock Lollipop 5.0.2
The update is in two parts for phones running stock Lollipop 5.0.2. The first part is less than 60MB (typically), and prepares the phone for the installation of the second, main part, which is around 1.1GB.
Open the 'Settings' app.
Scroll down and select 'About'.
Tap 'System update'
Agree to download the update by pressing 'OK'.
Once downloaded, 'System update downloaded' appears in the notification tray.
Tap this, and tap 'Install'.
Then repeat for the second part.
For phones running custom software
(investigating)
I just got HTC Mail update only!!!
The update could be available around 01 - 02 week, hope so
@gwhite5 seriously!??? No Sense 7 ?!!!
Its great news but plz provide me with the marshmallow ROM for dual sim models with root capabilities! ? thanks in advance
Any news about the a5_dwg models ?
I have A5 Dug (816w).
After OTA update I have Android 6 with Sense 7, not Sense 6...
For devices on custom recovery
I am running official ROM but on custom recovery TWRP and rooted. My question is will this update will be installable on this setup?( Haven't tried yet)
Also I tried rolling back to stock recovery but I have removed few system app in past without backup is there any way to get the apks for them . I got error for HTC Car app . Also will need help on how to install it as a system app, cuz its not avaialble on "/system/priv-app/Automotive_Home/Automotive_Home.apk" .
Any help is appriciated.
TIA
I finally managed to reinstall the automotive_home.apk as system app, i moved back to stock recovery and then tried the OTA update once again still getting the same error " unexpected content" on that path.
could someone please make a twrp backup of the android 6 on the a5_dug ?
@mshtob its already done bro check updates we are still waiting for a5_dwg
pratik14994 said:
@mshtob its already done bro check updates we are still waiting for a5_dwg
Click to expand...
Click to collapse
No sorry I meant a twrp backup because I have twrp and cyanogen mod I was hoping someone could have a twrp backup of stock marshmallow rom so I can restore it
I have A5_DUG (CID: HTC__622 / Asia_HK) and I didn't get the update yet...
Is it because it's rooted with many changes? I didn't have this problem with the previous update so is it just not released yet for my CID?
EDIT: I noticed that version-main is blank in the bootloader
Hi guys
I have desire 816 a5 dug..and i have an update to marshmallow in tow step.
I change my custom recovery to stock and i done full unroot.
When i tap to first step(54mg) after setup and reastart, my phone wait on white screen with htc logo for to long..i reastart again my phone but nothing will happen.
And i have to return my twrp back up to be true.
What should i do?
Thanks
THE_MOJTABA said:
Hi guys
I have desire 816 a5 dug..and i have an update to marshmallow in tow step.
I change my custom recovery to stock and i done full unroot.
When i tap to first step(54mg) after setup and reastart, my phone wait on white screen with htc logo for to long..i reastart again my phone but nothing will happen.
And i have to return my twrp back up to be true.
What should i do?
Thanks
Click to expand...
Click to collapse
you can use this MM backup
http://forum.xda-developers.com/desire-816/general/twrp-backup-htc-desire-816-a5dug-dual-t3336060
Extract recovery from the OTA file.
It happened to me and I extracted the recovery image from the downloaded OTA update.
copied the OTA zip file to computer. unzipped and extracted the firmware.zip file from it. Flashed recovery again to this new recovery (basically both are stock). This worked for me and i can go till the recovery screen.
---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------
THE_MOJTABA said:
Hi guys
I have desire 816 a5 dug..and i have an update to marshmallow in tow step.
I change my custom recovery to stock and i done full unroot.
When i tap to first step(54mg) after setup and reastart, my phone wait on white screen with htc logo for to long..i reastart again my phone but nothing will happen.
And i have to return my twrp back up to be true.
What should i do?
Thanks
Click to expand...
Click to collapse
It happened to me and I extracted the recovery image from the downloaded OTA update.
copied the OTA zip file to computer. unzipped and extracted the firmware.zip file from it. Flashed recovery again to this new recovery (basically both are stock). This worked for me and i can go till the recovery screen.
need lolipop recovery guys
Tnx for your help
kyyubikiller said:
It happened to me and I extracted the recovery image from the downloaded OTA update.
copied the OTA zip file to computer. unzipped and extracted the firmware.zip file from it. Flashed recovery again to this new recovery (basically both are stock). This worked for me and i can go till the recovery screen.
---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------
It happened to me and I extracted the recovery image from the downloaded OTA update.
copied the OTA zip file to computer. unzipped and extracted the firmware.zip file from it. Flashed recovery again to this new recovery (basically both are stock). This worked for me and i can go till the recovery screen.
Click to expand...
Click to collapse
I used recovery from "firmware.zip" file but did'nt work..after setup and reastart, my phone stoped on whit screen whit htc logo...i dont now what can i do anymore.
---------- Post added at 02:11 AM ---------- Previous post was at 02:06 AM ----------
Roberto Nigel said:
you can use this MM backup
http://forum.xda-developers.com/desire-816/general/twrp-backup-htc-desire-816-a5dug-dual-t3336060
Click to expand...
Click to collapse
Tnx but this backup did'nt work too
THE_MOJTABA said:
I used recovery from "firmware.zip" file but did'nt work..after setup and reastart, my phone stoped on whit screen whit htc logo...i dont now what can i do anymore.
---------- Post added at 02:11 AM ---------- Previous post was at 02:06 AM ----------
Tnx but this backup did'nt work too
Click to expand...
Click to collapse
How so? .. If you'r a5_dug it should work
tell me what have you done with it?
Roberto Nigel said:
How so? .. If you'r a5_dug it should work
tell me what have you done with it?
Click to expand...
Click to collapse
yes im sure my phone is a5_dug.
when i want to extract this back up, i see an error in end of extract process (99%). but the files will be extract correctly,apparently
i copied files to sd card and done full wipe, i restore this back up..but the process was ok until 60%, but suddenly the process will be 100% and writes successful and done. but after restart my phone stop in white screen with htc logo!
i repair the .zip back up but it dose not change.
i think the .zip file is broken-down.. i downloaded it with download manager.
Roberto Nigel said:
How so? .. If you'r a5_dug it should work
tell me what have you done with it?
Click to expand...
Click to collapse
fixed.. tnx a lot
the downloaded file was destroyed.
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
EDIT: I tried to install it through firmware finder and it didn't pass the verification at the end
https://drive.google.com/open?id=0B4baHcoSeBbgY21CVjlPNk45YlE
https://drive.google.com/open?id=0B4baHcoSeBbgYTZiR1ZDeUpoWnc
https://drive.google.com/open?id=0B4baHcoSeBbgV0g3ejBlMXlzdkk
I have downloaded the 3 zips in this update and verified the md5 they are all good if someone figures out how to install this
krchi said:
I just randomly went to firmware finder to refresh and found a new update for the FRD-L04, did anyone attempt to install this yet?
Click to expand...
Click to collapse
I found the same... Gonna try!
Jessooca said:
How did that work out for you Jorge??
Sent from my FRD-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
JorgeCS said:
Hi!
I tried but didnt worked. There´s no option to begin the update in the app...
Click to expand...
Click to collapse
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Well the good news I see out of this even if we cannot install is that the update is finally coming after 2 months of the other versions enjoying it for that long. Hopefully it fixes the battery drain.
Sent from my FRD-L04 using Tapatalk
Received the OTA update for the B380 version on my FRD L09C185 yesterday. But no notable change in the battery life till now.
krchi said:
Top right download full update it'll download once you hit that and remove the proxy but it won't get authorized when you go to install it.
Click to expand...
Click to collapse
Yep, you can't install this...
Can you install the full firmware from B162 though?
Gus194 said:
Can you install the full firmware from B162 though?
Click to expand...
Click to collapse
You can try and tell us
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Jessooca said:
So the 622mb update file is the correct B385 update file? Can i push it to the phone via adb? Or what's the best way to install it??
Click to expand...
Click to collapse
Likely you'd push both update.zip and the region specific zip to where the stock recovery is expecting, then from a powered-off state use the key combinations to force-udpate. I'm unsure why there are 3 zips this time though since B360 was only 2 zips, I haven't had time yet to look at the contents.
Telperion said:
Thanks for the find! Your file sizes are off unfortunately, they should be:
400MB - update_data_full_public.zip
622MB - update_full_FRD-L04_hw_usa.zip
1.3GB - update.zip
Here are the correct files: https://drive.google.com/open?id=0B0zE1Kk8sIB6M2R4QUVsN3JBOGs
Click to expand...
Click to collapse
Mines was just the OTA files you have the full ota files
Jessooca said:
Did you install the update you found?
Click to expand...
Click to collapse
I tried.
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
usmcnyc said:
I think you have to extract the update.app and do the update via recovery....if I remember correctly. I'd do it now but no USB-C cable here at work...
Click to expand...
Click to collapse
Tried that, compatibility error.
Telperion said:
Tried that, compatibility error.
Click to expand...
Click to collapse
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
usmcnyc said:
:crying:
---------- Post added at 03:30 PM ---------- Previous post was at 02:44 PM ----------
In theory, we could also just extract the recovery.img, system.img and vendor.img and flash via fastboot.....or no? I know that's generally the way I've flashed things on my Shield TV
Click to expand...
Click to collapse
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Telperion said:
Just tried that too, boot, recovery, and system will flash but vendor fails. When I load to the system it still shows B360 but certain parts of the OS don't work -- can't access Developer Options, for example. It seems as if this package just doesn't work right.
Update: If anybody else wants to attempt it, remove all PIN/password protection first. I had to factory reset.
Click to expand...
Click to collapse
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
usmcnyc said:
Sounds like we're stuck...thanks for trying all that though, saved me a huge headache...
Click to expand...
Click to collapse
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Telperion said:
Of note is that the 72309 firmware (B360) zips can be flashed from TWRP with no issue. This zip however fails to install.
Things I tried which failed:
Unpacking UPDATE.APP and force-updating from /external_sd/dload/ folder
Flashing extracted images from bootloader*
Modifying updater-script and flashing in TWRP (mountencrypt was throwing an error, others too)
Updating updater-script and update-binary and flashing in TWRP (same errors)
Flashing images from bootloader, boot and system worked but vendor failed, but the device did boot. It didn't, however, show the new software version -- but that may be because the software version is read from the vendor partition which wouldn't flash. In any event, flashing this way the device was unstable. I couldn't set a screen PIN and Developer Options would crash the Settings menu when I attempted to access it.
Someone more skilled than me would need to extract the contents of all 3 zips and make one TWRP-flashable zip.
Click to expand...
Click to collapse
There's a 1.9gb OTA on firmware finder...I'd download it here at work but the internet is too slow, it'd take hours.
Hi guys,
I hope you can enlighten me regarding my bricked phone.
I tried to convert to Dual SIM following this guide:
https://forum.xda-developers.com/p8lite/general/guide-debranding-converting-single-sim-t3305977
I tried to flash the version (ALE-L02) that was in that guide and but it failed during the fastboot process because of a partittion error. I guess that was because I've tried to flash a stock room from a different model version (mine is PRA-LX1).
To get the phone back up I tried to flash one of this stockrooms:
http://www.stechguide.com/download-huawei-p8-lite-2017-android-nougat-firmware/
https://www.guidebeats.com/2017/02/21/nougat-b140-huawei-p8-lite-2017/
Because I don't have a micro sd card at the moment I used the huawei extractor tool to remove the boot, cust, recovery and system from the files I got from those sites and try to flash via flashboot. The process is done without any kind of errors.
First boot after flash the phone appears that it will start because it displays the logo and the blue bubbles but soon after stays like the image here: https://s1.postimg.o...172118b7227.jpg and wont boot.
What should I do ?
Many thanks!
@squallx85
It's because you are flashing wrong firmware .By the way links aren't opening. What was your last firmware? I mean build number.
---------- Post added at 12:58 PM ---------- Previous post was at 12:52 PM ----------
Link for firmware.
http://www.carbontesla.com/tag/huawei-p8-lite-2017-pra-lx1/
Suleiman01 said:
@squallx85
It's because you are flashing wrong firmware .By the way links aren't opening. What was your last firmware? I mean build number.
---------- Post added at 12:58 PM ---------- Previous post was at 12:52 PM ----------
Just edit the links (thank you btw).
I didn't really save the build number before) but now it's giving me this one: PRA-LX1C33B120
I tried that firmware before too and it didn't work.
Thanks for the response
Click to expand...
Click to collapse
squallx85 said:
Suleiman01 said:
@squallx85
It's because you are flashing wrong firmware .By the way links aren't opening. What was your last firmware? I mean build number.
---------- Post added at 12:58 PM ---------- Previous post was at 12:52 PM ----------
Just edit the links (thank you btw).
I didn't really save the build number before) but now it's giving me this one: PRA-LX1C33B120
I tried that firmware before too and it didn't work.
Thanks for the response
Click to expand...
Click to collapse
Can you go to recovery?
Click to expand...
Click to collapse
Suleiman01 said:
squallx85 said:
Can you go to recovery?
Click to expand...
Click to collapse
only to the EMUI. I tried to flash twrp but despite saying it worked I can't go in.
Click to expand...
Click to collapse
@squallx85
There is an app called firmware finder. Download it a download firmware version C33BXXX and flash it via fastboot. The reason why your phone is stuck because you flashed C02BXXX instead of C33XXX.
Suleiman01 said:
@squallx85
There is an app called firmware finder. Download it a download firmware version C33BXXX and flash it via fastboot. The reason why your phone is stuck because you flashed C02BXXX instead of C33XXX.
Click to expand...
Click to collapse
Well I have followed your advice and downloaded the full ota and extracted the boot, cust, system and recovery from the update.app but it doesn't change anything
squallx85 said:
Well I have followed your advice and downloaded the full ota and extracted the boot, cust, system and recovery from the update.app but it doesn't change anything
Click to expand...
Click to collapse
Try resetting from Huawei recovery. I know it may seems that it won't make a difference but since you don't have any sdcard it is worth a shot.
Suleiman01 said:
Try resetting from Huawei recovery. I know it may seems that it won't make a difference but since you don't have any sdcard it is worth a shot.
Click to expand...
Click to collapse
already did that but the end result it's the same :\ I'll try to get my hands on a sdcard to try the other method (hopefully it will work)
So...quick update: I was able to get a sdcard and tried to update the firmware that I got from the firmware finder. When I start the process "holding volum up + down and the power button" the instalation stops at 5%. I really don't know how to get around this.
you're flashing the wrong firmware dude... the PRA-LX1 i for Huawei P8 Lite 2017... all the firmwares starting with ALE-LXX are for Huawei P8 Lite....
amageek said:
you're flashing the wrong firmware dude... the PRA-LX1 i for Huawei P8 Lite 2017... all the firmwares starting with ALE-LXX are for Huawei P8 Lite....
Click to expand...
Click to collapse
I understand that but I got the firmware from firmware finder and downloaded the version for my firmware and still it can't pass the 5% instalation process if connected to the pc. If is not connected to the pc it says instalation failed
any ideias how I could solve this ? I tried to install the firmware PRA-LX1C33B130 from firmware finder but it's stops at 5%. Do I need the exact firmware (PRA-LX1C33B120) ? If so, I really can't find it.
squallx85 said:
any ideias how I could solve this ? I tried to install the firmware PRA-LX1C33B130 from firmware finder but it's stops at 5%. Do I need the exact firmware (PRA-LX1C33B120) ? If so, I really can't find it.
Click to expand...
Click to collapse
This page has all the official firmware for your device. Press the update button to download one. Make sure it's C33xxxx (you can press F3/Ctrl+F and search for "C33") and that it's the full version, not OTA. Then follow the second half of this guide.
JpegXguy said:
This page has all the official firmware for your device. Press the update button to download one. Make sure it's C33xxxx (you can press F3/Ctrl+F and search for "C33") and that it's the full version, not OTA. Then follow the second half of this guide.
Click to expand...
Click to collapse
I did that and still doesn't work. After I flashed the firmware it goes on a bootloop. unfortunately nothing has changed
squallx85 said:
I did that and still doesn't work. After I flashed the firmware it goes on a bootloop. unfortunately nothing has changed
Click to expand...
Click to collapse
What does the update screen say? The one with the emui logo and the progress "circle"
JpegXguy said:
What does the update screen say? The one with the emui logo and the progress "circle"
Click to expand...
Click to collapse
When I tried the dload method: Instalation failed at 5%. It's similar to https://www.youtube.com/watch?v=16rHgp0GZ48 (1m30s) but with the screen saying my bootloader is unlocked.
When i flash it with fastboot it just stays like this : https://www1-lw.xda-cdn.com/files/2016/10/unlocked.jpg
can someone enlighten me on this subject? any ideas ?
I know I might be off topic,but anyone else had gapps removed after bootloader unlocking ? to be more specific, after I had unlocked the bootloader using adb and fastboot,I got a restart of the device and going directly to the main screen with some apps missing ( GPlay, google folder with gmail and stuff ) What I can do ? I got the PRA-LX1C432B126 firmware version. I also have the screen that squallx85 has ( the one who tells me that my phone is unlocked and no more trusted )
squallx85 said:
can someone enlighten me on this subject? any ideas ?
Click to expand...
Click to collapse
Hi,
Do you have solved your problem ?
Best Regards
Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
EDIT: The solutionwas to re-unlock the bootloader (just perform "fastboot oem unlock PERSONAL UNLOCK KEY). Thanks to AndreaEl for suggesting the solution.
i have had the same problem some days ago.
Re unlock bootloader and try again
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
opal06 said:
Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
Click to expand...
Click to collapse
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
opal06 said:
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
Click to expand...
Click to collapse
Have u tried using the method on this thread?
https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
AndreaEl said:
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Tried that, it doesn't work. And I'm at B381 by the way. See when I try to send the firmware update to the updater app and install it, nothing changes. The installation completes and after reboot, when I check from about phone I see that I'm still in B381(at least according to it )
---------- Post added at 12:39 AM ---------- Previous post was at 12:32 AM ----------
opal06 said:
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
Click to expand...
Click to collapse
My boatloader is already locked and I'm not rooted.
Click to expand...
Click to collapse
Steps:
Prepare and Notice
A. Warning! Flash phone might get it bricked. I am not responsible for it.
B. Phone is already Oreo firmware, only tested same brand update and downgrade.
C. Backup data, it might be restore factory default setting especially using downgrade ROM version.
D. Unlock bootloader before flash steps.
E. After update successfully, device might be locked again.
F. HWOTA8 Package (HWOTA8_2017110501.zip)
Flash Update
A. Use Vol-Dn + USB Cable to boot into fastboot mode.
B. Use Replace_Recovery.bat in HWOTA8 to flash TWRP recovery.
C. Disconnect USB cable, use Vol-Up + Power to boot into TWRP.
D. Create "HWOTA8" directory in MTP sdcard.
E. Put hwota8_update.zip, MHA_RECOVERY8_NoCheck.img, and three huawei update package (update.zip, update_data_public.zip, and update_all_hw.zip) files into "HWOTA8" directory.
F. TWRP install sdcard hwota8_update.zip, it will reboot and install update automatically.
Downgrade Nougat
A. Put update.zip, update_data_public.zip, and update_all_hw.zip files into HWOTA8 repack directory.
B. Run repack.bat to update zip files.
C. Go through "Flash Update" steps and use repacked zip files.
D. Enter recovery and do factory reset.
Rebrand
A. Put Put hwota8_rebrand.zip and "OEMINFO.bin" (From HWOTA) into SDCard HWOTA8 directory.
B. Use Replace_Recovery.bat in HWOTA8 to flash TWRP recovery.
C. Disconnect USB cable, use Vol-Up + Power to boot into TWRP.
D. Install hwota8_rebrand.zip, it reboots and factory reset failure.
E. Enter fastboot mode and unlock device again.
F. Use Replace_Recovery.bat in HWOTA8 to flash TWRP recovery and enter it.
G. Do "Downgrade Nougat" steps to the rebrand firmware, it fails and reboot but fine.
H. When going to system press "Vol-Up" to enter eRecovery, do "Low-level format data partition".
I. Wait all done and recovery menu show up, reboot and do "Downgrade Nougat" again.
J. Update should be successful this time, rebrand done.
Just one question my friend. This is only for update Oreo to Oreo right? Not for downgrade?
albertobom said:
Just one question my friend. This is only for update Oreo to Oreo right? Not for downgrade?
Click to expand...
Click to collapse
You should be able to install ROLLBACK with it.
I'm going to test later today.
Ok, this is update oreo for oreo?
aureliomilitao said:
Ok, this is update oreo for oreo?
Click to expand...
Click to collapse
Yes I belive and rollback as well.
albertobom said:
Just one question my friend. This is only for update Oreo to Oreo right? Not for downgrade?
Click to expand...
Click to collapse
ante0 said:
You should be able to install ROLLBACK with it.
I'm going to test later today.
Click to expand...
Click to collapse
Rollback installed now.
You have to modify script a little though, as rollback has no public zip.
So simply remove the line that says
echo --update_package=/sdcard/HWOTA8/update_data_public.zip > /cache/recovery/command
in hwota8_update.zip's update-binary.
You should even be able to install something that's not a ROLLBACK, as long as you factory reset after.
The rollback factory resets automatically.
ante0 said:
Rollback installed now.
You have to modify script a little though, as rollback has no public zip.
So simply remove the line that says
echo --update_package=/sdcard/HWOTA8/update_data_public.zip > /cache/recovery/command
in hwota8_update.zip's update-binary.
You should even be able to install something that's not a ROLLBACK, as long as you factory reset after.
The rollback factory resets automatically.
Click to expand...
Click to collapse
Amazing. Thanks my friend.
albertobom said:
Amazing. Thanks my friend.
Click to expand...
Click to collapse
Going Oreo directly to C432B197 does not work, fails at 6% in recovery.
But good that rollback installs.
ante0 said:
Going Oreo directly to C432B197 does not work, fails at 6% in recovery.
But good that rollback installs.
Click to expand...
Click to collapse
Thanks for the info my friend that works for me. :good:
---------- Post added at 05:43 PM ---------- Previous post was at 05:42 PM ----------
ante0 said:
Going Oreo directly to C432B197 does not work, fails at 6% in recovery.
But good that rollback installs.
Click to expand...
Click to collapse
BTW you change script back before test it right?
albertobom said:
Thanks for the info my friend that works for me. :good:
---------- Post added at 05:43 PM ---------- Previous post was at 05:42 PM ----------
BTW you change script back before test it right?
Click to expand...
Click to collapse
Of course xD
I did forget first though, and it failed because it couldn't find files...
Rollback installs fine with SuperSU and Adaway (modifies /system) installed.
ante0 said:
Of course xD
I did forget first though, and it failed because it couldn't find files...
Rollback installs fine with SuperSU and Adaway (modifies /system) installed.
Click to expand...
Click to collapse
OK then. This means I can stay beta and update whenever I want
---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------
@mankindtw my friends you're the best.
it worked, I used the rom on the 13th and it appeared in the FF a rom on the 27th, I downloaded the files and I did this procedure and now whenever new roms appear, just follow here
Is there a way to root Mate 9 with Oreo and which is the best method?
It works on MHAL29C567B190 EMUI 5.1?
Can I do this procedure to update ?
ante0 said:
Going Oreo directly to C432B197 does not work, fails at 6% in recovery.
But good that rollback installs.
Click to expand...
Click to collapse
Add "Downgrade Nougat" and new HWOTA8 package.
Curiousrge said:
It works on MHAL29C567B190 EMUI 5.1?
Can I do this procedure to update ?
Click to expand...
Click to collapse
No, you should use below HWOTA, not HWOTA8
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
mankindtw said:
Add "Downgrade Nougat" and new HWOTA8 package.
Click to expand...
Click to collapse
Did I just say how much I love you?
albertobom said:
Did I just say how much I love you?
Click to expand...
Click to collapse
I guess, you might love me even more now.
Have fun playing with it.
mankindtw said:
I guess, you might love me even more now.
Have fun playing with it.
Click to expand...
Click to collapse
You're the man.
Is there a way to disable vibration of the floating navigation dock when long pressed on oreo it is really annoying?