As few themes work on MiA1 and after unistalling them we get bootloop with Android One screen.........
So dirty flash doesn't work nor the fastboot without clean all.....so the only solution left is either Clean all or
Go to the substratum folder through TWRP recovery and find the SubstratumRescue.zip and SubstratumRescue_Legacy.zip?
Flash them through TWRP and you will be able to boot t your screen.
Related
I have a rooted Lenovo A6000 Plus.
Today, I was trying to install custom TWRP recovery, after which I planned to install XPOSED framework.
I installed the framework(used ADB). My device went into TWRP recovery.
I rebooted the device, but was unable to go into TWRP again.
So I flashed the recovery again. Again, my device went into TWRP recovery, but this time, it auto-installed XPOSED. After reinstallation, my device showed the Lenovo logo, after which the screen went black. I removed the battery to switch it back. But again, the Lenovo logo appeared, after which the screen went black. After a few times, I just let my phone sit at the black screen. L8r the boot animation appeared (I had a custom one installed).
Now my phone is just stuck at the animation.
P.S. I have tried removing the battery and rebooting many times.
PLEASE HELP URGENTLY!
@adityapathak343, the XPOSED package also comes with a Uninstaller zip, which you would've found on the same page. Just flash that zip with TWRP, and if the phone still doesn't boot then wipe the cache and dalvik partition through TWRP only.
flash stock rom
Download and flash stock ROM
It will definitely going to be ok
Download stock ROM from firmwarefilecom
Just download & flash from recovery
I have link but can't able to share right now
I've been getting bootloops after installing Magisk on my OnePlus 5 unlocked bootloader , rooted before at 4.5.15.
I directly updated it to 5.0.2 which resulted in many errors in the end had to flash it completely and then clean install the ROM .
The ROM works perfectly with almost no trouble.
I then flashed almost all Magisk versions I could get hold of (14.5,15.2,15.3,15.4(beta))
But none of them could get past the boot animation.
I've also flashed the no Verity mod file both before and after the flashing of Magisk nothing worked.
But everytime after all this I flash the Magisk uninstaller and I get easily get back to using the device but without root.
Anyone help me rooting this ?
The ROM has been downloaded from official OnePlus website and the twrp I'm using is the codeworkx version.
First do this then tell me how it went.
1. Boot to fastboot and flash twrp-3.2.1-0-universal-codeworkx-cheeseburger.img via command window, make sure you have adb installed on pc.
2. Then boot DIRECTLY to twrp.
3. Dirty flash OOS 5.0.2 over your current rom in twrp and then wipe dalvik and cache.
4. Then boot into fastboot DIRECTLY again and flash twrp-3.2.1-0-universal-codeworkx-cheeseburger.img again.
5. Boot into twrp directly and flash Magisk 15.2.zip
6. Finally boot into the system.
7. Optional: then you can go ahead and update Magisk via it's own flash tool.
I'm already on 5.0.2 so do I dirty flash it again?
i'm running stock january frimware with no root or any thing and wanna flash aosip 9.0,when i flash twrp 3230 i have working touch . and when i flash jan_twrp_root.img based on daze one toturial i lose my touch in twrp so i decided to start instructions for installing custom roms with twrp 3.2.3.0 because i have touch on it. after flashing rom i flashed twrp-installer.zip and after rebooting to recovery i did not have touch to flash gapps and when i change to the another slot after flashing twrp installer i have twrp working so did it and change the active slot with fastboot after that in twrp < reboot< change slot to the other i mean were the rom installed and doing gapps and magisk.zip rebooting to the system but i do not have touch in system and can not do nothing in lets go screen. testing the process with RR and Aosip rom and having the same results.
any suggestion?tnx in advanced
Not to hijack but I have a bonestock phone that is neither rooted and the bootloader is locked. Had a bad screen, replaced with two different screens. Both turn on no issue but zero touch. Super frustrated, flashed latest OTA and nothing.
had this issue, i couldnt have touch on one rom but the others worked, i used the adb recommended in the stock rom files thread (think this was the problem for me) but i ended up reverting back to stock with magisk, the roms are stable but have some issues and i didnt find it a plus of having a rom with essential, i did installed helix engine for the app optimization
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Dirty flash ROM or if 1st step doesn't work factory reset and install everything
Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!
I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen
Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.
i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.
I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.
has anyone experienced something similar?
when booting any twrp via fastboot always a black screen appears, I tried using adb twrp to install the .zip file:
"adb shell twrp install /sdcard/<filename>.zip
but the result is an error, only able to install custom twrp .zip like orangefox & pitchblack, but a new problem appears, I can't install custom rom.zip via custom twrp because the vendor problem can't mount.
instead of having to spend money to replace the screen with the original one, finally I found an easy solution to solve the black screen when booting twrp after replacing the non-original screen.
using CosmicDan TWRP which I found on github: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases
we know that the android 9 pie bug is that we can't install TWRP permanently, so after entering hotboot cosmic TWRP, then install LOS A11, then install twrp permanently, then you can replace another custom rom like PE12
thanks
boy_venz21 said:
has anyone experienced something similar?
when booting any twrp via fastboot always a black screen appears, I tried using adb twrp to install the .zip file:
"adb shell twrp install /sdcard/<filename>.zip
but the result is an error, only able to install custom twrp .zip like orangefox & pitchblack, but a new problem appears, I can't install custom rom.zip via custom twrp because the vendor problem can't mount.
instead of having to spend money to replace the screen with the original one, finally I found an easy solution to solve the black screen when booting twrp after replacing the non-original screen.
using CosmicDan TWRP which I found on github: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases
we know that the android 9 pie bug is that we can't install TWRP permanently, so after entering hotboot cosmic TWRP, then install LOS A11, then install twrp permanently, then you can replace another custom rom like PE12
thanks
Click to expand...
Click to collapse
i have the same issue, how can i fix it? please help me bro
Sojibsarkar said:
i have the same issue, how can i fix it? please help me bro
Click to expand...
Click to collapse
I thought explain it
Sojibsarkar said:
i have the same issue, how can i fix it? please help me bro
Click to expand...
Click to collapse
If u from stock Rom:
- hotboot twrp cosmicdan via fastboot
- install custom Rom, ex: LOS A11 or PE11, if u find error 28, u should download again the Rom, cause it's corrupt
- reboot bootloader, hotboot twrp cosmicdan
- install twrp cosmicdan with Tissot manager
- reboot recovery
- u can install Rom like PE12 etc