Database Develop

After B852 OTA Update: Software bricked ?

Hello Community,
Today I got a strange prob with my huawei ascend p7-l10:
After succeded update to B852 my Phone didnt boot properly. But Fastboot and Recovery works flawless.
Story:
My phone was on Stock firmware B839 (rooted), with unlocked bootloader and TWRP recovery flashed.
Today updated manager prompted: New Update (B852) available. So I flashed the stock recovery for EMUI 3.1 and rebootet my phone, then I installed B852 per OTA and flashed it successfully.
Then After the phone reboot I got the screen: "Optimizing Android Apps". On 71 from 91 Apps (Optimization) I directly got a black screen. I rebootet my phone....
Now the phone hangs directly after the Huawei Boot logo. rebootet... and again blackscreen
After a third reboot Android starts again with Apps Optimizing (but now not 91 Apps, only 80 Apps).
I rebootet more then three times and it didnt work.
I Also tried to wipe cache and dalvik, also tried to factory reset my phone. All without any success
Anyone knows, how I get this fixed ?
Have a nice day and also christmas days
EDIT: Sorry guys, topic can be closed. I solve the problem by myself.
Solution if anybody have similar issues:
1) Flash TWRP
2) Wipe Cache Dalvik and do a factory reset (within TWRP)
3) Flash any custom ROM (example My-Rom)
4) Download B839 (Complete) Firmware from (for example) http://www.huaweiblog.de/
5) create a dir called "dload" on SD-Card and put the UPDATE.APP in there
6) flash stock recovery for EMUI 3.1 (dont forget to activate ADB)
7) In Huawei update manager: do a local update and select the UPDATE.APP
8) After success flash: Boot again into recovery mode - First select Wipe Cache and then select Factory reset
9) Boot into normal android and connect with your WLAN
10) Check for updates and download B852 Firmware thru Huaweis update manager and install it
Optioal (only if root access wanted):
11) flash TWRP recovery again
12) Boot into recovery mode
13) Flash SuperSU zip file in TWRP.
done!! Now B852 (maybe with rooh) works flawless

helping root p9 eva-L09C432B394

