[Guide]How to update from B380 or B381 to B389, B394, B399, B401, B402 and root - Honor 8 Guides, News, & Discussion

This guide is for update within versions if you are rooted, if not, simply download and install de ota or with FF.
If you update to B394 from any version, downloading the last complete packet in update system, it locks the bootloader !!! be advised
If you update to B399 or B401, B402 from B394, downloading the last complete packet in update system, DO NOT LOCK the bootloader !!! good news
My first problem was when I was in B380 and rooted , the b389 ota arrived...then I unroot, put stock recovery and unistalled busybox, but ota failed at 8%
The solution to this :
1 - flash stock recovery from version you have
2 - download the last complete packet in update system , for me 2.41 Gb, not the ota
3 - (optional but useful for future) connect to pc and copy the 3 files downloaded the update in HWOUC to pc
4 - make the normal update in update system
7 - copy supersu 2.82.zip original file or Magisk to SD
8 - Flash last twrp recovery twrp-3.1.1-1-frd , enter in twrp recovery and:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
10 - Make a backup of boot (for future) if you want
11- flash supersu 2.82 original or Magisk
12 - reboot and it's done!!!!!!!!
Update to B394
if you have done all the process and you want now to update to b394, you can uninstall first supersu within options menu saying yes to all questions when uninstalling and without errors or bad uninstallation; then, delete binaries of busybox, flash stock recovery and try to install ota...for me the ota not installed and done with errors.
Then I installed b394 full and locked my bootloader, forcing me to format all because i unlocked the bootloader (remember to activate oem bootloader unlock on and usb depuration on).
After installing the same twrp recovery, I tested the magisk v14 and works perfect, but with an inconvenient, you have to disable the option of magisk manager "magisk hide" to work with fingerprint ,At version 15.3 I didn't see this error.
B394 to B399
Tried the uninstaller of magisk flashed with twrp to unroot and then put the stock recovery and failed, then I flashed stock boot and failed ....finally it worked downloading the last complete packet in update system.Then the habitual, flash twrp recovery, magisk v15.3 from twrp and magisk manager v5.5 in android...and worked perfect
B399 to B401
This time I only unistalled binaries from busybox and flashed stock recovery; then launched Full update (2.41 Gb) without problems.Then flashed twrp, magisk 15.3 from twrp as usual and nothing more...magisk manager detected all ok and I have a rooted device again.
B401 to B402
Simplified the process, now only flash the stock recovery 401 and make the full update packet (2.41Gb). Then flash twrp, enter in twrp, flash magisk 16.0, reboot and that's all. Install busybox script, adaway hosts and done.
Notes:
1 - If the system downloaded automatically the small ota update. you must to try to update with an obvious error, then you can download the full update packet.
1 - the installation of magisk is simple, in twrp flash the magisk.zip , reboot and install magisk manager to control all. This is another app to root and don't need supersu. The advantages to make this is magisk hide, it permits to work with apps that can't work if your phone is rooted.

Wow awsome guide. Thanks alot bro .+1

gopinaidu77 said:
Wow awsome guide. Thanks alot bro .+1
Click to expand...
Click to collapse
happy to help!

9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option

warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
in the options of the twrp, last tab , there's a thick that says this

deadko said:
in the options of the twrp, last tab , there's a thick that says this
Click to expand...
Click to collapse
Bro , y u should mount vendor?

warindo said:
9 - Tick the option "Keep vendor partition mounted" inside OpenKirin in Settings (last option in settings) for me is ticked as default
pla can y help for this option
Click to expand...
Click to collapse
gopinaidu77 said:
Bro , y u should mount vendor?
Click to expand...
Click to collapse
to root correctly with supersu original version

deadko said:
to root correctly with supersu original version
Click to expand...
Click to collapse
But i dont think modifying vendor part is good .

gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
I didn't say nothing to modify nothing, I said thick this option on, and in my case, I did nothing because is marked by default.

deadko said:
I did nothing to modify nothing, I said thick this option on, and in my case, I do nothing because is marked by default.
Click to expand...
Click to collapse
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part

gopinaidu77 said:
But i dont think modifying vendor part is good .
Click to expand...
Click to collapse
gopinaidu77 said:
Oh ,but i request u to remove that point. Since ticking that mean no sense as it allows to modify vendor part
Click to expand...
Click to collapse
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works

