My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
lukke04 said:
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
Click to expand...
Click to collapse
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
timberwolf60 said:
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
Click to expand...
Click to collapse
i saw the request of the message but i am not using a custom recovery on my phone,i use a custom dev rom made by miui france.
i think some china dev rom comes rooted by default with custom installer updater and gapps like mine.
i think twrp is not fully compatible with this device yet.
Have you try with sp flash tool method ?
http :// en.miui.com/forum.php?mod=viewthread&tid=156838&extra=page%3D4&mobile=2
I just installed TWRP for the first time ever. I used the Flashify App from the Play Store, installed it and gave it root permissions and just selected the TWRP image on the phones internal store. Seemed to work just fine and did not have to plug my phone into a computer
Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.
...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6
Try flashing COS 12.1 via fastboot.
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance
i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os
unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!
U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....
I kind of messed up. I have had no issues up till now. I have flashed Baikal os and found there were problems with youtube. I figured it was just that rom then found that every other rom I tried had the same issue. I flashed the stock Nougat (on accident mind you) and thought I could just do the update to 8.1 oreo. The issue is that it restarted into twrp. From there, I can't boot into any rom. I haven't tried stock rom but everything I have tried does not work. When twrp is finished flashing both the rom and gapps, I clean (sometimes not) the cache and restart into system. It keeps rebooting into twrp instead of into the rom. What should I do? I have never had this issue before...
Update: I can only boot into my phone if I boot from the bootloader. I can't boot from recovery, like clicking on boot into system from recovery.
Update # 2: using the tool by drtechie, I flashed the Oreo stock firmware/rom. The issue is that even with the recovery wiped, something keeps making my phone try to boot into recovery. I got the screen for people who dont have a custom recovery installed. Still clueless. Getting desperate because I kind of want my g5 plus back...
Factory reset your phone from twrp
I don't understand exactly what you are trying to say but if your problem is "Twrp bootloop means no matter what you do you are not able to get out from twrp" than type this in twrp terminal
In twrp terminal :
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
And again reboot to recovery. Flash any rom now you will be able to boot into system
Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?
Seems the same with what i experienced. Have you tried installing a fastboot rom? I had my oneplus 6t bootlooped into fastboot mode even if i try to turn it off, it just boots back automatically to fastboot mode. Last resort was to flash a fastboot rom. That worked for me.
thalesian2020 said:
Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?
Click to expand...
Click to collapse
What TWRP version are you trying to install?
jp0469 said:
What TWRP version are you trying to install?
Click to expand...
Click to collapse
I tried 3.3.1.1. and 3.2.3.0.
What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.
Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?
Quickest way to start over:
To get back straight your gonna need to access a Windows PC, and run the MSM tool. Make sure you install both OnePlus and Qualcomm drivers. ( Don't wait for Windows, just pre install the drivers) here are some links. Not my work. Please be sure to thank the developers for creating and hosting these tools ?
MSM Tool:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
OnePlus Drivers:
https://androidfilehost.com/?fid=11410963190603879743
Qualcomm drivers:
https://androidfilehost.com/?fid=11410963190603879743
thalesian2020 said:
Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?
Click to expand...
Click to collapse
Were you on Android 10 before (OOS)? That will do that. LOS 16 is Android 9 and should have no problems installing TWRP or booting to it.. For LOS 16 I'd go back to 9.0.17, then install LOS 6T.
I posted these LOS install instructions a long time ago for another user.
Remember the MSM Tool will relock your bootloader so if something goes wrong the MSM Tool is your only choice. That is why it is always the last thing I resort to.
Thread to get Fastboot stock Roms if you want to try that route first.
Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!
thalesian2020 said:
Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!
Click to expand...
Click to collapse
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.
OhioYJ said:
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.
Click to expand...
Click to collapse
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...
thalesian2020 said:
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...
Click to expand...
Click to collapse
Wiping, Dalvik / ART, System, and Vendor is generally a bad idea. You can do them in certain situations, this isn't one of those situations you should be wiping those though. Factory reset, means the slider on the main page of the wipe screen that says swipe to factory reset, format data is the button that says format data. Don't do anything extra. If you did, yeah I would go back to 9.0.17 using the fastboot rom again, that will put everything back on both slots.
like OhioYJ stated, don't use advanced wipe. re-run the msm tool. Then follow his instuctions. You shouldn't need to preform any manual data wiping. The process of flashing will do everything required. looks like you're almost there
Thanks guys. I will try it out and let you know.
Edit: So I finally managed to properly install LOS - OhioYJ, your instructions worked! I installed 9.0.17 and went from there without wiping any additional partitions.
One questions remains: in your instructions you mention that after installing LOS once, you can update LOS as normal and you mention doing it via the recovery with flashing TWRP or GAPPS later again. Is it possible to do the update via the normal update function of LOS as well? Or will that overwrite TWRP?
You guys are awesome. Thank you so much for your help!
I seem to be stuck on the fastboot screen as well. Being on a MAC, anytime i try to do something in fastboot it goes straight back to the fastboot screen. I Thought I was on Android 10.0 trying to install recovery for that lead to bootloop of fastboot, tried using the Pie recovery and same thing. I am open to suggestions.
Thanks.
OhioYJ said:
What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.
Click to expand...
Click to collapse
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2
callumbr1 said:
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2
Click to expand...
Click to collapse
Yeah it starting to seem like it maybe isolated to Lineage. You cant install TWRP with LOS 17. Someone else mentioned in the Omni thread that it worked. This thread is about Lineage, but that should be clarified, or clearer.