Hello.
I was participated in few subjects about this issue, so now I am asking again for help.
Short story.
I have Huawei p9 with b386 working twrp recovery and supersu. Next steps was upgrading to b394.
I make supersu full unistall from supersu app. Than flashing with nocheckrecovery
>fastboot flash recovery eva_l09b391_nocheckrecovery.img from this thread
>fastboot reboot
After that updated my device to b394 by OTA and everything was great.
Start to install recovery and supersu, but with my mistake was entering huawei recovery and I wipe my device, and bootloader was locked.
Unlocked it again and install twrp 3.1.1.1 open kirin from here - installed successfully.
Than flashed some version of supersu, I think 2.79 (which zip I don't kept) and root works ok. As everything was updated I decide to update supersu app, but then the problem appears.
When I am flashing any of SuperSU version, they were installed, but not worked. Here some picture
Then try different version of SuperSu (also two version ot 2.79), but still has no root. RootChecker says "Sorry, root access is not properly installed" , Adaway is stucking at home screee, ES File manager has no root explorer, terminal cannot make "su" and etc.
Try this method, but still same result
1. twrp -> flash -> UPDATE-unSU-signed.zip
2. restore original boot.img b394
fastboot flash boot L09-b394-BOOT.img
fastbook reboot
3. twrp -> advanced Wipe -> Wipe Dalvik/Cache and Cache only - reboot
4. twrp -> flash > SuperSU-v2.82-SR5-permissive.zip (no cleaning caches or else, never did before anyway)
Have you got any idea or try something different to have twrp and supersu on b394 without full wipe/clean/reset the device ?
Thanks in advance !

netaccs said:
Hello.
I was participated in few subjects about this issue, so now I am asking again for help.
Short story.
I have Huawei p9 with b386 working twrp recovery and supersu. Next steps was upgrading to b394.
I make supersu full unistall from supersu app. Than flashing with nocheckrecovery
>fastboot flash recovery eva_l09b391_nocheckrecovery.img from this thread
>fastboot reboot
After that updated my device to b394 by OTA and everything was great.
Start to install recovery and supersu, but with my mistake was entering huawei recovery and I wipe my device, and bootloader was locked.
Unlocked it again and install twrp 3.1.1.1 open kirin from here - installed successfully.
Than flashed some version of supersu, I think 2.79 (which zip I don't kept) and root works ok. As everything was updated I decide to update supersu app, but then the problem appears.
When I am flashing any of SuperSU version, they were installed, but not worked. Here some picture
Then try different version of SuperSu (also two version ot 2.79), but still has no root. RootChecker says "Sorry, root access is not properly installed" , Adaway is stucking at home screee, ES File manager has no root explorer, terminal cannot make "su" and etc.
Try this method, but still same result
1. twrp -> flash -> UPDATE-unSU-signed.zip
2. restore original boot.img b394
fastboot flash boot L09-b394-BOOT.img
fastbook reboot
3. twrp -> advanced Wipe -> Wipe Dalvik/Cache and Cache only - reboot
4. twrp -> flash > SuperSU-v2.82-SR5-permissive.zip (no cleaning caches or else, never did before anyway)
Have you got any idea or try something different to have twrp and supersu on b394 without full wipe/clean/reset the device ?
Thanks in advance !
Click to expand...
Click to collapse
Wait a little, pre-rooted (by Magisk) Magic Rainbow v3 is just around the corner to be publicly released
https://forum.xda-developers.com/showpost.php?p=74863763&postcount=857
You'lll need a clean b394 and TWRP to flash

I prefer original firmware, but if there no other solution...

netaccs said:
I prefer original firmware, but if there no other solution...
Click to expand...
Click to collapse
It's based on stock b394, with pre-installed root, AdAway, BusyBox, Viper4Android, K-Settings

netaccs said:
Hello.
I was participated in few subjects about this issue, so now I am asking again for help.
Short story.
I have Huawei p9 with b386 working twrp recovery and supersu. Next steps was upgrading to b394.
I make supersu full unistall from supersu app. Than flashing with nocheckrecovery
>fastboot flash recovery eva_l09b391_nocheckrecovery.img from this thread
>fastboot reboot
After that updated my device to b394 by OTA and everything was great.
Start to install recovery and supersu, but with my mistake was entering huawei recovery and I wipe my device, and bootloader was locked.
Unlocked it again and install twrp 3.1.1.1 open kirin from here - installed successfully.
Than flashed some version of supersu, I think 2.79 (which zip I don't kept) and root works ok. As everything was updated I decide to update supersu app, but then the problem appears.
When I am flashing any of SuperSU version, they were installed, but not worked. Here some picture
Then try different version of SuperSu (also two version ot 2.79), but still has no root. RootChecker says "Sorry, root access is not properly installed" , Adaway is stucking at home screee, ES File manager has no root explorer, terminal cannot make "su" and etc.
Try this method, but still same result
1. twrp -> flash -> UPDATE-unSU-signed.zip
2. restore original boot.img b394
fastboot flash boot L09-b394-BOOT.img
fastbook reboot
3. twrp -> advanced Wipe -> Wipe Dalvik/Cache and Cache only - reboot
4. twrp -> flash > SuperSU-v2.82-SR5-permissive.zip (no cleaning caches or else, never did before anyway)
Have you got any idea or try something different to have twrp and supersu on b394 without full wipe/clean/reset the device ?
Thanks in advance !
Click to expand...
Click to collapse
When you like supersu install only v2. 82 sel permissive and busybox 1.27.2 YDS universal or magisk v 14.0 or beta 14.5. i like supersu but on this moment magisk is better. magisk must flash in recovery
---------- Post added at 08:08 AM ---------- Previous post was at 08:03 AM ----------
Update via ota to b394. When system lock bootloader unlock them(fastboot maybe show red stat unlock). After factory reset low level flash twrp 3.1.1.1 open kirin not from twrp. me. After install twrp flash super su or magisk without factory reset from twrp. Download full ota from ota update (b391)

Magisk 14.5 beta give me some error at the beginning of flashing. Will try both versions 14.0 and 14.5 again and paste the results.

Finally I made this steps.
twrp -> flash -> UPDATE-unSU-signed.zip
Enter to fastboot mode
fastboot flash boot L09-b394-BOOT.img
fastboot flash recovery b394_recovery_stock.img
After quick setup start root+recovery procedure.
Enter fasbtoot mode
fastboot flash recovery twrp-3.1.1-1-eva.img
Enter in twrp (vol up + power until logo) and flash SuperSU-v2.82-SR5-permissive.zip.
Everything seem to work ok.
Thanks all for helping !

I found what make supersu stop working.
When restoring from huawei backup app, there is option to restore "system data" than "settings".
So definitely it makes something.
How can I detect what is the reason after restoring this settings from systemdata huawei backup ?

[GUIDE] OTA on TWRP

i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)

in my personal experience, if you get rebood to twrp, flash Disable Dm Verity ForceEncrypt to boot into rom

title
Was Magisk installed before the update? Since you are saying it rebooted to TWRP without you knowing, were you able to restore stock images before updating? Could you also provide information concerning the update? For example, miui version (updating from vXXX to vXXX)
jjsan said:
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
Click to expand...
Click to collapse

Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0

jjsan said:
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
Click to expand...
Click to collapse
What I meant was whether you uninstalled Magisk/restored original boot img prior to the update because sometimes not doing so tends to result in bootloop (happened to me before). I needed some information before I attempt the update myself. Thank you for replying.
P.S. One more question: All data was preserved, right?

Question Question about OTA update zip file

My phone M2102K1G came with IN ROM as I bought the phone in India during launch.
I unlocked bootloader and flashed Xiaomi.eu's fastboot ROM which is based on CN ROM and my model was then M2102M1C. I didn't like the Xiaomi.eu ROM and switched to Global MI fastboot Rom. Rooted as well. Very happy with this
I did not fastboot flash TWRP and left my phone on stock recovery. I have tested fastboot boot TWRP and that works well though the initial language (TWRP) is Chinese and you have to first switch the language to English. I haven't flashed anything via TWRP as yet.
My question is:
OTA zip file (Global MI Rom)
Can i flash it via TWRP?
Even though my phone is for the India IN region?
And if I can flash it via TWRP, then do I immediately flash with Magisk zip as well to keep root?
Thanks to anyone who had the patience to read through this and can hopefully reply.

In case you want update a stock ROM without TWRP and keep root throughout the updates here is my guide to do so.
Download on your phone latest recovery package manually from trusted websites. You can find the ROMs and firmware specific for your device on here https://xiaomifirmwareupdater.com/miui/star/ remember to download the recovery version
Disable magisk modules and reboot
Upon reboot go to settings->system version->Miui(top left button)-> in the updater click several times on the main icon to unlock hidden settings->once unlocked tap on the three dots on the top right and select "choose update package"->browse your folder to find the downloaded recovery package,select it and press the V button on the bottom->update will start->wait until completion and reboot
Once rebooted follow the procedure to flash magisk.zip
Reboot the phone into fastboot
Connect phone to the pc
Boot into twrp
Once in twrp flash dalvik and cache
Flash magisk.zip and rewipe dalvik and cache
Reboot system and voila

xNAPx said:
In case you want update a stock ROM without TWRP and keep root throughout the updates here is my guide to do so.
Download on your phone latest recovery package manually from trusted websites. You can find the ROMs and firmware specific for your device on here https://xiaomifirmwareupdater.com/miui/star/ remember to download the recovery version
Disable magisk modules and reboot
Upon reboot go to settings->system version->Miui(top left button)-> in the updater click several times on the main icon to unlock hidden settings->once unlocked tap on the three dots on the top right and select "choose update package"->browse your folder to find the downloaded recovery package,select it and press the V button on the bottom->update will start->wait until completion and reboot
Once rebooted follow the procedure to flash magisk.zip
Reboot the phone into fastboot
Connect phone to the pc
Boot into twrp
Once in twrp flash dalvik and cache
Flash magisk.zip and rewipe dalvik and cache
Reboot system and voila
Click to expand...
Click to collapse
Ok thanks.
I'm definitely gonna follow these steps the next time I get an OTA update.
Don't need to be rooted to flash boot TWRP is it?

No, you don't need,but you don't flash twrp, you just boot into twrp

If I have a unlocked and rooted phone with stock recovery, what happens if I just update normally via the stock update procedure? Will it not work?
Without disabling Magisk or anything and just updating.

Honestly I don't know but I can say that magisk wasn't fully working after updating without reflashing it

Okay.
So I cannot flash the OTA zip.
But have to update using the full recovery ROM for the updated version.
And then flash Magisk via fastboot boot TWRP

xNAPx said:
In case you want update a stock ROM without TWRP and keep root throughout the updates here is my guide to do so.
Download on your phone latest recovery package manually from trusted websites. You can find the ROMs and firmware specific for your device on here https://xiaomifirmwareupdater.com/miui/star/ remember to download the recovery version
Disable magisk modules and reboot
Upon reboot go to settings->system version->Miui(top left button)-> in the updater click several times on the main icon to unlock hidden settings->once unlocked tap on the three dots on the top right and select "choose update package"->browse your folder to find the downloaded recovery package,select it and press the V button on the bottom->update will start->wait until completion and reboot
Once rebooted follow the procedure to flash magisk.zip
Reboot the phone into fastboot
Connect phone to the pc
Boot into twrp
Once in twrp flash dalvik and cache
Flash magisk.zip and rewipe dalvik and cache
Reboot system and voila
Click to expand...
Click to collapse
How will I get boot.img from the recovery ROM?
Only fastboot ROM will have boot.img

I think you have a bit of confusion, only thing you have to di is download magisk.zip on your phone, boot into twrp and flash it, simple

How to Install OTA Updates on Rooted Android Devices using Magisk [Without Losing Root]
An OTA update has arrived, but you cannot install it because your Android device is rooted? Well, that's a known downside of rooting Android. In this guide, you will learn how to install OTA updates…
www.thecustomdroid.com

keneth_c said:
If I have a unlocked and rooted phone with stock recovery, what happens if I just update normally via the stock update procedure? Will it not work?
Without disabling Magisk or anything and just updating.
Click to expand...
Click to collapse
Yes, you will probably have to reinstall Magisk as root will more than likely be broken. The update server still sees a stock rom and as long as you have stock recovery, the stock OTAs will work.

The guide posted above explains properly the steps. Will try that next time around.

Question Root lost after official update - help?

I was unlocked and rooted at Indian 12.5.2 ROM for the longest time. Got a notification for 12.5.5 and installed it. That took away root, but that was expected.
Now I've installed official TWRP, but as soon as I install Magisk (either via zip from recovery or patched twrp recovery image via the Magisk app), when I try rebooting to system, phone instead boots back to TWRP with a 'Android Rescue Party Trigger' error.
Happened every single time I've tried above - phone tries booting and then boots to recovery, and only way to boot system again is to install unpatched TWRP recovery, but then there's no root.
What should I do?