deadko said:
I didn't invent that part myself, is the rooting instructions I read in twrp 3.1.1-1 (you can go to the post I linked, and read it) , and only knows that it works
Click to expand...
Click to collapse
Ok , thanks though

On point 4 - download complete package - but where? On update app there offer only ota update package not full.

Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
at the tab up to the right in update system

Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
Click on 3 dots on the top right corner . U will see the option.

deadko said:
4 - download the last complete packet in update system , for me 2.41 Gb, not the ota
Click to expand...
Click to collapse
My option is greyed out, what should i do?

Nortonko said:
On point 4 - download complete package - but where? On update app there offer only ota update package not full.
Click to expand...
Click to collapse
fabh2o said:
My option is greyed out, what should i do?
Click to expand...
Click to collapse
the ota is avaliable for you?

deadko said:
the ota is avaliable for you?
Click to expand...
Click to collapse
Yes i'm downloading it right now
Edit: i'm downloading the 2,41 gb update, thanks for the support.

I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.

Snowjack said:
I had B381, TWRP & Root and I just used points from guide - 2.2,3,6,7,8,9,11,12. I had to remove SuperSU in the app - complete unroot option. Flashed stock recovery.img (and recovery2.img) in fastboot mode, which I extracted from my firmware version update.app. Restarted the device and did a full OTA update to B389, hard reset, flashed latest TWRP 3.1.1-1 in fastboot mode, than installed modified SuperSU for EMUI 5.0 from XDA and all is done.
Click to expand...
Click to collapse
very large process, but you make a hard reset, and my process is to preserve data and use original supersu not the modified , thanks for info

Related

Android N Preview npc56p (flashable & image with no encryption and dm verification)

Android N Preview npc56p (flashable & image with no encryption and dm verification)
This thread is for the first Android N Preview.
For Android N Preview 2 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview image released by Google on 3/9/2016. After the installation you will have TWRP recovery 3.0.0-1 and the data partition will be erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery
1- You need to have TWRP installed on your phone.
2- Download this flashable zip.
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N. If your internal storage is unencrypted before flashing it remains unencrypted. Your TWRP is also upgraded to 3.0.0-1.
Method 2: Flash update using a computer
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.0-1.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root
To obtain root after installing this update you should flash SuperSU 2.70 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726. Note that at least at the moment (as of SuperSU 2.70) the root method is a hack solution which requires a lot of further refinement. Many programs are still unable to acquire root and mount the system partition for R/W. However, it is possible to install the android terminal emulator, do an su, mount /system as rw, and do all the modifications within the terminal emulator. Of course you can always use TWRP to modify the system, for which you don't even need to root the device.
Hot dog! First for once... Thanks!
Sent from my Nexus 6 using Tapatalk
#2
will this wipe internal storage ? or only data partition?
For anyone interested...
I enrolled in the Developer Beta program and the OTA worked for me even though I was rooted with SuperSU v2.68.
However, despite installing TWRP 3.0.1 and then SuperSU v2.68 again, root doesn't stick. Fortunately the only critical previously-root-only app I want is a firewall, and Netguard doesn't need root. I can live for a while without Double Tap To Wake, Wakelock detector, Quick Reboot, etc. And the only app that seems to crash is BBC Radio Player, though BBC News and iPlayer still seem ok (warning about libraries, but still plays). And Battery Bot Pro seems to have lost its status bar display...
So it does pretty much what the warnings say - it's stable but not everything will work.
so if i flash this i will still have twrp once rebooted?
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
It would be nice moving forward if Google just made SuperSU/root part of their factory image under developer options. So once you enable developer option, there's a little toggle next to OEM unlock that says "root/SuperSU".
Would make life much easier.
simms22 said:
if you only flash the boot.img and system.img, then yes. if you flash the whole thing, which includes a stock recovery, itll install the stock recovery. but all you have to do is type in one line into fastboot to reflash twrp.
Click to expand...
Click to collapse
kidhudi said:
so if i flash this i will still have twrp once rebooted?
Click to expand...
Click to collapse
The zip doesn't include stock recovery so if you flash everything according to the instructions you will have twrp at the first reboot.
This kernel worked great thanks. I'm still decrypted and didn't have to wipe internal storage. I didn't run the .bat I manually flashed the img files. Wiped data with TWRP.
so can we flash this via twrp?
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
no, those are IMG format, flash via fastboot.
I'd wait for root ready then flash...
omaralkha99 said:
so can we flash this via twrp?
Click to expand...
Click to collapse
It literally says right next to the link, "Note that it is NOT a flashable zip."
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
it says twrp recovery in title, so I was wondering....
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
chapelfreak said:
what about phh superuser? he modified his root to run for android n http://forum.xda-developers.com/and...apable-superuser-t3216394/page30#post65748721
Click to expand...
Click to collapse
I flashed that boot img and now i am encrypted and boot-looping. No access to SD card.
Does this build have new bootloader and radio? If so, is it backward compatible to Marshmallow roms or do we need to flash back M bootloader and radio to get M roms work?
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
PainToad said:
It literally says right next to the link, "Note that it is NOT a flashable zip."
Click to expand...
Click to collapse
I lold at this. :laugh::laugh::laugh::laugh:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
kclive said:
Flashed and everything is working great except I have no LTE and the only internet I get is on wifi. Running on Verizon sim on StraightTalk.
Click to expand...
Click to collapse
Toggle on and off airplane mode. Turn off wifi and see if it works. I was at work and had to do this a few times
Flashed phh kernel (su-noverity - 3rd one) and installed this superuser. I now have root working.

