Develop Bugs

Boot loop and factory image restore

Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.

Try the flash all script again with latest firmware and let it boot up completely. It will take a while, once booted, flash TWRP and root if you want.

ntropia said:
Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.
Click to expand...
Click to collapse
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app

androidddaaron said:
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
That's an interesting perspective, actually.
I didn't know that you needed a special image for rooted devices.
Although, I would imagine that's always possible to 'un-root' it, and honestly I was hoping that 'fastboot flash -w...' would have removed any trace of the root.
Is that the case?
Either way, where could I find these modified images?
Thanks a bunch!

Solved
I found the solution which, as it happens when nothing seems to be wrong, was fairly trivial.
Basically, the scripts provided with the stock ROM from Google has problems, and this last command fails:
Code:
fastboot update image-bullhead-mmb29p.zip
saying that system.img is missing.
To fix that, you have to manually extract the content of the files and proceed to flash manually userdata, system, etc...
The problem is that if you don't flash also vendor.img, you're in trouble, and the device will not boot.
Some of the guides that I've found were suggesting that you need to do it for the Nexus 9, and I didn't notice when other guides were mentioning it.
Once you flash the vendor.img, the boot loop is gone.
I'll put it here, I hope it can be helpful to somebody.
Thanks to androidddaaron and k.s.deviate for the support!
(I've thanked also used the thank button near the posts, but if there's more to do, let me know)
Now, back to mess up the Project Fi SIM...

Help with booting problems?

Hello,
I just noticed something the other day and I do not know if this has any effect on my problem with the phone getting a usb not recognized error so I wanted inquire!
So I did a completely clean install of the [ROM] [Touchwiz-PC1,PD1] [100% Stock, Root, No KNOX, No Itson] [4/5/2016] deodox rom and have noticed that my boot screen no longer shows multiple lines while booting. The only thing I get now is:
Set Warranty Bit : Kernel
Before I would get that and several other lines including one about Knox. I also do not get the Sprint logo as one of the bootup screens. My question is, is this rom suppose to do this or did I do something wrong? I followed the directions 100%. I also notice that I also now get an error that it cannot do a fingerprint unlock on boot and I have to enter my emergency password.
Last but not least, if there is a problem. Is there anyway to put a OG5 rom on my micro sd card (I have a card reader I can put the micro sd card into to transfer files, I cannot odin) and restore it to then?
Thanks for any help!

Most of what you describe is not abnormal.
Your fingerprint may be data left over from Lollipop. Try deleting your fingerprints and add them back.
Be aware, if you factory reset, you'll need to flash systemless root again. Google search SuperSU zip if you need it; it's also linked in the ROM thread. If you factory reset for any reason, make sure you don't keep our have a folder in root folder named /carrier/ItsOn. The apk in that folder could activate causing numerous reboot prompts to complete activation.
Eventually, you're going to need access to a PC to do what you want. You might be stuck and unable to update; modified partitions can cause the failure to update on OTA and KIES. Custom stockish ROMs are coming but they won't be for PD1; it's already outdated.
You can't go back to Lollipop without a PC because you need to revert your bootloader to Android 5.1 to run that ROM. Without a TWRP backup to restore, you should also Odin the full stock tar rather than just the bootloader.
Sent from my SM-N910P using Tapatalk

samep said:
Most of what you describe is not abnormal.
Your fingerprint may be data left over from Lollipop. Try deleting your fingerprints and add them back.
Be aware, if you factory reset, you'll need to flash systemless root again. Google search SuperSU zip if you need it; it's also linked in the ROM thread. If you factory reset for any reason, make sure you don't keep our have a folder in root folder named /carrier/ItsOn. The apk in that folder could activate causing numerous reboot prompts to complete activation.
Eventually, you're going to need access to a PC to do what you want. You might be stuck and unable to update; modified partitions can cause the failure to update on OTA and KIES. Custom stockish ROMs are coming but they won't be for PD1; it's already outdated.
You can't go back to Lollipop without a PC because you need to revert your bootloader to Android 5.1 to run that ROM. Without a TWRP backup to restore, you should also Odin the full stock tar rather than just the bootloader.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have a PC, the problem is that it will no longer recognize my phone by USB. It always gives the USB not recognized error. I do have a folder in root called carrier but when I try to go into it with root it tells me my phone is not rooted. This does not make sense as my phone is rooted , per the installtion of the rom and I have other apps I have given root access too.
Arrg! Thanks for the info, any more will help greatly!

