Database Develop

Stuck in boot up screen

ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks

JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?

It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP

JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk

Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks

bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.

Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.

bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!

Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?

bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk

UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.

[RECOVERY][X704F][OFFICIAL] TWRP 3.3.X for Lenovo Tab4 10 Plus

Official Downloads
https://twrp.me/lenovo/lenovo_X704F.html
Unofficial Downloads
https://www.androidfilehost.com/?w=files&flid=295687
Changelog for unofficial builds
twrp-3.3.1-0-X704F-20190604-codeworkx.img
- Updated to twrp 3.3.1
- Updated prebuilt kernel
- Removed lenovocust from backup
twrp-3.3.0-0-X704F-20190523-codeworkx.img
- initial build
Sources
Device tree: https://github.com/Teamwin/android_device_lenovo_X704F
Kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953

I've seen you are working with yener90 for this device. His TWRP is valid for F, L and few other variants.
Are you able to let us know if yours is the same? Or still testing and too early to know?
Thank you (I follow you in the OnePlus 5 project too).

Flowah123 said:
I've seen you are working with yener90 for this device. His TWRP is valid for F, L and few other variants.
Are you able to let us know if yours is the same? Or still testing and too early to know?
Thank you (I follow you in the OnePlus 5 project too).
Click to expand...
Click to collapse
That seems to be the case
"TARGET_OTA_ASSERT_DEVICE := TB-X704A,TB-X704F,TB-X704L,TBX704,tb_x704a,tb_x704f,tb_x704l"
(https://github.com/codeworkx/android_device_lenovo_X704F/blob/android-9.0/BoardConfig.mk)

There's official support now.
https://twrp.me/lenovo/lenovo_X704F.html

twrp-3.3.1-0-X704F.img verified working on a new TB-X704V. Everything seems to be working.
---------- Post added at 19:36 ---------- Previous post was at 19:04 ----------
Maybe I spoke too soon.
I tried installing Yener90's Lineage OS 16 image only my TB-X704V device and it failed to boot. That's fine, but then I tried to restore the OEM image that I had backed up previously. Unfortunately, I am not able to get back to a booting system.

black.kahder said:
twrp-3.3.1-0-X704F.img verified working on a new TB-X704V. Everything seems to be working.
---------- Post added at 19:36 ---------- Previous post was at 19:04 ----------
Maybe I spoke too soon.
I tried installing Yener90's Lineage OS 16 image only my TB-X704V device and it failed to boot. That's fine, but then I tried to restore the OEM image that I had backed up previously. Unfortunately, I am not able to get back to a booting system.
Click to expand...
Click to collapse
Look at the other thread. 3.3.0 works as expected. Use the old twrp for my current ROM or wait for the next update, which will support 3.3.0

I don't have experience customizing TWRP images for specific devices, so let me apologize in advance for my n00b questions...
How similar are the x704f and x705f tablets? I'm wondering if it might be possible to use an x704f TWRP image on an x705f. Lenovo recently released a stock ROM for Pie on the x705f. Now I'm finally able to unlock the bootloader. The previous stock ROM would not respond to fastboot oem unlock commands. I was then able to fastboot flash a bootloader image pre patched with Magisk so now the tab is rooted and happy. However, I still feel insecure without TWRP as it seems to be a key tool that I use for emergency ADB access, flashing, and making nandroid backups. How big of a project do you think it would be to make a customized image for the x705f? Do you think that is something where I would have to start from scratch? Or could the x704f image be used as a template that I could easily modify with information specific to the x705f?
Thanks for your time. I truly appreciate any help or advice you can give me on this.
Chaser

on my tb-x704f twrp on starts in landscape orientation. the last version i used was 3.2.3 and here i could use both orientations.
i also can't restore an backup because i can't write to the system partition. can this https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259 fix the problem?

gene2 said:
i also can't restore an backup because i can't write to the system partition. can this https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259 fix the problem?
Click to expand...
Click to collapse
No, it won't, it's a magisk module that allows R/W to the system partition after boot up to
facilitate some apps. that require it for full root access.

The problem was that i had no r/w to system partition. the restore works, but the system doesn't start. i have a boot loop with the lenovo logo. i have wiped dalvik, cache and system. after that i also made the normal wipe. then i restored the backup and after restart i have the boot loop. is there anything more to do? this was all i have to do on my other devices.

gene2 said:
The problem was that i had no r/w to system partition. the restore works, but the system doesn't start. i have a boot loop with the lenovo logo. i have wiped dalvik, cache and system. after that i also made the normal wipe. then i restored the backup and after restart i have the boot loop. is there anything more to do? this was all i have to do on my other devices.
Click to expand...
Click to collapse
Sounds like encryption is compromised, restore stock ROm, re-boot and start again.
See my other post to you here:-
https://forum.xda-developers.com/showpost.php?p=80273515&postcount=5

Hello, I have tried TWRP for TB-X704F on TB-X704A, but though my bootloader is unlocked, I have the latest SDK tools, and fastboot flash recovery recovery.img seems to take, nothing I do causes the device to boot into TWRP. I cannot sideload lineagos using stock recovery, and so for now I seem to be stuck. Any suggestions? I'd like to move past Android 7.1 for a more secure OS.

I've had the EXACT same problem with a TB-X704A. I've been waiting for someone else to say so. I'm sorry I don't have a solution but I'm hoping someone more knowledgeable then me sees our problem. Thanks to everyone, especially codeworkx who does this stuff!

Mddaddy said:
Hello, I have tried TWRP for TB-X704F on TB-X704A, but though my bootloader is unlocked, I have the latest SDK tools, and fastboot flash recovery recovery.img seems to take, nothing I do causes the device to boot into TWRP. I cannot sideload lineagos using stock recovery, and so for now I seem to be stuck. Any suggestions? I'd like to move past Android 7.1 for a more secure OS.
Click to expand...
Click to collapse
You have to reboot to recovery manually not via fastboot. Unplug from pc and hold power and volume up it should boot into twrp this way cus f version should work
---------- Post added at 04:02 AM ---------- Previous post was at 03:55 AM ----------
kirknado18 said:
You have to reboot to recovery manually not via fastboot. Unplug from pc and hold power and volume up it should boot into twrp this way cus f version should work
Click to expand...
Click to collapse
Twrp for tb x704f should work on all 704 versions but you have to boot into recovery manually not through adb fastboot it wont boot up that way for some reason. Let me know if this solves the problem.

I wanted to update from LineageOS 16 to LineageOS 17. Instructions there say to upgrade to latest TWRP (https://forum.xda-developers.com/th...m-lineageos-17-0-lenovo-tab4-10-plus-t4016705). I downloaded the unofficial twrp-3.3.1-0-X704F-20190604-codeworkx.img, flashed using adb, but when trying to go into recovery mode - will not go into recovery. Tries, then reboots again, and goes into LineageOS 16.
Downloaded the "official" version form (https://dl.twrp.me/X704F/), version twrp-3.4.0-0-X704F.img, again flashed using adb - again same results. Cannot get into recovery mode, boots twice and goes back into LineageOS 16.
So - something didn't go quite right - how do I get into recovery mode?

tundrwd said:
I wanted to update from LineageOS 16 to LineageOS 17. Instructions there say to upgrade to latest TWRP (https://forum.xda-developers.com/th...lineageos-17-0-lenovo-tab4-10-plus-t4016705). I downloaded the unofficial twrp-3.3.1-0-X704F-20190604-codeworkx.img, flashed using adb, but when trying to go into recovery mode - will not go into recovery. Tries, then reboots again, and goes into LineageOS 16.
Downloaded the "official" version form (https://dl.twrp.me/X704F/), version twrp-3.4.0-0-X704F.img, again flashed using adb - again same results. Cannot get into recovery mode, boots twice and goes back into LineageOS 16.
So - something didn't go quite right - how do I get into recovery mode?
Click to expand...
Click to collapse
Unplug from USB. Hold power and volume up buttons until the bootloader loads. Use the volume rocker to select "Recovery mode". Press power button to confirm.

jfaheyfan said:
Unplug from USB. Hold power and volume up buttons until the bootloader loads. Use the volume rocker to select "Recovery mode". Press power button to confirm.
Click to expand...
Click to collapse
I'm aware of how to get into recovery - it WON'T go into recovery. Starts up, the Moto screen flashes, it reboots, Moto screen again, then loads LineageOS. So I simply cannot get into recovery once selecting "Recovery Mode".

tundrwd said:
I'm aware of how to get into recovery - it WON'T go into recovery. Starts up, the Moto screen flashes, it reboots, Moto screen again, then loads LineageOS. So I simply cannot get into recovery once selecting "Recovery Mode".
Click to expand...
Click to collapse
What model is your tablet?

I have an A model and an F model. I've used the same TWRP on both the A and F. This particular instance is just the A model - TBX-704A

tundrwd said:
I have an A model and an F model. I've used the same TWRP on both the A and F. This particular instance is just the A model - TBX-704A
Click to expand...
Click to collapse
You're not the first:
https://forum.xda-developers.com/showpost.php?p=81254945&postcount=12
https://forum.xda-developers.com/showpost.php?p=82183753&postcount=13
Not sure of the significance, but "Moto" doesn't appear in the boot sequence of my TB-X704N (changed to TB-X704L after I installed LOS 17.1). I get "Lenovo" in an orange rectangle.
My next step would be to try https://dl.twrp.me/X704F/twrp-3.3.1-0-X704F.img . Better yet would be to hear from someone who's installed LOS 17.1 on an "A" model.
---------- Post added at 08:03 PM ---------- Previous post was at 07:42 PM ----------
I installed TWRP 3.4.0 on my TB-X704N (Chinese Tab 4 10+ with 4G) three weeks ago. I went on to install LOS 17.1 (https://forum.xda-developers.com/th...7-0-lenovo-tab4-10-plus-t4016705/post81141501). Everything went well just by following instructions. Thank you, codeworkx!

How I went from T-mobile 9.5.5 to International 9.5.3 Step by Step

These are just the steps I took and not my files and all credit goes to everyone except me.
You need ADB installed on your PC, this guide is assuming you have ADB up and running and know how to flash TWRP or other things to other phones. I don't have time to list all that.
You take full responsibility if something goes wrong.
I used a USB OTG because of TWRP decryption issues.
To start you need to be Sim unlocked from T-Mobile and received your unlock token from OnePlus, once that's done unlock your bootloader.
The files you will need are:
9.5.3 OTA full zip found here: https://forum.xda-developers.com/showpost.php?p=79545506&postcount=3
TWRP found here, I did not end up using the installer: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 I always rename it to twrp.img so it's easier/shorter to type in cdm later.
Transfer the 9.5.3 OTA zip to your USB OTG
Once your bootloader is unlocked you will need to boot the OS and enable developer options and USB debubbing,
From command prompt (CMD) on your PC type "adb reboot bootloader"
Once the bootloader loadds type "fastboot getvar current-slot" this will tell you which slot is currently active.
Then change to the inactive slot by typing "fastboot --set-active=a or b" so if your active slot was a then it would look like this "fastboot --set-active=b"
Now type either "fastboot flash boot_a twrp.img" or "fastboot flash boot_b twrp.img" based on which your inactive slot is. Thanks @twinnfamous
Once done TWRP should boot. Once in TWRP unplug from your PC and plug in your USB OTA swipe to allow modifications
Select install
Select storage from bottom
Select USB
Select the 9.5.3 OTA file you saved on your USB OTG, let it run (takes a few minutes) once done DO NOT reboot.
I did have a few errors but it was fine for me
Select the home button, once in the TWRP home screen select reboot and switch slots then back to TWRP home screen.
Select install
Select storage from bottom
Select USB
Select the 9.5.3 OTA file you saved on your USB OTG, let it run (takes a few minutes)
I did have a few errors but it was fine for me
Now you have 9.5.3 installed on both slots, reboot
At this point my phone boot looped back to stock recovery (TWRP was replaced, expected) where I selected English - Wipe data and cache - Erase everything (Music, pics, etc) once done my phone booted into International 9.5.3 OOS.
Again I take no credit for this I'm only posting the steps I took.
Thanks and credit goes to:
@twinnfamous for posting the steps he used and what I followed and this is based on.
@mauronofrio for the TWRP I used

What is the reason for flashing it to both slots? Does TWRP need to be installed or is it just used for initial install and then OnePlus's recovery will be used?

I'll just sit here and wait till the MSM Tool comes out!

TechOut said:
What is the reason for flashing it to both slots? Does TWRP need to be installed or is it just used for initial install and then OnePlus's recovery will be used?
Click to expand...
Click to collapse
it appears he just used it for booting, TWRP is not mandatory for an OS to operate, its just an option. He is flashing to both slots b/c if you get updates u won't get the T-MO update U will get the Global Updates. So when the update comes out it is going to install on the inactive slot so it will overwrite the Global instead of the T-Mo which could cause problems. So overall u want Global on both Slots.

So something weird when I was trying yesterday and not sure if someone came across that.
After I flashed oos rooted and was working just fine, while I was messing with substratum and magisk, the phone would boot, lose TMobile signal, and show the two empty simcards and won't get data.
I am finally back on 9.5.3 running just fine rooted but not sure what that has happened.

Bradl79 said:
it appears he just used it for booting, TWRP is not mandatory for an OS to operate, its just an option. He is flashing to both slots b/c if you get updates u won't get the T-MO update U will get the Global Updates. So when the update comes out it is going to install on the inactive slot so it will overwrite the Global instead of the T-Mo which could cause problems. So overall u want Global on both Slots.
Click to expand...
Click to collapse
Slots b/c? What phone are you using. it's a/b!!

se7ensde said:
Slots b/c? What phone are you using. it's a/b!!
Click to expand...
Click to collapse
"b/c" is a way to abbreviate "because"

se7ensde said:
Slots b/c? What phone are you using. it's a/b!!
Click to expand...
Click to collapse
lol its was short for because lol not the slots

What is the reason for doing this exactly? What benefits are there and specifically what are you hoping to accomplish ? I want to know because I also have the tmobile version.

TechOut said:
What is the reason for flashing it to both slots? Does TWRP need to be installed or is it just used for initial install and then OnePlus's recovery will be used?
Click to expand...
Click to collapse
If you are coming from T-Mobile software and don't flash to both slots you will end up in Qualcomm crash dump error. And not be able to boot

Spewed said:
What is the reason for doing this exactly? What benefits are there and specifically what are you hoping to accomplish ? I want to know because I also have the tmobile version.
Click to expand...
Click to collapse
When updates come out there is no waiting for them. You download from the OnePlus site and do a local upgrade.
Also the ROMs that are based on Magisk modules don't work on T-Mobile software.

matteosaeed said:
So something weird when I was trying yesterday and not sure if someone came across that.
After I flashed oos rooted and was working just fine, while I was messing with substratum and magisk, the phone would boot, lose TMobile signal, and show the two empty simcards and won't get data.
I am finally back on 9.5.3 running just fine rooted but not sure what that has happened.
Click to expand...
Click to collapse
What did you do to get back? I'm on international by another method and have this issue.

Beachbum2049 said:
What did you do to get back? I'm on international by another method and have this issue.
Click to expand...
Click to collapse
I tried a bunch of things, my highlight was the following
flashed twrp on slot A and B using "fastboot flash boot twrp.img"
Then downloaded the oxygen os OS 9.5.3GM21AA
https://support.oneplus.com/app/answers/detail/a_id/4312
Flashed that via twrp and my OTG usb. Regardless of decryption and data, all good.
Then, went to the oxygen os recovery "it flashes itself after you flash the oxygen os firmware instead of twrp" and erased everything and started fresh.
ALSO I am on this one now and it is working fine, and flashed via fastboot. Make sure you know your slots or pay attention to what happens.
" 9.5.4-GM21AA-OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3-FASTBOOT.zip"
https://androidfilehost.com/?w=files&flid=294300
to find out which slot you're in
fastboot getvar current-slot
to change slots
fastboot --set-active=a
or
fastboot --set-active=b
then run to verify.
fastboot getvar current-slot
---------- Post added at 07:18 AM ---------- Previous post was at 07:18 AM ----------
Also, stay away from the firmware with the E in them "assume they are European and by default looks for the 2 sims, could be fixed in the future". happened to me when I was in 9.5.5
---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------
Also to add after doing the 9.5.4 via fastboot, i flashed the magisk zip no problem. I am even on renovate ice with no problem on the 9.5.4 and flash magisk zip no problem.
https://forum.xda-developers.com/on...vate-ice-oxygenos-tweaks-stables-svn-t3934356
---------- Post added at 07:32 AM ---------- Previous post was at 07:20 AM ----------
Also,
my wifi was broken and flashed skydragon kernel and that fixed it.

matteosaeed said:
I tried a bunch of things, my highlight was the following
to change slots
fastboot --set-active=a
or
fastboot --set-active=b
Click to expand...
Click to collapse
This is where I made a mistake. Thank you for posting this!

Beachbum2049 said:
This is where I made a mistake. Thank you for posting this!
Click to expand...
Click to collapse
UW, let me know if you need more help. It is a little tricky. I believe that I am on Slot A and all working fine. It is nice having twrp to be able to change slots if for some reason I ended up on B.

matteosaeed said:
UW, let me know if you need more help. It is a little tricky. I believe that I am on Slot A and all working fine. It is nice having twrp to be able to change slots if for some reason I ended up on B.
Click to expand...
Click to collapse
Does TWRP stay installed or does it go back to the OnePlus recovery after both slots are flashed

TechOut said:
What is the reason for flashing it to both slots? Does TWRP need to be installed or is it just used for initial install and then OnePlus's recovery will be used?
Click to expand...
Click to collapse
Yes.
You can only flash the active slot.
You need to have twrp installed on both slots.
You want both slots to be on the same OS.

TechOut said:
Does TWRP stay installed or does it go back to the OnePlus recovery after both slots are flashed
Click to expand...
Click to collapse
If you flash OOS via twrp, then you get OOS recovery, you need to fastboot flash boot twrp.img on both slots, then it sticks. I am using the decrypted version.

Will this work if you are on T-Mobile 9.5.6?

likecookies said:
Will this work if you are on T-Mobile 9.5.6?
Click to expand...
Click to collapse
I don't see why not as it replaces the entire OS.

TWRP reverts back to MI Recovery 3.0 every single time

So, I have a Global version Mi 9.
Since the Global Beta is now gone, I want to use Xiaomi.eu ROM.
I unlocked bootloader, I flash TWRP, then I even flash the Disable Force Encryption, but every single time I reboot, the recovery reverts back to MI Recovery 3.0.
What am I doing wrong ?

AFAIK, MIUI installs her own recovery after a reboot.

I always download ROM and enter TWRP to flash ROM !
Currently speaking, MI9 TWRP without the other TWRP mod, such as OrangeFox to ensure TWRP won't be replaced by Mi recovery after OTA updated.
I see a magisk app - "TWRP A/B Retention script" may be current solution to help you keep TWRP after OTA but it must be flashed again after OTA updated every time.
Ataemonus said:
So, I have a Global version Mi 9.
Since the Global Beta is now gone, I want to use Xiaomi.eu ROM.
I unlocked bootloader, I flash TWRP, then I even flash the Disable Force Encryption, but every single time I reboot, the recovery reverts back to MI Recovery 3.0.
What am I doing wrong ?
Click to expand...
Click to collapse

You do not understand.
TWRP is NOT replaced after OTA, it is replaced after rebooting, immediately, after flashing it, before I can even upload the .zip file with the custom ROM to install it.

Ataemonus said:
You do not understand.
TWRP is NOT replaced after OTA, it is replaced after rebooting, immediately, after flashing it, before I can even upload the .zip file with the custom ROM to install it.
Click to expand...
Click to collapse
After flashing twrp, are you using fastboot boot twrp? If so, you need instead to use buttons, not the fastboot commands. Flash twrp, then hold vol up and power together until the phone reboots and vibrates, then let go of power but keep holding vol up. That should make twrp stick

reg66 said:
After flashing twrp, are you using fastboot boot twrp? If so, you need instead to use buttons, not the fastboot commands. Flash twrp, then hold vol up and power together until the phone reboots and vibrates, then let go of power but keep holding vol up. That should make twrp stick
Click to expand...
Click to collapse
Exactly.
1) Boot into fastboot
2) fastboot flash recovery twrp.img
3) fastboot reboot (immediately after device reboot, in black screen, hold VOL+ button)
4) TWRP logo will appears

Yes, I can boot to TWRP, but one time only. I use the volume up button after flashing to enter TWRP.
I need to format the data partition, before I upload the .zip file, and after I format the data partition and I reboot the phone, no more TWRP, MI Recovery 3.0 again.
In the end, I managed to install the xiaomi.eu ROM, but only by pushing the file into the tmp folder and not rebooting after I format the data partition.
Strange how MIUI enforces their own recovery software over TWRP, I had no such issues with the Mi 6, two years ago.

Ataemonus said:
Yes, I can boot to TWRP, but one time only. I use the volume up button after flashing to enter TWRP.
I need to format the data partition, before I upload the .zip file, and after I format the data partition and I reboot the phone, no more TWRP, MI Recovery 3.0 again.
In the end, I managed to install the xiaomi.eu ROM, but only by pushing the file into the tmp folder and not rebooting after I format the data partition.
Strange how MIUI enforces their own recovery software over TWRP, I had no such issues with the Mi 6, two years ago.
Click to expand...
Click to collapse
Which twrp you using?

I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825

Ataemonus said:
I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
Click to expand...
Click to collapse
Yep, that one should deffo be fine, not sure why it's not sticking and you're having the issues, sorry bud

As I said, sorted in the end, now on Xiaomi.eu 9.8.1.
Must have been the latest MIUI beta 9.6.27 that was so ... aggressive with the recovery software

Ataemonus said:
I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
Click to expand...
Click to collapse
Install twrp twice in fastboot

having a similar problem, can't install TWRP, the fastboot flash works, no errors, but when I log in ON+VOL UP it comes always MI recovery

claudioita said:
having a similar problem, can't install TWRP, the fastboot flash works, no errors, but when I log in ON+VOL UP it comes always MI recovery
Click to expand...
Click to collapse
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.

sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
You used twrp for Mi9TPRO or mi 9?
Is your link correct?

claudioita said:
You used twrp for Mi9TPRO or mi 9?
Is your link correct?
Click to expand...
Click to collapse
I am using a Mi 9 (Cepheus), and the TWRP that I am using is from Mauronofrio, version 3.3.1-52. The post to that TWRP is here.

sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
no it does not work
---------- Post added at 09:15 PM ---------- Previous post was at 08:46 PM ----------
sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?

Bit late so not sure if the issue is still prevalent, but did you try flashing TWRP from within TWRP itself?
That's what I did, flashing TWRP within fastboot, then rebooting to enter TWRP (I use buttons for this), then moving the TWRP img to internal storage and use the install function within TWRP to flash the image.

[MAGISK] [BOOT] Pre rooted Boot.img for Oneplus 6T Android 10 Open Beta 1

Hi Guys
UPDATE 2: (2/11/2019) Boot img now patched to Magisk V20.1 and added Google Drive as a mirror
UPDATE: It has come to my attention that some users are having issues with this version, please note this is still in beta and root isn't fully supported yet, also please make sure your running the latest magisk manager (version 7.3.5 at the time of this update) BEFORE flashing the patched boot IMG, those currently having issues, try flashing the stock IMG provided and installing the latest magisk manager then flashing the patched IMG
here is a working magisk patched boot img for you guys wanting root on your new android 10 open beta 1 software.
PLEASE BE AWARE THIS DOESNT COME WITH TWRP, THIS MAY ALSO BREAK THE ORIGINAL STOCK RECOVERY, BY FLASHING THIS BOOT IMG, YOU TAKE FULL RESPONSIBILITY FOR YOUR DEVICE AND NEITHER I OR XDA WILL BE HELD RESPONSIBLE
this DOESNT contain TWRP but is just rooted with magisk v20.0
simply flash the provided file in fastboot with the following command
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
Please note this will ONLY work with the OnePlus 6T
i have also provided the stock android 10 boot img in case anything goes wrong
DOWNLOADS::
[CURRENT VERSION - Magisk V20.1]
Mega -> https://mega.nz/#!YI5BkICC!66fiUUdmg1EgGcTNExHZ52IoliVY4HBMBdwxErpI-co
Google Drive -> https://drive.google.com/file/d/1xyRPzsKh1kQXK0_RpdnesuR85vc6FvRf/view?usp=sharing
[OLD Versions]
[Magisk V20.0]
https://mega.nz/#!cQRFwA7b!R1yLz1ozFUTEOLXv-OREK-oF5YeUGN1PrWvSSh22vHw
Stock Boot img
https://mega.nz/#!1BAnRCoK!nu6UVAnR2yHnbaf54FEhc7U_3oEyP1q2BFMU0LK7XC4
Credits:
@oneplus for the phone and stock boot image
@topjohnwu for magisk and his boot image patcher

Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.

Do i need a computer for this ?

techlogik said:
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Click to expand...
Click to collapse
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img

charlie95113 said:
Do i need a computer for this ?
Click to expand...
Click to collapse
yes because fastboot command is needed, henced done using pc.

mywebslave said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I also used the payload extractor and took the stock boot.img and patched it with Magisk myself. Same issue. So obviously Magisk just doesn't suppor this phone yet and Devs need to work on it.
Thx

techlogik said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I tried patching the stock boot.img myself as well, it ends up being the exact same size as the TS for this method...same problem.
Thx
Click to expand...
Click to collapse
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.

mywebslave said:
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
Click to expand...
Click to collapse
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks

techlogik said:
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
Click to expand...
Click to collapse
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.

mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
So should we be using this instead?
Sent from my ONEPLUS A6013 using Tapatalk

mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine

zhenliang1102 said:
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
Click to expand...
Click to collapse
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot

when i flash the magisk_patched.img and my cellphone reboot my cellphone does not recognize my simcard and have no network, am back on the stock boot.img

cultofluna said:
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
Click to expand...
Click to collapse
I doubt this would work because the patched image is only 26mb while the stock boot image is 64mb. Someone mentioned this in the OB thread

Black screen after the update
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.

Hy, do you have proximity sensor problem after update?! Thanks...is anything i can do?

jack5225 said:
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Click to expand...
Click to collapse
Same happened to me
Phone boots to a Black screen
adb reboot bootloader -> works
fastboot flash boot boot.img -> works
Only Patched boot.img -> boots to black screen
Sent from my ONEPLUS A6010 using Tapatalk

Same for me. Softbrick and phone doesn't boot. It also encrypted my whole /data with diferent password i think and I had to wipe whole /data partition. System boots after wiping data storage but as soon as I install magisk it doesn't want to boot again. I guess I will wait for final image and TWRP support.

i couldnt flash it manually (via cmd), but all in one tool managed it well.
worked fine and quick,thank you

Crazy that some phones it is working and others it doesn't. Nothing we are doing wrong, OP has work to do still. I can imagine this official update to Q is going to cause a support fiasco...if you want to root that is. ROFL. All works fine with stock though upgrade. Understand it is Beta, but they claim a November official release
We are going to need some Dev help. Or going to need to sell this phone and upgrade to the 7t or Pro..haha