Anyone who installed TWRP and rooted on Marshmallow able to update to Nougat?

If so, how? Thanks!
magicmanfk said:
If so, how? Thanks!
Click to expand...
Click to collapse
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
worked for me perfectly
pjcarrmole said:
This was totally bugging me too but after a whole day of trying I've finally managed it.
1) Go to this thread here
2) Boot into fastboot and flash the boot.img and system.img as suggested in the thread
3) Also flash the original recovery using "fastboot flash recovery recovery.img"
4) Go to the official asus support site here and download the update files you need, the last two
5) Download Version V11.41.87.2 and place the file in the internal storage of your sd card, once you pull the cable out your phone the phone should detect a update file and ask if you want to install it. Click OK.
6) The phone will unpack the update and reboot and install it
7) Delete this update file and then add the latest Nougat update file (Version V20.31.49.2)
8) Do the same again and install it and there you have it... the key is that you have to install each incremental update rather than go straight to the latest.
Oh and I don't know if it makes any difference, but I decided to turn off adb debugging once I'd flashed the various boot, system and recovery images before I started to update using the Asus method.
Also I have successfully re-flashed TWRP through fastboot on Nougat.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Devalorize said:
Thanks for the instructions; worked for me. Were you able to re-root? I tried to by following this guide: https://www.reddit.com/r/zenfone/comments/6gqha5/zenfone_3_ze553kl_z01hd_root/
But on step 8 of the supersu website, my phone gets stuck on "starting adb sideload feature." I had already tried installing supersu via twrp, but still no root.
Click to expand...
Click to collapse
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Devalorize said:
This worked for me, thanks. It's too bad Xposed doesn't support Nougat yet. Missing my Xposed modules.
Click to expand...
Click to collapse
Magisk has a few modules for it but nothing like Xposed.
I'm going to do a full back up and then see how well ZenUI plays with Substratum as most of the ZenUI Themes are pretty poor and I want an all black theme. I'll let people know how it goes if anyone is interested in using substratum.
---------- Post added at 10:28 AM ---------- Previous post was at 09:32 AM ----------
pjcarrmole said:
I flashed TWRP from one of the other threads on here filename twrp-3.1.0-0-Z01H-20170408.img to be precise.
I then flashed the latest version of magisk the zip found here
Then selecting core files only and magisk hide options I have root that passes the latest safetynet checks. No problem.
Click to expand...
Click to collapse
Oh, if you're having trouble getting TWRP to stick don't reboot the system but reboot back into Recovery, by holding the Vol - & Power together and using the Volume buttons to select Recovery.
After this you can then reboot normally.