h4kudoshi said:
I have a PC, the problem is that it will no longer recognize my phone by USB. It always gives the USB not recognized error. I do have a folder in root called carrier but when I try to go into it with root it tells me my phone is not rooted. This does not make sense as my phone is rooted , per the installtion of the rom and I have other apps I have given root access too.
Arrg! Thanks for the info, any more will help greatly!
Click to expand...
Click to collapse
Did you enable developer options (tap build # in Settings/About device 7 times or more until enabled) and enable USB debugging in developer options?
Yes you should be able to detect device when you plug in to PC but you may not see COM connected in Odin without USB debugging.
If it's always not detecting, could be bad USB cable (broken out missing data lines) or bad PC USB port. Try others first, if that's the case. Hardware failure is rare but has been reported as suspect. Hopefully, it's simple rather than that.
Sent from my SM-N910P using Tapatalk

[root] [ZS570KL] Asus Zenfone 3 Deluxe fast rooting method. Despite TWRP

Not tested on nougat.
I use adb and fastboot , twrp, supersu.
Files We need:
TWRP: It's bogus, in my phone the screen flips upsidedown: Connect a mouse thru female usb or try to figure out how to tap in a rotated screen with a non rotated touch panel.
TWRP Download -> https://drive.google.com/file/d/0B0XMYw0cbs_cdm5FZW1DQXl4MFU/view
SuperSU file - > https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
For ADB access thru MAC:
1.- First of all we have to get open USB debug mode to get adb acces to the phone by going to Settings -> About -> Software Information -> Tap 7 times over Build number.
2.- After we get Developer options available we have to put the phone on usb debugging by goig to "Settings-> Developer Options" Activate USB Debugging.
3.- Install android platform-tools on your PC/Linux/MAC , in my case had work on MAC and no devices acces thru ADB on PC :silly: .
platform-tools -> http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Here you have the 3 options to download ADB and FASTBOOT
4.- Connect your phone to the PC (USB) and copy SuperSu to the root of your phone, a place that its easy too acces, cause TWRP, for the moment flips the screen.
5.- Copy TWRP3.0.XXX.zip to the folder where you have platform-tools installed.
6.- Reboot your phone to bootloader and in Linux could work too:
./adb reboot bootloader [./ is placed cause I don't put platform-tools on the my PATH]
After the boot, then we have to boot on TWRP
./fastboot boot twrp-3.0xxxx.zip (you don't flash anything) If you want to flash TWRP, at your awn risk, ./fastboot flash recovery twrp-3.0xxxx.zip".
Well, now you have to see TRWP on your phone screen.
My recomendation is to play a little bit with the flipped screen if you don't have a female USB to plug a mouse.
7.- Trying to make a complete backup of the phone could be a good practice to move on TWRP with the flipped screen . Tap backup option and make a Backup. Always recomended!
8.- After Backup, you can go to INSTALL SuperSU.zip file. "Install -> look for your SuperSU.zip file "
9.- Go to Playstore and install supersu app.
Now you can test your root, after reboot for example tryin to install some APP that requires root. Fast move:
./adb shell
su root
It has to appear a screen to grant root access to the phone.
10. Done!
Well I think thats my second post at all, hope can help someone to root the phone.
I placed In Questions and Answers cause XDA says want to protect us from SPAM.
Feel free to correct me anything.
Kronen_75

Your links do not work.

jnmacd said:
Your links do not work.
Click to expand...
Click to collapse
Links are corrected. Thanks!

You can also substitute Magisk instead of Supersu if you need to use any of the pay apps or have root sensitive apps...

Without the right Twrp, many benefits to rooting are missing such as removing stock rom applications. Seems without being able to boot to a recovery, even Titanium cannot remove apps because it needs to clean the dalvic.. Can't do it without a recovery
Sent from my ASUS_Z016D using XDA-Developers Legacy app

Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA

You should change your title !!
Tested on nougat.
The variant ZS550KL can be rooted with same method on latest firmware with nougat

Very nice guide, Thank you. Could you please provide updated links to both TWRP and SuperSU. I am currently using TWRP 3.1.1-0 and it functions properly after hanging for approximately 45 seconds on boot. This may be due to the fact my phone is encrypted. I initially rooted without installing TWRP (fastboot boot twrp.img) but have since flashed it. Both ways work well. The posted version of SuperSU did result in root but caused me to lose cell service! The phone could "see" the sim card but not use it. Updating to SuperSU 2.82 solved that issue. This was all done on my finally rooted ZenFone 3 Deluxe Special Edition (Z016D)!!!

I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).

Sandman45654 said:
I unfortunately figured something out the other day. Using TWRP 3.1.1-0 I am able to install zip files, complete wipes, make & restore backups. The issues only arise after you restore your nandroid image. Everything works except for two things.
1. The ability to hear audio during phone calls. The phone is actually able to place calls but you are unable to hear or record any phone audio. Oddly enough I was able to play music and use voice dictation. It was only in-call audio that seemed to be affected.
2. If you have a pin set when you create your nandroid image your pin will no longer work once restored. You will be locked out of your own phone!!
Fortunately both are fairly easily resolved and keep TWRP relatively useful, although a bit bothersome!
To resolve the pin issue it is necessary to use the TWRP file manager or ADB to delete 5 files (listed below) and regain entrance to your phone. Once deleted simply reboot the phone and reset your pin. If you remove your pin before creating a backup this issue is averted completely.
/data/system/gatekeeper.pattern.key
/data/system/gatekeeper.password.key
/data/system/locksettings.db
/data/system/locksettings.db-wal
/data/system/locksettings.db-shm
To re-enable call audio use TWRP (install zip) to reflash the same version firmware from the Asus website over your current install without wiping. This will restore any system apps you may have removed but you should still have root and can easily remove them again. There will be two errors when performing the flash, which is why I believe root is retained but the system image will be reflashed. Reboot and enjoy
I sincerely hope I have not caused anyone any issues! Or that someone else finds this information useful. I have tested everything in this post at least three times. All testing was done on the most recent Android 7 firmware on my ZenFone 3 Deluxe Special Edition (SnapDragon 821/6/256).
Click to expand...
Click to collapse
The second issue happens in all the phones/twrp.
It's possible to install the firmware from asus website with twrp?? To update i flash the stock recovery, install the firmware, then reflash twrp and supersu. Didn't know that! It updates successfully with twrp??

Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.

Sandman45654 said:
Thank you Ryder for confirming my suspicion that the pin issue may have been a more common one with TWRP. This is the first phone I actually cared enough about to use a pin. I was thrown for a loop when I first booted my fresh nandroid restore and the pin I know I've been using was incorrect!
As for installing firmware, with the two errors that occurred during I don't know that you would be able to do full scale upgrade to a higher version. To reinstall the system partition however it does seem to work quite well. I tested this part four times. To do so download the correct device/version firmware to the phones storage, click install, and select that file. After it completes I like to wipe both the cache and the dalvik cache before restarting the phone. The audio issue was unfortunately easily reproduced on my phone, but thankfully equally easy to resolve. This worked for me each time without fail.
Click to expand...
Click to collapse
You said that the two issues occurred when you restored the nandroid backup and to fix one of them by installing the zip firmware from asus website with twrp... I don't understand. I can install zip firmware with twrp or i have to flash the stock recovery and install with it? Errors may occur using the twrp? Sorry

Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.

Sandman45654 said:
Everything done in my post so far has been in TWRP. Honestly I didn't even back up the recovery image. TWRP seemed to work flawlessly so I bit bullet and flashed it.
On a sidenote I am currently testing the usability of FlahFire on this device. It appears to create a very nice fastboot installable recovery image! I have yet to restore the image however. I will post my findings here once I have thoroughly tested it.
Click to expand...
Click to collapse
Ok. I'm interested in flashing zip firmware to update. Never tried that. I thought that firmware can be installed only with stock recovery. The stock recovery can be downloaded in an asus forum website

This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!

Sandman45654 said:
This is the first time I have flashed anything in almost a year. I got to thinking and this is the most success I have had was flashing a stock image with TWRP! I doubt it will perform a full flash. I believe the errors are most likely for the boot and recovery partitions. As a save my butt reflash the system partition it does work. It sounds like it's time to find some TWRP changelogs!
Click to expand...
Click to collapse
I don't care about stock images... If i can't flash the zip with twrp to update successfully then i reflash the stock recovery and after the update root again with twrp and supersu. By the way, the zip firmare contains factory images? I thought it contains different kind of files

Ryder. said:
By the way, the zip firmare contains factory images? I thought it contains different kind of files
Click to expand...
Click to collapse
I lack the knowledge to answer that with enough certainty to even call it an answer! This is my foray into the insides of this phone and I don't want to start posting my hunches.
What I do know is you can flash the system partition using TWRP. I have done it several times. Asus's zips run as a script based zip install. You are offered no options during install. When the script runs you will see two errors quickly scroll past.

Ryder. said:
Download the right twrp here: https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
Click to expand...
Click to collapse
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.

Sandman45654 said:
Are you creating these TWRP builds? If so thank you very much! TWRP-3.1.1-0-Z016-20170826 seems to work flawlessly! No lag on boot and no known issues after restoring a backup unlike before.
I wanted to post my finding about FlashFire by Chainfire. I have had great success with the fastboot backup! It is the only option I have tested extensively however. I have been running the same fastboot restored phone since soon after my last post on this topic with no issues discovered.
Click to expand...
Click to collapse
No. It's not me. It's another user which i don't remember the nickname

Ryder. said:
No. It's not me. It's another user which i don't remember the nickname
Click to expand...
Click to collapse
Okay thank you. If you happen to find out/remember please let me know. I would like to give credit with my project and thank them for their hard work.

Mi A2 Lite bricked?

Hi guys,
I'm having trouble with my A2 Lite. Right after unboxing the phone I installed Magisk as described in the guide (https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626), which worked like a charm. Today, I wanted to install a OTA security update. After the update was downloaded I got an error and I remembered that I had to "uninstall" Magisk, as described in "step a" of the guide. So I did exactly as described in the guide. After Magisk was "uninstalled" I closed the app and tried again to install the OTA security ("step b") update. Unfortunately I got the same error message again ("Can't install update"). So I thought f*** it - I skipped "step b" and proceeded to "step c" and installed Magisk into an empty slot. After that I hit "reboot" and now my phone's in a bootloop :-/
bootloader is unlocked, oem unlock and debug usb are activated. I'm able to enter fastboot, but no recovery, whatsoever.
Is there any way to fix this?

just letting you guys know that "fastboot set_active b" did the trick. I don't know what the hell went wrong though. I did everything according to the guide, except for trying to update the ota update (and failing) before uninstalling Magisk.
Now, the phone is booting correctly, but I still can't install the ota update. it says "Couldn't update" and "Installation problem". What the heck...

lunatikk said:
just letting you guys know that "fastboot set_active b" did the trick. I don't know what the hell went wrong though. I did everything according to the guide, except for trying to update the ota update (and failing) before uninstalling Magisk.
Now, the phone is booting correctly, but I still can't install the ota update. it says "Couldn't update" and "Installation problem". What the heck...
Click to expand...
Click to collapse
This is probably due to the root as it modified the system partition. Check the thread regarding on how to update without losing root.

fake__knv said:
This is probably due to the root as it modified the system partition. Check the thread regarding on how to update without losing root.
Click to expand...
Click to collapse
Could you explain further? Will flashing the stock boot.img fix the issue and will I lose all data on the phone after flashing the boot.img?
thanks

lunatikk said:
Could you explain further? Will flashing the stock boot.img fix the issue and will I lose all data on the phone after flashing the boot.img?
thanks
Click to expand...
Click to collapse
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).

BubuXP said:
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
Click to expand...
Click to collapse
Hi BubuXP
I followed your troubleshooting guide and flashed the boot.img as instructed. Flashing the boot.img didn't do the trick so I continued with flashing the system.img. I checked for the correct build no. of course and for both boot.img and system.img the active slot "b" was chosen. After flashing the system.img I got stuck at a bootloop. I tried to set the active slot to "a", but that didn't help either: Now it wasn't in a bootloop anymore, but it was stuck at the boot animation (horizontal beam) loading forever. After 10 minutes I tried to restart - still the same problem.
What's going on here??
edit:
I flashed daisy_global_images_V9.6.4.0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2 using MiFlash and the "Save user data" option. It was flashed successfully. However, when I start the phone it askes for a password and won't boot up into android if not entered. What the hell...? I deactivated my screenlock pin before I started all this. Is there a default password or what's the problem here?
regards

lunatikk said:
Hi BubuXP
I followed your troubleshooting guide and flashed the boot.img as instructed. Flashing the boot.img didn't do the trick so I continued with flashing the system.img. I checked for the correct build no. of course and for both boot.img and system.img the active slot "b" was chosen. After flashing the system.img I got stuck at a bootloop. I tried to set the active slot to "a", but that didn't help either: Now it wasn't in a bootloop anymore, but it was stuck at the boot animation (horizontal beam) loading forever. After 10 minutes I tried to restart - still the same problem.
What's going on here??
edit:
I flashed daisy_global_images_V9.6.4.0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2 using MiFlash and the "Save user data" option. It was flashed successfully. However, when I start the phone it askes for a password and won't boot up into android if not entered. What the hell...? I deactivated my screenlock pin before I started all this. Is there a default password or what's the problem here?
regards
Click to expand...
Click to collapse
Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens.
I can only suggest to change the active slot, maybe with this you can resolve.
I will also update my troubleshooting section of the rooting guide to make the data backup as the first option to be safe.
If you can sacrifice the data, you can simply format the data partition via fastboot or reflash using the flash_all.bat script.

BubuXP said:
Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens.
I can only suggest to change the active slot, maybe with this you can resolve.
I will also update my troubleshooting section of the rooting guide to make the data backup as the first option to be safe.
If you can sacrifice the data, you can simply format the data partition via fastboot or reflash using the flash_all.bat script.
Click to expand...
Click to collapse
I also thought that it had something to do with encryption. In the security menu, where I turned off the display lock, it said that the phone is encrypted. However neither pin nor fingerprint could unlock the phone.
I had to go for ultima ratio and flash my device with the newest fastboot image and miflash (save user data option didn't work either, btw.).
I lost all data on the device, but now everything works fine and the OTA update also ran through without any issues.
Now, I'm not sure if I will fiddle with magisk again. I really don't have no clue about what went wrong at all...
Thanks

lunatikk said:
I also thought that it had something to do with encryption. In the security menu, where I turned off the display lock, it said that the phone is encrypted. However neither pin nor fingerprint could unlock the phone.
I had to go for ultima ratio and flash my device with the newest fastboot image and miflash (save user data option didn't work either, btw.).
I lost all data on the device, but now everything works fine and the OTA update also ran through without any issues.
Now, I'm not sure if I will fiddle with magisk again. I really don't have no clue about what went wrong at all...
Thanks
Click to expand...
Click to collapse
Thanks for sharing.
Maybe something to try for next time to restore data, I don't know.
I haven't tested yet but I did make a backup using the method explained here
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
I have yet to try (or need) the restore function but running that backup created a 6gb file. My understanding is this is the majority of your apps, data, messages, etc
Without twrp I was hesitant to root but with the bit of knowledge and files shared here so far I have moved forward and glad I did. I haven't had to flash the stock image yet but hopefully this backup helps ease the pain. It is nice to be able to modify at will

BubuXP said:
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
Click to expand...
Click to collapse
Had the same problem. I tried to install the OTA of March, followed the guide to install OTA with Magisk, but after unistalling Magisk, i tried to install the OTA but it gave me this message "installazione riprenderà automaticamente quanto il dispositivo non sarà attivo";
I looked for some help online, but didn't find anything, so skipped to the point c, and i got this bootloop now.
I tried the "set_active b" command, but I'm still in bootloop. I tried to flash the stock rom but apparentrly it's impossible to do it without recovery (which I'm unable to open), so... Help?
EDIT: By using miFlash and using the flash_all command I flashed the most updated ROM I found on MIUI.en, which is the january's one. It worked, even if the build version (10.0.3) is different from the one I had previously (10.0.4). The system says that there's an available update, but i'm too afraid to try it. Suggestion are accepted!

OnePlus 7t root and TWRP recovery

So it's been awhile since I've had a phone I cared to get into installing root and custom stuff but I just bought a 7t and am trying to get it all working. I have the bootloader unlocked and the latest version of TWRP flashed but every time I'm in TWRP it shows up as 0mb and can't mount the storage. I tried "fastboot format userdata" in adb and it worked for one boot cycle but once I rebooted TWRP after that I was back to the 0mb and can't mount storage (I also still cannot format storage from TWRP before anyone tells me to try that) so what gives? What am missing?

You're missing the search functionality of the forum.
TWRP does not currently support reading data partition when encrypted by OOS. It does work, however, for custom ROMs, as long as you don't use a PIN, but a pattern. It also does not support formatting data partition, regardless of the ROM you're using.

morphvale said:
You're missing the search functionality of the forum.
TWRP does not currently support reading data partition when encrypted by OOS. It does work, however, for custom ROMs, as long as you don't use a PIN, but a pattern. It also does not support formatting data partition, regardless of the ROM you're using.
Click to expand...
Click to collapse
Well that's disappointing. So it sounds like there's really not too much point to it then. So I'm assuming there's a guide on how to install root and magisk via fastboot commands?

Again, you're missing the search functionality.
You can see it on the home page of the 7T, under ONEPLUS 7T GUIDES, NEWS, & DISCUSSION, third topic right now..

morphvale said:
Again, you're missing the search functionality.
You can see it on the home page of the 7T, under ONEPLUS 7T GUIDES, NEWS, & DISCUSSION, third topic right now..
Click to expand...
Click to collapse
Still leaving trouble using the search function to find what I want but I'll figure it out. So is it worth installing a custom rom on this phone or should I just try and root the phone on the stock OS? I'm very new to this phone and everything that goes along with it.

Justin541 said:
Still leaving trouble using the search function to find what I want but I'll figure it out. So is it worth installing a custom rom on this phone or should I just try and root the phone on the stock OS? I'm very new to this phone and everything that goes along with it.
Click to expand...
Click to collapse
@Justin541 - If you need any help just PM me. Ill get you going.. As long as your bootloader is unlocked, the rooting process is easy. All you have to do is:
- Install magisk manager (here)
- Download a patched boot.img from here(try to find the boot.img that matches the build your on, all though it probably doesnt matter)
- Boot into bootloader (adb reboot bootloader) and BOOT(dont flash) the patched boot.img (fastboot boot patched_boot.img)
- When phone is booted, open up magisk manager and do a direct install. Booting the patched boot.img is what you gives you a temporary root to be able to install magisk.