Database Users

[A] For all of you, ending up in "bootloop" updating Android

I finally managed to install Android 5.0 Lollipop on my Nexus 4.
First I flashed it using the factory images and fastboot and it was working fine, but after one week the sensors did not work anymore. CPU-Z showed no avalaible sensors. So I tried to reflash system.img and then the misery started. I was not able to boot, having the 4 spinning dots for hours, even over night (~8h). I tried every combination one could think of, e.g. installing the factory image, sideloading the OTA, installing flashable zips of the stock rom, I also tried custom roms and formated and also erased every partition using "fastboot erase ... or fastboot format ...". Literally nothing worked except installing the Android 4.4.4 factory image. So I ended up having a nandroid of Android 4 and from time to time installing Android 5 which did never work.
Today I was using the file manager in the TWRP custom recovery and I thought Android 5 not booting may be due to the encryption I had, when Lollipop was running well, the next thought was to try to reset the phone to a "real" factory state, because factory reset in recovery may format /system and /cache etc but the rest of the root file system is still present.
After some search I found this tutorial and I am happy to say that it worked and I rebooted my phone twice without having a "bootloop".
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
I did it on a Windows 7 laptop and followed the tutorial closely except I did not flash the flashfactory.zip he mentions (the links are down anyways), but I flashed the Android 5 factory image in fastboot. I have a 8GB Nexus, so I did not have to do the part for the Nexus 16GB.
I hope I can help some of you who tried to install Android 5.0 and ended up like me. First thing to try is always a factory reset, but if it does not work like in my case, this tutorial may help. If anyone has any questions, feel free to ask!
Also found this:
https://android.googlesource.com/platform/frameworks/base/+/8de29d6
greetz

HI,
I'm also facing same problem and tried all things mentioned in OP except the worked one. The links in the referenced thread are down. Can you please upload the LGNPST and the factory image flashable with LGNPST ?? Searched for so long, no result.
Please help to fix my phone..
Thanks in advance.

njarun said:
Searched for so long, no result.
Please help to fix my phone..
Thanks in advance.
Click to expand...
Click to collapse
Seriously?
Your searching skills Sir, leave much to be desired.
I was able to successfully DL all files from the following links as of this posting.
Working link to LGNPST_1.3+Components in this post:
http://forum.xda-developers.com/showpost.php?p=47787622&postcount=32
AND
IN this thread
http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
Working link to N4 Android 4.2 JOP40C TOT file HERE and LGNPST w/ Nexus 4 Unbricking Tools Package HERE
Best of luck

COS13 rooting failed, stuck in boot loop

Hi all,
I got a brand new Wileyfox Storm which I liked to have rooted. When I booted the phone I got several updates which I installed first.
After updating I followed this guide: http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992
And also with a little bit help from the Cyanogen wiki: https://wiki.cyanogenmod.org/w/Install_CM_for_kipper
Reason I chose for this method is because I tried the recommended WinDroid Toolkit before but the server doesn't has the required files anymore so that program is useless for the Wileyfox Storm.
I'm running Cyanogen Os version 13.1.2-ZNH2KAS3NA-kipper btw (offical FOTA).
When I followed Bobslesbricoleurs tutorial to unlock the bootloader I got a message but not one I expected. It said:
<bootloader> Device already : unlocked !
OKAY [ 0.000s]
finished. total time : 0.000s
Does this mean I got my Wileyfox Storm with bootloader already unlocked? That how I read it...
I continued to start rooting it, but not before testing if I could still boot but everything was fine.
I tried to flash the attached custom recovery I got OK and a 'remote: size too large' error. It didn't successful flashed the recovery.
I checked if everything still was ok and it was. I could boot and everything.
So I tried something different. I'm not new to flashing (I've had a Galaxy S2 for 5 years which was running on CM13) so I went to the Cyanogen site and downloaded the latest stable (snapshot) recovery for kipper which was cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kipper-recovery.img.
I tried to flash that recovery and it succeeded. I could still boot recovery and system... except that after booting system the ROM would replace the recovery back to stock.
I did some research on this but I couldn't find any helpful information about it for the Storm device. So I Googled it in general and read somewhere that COS had a developers toggle to disable 'updating recovery'.
This is probably where I made my mistake because I unchecked that update recovery toggle and reflashed the snapshot recovery that worked before.
I'm not very sure, I should have written this down, but if I remember correctly the system could still boot.
I didn't know how to flash the SuperSu-v2.46_signed.zip with fastboot, the tutorial didn't specify this and I'm used to flashing from recovery (fastboot is kinda new to me, although I have worked with adb commands before).
So I booted the rom, installed AirDroid to push the zip to my internal storage and I went back to the recovery.
I flashed the SuperSu-v2.46_signed.zip with the update option in the recovery.
And now the rom is in a boot loop.
I already tried a full factory reset but it's still boot looping.
I know that in the tutorial topic FluffyTwit has had a similar problem, not sure if it's the same but it looks like it.
The given solution is "Flash stock boot.img from stock rom zip, reboot" to which he replied " flashed the whole .zip file because I saw a tutorial on some website...".
But at this stage I'm a bit afraid that I'll do it wrong again, as the instructions are either out-dated or they're just not 100% correct. Could someone help me out and/or confirm the exact steps I should do to get my device back up and running?
I'd rather keep the device stock without root than rooting it with risks of bricking. I have a feeling this device isn't as safe to rooting as I'm used to..
Thank you in advance.
Edit: I've found my solution and had to change something.
You can read it here starting from Edit 2.
http://forum.xda-developers.com/showpost.php?p=68632922&postcount=84

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!

