Database Info

Soft bricked MHA-L29C432; please help!!!!

Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!

How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579

dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.

If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app

you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1

Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.

Stuck in Bootloop! fastboot OK, can't load recovery (Failed flashes?)

Please Help- device stuck in bnoot
Current status:
Stuck in bootloop
Fastboot loads ok, can supposedly flash recovery_ramdisk & system
TWRP doesn't load after flashing recovery (or recovery_ramdisk with EMUI version) - I get "load failed" error screen
EMUI8 was probably not completely installed
Initial condition
Honor 6X w/ stock EMUI 5.1 (Nougat)
Traceback
Goal was to install LineageOS 15.01.
This is what I tried:
Unlocked bootloader (&wiped device)
EMUI8 was a pre-requisite, so followed this guide to upgrade
Ran script in guide, which loaded twrp followed by EMUI update screen (as expected)
EMUI update ran for a while, restarted (I think) at least once, but then showed failure screen
Tried rebooting- no system, stock recovery. (fastboot still loaded fine)
Couldn't install TWRP or use script anymore - after some research looked like this was because boot directories changed in Android 8 (recovery -> recovery_ramdisk)
Was able to install EMUI8 version of TWRP, but unable to flash rom or rerun update script (it used recovery2 partition, apparently changed to erecovery_ramdisk, which I couldn't flash to)
loading TWRP was unreliable, worked sometimes and didn't other times
Somewhere around here it seems like I deleted stock recovery (erecovery) while trying various workarounds
Tried installing ElementalOS
The included TWRP loaded, ROM Installation seemed to work but got error in the end (don't remember details)
rebooted device - can no longer boot to recovery ( Error screen: "Func no: 11 (recovery image) Error no: 2 (load failed!))
device stuck in bootloop and Flashing recovery_ramdisk/recovery has no effect!
can still enter fastboot without any problems
I'm hoping there's some way to recover to fix the recovery/system partitions so I can upgrade or at least revert to stock ROM!
Any help will be greatly appreciated

SuperSpasm said:
Please Help- device stuck in bnoot
Current status:
Stuck in bootloop
Fastboot loads ok, can supposedly flash recovery_ramdisk & system
TWRP doesn't load after flashing recovery (or recovery_ramdisk with EMUI version) - I get "load failed" error screen
EMUI8 was probably not completely installed
Initial condition
Honor 6X w/ stock EMUI 5.1 (Nougat)
Traceback
Goal was to install LineageOS 15.01.
This is what I tried:
Unlocked bootloader (&wiped device)
EMUI8 was a pre-requisite, so followed this guide to upgrade
Ran script in guide, which loaded twrp followed by EMUI update screen (as expected)
EMUI update ran for a while, restarted (I think) at least once, but then showed failure screen
Tried rebooting- no system, stock recovery. (fastboot still loaded fine)
Couldn't install TWRP or use script anymore - after some research looked like this was because boot directories changed in Android 8 (recovery -> recovery_ramdisk)
Was able to install EMUI8 version of TWRP, but unable to flash rom or rerun update script (it used recovery2 partition, apparently changed to erecovery_ramdisk, which I couldn't flash to)
loading TWRP was unreliable, worked sometimes and didn't other times
Somewhere around here it seems like I deleted stock recovery (erecovery) while trying various workarounds
Tried installing ElementalOS
The included TWRP loaded, ROM Installation seemed to work but got error in the end (don't remember details)
rebooted device - can no longer boot to recovery ( Error screen: "Func no: 11 (recovery image) Error no: 2 (load failed!))
device stuck in bootloop and Flashing recovery_ramdisk/recovery has no effect!
can still enter fastboot without any problems
I'm hoping there's some way to recover to fix the recovery/system partitions so I can upgrade or at least revert to stock ROM!
Any help will be greatly appreciated
Click to expand...
Click to collapse
Well when bricked the first thing you should try to do is flash TWRP. Which isn't working now? Can you somehow re flash and boot into TWRP? What TWRP are you using. Please try this one and let me know if it boots.
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Another thing you could try is Dload method. It requires an SD Card. Extract the Update.zip you downloaded on your PC and now create a Folder called Dload in your SD Card and copy the contents of the extracted zip into the folder. Put SD Card in phone and Hold all three buttons i.e. Power and Volume Up & Down at the same time. Firmware should start flashing. Once it finishes, while device is booting, press and Hold Power and Volume Up to boot into eRecovery and Perform a Wipe Data/Factory Reset. The Wipe Cache and reboot. If this works, then lemme know and then I'll help you flash a Custom ROM.

Mannan Qamar said:
Well when bricked the first thing you should try to do is flash TWRP. Which isn't working now? Can you somehow re flash and boot into TWRP? What TWRP are you using. Please try this one and let me know if it boots.
removed because I don't have link posting permission
Another thing you could try is Dload method. It requires an SD Card. Extract the Update.zip you downloaded on your PC and now create a Folder called Dload in your SD Card and copy the contents of the extracted zip into the folder. Put SD Card in phone and Hold all three buttons i.e. Power and Volume Up & Down at the same time. Firmware should start flashing. Once it finishes, while device is booting, press and Hold Power and Volume Up to boot into eRecovery and Perform a Wipe Data/Factory Reset. The Wipe Cache and reboot. If this works, then lemme know and then I'll help you flash a Custom ROM.
Click to expand...
Click to collapse
Thanks for the reply
Unfortunately TWRP doesnt boot (tried flashing the image you posted, same error screen- image below)
Dload method- I can't boot into erecovery atm- not sure if it's wiped or just can't be reached.
Also- the EMUI8 update I downloaded contained 3 zips- update.zip, update_all_hw.zip, and update_data_public.zip. do I only need the update.zip? (I can't boot into erecovery anyway, so it's a moot point until I do)
Image: (remove space, forum won't let me post images)
http s://i.imgur.com/tFUKDOC.jpg

SuperSpasm said:
Thanks for the reply
Unfortunately TWRP doesnt boot (tried flashing the image you posted, same error screen- image below)
Dload method- I can't boot into erecovery atm- not sure if it's wiped or just can't be reached.
Also- the EMUI8 update I downloaded contained 3 zips- update.zip, update_all_hw.zip, and update_data_public.zip. do I only need the update.zip? (I can't boot into erecovery anyway, so it's a moot point until I do)
Image: (remove space, forum won't let me post images)
http s://i.imgur.com/tFUKDOC.jpg
Click to expand...
Click to collapse
Ok the SW you downloaded is NOT a Dload rom, plus you do not enter eRecovery to flash it. Use the "force" method by pressing and holding all three buttons on power up.
Download a rom from here :-
https://androidhost.ru/
Also instructions are in the zip.

Sparkrite said:
Ok the SW you downloaded is NOT a Dload rom, plus you do not enter eRecovery to flash it. Use the "force" method by pressing and holding all three buttons on power up.
Download a rom from here :-
Also instructions are in the zip.
Click to expand...
Click to collapse
Tried downloading a rom from androidhost.ru- it had the update folder structure described,
and I put the unzipped dload folder into microSD root like the instructions said.
But pressing vol up+down+power doesn't load any update screen for me.
It just goes to bootloop again.
Is there anything else I can try?
Thanks

Need to upgrade but have questions

Hi guys. I rooted my phone after purchase about two years ago using https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
I am still running the same version now
Twrp
Model: MHA-L29
Build: MHA-L29C567B183
EMUI: 5.0
Android Version: 7.0
Any one got suggestions and steps to get to a newer version. I think I need to switch back to Erecovery etc but if someone had some exact steps and a good version to move to would be great. I had thought about installing magisk but my main concern is being able to run games like Pokemon go or Mario kart and they seem to be detecting my root. Not even sure having root is worth it anymore.

I installed stock recovery and did ota updates.. working like a champ!

mpencexda said:
Hi guys. I rooted my phone after purchase about two years ago using https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
I am still running the same version now
Twrp
Model: MHA-L29
Build: MHA-L29C567B183
EMUI: 5.0
Android Version: 7.0
Any one got suggestions and steps to get to a newer version. I think I need to switch back to Erecovery etc but if someone had some exact steps and a good version to move to would be great. I had thought about installing magisk but my main concern is being able to run games like Pokemon go or Mario kart and they seem to be detecting my root. Not even sure having root is worth it anymore.
Click to expand...
Click to collapse
Did you really flash TWRP to eRecovery? It is possible but people usually (specially if not installing Magisk on EMUI 9) flash TWRP to (EMUI) Recovery - which is not the same as eRecovery
So, do two tests:
- switch off
a) disconnect any USB
- press and keep pressing Vol+
- boot by Pow
In test b), do the same but with the phone connected to charger.
If it boots to TWRP in case a), then you flashed TWRP (as usual) to EMUI Recovery.
But if it boots to TWRP in case b), then you really flashed TWRP to eRecovery
If you have stock eRecovery, then in case b), once booted to eRecovery, do not accept Install latest or Factory reset, just Reboot or Shutdown
---
If you rooted by SuperSU, find an option like Full Unroot, or google for and find a zip for TWRP for unrooting - do unroot
Maybe, there are similar options for unrooting from phhSuperUser
Do not accept any OTA yet - if it comes
---
Install Firmware Finder app (from Playstore or from its thread on XDA).
Open, it will show firmwares for your MHA-L29C567
Scroll to the bottom to find your b183. Must be FullOTA-MF or FullOTA-MF-PV (2017.03.22)
Download its update.zip file, copy to PC, unzip to get update.apk - open it by Huawei Firmware Extractor (find its thread on XDA, read how to use it)
Extract Recovery.img (if you need to restore stock Ramdisk) or Recovery2.img (if you really need to restore stock eRecovery)
Extract also Boot.img
Flash Boot.img to Boot and Recovery.img to Recovery (if restoring Recovery), from TWRP or from Fastboot (similarly as you flashed TWRP from Fastboot back then)
Or, flash Boot.img to Boot and Recovery2.img to eRecovery, if you need to restore eRecovery
Now you should have stock Recovery and stock eRecovery - both tests a) and b) must not boot to TWRP
Also, you should have stock Boot - boot to system, check with RootChecker - there must be no more root
----
Have a proper SIM card and WiFi connection, go to Settings, System, Update, go to its menu and take the option to get Full OTA package
If it doesn't give you OTA update, boot to eRecovery (option b) as above, phone connected to the charger) and take Install latest firmware and recovery. Follow by Factory reset, only then boot to system
If eRecovery also fails to update from b183, you can try to update by HiSuite - it has also an option to choose installing a firmware
---
If it still fails to update, you can download by Firmware Finder b190 FullOTA-MF-PV (2017.10.31)
Download both zip files, do not unzip, copy them as downloaded to DLOAD folder on SD card (not Internal memory)
Switch off, press and keep pressing both Vol+ and Vol-, then boot by Pow
It should update to b190, and hopefully you will start receiving OTA updates for Oreo and Pie (must have SIM card)
If not - to be cont.

[SOLVED] Installing ANY custom ROM bricks Oneplus 6

Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.

This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk

But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged

What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.

Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain

Fixed!
Now I'll write a guide for those in the same situation.

franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.

i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.

I messed up - stock ROM update via TWRP :(

Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?

kold11 said:
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
Click to expand...
Click to collapse
To force restart I need to use power button and both volume keys..
To keep TWRP you need to flash rom, then without restart flash TWRP again, then restart TWRP, then flash Magisk.
Likely the r reason why your system doesn't boot is because it can't decrypt your data.
Why this happens I don't know, maybe in the upgrade they changed something related to the exception and then by downgrading again it isn't able to read it anymore.
I would suggest to:
Flash the latest rom.
Flash TWRP
Reboot TWRP
If TWRP then doesn't ask for PIN or password, then I'm afraid you have lost your data. I hope you have a backup.
I'm that case format (not just clear) data -> yes
Reboot TWRP
Then flash Magisk.

Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.

kold11 said:
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
Click to expand...
Click to collapse
I would suggest do restore your device with msm unbrick tool.
1. From recovery, turn off (i noticed, that when tried to turn off from somewhere else, the device would auto reboot later in downlaod mode)
2. In windows, turn off the connection & open device manager: Get this driver http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab
3. Press volume/down + volume/up, after about 5s connect to pc
4. Your device should show up in device manager, open it and install the driver manuell from step 2 (keep device options open... if fail you need to uninstall the driver before trying again)
5. Now wait for about 40s, if your device stays in download mode, you can open & start the msm tool (leave the options in msm as they are)
6. It will take about 280s, then the device will reboot.... (its normal that it stays longer at the oneplus logo at first start)
MSM Thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
I've also uploaded the 10.0.5OOS Unbrick tool on mega, because android file hosted downloads are so terrible: https://mega.nz/file/ArZFkYpS#Z_rOIwZeYN27IG6L8rOi-yfw8wXGiwvK-uWVDlsmvTI