Foolproof way for OTA-update with Magisk installed

Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Tiemichael said:
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Click to expand...
Click to collapse
Hey!
Following the official Magisk procedure works, at least for me.
You just have to be careful to restore backup image before starting the OTA download and installing to second slot (After OTA) before rebooting.
Reading this thread:
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
I found there’s a lot of confusion (I was confused also and made a few mistakes), but my conclusions are:
- That method is to be used just ONCE in order to gain root, and not every month.
- Always try to use your own patched image if you have the opportunity
- You have to use “fastboot BOOT” and not “fastboot FLASH” when first rooting, otherwise you won’t be able to restore boot image and OTA will fail
- Follow official procedure as a cooking recipe
If you don’t want to root using a patched boot image, you can also use latest TWRP (As of now latest is recovery-3.2.1-2-oreo.img)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
And boot to TWRP image in order to install Magisk ZIP (did this yesterday and also worked), but the update via OTA method should be the same.
Best regards.
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Keeping phone to stock and not rooting for only one OTA in more than a month? I think its not worth it!!
I always root my phone and when OTA arrives i just flash twrp version of it and root it again ?
Siebenmik said:
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Click to expand...
Click to collapse
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
_mysiak_ said:
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
Click to expand...
Click to collapse
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Tiemichael said:
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Click to expand...
Click to collapse
Yes, exactly. I didn't have any issue with OTA installation yet.
Tiemichael said:
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
Click to expand...
Click to collapse
I forgot saying that using restore image in magisk didn't work. Even though I didn't flash the patched boot.
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where to enable secured startup?
Skeuomorphic said:
Where to enable secured startup?
Click to expand...
Click to collapse
create a pattern from security setting and it will prompt to enable secure startup.. just press yes..
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Finally a different answer, I have secure boot disabled maybe this is the reason ending into bootloop for past 3 montly security updates. Will try this for May update.
coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Tiemichael said:
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Click to expand...
Click to collapse
Settings->Security & Location->Screen lock->Pattern
This what was working for me just now:
Detailed steps performed 20.4.2018:
Backup Titanium
Backup Magisk Modules
Switch on Secured Booting (e.g. Pin) => not same a normal pin!
Open Magisk
Uninstall Magisk​
Restore Images​
Start OTA update
Downlowd​
Step1​
Step2​
Go Back to Magisk
Install to 2nd slot​
Reboot​
It was working ... very easy!
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
I didn't update my phone for a very long time, then I decided to finally go for the latest MIUI on my Mi Max and basically I flashed full new ROM via fastboot & MiPhone.
You can see detailed description here: https://forum.xda-developers.com/showpost.php?p=78050983&postcount=41
I think it should work with other Xiaomi phones too but please correct me if I'm wrong
The only difference is that I had SuperSu before, but maybe with Magisk it's the same to do - also correct me if i'm wrong
quetzalcoatl2435 said:
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
Click to expand...
Click to collapse
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
H.A.L. 9000 said:
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse
freekarol said:
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Click to expand...
Click to collapse
Yeah, but you need a PC for this. If I need access to a PC every time there's an OTA update, might as well download and flash a full ROM. ?
Official Magisk OTA guide works anytime anywhere, no PC needed.

updating failed

So, I just rooted my Huawei P Smart, the 136 update shows up, it does all the install steps, reboots and then says it failed. Do O need to do something on the twrp boot?
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
airb05 said:
Download the full firmware, we lose the option to just update via normal update and we can update with a full system update
Click to expand...
Click to collapse
Just did that, 2 GB download, tries to install, reboots, goes to twrp, then I reboot to normal system and still says update failed.
Pretty sure you'll need stock recovery to update the "normal" way.
callmeWhiskers said:
Pretty sure you'll need stock recovery to update the "normal" way.
Click to expand...
Click to collapse
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
siivet said:
So I'll need to unroot and root again ? Anyway to update without doing that? Cause Im pretty sure ill screw up if I try it, barely made the root LOL
Click to expand...
Click to collapse
I'm not an expert - I always use HuRUpdater to update. It just requires you to download the (exact) right files, renaming them correctly and (like rooting with Magisk) just simply flashing a single .zip in recovery. In case you try it out, remember rule#1: Always make sure you have a (nandroid)backup.
Here are the relevant lines from my "Huawei-related-findings" text file:
#update
"Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
• HUAWEI stock recovery installed
• unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install)."
Click to expand...
Click to collapse
#source XDA
 @st_voss (u=1065667)