What version of TWRP did you flash first?

I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.

Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.

I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.

Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.

Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

Moving from stock Android 5.0.1 to Resurrection Remix N v5.8.5.

Hello community!
First of all, I feel I have to apologize to you all since I know I have clogged the forum with a lot of requests of help about upgrading my smartphone... They are scattered all over the place so I have decided to gathered in a definitive one.
I have edited this post to make it a comprehensive guide for all the people who want to upgrade their HUAWEI P8 LITE ALICE from the stock Android 5.0.1 to the Resurrection Remix N v5.8.5. Before go any further I want you to read the following disclaimer:
PLEASE PLEASE PLEASE READ THIS!!
I am not a developer. I am not a programmer. I have been greatly helped by the user Botar230 so, unfortunately, I cannot help you in case of problems. I myself had problems and had to ask for help. The only thing I can say is to be always polite and try to explain, as best as you can, what's going on.
I will try to be as much clear as possible here but keep in mind that english is not my native language so it is possible that I might mistaking something. My apologize. I am not responsible for any damage you may do to your mobile and I am not responsible to any data loss it may occur. You should ALWAYS do a backup before proceeding. ALWAYS.
I've decided to flash Resurrection Remix N v5.8.5. because it is pre-rooted with Magisk.
BEFORE start to upgrade your mobile, read all this post twice and be sure to understood all the things I have written here. Check the links, check if you have the correct files, check if your mobile is fully charged, check if the bootloader is unlocked, check if you have the right ADB files and drivers downloaded and installed. Please do it BEFORE you start everything.
Done? Everything is fine? So, here we go!
GOAL: Moving from stock Android 5.0.1 to Resurrection Remix N v5.8.5.
MY MOBILE: Huawei P8 Lite ALICE (ALE-L21) unbranded single SIM - Build number: BalongC50B311 - Kernel 3.10.61-gcd3fde7 - EMUI 3.1
BOOTLOADER STATUS: unlocked, checked via ADB
The build number and the kernel number might differ. You should check them carefully and search around this forum how to proceed properly. Also, I totally don't know what to do if you have a double SIM phone. Sorry.
These are the files I have downloaded and put on the MicroSD before starting the whole process:
b895_update.zip
open_gapps-arm64-7.1-nano-20180702
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
The file TWRP_3.1.1-0_ALICE_BL.img have to be put in the same directory where adb.exe is since you will flash it via adb command: fastboot flash recovery TWRP_3.1.1-0_ALICE_BL.img once you have entered in fastboot mode AND you have checked that your bootloader is unlocked.
Now, the next steps that worked for me are:
install TWRP_3.1.1-0 via ADB
Factory reset (Wipe -> Swipe to wipe)
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload as suggested by Botar230. I find myself comfortable to use ADB.)
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload
Flash RR-N-v5.8.5-20180302-alice-OpenKirin) via TWRP AND at the same time...
Flash Open Gapps via TWRP. You HAVE TO USE THE ARM64 - 7.1 VERSION!!!
Reboot your device. It is done! :good:
NOTE!! Updating the phone to b895 will take really a lot of time. Seriously. It might be scary but it's ok. It will update EMUI too.
NOTE!! When you install TWRP via ADB, the TWRP_3.1.1-0_ALICE_BL.img file MUST BE in the same directory where the adb.exe file is.
At this point, everything should be fine, working and squeaky clean!
The ROM is pre-rooted with Magisk and that's pretty cool!
At this point I think my brief tutorial is over. If you find out something important missing or wrong, please point it out! It will help other people! Thank you!
Some links about ADB that I found quite useful:
How to Install TWRP Recovery via Fastboot On Any Android Device
How to Use ADB & Fastboot Commands with your Android Device
ADB Shell
Once again I have to thank the immense patience of BOTAR230 and all the people that worked so hard to make everything possible: I mean the guys (and gals? Maybe, I don't know... ) behind the Resurrection Remix ROM, behind the TWRP project and the Open Gapps and the many more I probably forgot! Thanks everyone!

DaGreatAssyr said:
Hello community!
First of all, I feel I have to apologize to you all since I know I have clogged the forum with a lot of requests of help about upgrading my smartphone... They are scattered all over the place so I have decided to gathered in a definitive one.
Next, I am quite insecure on all the steps so I will try to make a comprehensive list and keep it updated hoping it will help all the Huawei P8 Lite ALICE users that will do the same process I am about to do. Let's proceed!
GOAL: Moving from stock Android 5.0.1 to OpenKirin's MoKee
MY MOBILE: Huawei P8 Lite ALICE (ALE-L21) unbranded single SIM - Build number: BalongC50B311 - Kernel 3.10.61-gcd3fde7 - EMUI 3.1
BOOTLOADER STATUS: unlocked, checked via ADB
Now, the next steps would be to root the mobile. My wild guess are
install TWRP_3.1.1-0_ALICE_BL via ADB
install Magisk to root Android 5.0.1
At this point I am not perfectly sure if those steps are right AND if Magisk is the right choice to root Android 5.0.1 on my mobile. Are there other ways to do that?
Once the device is rooted, the next steps should be:
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed)
install again TWRP_3.1.1-0_ALICE_BL via ADB
install again Magisk to root Android 6.0
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
That's the theory. I've used SR5-SuperSU-v2.82-SYSTEMMODE but it bricked the phone after I updated to Android 6.0 and the user Botar230 told me that it is no longer updated and used and suggested me to use Magisk instead.
The files I have are:
b895_update.zip
open_gapps-arm-7.1-stock-20180626.zip
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
pa_alice-7.3.1-EOL-20180203.zip
TWRP_3.1.1-0_ALICE_BL.img
Previously, I have updated my device to Android 6.0 and installed TWRP 3.1.1-0 and everything went really good. When I tried to root the phone with SuperSU-v2.82, it bricked. Now the phone is restored to its initial conditions, brandless.
I have read THIS POST but it's pretty old and most of the link there are not working anymore.
So, if someone is kindly willingly to give me a hand (yeah, another one, I know... ) on this subject, I'd really appreciate it. Again.
Thanks in advance!
Click to expand...
Click to collapse
I didn't fully understand you, so I'll write a quick guide how to move from stock android 5.0.1 to any other custom ROM (I've read that you already unlocked your bootloader and flashed twrp so I'll skip those two)
First of all, use this version of TWRP.
1. Boot into TWRP
2. Factory reset (Wipe -> Swipe to wipe)
3. Flash B896 update (B895 is fine too)
4. Flash TWRP (Install -> Select image -> Recovery)
5. Flash a custom ROM of your choice
6. Flash Open GAPPS (I recommend flashing NANO version)
7. (Optionally) Flash Magisk if your custom ROM isn't pre-rooted (if unsure, check the root status before flashing)
Fun fact: You don't need to put every file on SD card to flash it. You can also use sideload

