Phone keeps booting to TWRP - Xiaomi Mi Mix 2 Questions & Answers

Hi, so i got someone to root my phone to enable a safetynet pass on an app with Magisk
Suddenly now as soon as the screen turns off via sleep or lock it myself, I will boot into TWRP recovery.
This is becoming a huge problem for me now so im trying to find a solution asap.
Do i unroot my phone and just reset it all to norm? If so how do i go about doing this step-by-step as im not too entirely familiar with root which is why i got someone else to do it.

Re-flash the stock recovery. Even I was facing this kind of issue after rooting. I wasn't able to get my Mix 2 booted after installing TWRP for rooting. However, I got it solved by re-flashing stock recovery.
I was long time ago, but I think it should work for your as well. In you want to root your Mix 2, instead of flashing TWRP, boot it right away, flash magisk to get root access & reboot, you should not get any such bootloop issue whatsoever.

Related

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk

bootloop issue?

Hi,
I think I have the bootloop issue. I was running purenexus marshamellow.
At first, I couldn't get past boot after many attempts,phone kept going dark. I wasn't even able to boot into bootloader. So, I removed the sim card to put in a backup phone. The next day I went to work on the phone to see what was wrong with it. Amazingly it booted up. So I connected to adb and downloaded all my personal media (adb pull). At that point I have never read about the bootloop issue, phone has been solid for a while and I don't keep up with the news. So then I decided to do a clean flash of purenexus. I noticed Nougate is available and decided to go with that.
For the most part, I can boot into bootloader without any problems now. So I flashed, the bootloader, the vendor image and radio. I went to reboot into TWRP and I got the bootloop issue. So I decided to flash the latest TWRP. Then I was able to boot into TWRP. I was able to wipe the cache/data. However, when I went to install purenexus, it would freeze and reboot. At that point I realized something is wrong and I came here. I read about the bootloop issue. So now I am wondering if I have that issue? I'm pretty certain I do, except that I can reliably boot into the bootloader. TWRP and android itself will cause reboots, but not the bootloader.
So should I send in the phone to get replaced? Or is there anything else I should try?
Also, I am halfway done towards installing purenexus, is there a way for me install in the bootloader without having to go into twrp?

att g3 stuck in factory restore stage 2 (not sure if this goes here sorry)

I tried restoring back to factory after being stuck in a boot loop, thinking my root was the issue or something idk. I used flash tool to try and flash back to stock and fac reset and it gets to the end where MiniOS tries to do its thing but i get no promts and it just says factory reset status 2. its driving me insane trying to get this thing flashed back to stock. i dunno if im missing anything or something but im foloowing the steps like to the letter and it keeps bricking. any help or advice here that could help me out? and sorry if this doesnt go here and stuff. im new to the forums and all that.
Hi,
I had the same problem yesterday. Even worse after that factory reset status 2 my phone couldn't be detected anymore by flashtool 1.8. So I tried the kdz method. This worked for me and from stock I was able to use one click root and flash twrp with flashify. Then I went straight to android 8.1 with magisk root. Don't forget to flash mr bump after root without any reboot in between.
f4lkon said:
Hi,
I had the same problem yesterday. Even worse after that factory reset status 2 my phone couldn't be detected anymore by flashtool 1.8. So I tried the kdz method. This worked for me and from stock I was able to use one click root and flash twrp with flashify. Then I went straight to android 8.1 with magisk root. Don't forget to flash mr bump after root without any reboot in between.
Click to expand...
Click to collapse
yeah i ended up getting it out of status 2 and tried to run stock for a bit but ended up having issues where it would just randomly shut itself off. and then boot loops. switched out like 3 different batteries, (1 that came with the phone, a not so great quality 6000mAh, and a new stock lg battery) and still having boot loop issues. so im thinking that the phone is just dead. so with tax season coming up soon i may just wait and get that new sexy razer phone. i need something new anyway and better than this walmart zte placeholder im using. lol

Urgent Help Required || Phone in Bootloop after installing Magisk Module

Hello forum members,
In a bit of mess here and panic too. I installed a pixel related module from MAGISK and rebooted the device and now my device is stuck in bootloop, it goes until the red dot in middle and 2 circles rotating around it and then restarts.
The phone is rooted on stock rom and have blu_spark v8.68 installed. I am able to enter the recovery.
The problem is I cannot loose my data, have no backup whatsoever. In recovery mode under file manager I am still able to see all my data. I need to know a way how can I retrieve my data or flash a new rom without loosing my data.
Please, please help me out.
Thanks,
Taha Sumra
tahasumra said:
Hello forum members,
In a bit of mess here and panic too. I installed a pixel related module from MAGISK and rebooted the device and now my device is stuck in bootloop, it goes until the red dot in middle and 2 circles rotating around it and then restarts.
The phone is rooted on stock rom and have blu_spark v8.68 installed. I am able to enter the recovery.
The problem is I cannot loose my data, have no backup whatsoever. In recovery mode under file manager I am still able to see all my data. I need to know a way how can I retrieve my data or flash a new rom without loosing my data.
Please, please help me out.
Thanks,
Taha Sumra
Click to expand...
Click to collapse
Since it seems the bootloop was caused by Magisk, you can try uninstalling Magisk in recovery and reboot to system.
Link: https://github.com/topjohnwu/Magisk/releases/download/v17.3/Magisk-uninstaller-20181020.zip

Unable to boot phone once TWRP installed?

Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/
Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)

Categories

Resources