https://forum.xda-developers.com/showpost.php?p=73011427&postcount=2
#update
“It's recommended to use a proper custom recovery (with running oeminfo_nvm_server service) like for example*my version of TWRP.
How to use:
Warning: Make sure you know what you are doing and do not flash firmware from other devices.
1. Download firmware files (for official firmware use Huawei Firmware Finder).
2. Put files you want to flash in a seperate folder on sdcard.
Supported zip files to flash are (name must match):
◦ update.zip (use FullOTA file)
◦ update_all_hw.zip
◦ update_data_public.zip
3. Optional: Put recovery.img in same folder if you want to keep custom recovery.
4. Put HuRUpdater zip in same folder.
 5. Select*only HuRUpdater*to flash in custom recovery.
6. Follow instructions on screen. Flashing can take multiple minutes.
Problems:
• If firmware includes factory reset
◦ Factory reset is not supported by custom recovery. Therefore HuRUpdater will flash stock recovery before launching factory reset. After flashing firmware and doing factory reset, you need to flash recovery manually.”
Click to expand...
Click to collapse
#source XDA
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
#notes HuRUpdater_0.4.zip working
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Yes, I'm im the same boat - I guess you also get the "can't have connection" error using the FF app. During the last weeks they had troubles with their service regarding hackers and moving to a new server (according to their telegram group), which have been fixed ("all services working normally now"), and many can use it again - for whatever reason some still can't connect. I tried reinstalling the app, using proxies from different countries - still doesn't let me connect.
But their web interface is working: https://pro-teammt.ru/firmware-database/ though you can't check iirc, if the firmware has been approved for your IMEI.
According to this post:
sun75 said:
It's online now! I suggest you to download the "2018.08.30" .158 "2379" release, if you have a FIG-LX1, L31 board phone.
Click to expand...
Click to collapse
You apparently can download this release (2379) if you own this device/board- though the last time I updated mine (.148) I used the 2079 (154226) one despite owning the exact same device. I'm slightly confused about this
I didn't try the above mentioned update myself.
siivet said:
Thanks mate, the Huawei Firmware Finder seems like its not working for the moment, but as soon as it is ill follow your tip
Click to expand...
Click to collapse
Try installing an older version of the Firmware Finder app - I switched from (current) v9.0 to v8.9 and it works now
https://apkpure.com/firmware-finder...efinder/download/86-APK?from=versions/version
..

Oneplus 5 Update fails