Botar230 said:
I didn't fully understand you, so I'll write a quick guide how to move from stock android 5.0.1 to any other custom ROM (I've read that you already unlocked your bootloader and flashed twrp
Click to expand...
Click to collapse
Hello Botar230! At the present time, I only unlocked the bootloader.
No TWRP installed so far.
Thank you for adding some steps I have missed (like the factory reset and the GApps! :good: )!!
The TWRP version I have is the same you suggested me so this is fine!
Yes, now that I think about, nearly all the custom ROM are pre-rooted and there's an option to switch the root in the setting panel but I will check it eventually.
I have make corrections in my list after your suggestion:
install TWRP_3.1.1-0_ALICE_BL via ADB
Factory reset (Wipe -> Swipe to wipe)
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload)
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
The files I have are:
b895_update.zip
open_gapps-arm-7.1-stock-20180626.zip (I will not use these)
open_gapps-arm-7.1-nano-20180630.zip (I will use these one! )
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
pa_alice-7.3.1-EOL-20180203.zip
TWRP_3.1.1-0_ALICE_BL.img

Everything looks good now. Btw you don't need to flash nano gapps exclusively, it's just a matter of your personal preference which one you choose.
Sent from my LG-K220 using XDA Labs

Botar230 said:
Btw you don't need to flash nano gapps exclusively, it's just a matter of your personal preference which one you choose.
Click to expand...
Click to collapse
To be honest, I don't know what to choose between all the options I have seen on the website. Let's say that if the installation works properly it's a matter of seconds to make a backup and try another Gapp. For the moment I will follow your suggestion.
That's what I have done so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload DONE AND OK!
Everything is working fine so far but I am a little bit nervous about these one. I will take a deep breathe and I will proceed right now. I can flash the ROM and the Gapps with TWRP, right? I am mostly sure about but a confirm could ease my fear of bricking the phone again... :silly:
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk

DaGreatAssyr said:
To be honest, I don't know what to choose between all the options I have seen on the website. Let's say that if the installation works properly it's a matter of seconds to make a backup and try another Gapp. For the moment I will follow your suggestion.
That's what I have done so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideloadDONE AND OK!
Everything is working fine so far but I am a little bit nervous about these one. I will take a deep breathe and I will proceed right now. I can flash the ROM and the Gapps with TWRP, right? I am mostly sure about but a confirm could ease my fear of bricking the phone again... :silly:
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
Click to expand...
Click to collapse
Yes, everything is correct.
Sent from my LG-K220 using XDA Labs

Botar230 said:
Yes, everything is correct.
Click to expand...
Click to collapse
First of all, thank you for your immense patience!!
That's what happened so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload DONE AND OK!
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin) DONE AND OK!
I had to install the open_gapps-arm64 since the system required the ARM64 but apart that...
Flash open_gapps-arm64-7.1-stock-20180630.zip DONE BUT NOT OK! - I've tried to install the NANO and the STOCK Gapps but every time I got the same error message on TWRP: "failed to mount data: operation not supported on transport endpoint". Google Play and all the Google apps cannot connect: the Google error message is always the same: "couldn't sign in". I've double checked the login and they work both on my PC and on the other phones so I'm sure they are correct. Now I'm searching what kind of error it is but I'm not finding much infos about. Plus, there is the warning message saying that "Google Play services has stopped" and it keeps popping on the screen.
Check whether the ROM is rootable and eventually flash Magisk NOT DONE YET but it seems that it is not pre-rooted.
I am searching the web to understand what's going on here.

It's probably because the custom ROM that you've chosen uses f2fs file system on /data partition instead of ext4. Try to do this:
Boot to TWRP -> Wipe -> Advanced wipe -> Choose Data -> Repair or change file system. From here you can see if the file system of /data is ext4 or f2fs. If it's f2fs, then click Change file system and choose ext4.
Before doing all of this, you should flash b895 again, do a factory reset, flash twrp, flash your custom ROM, change /data file system, and finally gapps so there will be no conflicts between old and new gapps.

Hello again!
Sorry for the silence, got some busy day but here I am.
Before doing what you told me, I've tried to do a backup with TWRP and I've been flooded with error messages:
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to recreate /data/media folder
Unable to mount storage
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount /data/media/TWRP/.twrps
And, of course, the backup process failed.
At this point I cannot do anything with TWRP.
I cannot backup, cannot flash a ROM or a ZIP.
The phone works fine, it boots and I got no problems. I can boot it via ADB too.
I'm really scared it will brick or loop sooner or later. I am keeping it turned off and wait for any other advice before proceeding since it would be quite pesky to restart from scratch again....
Following your directions I've seen that the data file system is ext3.

DaGreatAssyr said:
Hello again!
Sorry for the silence, got some busy day but here I am.
Before doing what you told me, I've tried to do a backup with TWRP and I've been flooded with error messages:
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to recreate /data/media folder
Unable to mount storage
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount /data/media/TWRP/.twrps
And, of course, the backup process failed.
At this point I cannot do anything with TWRP.
I cannot backup, cannot flash a ROM or a ZIP.
The phone works fine, it boots and I got no problems. I can boot it via ADB too.
I'm really scared it will brick or loop sooner or later. I am keeping it turned off and wait for any other advice before proceeding since it would be quite pesky to restart from scratch again....
Following your directions I've seen that the data file system is ext3.
Click to expand...
Click to collapse
Don't worry, it won't brick. Maybe the internal storage is encrypted. In order to remove encryption, go to Wipe -> Format data.

Hello Botar230! Something funny (in a very positive way) happened! I did as you told me: I booted in recovery mode and went to WIPE -> FORMAT DATA.
Then I considered to install the other ROM I had, RR-N-v5.8.5-20180302-alice-OpenKirin and it has been the best idea I could have!!! :laugh:
After I formatted the data, I rebooted in recovery mode and checked that the problems where all disappeared and they actually did. Then I flashed the OpenKirin ROM and the Nano Gapps you told me.
SURPRISE SURPRISE the OpenKirin ROM is pre-rooted with Magisk 15.3 and the installation, this time, went perfectly fine without any trouble! Plus, Magisk updated to the latest version, the 16!
As I promised, I will now update my first post on how to upgrade my mobile phone hoping it will be useful for someone else but first I want to enjoy my brand new phone!
And, of course, I want to thank you for all the support you gave me in these days! You have been really patient and kind! I am really sorry I cannot help you back since (as you have noticed...) I am not much of an expert so all I can give you is my gratitude and thankfulness! THANK YOU 1000 TIMES BOTAR!! :highfive:

You're welcome. Have a nice day! :highfive:
Sent from my LG-K220 using XDA Labs

[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!

From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !

Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number

I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch

Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!

Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-

It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse

Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.

finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed

Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well