Related
[FONT="]As some of us including myself have been wondering how do i update my honor 7 while running android 5.0.2 to the latest Marshmallow 6.0 update if my honor 7 is rooted?
[/FONT]
[FONT="]I have successfully updated to The latest Marshmallow 6.0 using this method[/FONT][FONT="] and i was running b180 rooted
[/FONT]
[FONT="]I have a uk version of honor 7 so the process will be the same except the firmware files for your country.[/FONT][FONT="]
[/FONT][FONT="]Please back your phone as i have done with titanium backup and Hisuite
[FONT="]I[/FONT] don't take any responsibility for any damage caused by your mistakes[/FONT][FONT="]
[/FONT] [FONT="]Step 1: We need to unroot honor 7 before doing anything else
open superSU scroll down and you will see an option full unroot click and phone should reboot sometime it may not reboot so dont worry just to be sure download root checker app from play store to see if unroot has been successful[/FONT]
[FONT="]Step 2: Head to your computer and download and install the following tool:
[/FONT][FONT="]http://forum.xda-developers.com/show....php?t=2433454[/FONT]
[FONT="]Step 3: Download the [FONT="]full[/FONT] complete update file (B121) from:
[/FONT][FONT="]http://www.modaco.com/forums/topic/3...s-121115-b140/[/FONT][FONT="]
Then, extract it and get its UPDATE.app file.[/FONT]
· [FONT="]Step 4: [/FONT]Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img),) from the UPDATE.app file that you have extracted from Step 3.
[FONT="]Step 5: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.[/FONT]
[FONT="]Step 6: Type the following commands and execute them one by one
[/FONT]
Code:
fastboot reboot bootloaderTest if your device is detected by typing
the following command fastboot devices while you are in the bootloader mode
Then execute the these commands
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
[FONT="]Step 7: Navigate to your sd card and copy the dload [/FONT]folder that you have extracted from Step 3 to the root of your sd card. Note inside the dload folder is the update file UPDATE.APP
· [FONT="]Step 8: Hold volume + and volume – at the same time then hold the power button don’t let go until you see Huawei software installation screen, Once installation is done phone will reboot and android system will load after setup process you will get a ota update notification, Click on it and update to b180 [/FONT]
· [FONT="]Step 9: Go to http://www.hihonor.com/uk/support/ and [/FONT][FONT="]Download the latest complete update file honor 7 firmware[/FONT][FONT="] (PLK-L01, Andriod 6.0, EMUI4.0, C432B330, United Kingdom) [/FONT]
Step 10: Extract The files download in Step 9 And you will see a folder called dload copy that folder to the root of your sd card .
Note if you already have a folder called dload then just copy the APDATE.APP from the dload folder to your sd cards dload folder
· [FONT="]Step [FONT="]11[/FONT]: Hold volume + and volume – at the same time then hold the power button don’t let go until you see Huawei software installation screen[/FONT]
You may get installation failed error don’t worry just reboot the system and enjoy the Official Marshmallow 6.0 update.:good:
Thanks for the guide, however, I couldn't get it to work on my UK H7. I'm already on B180 with no root and bootloader still locked so I just proceeded from step 9. I placed the UPDATE.APP from the update.zip I downloaded to the dload folder but it fails (like you said) but when i reboot i'm still on B180.
I also tried just placing the update.zip directly into dload but that also fails after attempting a local update.
Any ideas?
Andy4Shurr said:
Thanks for the guide, however, I couldn't get it to work on my UK H7. I'm already on B180 with no root and bootloader still locked so I just proceeded from step 9. I placed the UPDATE.APP from the update.zip I downloaded to the dload folder but it fails (like you said) but when i reboot i'm still on B180.
I also tried just placing the update.zip directly into dload but that also fails after attempting a local update.
Any ideas?
Click to expand...
Click to collapse
I used german file and it failed at 98% but when phone reboot its b330... i was on b180.
its strange but everything works fine.
no root of course
Tile0107 said:
I used german file and it failed at 98% but when phone reboot its b330... i was on b180.
its strange but everything works fine.
no root of course
Click to expand...
Click to collapse
Did you start from step 1 or did you already have B180 like me?
I downloaded this file: http://www.hihonor.com/de/support/details/?DOC_ID=77508
than i create dload folder and copy this,( unziped and take update.app) to sd card. Next i open the updater and start.
phone restart goes to 98% than i saw on screen "failed", phone reboot and its b330 i dont know how but work fine...
Tile0107 said:
I downloaded this file: http://www.hihonor.com/de/support/details/?DOC_ID=77508
than i create dload folder and copy this,( unziped and take update.app) to sd card. Next i open the updater and start.
phone restart goes to 98% than i saw on screen "failed", phone reboot and its b330 i dont know how but work fine...
Click to expand...
Click to collapse
Thanks Tile, we both started from the same point with the same firmware then :/
I'll try again.
Andy4Shurr said:
Thanks Tile, we both started from the same point with the same firmware then :/
I'll try again.
Click to expand...
Click to collapse
Oh and one more thing my phone dont wipe after this update. I tried again now to update it was completed and phone restart, now my phone was wiped...
Strange...
Andy4Shurr said:
Thanks for the guide, however, I couldn't get it to work on my UK H7. I'm already on B180 with no root and bootloader still locked so I just proceeded from step 9. I placed the UPDATE.APP from the update.zip I downloaded to the dload folder but it fails (like you said) but when i reboot i'm still on B180.
I also tried just placing the update.zip directly into dload but that also fails after attempting a local update.
Any ideas?
Click to expand...
Click to collapse
Hi Andy
I think it maybe because you are not rooted or you may have done something different.
Try downloading the files again.
If not follow this official guide if you are not rooted http://www.modaco.com/forums/topic/377073-how-to-update-your-honor-7-to-marshmallow/
Tile0107 said:
Oh and one more thing my phone dont wipe after this update. I tried again now to update it was completed and phone restart, now my phone was wiped...
Strange...
Click to expand...
Click to collapse
I backed up, just in case.
I tried again, the update went really quick (like 15 seconds) then said it was complete and I restarted. Since then it has been sat with the honor boot up logo for about 10 minutes... I'm just going to wait and hopefully it will boot into the android system
EDIT: So it's not progressing from the boot logo... I went into the recovery and wiped/factory reset to see if that would help but it's just sat at the boot logo again and won't go any further
I can obviously get to recovery and to the update screen so I'll have to try and download the full B121 ROM and put it on my SD card to try again.
Andy4Shurr said:
I backed up, just in case.
I tried again, the update went really quick (like 15 seconds) then said it was complete and I restarted. Since then it has been sat with the honor boot up logo for about 10 minutes... I'm just going to wait and hopefully it will boot into the android system
EDIT: So it's not progressing from the boot logo... I went into the recovery and wiped/factory reset to see if that would help but it's just sat at the boot logo again and won't go any further
I can obviously get to recovery and to the update screen so I'll have to try and download the full B121 ROM and put it on my SD card to try again.
Click to expand...
Click to collapse
Are you running custom recovery or stock?
If you are on stock recovery Start a fresh install
download the full B121 firmware flash it and after setup you should get OTA update notification proceed with the update once the update it done to b180 download the full firmware for marshmallow from here http://www.hihonor.com/uk/support/details/?DOC_ID=77509
Extract the zip file once done you will see a dload folder copy the UPDATE.APP to you dload folder in your sd card then go to settings and update click on local update and update the phone.
Let me know if it worked.
alphadude said:
Are you running custom recovery or stock?
If you are on stock recovery Start a fresh install
download the full B121 firmware flash it and after setup you should get OTA update notification proceed with the update once the update it done to b180 download the full firmware for marshmallow from here http://www.hihonor.com/uk/support/details/?DOC_ID=77509
Extract the zip file once done you will see a dload folder copy the UPDATE.APP to you dload folder in your sd card then go to settings and update click on local update and update the phone.
Let me know if it worked.
Click to expand...
Click to collapse
Yes, full stock. Never rooted or unlocked bootloader. I agree, I think the full 121 upgrade path is probably the best option now, I'm in the process of copying over the update.app from the 121 firmware to my sd card as we speak. I tried the 330 update while I was at work and didn't have my usb sd card reader so I've only just managed to get home and start that now.
EDIT: I'm just getting the update failed message now when attempting to install the B121 Update.App... about 6% into the update, then just asks to reboot system which gets stuck at the boot logo again :/
EDIT 2: After repeatedly trying and switching between B100, B120 and B330 update.App files to try and reflash the firmware the B330 version finally decided to do a full install and complete 100%. Very strange how it literally just decided to work this time but all's well that ends well I guess. If anyone else has this issue then just persevere and keep trying, hopefully it will just work one time!
Thanks Tile and Alphadude for trying to figure it out
for unrooted B180 this is how i did it
I went from B180>B320>B330
downloaded B320 to sd card
extracted intermediate file to sdcard/dload
EMUI update app and manual update
it restarted and did its buisness
deleted the UPDATE.APP from dload folder and copied in the full UPDATE.APP
EMUI update app and manual update
it restarted and did its buisness
then once restarted back into the emui update app and it said the 330 update was available OTA
no data loss through any of it
joelk2 said:
for unrooted B180 this is how i did it
I went from B180>B320>B330
downloaded B320 to sd card
extracted intermediate file to sdcard/dload
EMUI update app and manual update
it restarted and did its buisness
deleted the UPDATE.APP from dload folder and copied in the full UPDATE.APP
EMUI update app and manual update
it restarted and did its buisness
then once restarted back into the emui update app and it said the 330 update was available OTA
no data loss through any of it
Click to expand...
Click to collapse
Which b320 download did you use, do you have a link.
sbellseb said:
Which b320 download did you use, do you have a link.
Click to expand...
Click to collapse
I used this one from the French honor sitehttp://www.hihonor.com/fr/support/details/?DOC_ID=72951
joelk2 said:
I used this one from the French honor sitehttp://www.hihonor.com/fr/support/details/?DOC_ID=72951
Click to expand...
Click to collapse
I'll try that one. I followed a different one which failed. Thanks.
sbellseb said:
I'll try that one. I followed a different one which failed. Thanks.
Click to expand...
Click to collapse
Make sure you flash the intermediate file first and then the main update
I doff my cap. It worked. An error at 95%, plodded on through and I'm now on MM B330.
Good work. I've noticed an improved battery life on b330
joelk2 said:
Good work. I've noticed an improved battery life on b330
Click to expand...
Click to collapse
There's nothing great that I've come across yet. No data lost either doing the upgrade so I'm happy to be on MM.
After the update everything else seems to be working fine and smooth, but i've had several sudden restarts and couple of freezes.
Hi guys.
First of all, Please understand although I'm not good at English.
I have rooted wifi version m3. (BTV-W09C233B030)
I use TWRP and installed SuperSU.
I used erecovery to erase and install TWRP.
and now. I want rollback rooting and upgrade to nougat.
To do that, I heard that the stock firmware was needed, and I downloaded the full version of the file(full version BTV-W09C233B029) using the firmware finder.
Can you tell me in detail from here?
Thanks : )
First of all, I would like to let you know that :
- I've successfully installed Nougat BTV-DL09-C100-B302 but... I was unable to root it with "twrp_BTV-DL09_5_greatslon.img" + "TWEP-SuperSU-v2.79.zip".
- I've then done a rollback thanks to the "C900B300 - ROLLBACK from 7.0 EMUI 5.0 to 6.0 EMUI 4.1 6.0" package from the Huawei website.
- Then, successfully re-installed BTV-DL09-C100-B009
(1) By putting update.app inside "dload" folder (to be created or to be emptied) on the external sdcard
(2) Switched off the mediapad.
(3) Switch on pressing Volume up+down+power button and install will start.
- Successfully upgraded to BTV-DL09-C100-B010 -> BTV-DL09-C100-B301 with "Firmware finder 4.2" downloaded the from Google Store.
Unfortunately, again, I was unable to root it and I've identified this error while flashing "TWEP-SuperSU-v2.79.zip" with "twrp_BTV-DL09_5_greatslon" : "Boot image patching" process fails to patch "sepolicy" and give the error "--- failure, aborting" ; basically, the SU binary is not installed in the System. It's a kernel issue and I guess TWRP has to be patched for these new ROMS or the concerned file must be patched differently, with another tool (BTV-XX09-XXX-B301/B302). Or I'm doing something wrong if someone else has managed to root its mediapad running these updates.
If you don't need your mediapad to be rooted or if you know how to root it , installing Nougat is quite simple :
1) First replace TWRP with the stock recovery image. To do so, extract recovery.img from BTV-W09C233B029 with "HuaweiUpdateExtractor" for Windows.
Considering that you have the ADB drivers correctly installed, reboot in fastboot mode with the command : "adb reboot-bootloader" (or adb reboot bootloader). Then type : fastboot flash recovery recovery.img and then "fastboot reboot". I'm doing all that under parallel destop (Windows 10) on a macbook pro.
2) Then, install you stock rom BTV-W09C233B029 :
(1) Put the file "update.app" inside a dload" folder (to be created or to be emptied) on the external sdcard.
(2) Switched off the mediapad.
(3) Switch it on while pressing volume up+down+power buttons. Install will start.
3) Download Firmware finder 4.2 from the google store and install the required Nougat OTA file for your mediapad thanks to the proxy method (localhost / port:8080 ; you will be proposed to download a Firmware Finder ADD-ON from the Google Store. It helps to push the local file to the official system updater in Settings). Not that you don't have to download the OTA file with the Firmware Finder ; you can just use Firmware Finder to trick the local update installation and then manually put the update.zip file on the internal sdcard in this directory : HWFF/null/update.zip. (Firmware Finder servers are very slow at times so you better download the OTA file yourself on the site mentioned in other xda threads).
Good luck.
Thank you
thank you very much!
It's a really easy way. I learned a lot thanks to this.
Unroot was completed without any problems.
Thanks again
My pleasure, glad you've been able to sort this out. :good:
You can try a factory reset. Used to happen to mine also when running BTV-DL09-C100-B006. Not occurred on B009 and Nougat. Can be caused by many things when unlocked / rooted / xposed framework and so on installed. If stock, I would do a backup and try a factory reset. I also remember having tried to activate both navigation menu + fingerprint sensor for navigation than removed the navigation menu and it had solved the issue if I remember well. Maybe a coincidence though... don't know.
Long story short; I wiped system and everything on this device, so all I really have on it working now is TWRP. The official FullOTA updates fail in TWRP, erecovery fails, and recovery in hisuite fails. I assume the last two will fail because of the third party recovery. So I guess I'm wondering if anyone can point me in the direction of the official recovery that I can fastboot flash, or any other way to reload the ROM?
Full story; I got this new tablet last week, and I unlocked, installed TWRP, and rooted successfully. Then I broke google services with a dodgy gapps install that I didn't need, couldnt figure out how to unflash it, and wiped everything like an idiot.
Thanks if anyone can help.
Update; I guess the root of the problem is that I'm unable to mount /data? Any actions I take in TWRP give me the error "Failed to mount '/data'", including if I do a wipe data or try to change the file system. I've used "Huawei Update Extractor" to see if there is a data.img, but it looks like no.
Update 2: Still not sure what this was all about, but I extracted system.img from "Huawei Update Extractor" and fastboot flashed that, and it looks like everything is working again. Haven't checked TWRP to see if it still gives errors on the data partition, but I'm at least in the OS and google play services are working.
Download latest firmware for your device from Huawei server and extract it. Make a new folder on external sdcard, named dload. Copy extracted file (update.app) in this folder. Power off device and turn it on using 3 button method: volume up + volume down + power - old all 3 buttons simultaneously.
It will start the update/flash process. It will install factory firmware on your device.
When you download Firmware, in the archive you will find these steps (PDF file).
Next time you can try this
Sent from my BTV-DL09 using Tapatalk
30adi said:
Download latest firmware for your device from Huawei server and extract it. Make a new folder on external sdcard, named dload. Copy extracted file (update.app) in this folder. Power off device and turn it on using 3 button method: volume up + volume down + power - old all 3 buttons simultaneously.
It will start the update/flash process. It will install factory firmware on your device.
When you download Firmware, in the archive you will find these steps (PDF file).
Next time you can try this
Click to expand...
Click to collapse
Wrong. He installed TWRP so there is not a functional recovery.
The right thing is to extract the Recovery from the Update.app and flash it, then use the dload method.
nicolap8 said:
Wrong. He installed TWRP so there is not a functional recovery.
The right thing is to extract the Recovery from the Update.app and flash it, then use the dload method.
Click to expand...
Click to collapse
Actually, I did try that, but I put stock recovery back on and and tried the dload method, it still failed int he same way as with TWRP installed.
What ended up working was extracting system.img from the update and fastboot flashing it. Not very intuitive. I am still getting "Failed to mount '/data'" errors in TWRP now, but haven't looked much into it yet. That is weird, I guess if everything is working it is more a problem with TWRP, because if everything is running and booting /data should be fine.
[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 tried to install the update for my OnePlus5 but TWRP gives ERROR 7 i also tried to wipe my data (including system),
i also tried to install the update with the stock recovery (without root) and the update just fails
oxygen updater won´t work aswell
thanks in advance
i´ve trieded newer versions of oxygen os too
sry for my bad english i am german
Hi!
Are you trying to install a full OTA zip (1GB+ in file size), or a partial OTA (more around 50 MB - 200 MB) over your current 5.1.2 ROM?
At this point I would suggest you flash a full OTA zip of OOS 5.1.4, either through TWRP or OnePlus' recovery. @Titokhan provides a list of mirrors where you can download full signed flashable zips. Make sure to compare the MD5 signature of your downloaded file with the reference signature inscribed on the download page -- this makes sure your download is not corrupted.
Alexandre-P said:
Hi!
Are you trying to install a full OTA zip (1GB+ in file size), or a partial OTA (more around 50 MB - 200 MB) over your current 5.1.2 ROM?
At this point I would suggest you flash a full OTA zip of OOS 5.1.4, either through TWRP or OnePlus' recovery. @Titokhan provides a list of mirrors where you can download full signed flashable zips. Make sure to compare the MD5 signature of your downloaded file with the reference signature inscribed on the download page -- this makes sure your download is not corrupted.
Click to expand...
Click to collapse
i used the OTA before but i will try the OTA you suggested
thanks in advanced:good:
Edit: can i theoretically use a newer version than 5.1.4?
Fredwuz said:
Edit: can i theoretically use a newer version than 5.1.4?
Click to expand...
Click to collapse
OnePlus enabled Treble on the OP5 around stable release 5.1.5, and release notes for 5.1.5 stressed that the device should be on 5.1.4 before applying the 5.1.5 upgrade. The release notes for 5.1.6 also stressed that the user first upgrade to 5.1.5 before applying the 5.1.6 system upgrade. Based on that information, I would highly suggest you make sure your device works correctly on 5.1.4 first, then 5.1.5, followed by 5.1.6, and only then you upgrade to a later release.
Alexandre-P said:
OnePlus enabled Treble on the OP5 around stable release 5.1.5, and release notes for 5.1.5 stressed that the device should be on 5.1.4 before applying the 5.1.5 upgrade. The release notes for 5.1.6 also stressed that the user first upgrade to 5.1.5 before applying the 5.1.6 system upgrade. Based on that information, I would highly suggest you make sure your device works correctly on 5.1.4 first, then 5.1.5, followed by 5.1.6, and only then you upgrade to a later release.
Click to expand...
Click to collapse
so i flashed version 5.1.3 and it did work but when i tried to flash to version 5.1.4 TWRP was stuck in "Patching system image unconditionally..." did i do something wrong?
After i flashed to 5.1.3 the devices worked normal as always
Here's what I would do:
1. Flash 5.1.3 -- don't re-root, don't flash TWRP.
2. At this point, if you try to boot to recovery, you should have OnePlus' recovery. That's cool, just leave it that way.
3. Boot to system. Allow the system to find newer upgrades, and apply them using the system updater as they come.
4. When you're all updated again to latest release, follow instructions to TWRP and root the device.
Alexandre-P said:
Here's what I would do:
1. Flash 5.1.3 -- don't re-root, don't flash TWRP.
2. At this point, if you try to boot to recovery, you should have OnePlus' recovery. That's cool, just leave it that way.
3. Boot to system. Allow the system to find newer upgrades, and apply them using the system updater as they come.
4. When you're all updated again to latest release, follow instructions to TWRP and root the device.
Click to expand...
Click to collapse
now the updater says my system is up-to-date but i only have 5.1.3 installed
Fredwuz said:
now the updater says my system is up-to-date but i only have 5.1.3 installed
Click to expand...
Click to collapse
Reboot, wait some time.
What is sometime are about 5 hours enough?
Sent from my OnePlus5 using XDA Labs
Fredwuz said:
What is sometime are about 5 hours enough?
Click to expand...
Click to collapse
You can try to use a VPN(app) which connects to another country to force the update. Or flash it with the stock recovery by downloading the file, place it in .ota folder and update it.
strongst said:
You can try to use a VPN(app) which connects to another country to force the update. Or flash it with the stock recovery by downloading the file, place it in .ota folder and update it.
Click to expand...
Click to collapse
I tried to use tunnelbear and connected to USA but the updater won't find an update now I will try the other method but can't I just use the lokal Upgrade Option in the updater?
Edit: I have to use version 5.1.4 or?
Sent from my OnePlus5 using XDA Labs
Fredwuz said:
I tried to use tunnelbear and connected to USA but the updater won't find an update now I will try the other method but can't I just use the lokal Upgrade Option in the updater?
Click to expand...
Click to collapse
Yes you can, that's what I suggested already
My experience with the 5.1.4 update - ERROR 7 & Treble error fix
Hi, I have 3 OnePlus 5's in my household and I have gotten them all to update to 5.1.4, then 5.1.5, then 5.1.6+ with this method.
(5.1.4 and then 5.1.5 is needed before flashing 5.1.6 or greater).
In my experience, no matter what caches I cleared or what recoveries I had used, 5.1.4 was not flashable on all three devices with the bootloader unlocked. If you have the patience and time, this method should 99.99% work for you if done correctly (leaving a 0.01% chance of failure just in case it does fail lol but that shouldn't happen.)
1.) Firstly, back up your device. I suggest doing this by making a full titanium backup, and copying all the files on the internal storage to a folder on your computer.
This may take a while to copy. In my experience, the fastest way to copy all the data off to the computer is to boot the device into TWRP recovery, plug a good USB C cable in to the device and to the PC's USB port, unlock the device in TWRP (put in the password/pattern to decrypt and mount the data partition [Ignorable if you dont set a password on the device]), and use the adb pull command to pull the files off the device. I found that ADB pull works much faster than an mtp file transfer in windows explorer.
Steps for ADB pull:
Ensure adb is installed on the computer with adb drivers. For Windows, open command prompt or powershell as admin. Type in adb devices and hit enter. If your OnePlus device comes up, then all is good. Use the command (without the square brackets):
[ adb pull /sdcard "XXX/." ]
Replace XXX with a directory on your computer (for example, you can do [ adb pull /sdcard "C:\Users\YOURUSERNAME\Desktop\OnePlus/." ]
If anyone notices any issues with this command please let me know so I can update the post. I am writing this off memory, so there may be minor mistakes.
2.) After your device backs up and you're happy with the backup (i.e. everything you need backed-up is saved off of the phone onto the computer), It's time to relock the bootloader and restore the firmware on the phone.
I haven't tried a simple fastboot OEM relock command, so I cannot say whether that is sufficient enough.
What I did was follow this thread:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Download the Driver and the Oxygen version.
Once downloaded, extract the driver Driver_OnePlus5.zip file to its own folder. Extract the firmware to its own folder (cheeseburger_23_O.13_170803).
3.) Using the firmware restoring tool to relock the bootloader and restore the device to factory firmware condition.
Now:
Turn off your OnePlus 5 device.
Hold volume up key.
Plug USB cable in to the PC and the Type-C side to the device. Make sure only volume up is held whilst you do this.
Open device manager and check for missing drivers/driver issues. If the driver isn't detected, use device manager to browse for the extracted Driver_OnePlus5 folder you made earlier.
The LED light on the OnePlus 5 should be yellow if I can remember correctly.
Open msm download tool as an adminstrator (right click, run as administrator)
Click the start button on the top left of the msm download tool. (If nothing happens, make sure drivers are installed properly and that the device is in download mode [Repeat the above steps])
If successful, one of the "Device Type" should show your device connected {com device} and the download process and time row will update. Wait for the download progress to finish. The device will reboot on its own when completed. The status should turn green and say done/finished (If I remember correctly).
When your device reboots, do a quick setup. Don't bother putting your google account in or restoring anything if you plan on unlocking the bootloader later for TWRP or other reasons.
Unlocking the bootloader will wipe the phone. For now, just focus on the updates.
Connect the device to Wi-Fi. I found one of the devices I used this method on wouldn't connect to Wi-Fi (modem issue or something). Luckily, I had the 5.1.4 update already downloaded on the computer so I copied the update to the root folder on the device and used the local upgrade option in the OTA update options (in the phone system update settings). Updating the firmware fixed my Wi-Fi issue.
Basically, just do the OTA updates as you would normally. Start with 5.1.4, then you can do the 5.1.5. Do not jump to 5.1.7 because OnePlus only just added treble support in 5.14/5.15 releases so it is important do do those in order first. If you can, do 5.1.4, 5.1.5, 5.1.6 and then 5.1.7 in order. Just follow the updates that the OTA screen allows you to take.
Notes for the Pie update:
I haven't had issues installing Pie with the bootloader unlocked, so if you wish to stay on oreo for now and update later with an unlocked bootloader, that should be fine.
If your bootloader is locked, and you're on at least OOS 5.1.5, you should be able to flash the Pie OTA with the stock recovery without issues.
If you encounter issues installing Pie, and your bootloader is unlocked follow this:
Unlocked bootloader - Pie Update - Removing compatibility.zip from firmware archive:
Method 1: Pre-Removed compatibility.zip modified firmwares:
For STABLE:Follow this link:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Download " OxygenOS 9.0.0 Full Zip (modified, without compatibility.zip) ".
For BETA:Follow this link:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
Download " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) ".
You will need a Pie-compatible recovery. Download a compatible custom Recovery (TWRP) (Also available on https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 )
Flash a Pie-compatible TWRP and boot into it.
Copy the downloaded " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) " to the device.
In TWRP, use: Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe.
I would recommend taking a nandroid backup before proceeding, if you have any important data on the device.
Flash the downloaded " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) ".
Wipe dalvik-cache and cache.
Enjoy Pie.
Method 2: Manual Method to remove compatibility.zip for unlocked bootloaders:
Download the FULL firmware OTA (from device settings, or from the OnePlus website).
Copy the firmware to the computer (If downloaded on the device, it will be in the ".ota" folder. Else, it is available on the OnePlus firmware downloads page.
Open the firmware archive with 7-Zip.
Delete Compatibility.zip from the archive.
Copy the now-modified firmware back to the device.
You will need a Pie-compatible recovery. Download a compatible custom Recovery (TWRP) (Also available on https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 )
Flash a Pie-compatible TWRP and boot into it.
In TWRP, use: Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe.
I would recommend taking a nandroid backup before proceeding, if you have any important data on the device.
Flash your manually-modified OTA/firmware archive in TWRP.
Wipe dalvik-cache and cache.
Enjoy Pie.
DO NOT use winrar or any other non-recommended programs to remove compatibility.zip. I found that winrar causes treble errors or error 7.
4.) Re-unlocking the bootloader & Restoring your data.
Once you've installed 5.1.5 or greater, you can now safely go into developer settings and enable oem unlocking, and then reboot to the bootloader to unlock the bootloader (which will wipe/erase the phone data but keep the version to whatever you updated it to). You may then proceed to install TWRP, magisk if you plan on restoring with titaniumbackup, and restore all your sd card contents (or the sd card contents that you need) back from the computer backup the the device (I usually use ADB Push whilst booted in TWRP recovery because it copies quicker than MTP).
Updates should work from now on ( I was able to install android PIE Beta with the bootloader unlocked [See the Pie notes above]. Only had issues with the 5.14 / 5.15 updates with the bootloader unlocked ).
Hope this helps. If anyone has any more information, or questions about this method, do share. Like I said earlier, if done correctly, this method should definitely work for you guys.
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Sent from my OnePlus5 using XDA Labs
Fredwuz said:
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Click to expand...
Click to collapse
Sent from my OnePlus5 using XDA Labs
Fredwuz said:
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Click to expand...
Click to collapse
Glad you got it working! Happy new year to you as well