Hello everyone,
For a while now, I have been delaying this, because I can't afford to lose the content that I have on this device
I have a Oneplus 5 OxygenOS 5.1.4 release that I can't install. Everytime I do, it just fails, and reboot. A while after, I have a new notification telling me that the update is available
My phone is not rooted but I think the bootloader is unlocked. TWRP isn't installed either
Is there any way for me to easily update my phone witout risks of losing what I have on it ? Might be a dumb question, but I'm a huge noob
Thansk a lot for your help
Mouchoir said:
Hello everyone,
For a while now, I have been delaying this, because I can't afford to lose the content that I have on this device
I have a Oneplus 5 OxygenOS 5.1.4 release that I can't install. Everytime I do, it just fails, and reboot. A while after, I have a new notification telling me that the update is available
My phone is not rooted but I think the bootloader is unlocked. TWRP isn't installed either
Is there any way for me to easily update my phone witout risks of losing what I have on it ? Might be a dumb question, but I'm a huge noob
Thansk a lot for your help
Click to expand...
Click to collapse
Do you get the bootloader unlock warning message at boot? Is the device new or used? You want to update from 5.1.4 to 5.1.5 with ota right? Does the ota download 1.7GB or detect root before downloading?
Hello strongst and thanks for your answer
The phone is old but it's always been mine. I rooted it a while back but I reinstalled everything, which is why the bootloader is unlocked even tho the phone isn't rooted.
I do have the warning message when I boot
I'm trying to update with OTA indeed. When I do so, it downloads the update, reboots, and then I get this :
"Instaling, please wait..." and a few seconds after "Installation failed"
Then I just rebot the phone and everything is back to its initial state
strongst said:
Do you get the bootloader unlock warning message at boot? Is the device new or used? You want to update from 5.1.4 to 5.1.5 with ota right? Does the ota download 1.7GB or detect root before downloading?
Click to expand...
Click to collapse
You did not answer all questions, so I only can guess...
Mouchoir said:
Hello strongst and thanks for your answer
The phone is old but it's always been mine. I rooted it a while back but I reinstalled everything, which is why the bootloader is unlocked even tho the phone isn't rooted.
I do have the warning message when I boot
I'm trying to update with OTA indeed. When I do so, it downloads the update, reboots, and then I get this :
"Instaling, please wait..." and a few seconds after "Installation failed"
Then I just rebot the phone and everything is back to its initial state
Click to expand...
Click to collapse
I'm guessing it downloads partial ota and not a full rom like about 1,7GB so the update fails. In case you have twrp you can easily download the 5.1.5 FULL zip from here and flash it https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
I am sorry that my answer wasn't complete.
- I do have the bootloader message
- The device is a year old, but only used by me
- It's trying to download 5.1.4 OTA which is 1609MB. It downloads everything and tries to install it
- No root is detected
- I don't have TWRP on the phone
Thanks for your answers
Best way it simply install latest TWRP like Sian, do a dirty flash with the full OOS Rom package (5.1.7) for force update.
1/ Do a full backup of your data / sms / pictures on your computer (just for be sure, you must always backup for big changes, especially with encrypted roms)
2/ install TWRP Sian
3/ On TWRP > Wipe > Dalvik/ART - Cache paritions
4/ Install > the latest stable OOS 5.1.7 Rom
5/ Just after that flash Magisk (if you want keep the custom recovery) or don't flash Magisk (stock recovery will erase TWRP after SetupWizard)
Hello Pho3nX, thanks for your answer.
I tried to figure out what "TWRP Sian" is, but I couldn't find anything. I found this one : https://twrp.me/oneplus/oneplus5.html and I'm planning on following the "Fastboot Install Method". Is that OK ?
Do you recommand me to flash Magisk ?
Thanks a lot
Mouchoir said:
Hello Pho3nX, thanks for your answer.
I tried to figure out what "TWRP Sian" is, but I couldn't find anything. I found this one : https://twrp.me/oneplus/oneplus5.html and I'm planning on following the "Fastboot Install Method". Is that OK ?
Do you recommand me to flash Magisk ?
Thanks a lot
Click to expand...
Click to collapse
This : [RECOVERY] TWRP-3.2.3 with Pie decryption support [experimental]
And yes i advise to install Magisk for keep TWRP & tools / root, permit using useful root app like Titanium/Theme/Adaway/Explorer etc...
Pho3nX said:
This : [RECOVERY] TWRP-3.2.3 with Pie decryption support [experimental]
And yes i advise to install Magisk for keep TWRP & tools / root, permit using useful root app like Titanium/Theme/Adaway/Explorer etc...
Click to expand...
Click to collapse
Hello
I'm back Thanks for your answer. However, there is no explaination on how to use the .img I've downloaded. Could you point me to some instructions ?
Sorry I'm not good at this stuff
Mouchoir said:
Hello
I'm back Thanks for your answer. However, there is no explaination on how to use the .img I've downloaded. Could you point me to some instructions ?
Sorry I'm not good at this stuff
Click to expand...
Click to collapse
If you have no twrp already installed on your device you must flash the twrp.img file with fastboot like "fastboot flash recovery twrp.img"
Hello,
You haven't heard from me because I wait to be at home so I can safely follow your instructions.
I just saw a news about Android Pie 9.0 beta being released for Nexus 5.
Pho3nX said:
4/ Install > the latest stable OOS 5.1.7 Rom
Click to expand...
Click to collapse
Would it work if I download it instead of the one you sent me ?
Thanks a lot
Mouchoir said:
Hello,
You haven't heard from me because I wait to be at home so I can safely follow your instructions.
I just saw a news about Android Pie 9.0 beta being released for Nexus 5.
Would it work if I download it instead of the one you sent me ?
Thanks a lot
Click to expand...
Click to collapse
Error 7 for me i tried i'm with unlocked bootloader latest TWRP by Eng.stk and i removed form the zip also compatibility.zip
Hello,
I finally managed to install the zip thanks to TWRP, but it seems that my cellphone is stuck on the boot turning logo with the two red dots turning around the big red one
Fixed : https://forum.xda-developers.com/oneplus-5/help/bricked-oneplus-5-t3884364

Categories

Resources