Help! PO6T stuck in fastboot mode after trying to flash TWRP - OnePlus 6T Questions & Answers

Hey everabody,
I tried to install TWRP on my OP6T, using the guide from lineage OS (https://wiki.lineageos.org/devices/fajita/install) but after the fifth Step in "Temporarily booting a custom recovery using fastboot", my device stuck into fastboot logo and after restarting the phone, i wasn´t able to reboot the OOS system or to get into TWRP, I could see only the warning, that the bootloader is unlocked or the fastboot mode. I tried several other guides to install TWRP on my phone, but the all lead to the same problem. I also tried to relock the bootloader to get rid of the warning screen, but that also didn´t work.
Than, I tried to flash stock ROM with the Tool All in one (https://forum.xda-developers.com/oneplus-6t/how-to/tool-tool-one-driversunlocktwrpfactory-t3860279) but I got an Error (something about personal data) now I am able to start the Phone, but it remains in the starting animation of OOS.
Now I just want my phone to work again, with OOS or Lineage OS. Please help me. Best reagards.
Update : phone restarts after flashing stock again, but play store does not download anything. I still want to get Lineage OS, twrp...

Wow... It's scary how wrong those instructions are. Those need to be changed. Don't follow those. They will not work for this device.
These instructions will help you get Lineage on your 6T if thats what you want to do. It's the same process LOS 17 or 16. Just make sure if you are doing LOS 16, start with OOS 9.0.17, if you are doing LOS 17, start with 10.3.2 (latest OOS). Don't mix Android 9 and 10. When booting TWRP from fastboot boot the correct TWRP img, Pie for Android 9, Q for Android 10. The installer works for either.
At this stage you will need to restore your phone. Replacing the boot partition would likely make it boot again. Some people have posted this. I would go this route if you need to get data off of it. If you don't care about data (hopefully you backed up already) I would use the fastboot ROM at this point to start over. OnePlus 6T Fastboot ROM thread.
Once you have that, install TWRP. Funk Wizard's guide's are always good for this stuff. It's basically boot the TWRP img from fastboot, then run the installer, reboot to recovery, install Magisk if running OOS (otherwise TWRP will be replaced on boot). Magisk Link
Any questions ask.

Thank you very much
OhioYJ said:
Wow... It's scary how wrong those instructions are. Those need to be changed. Don't follow those. They will not work for this device.
These instructions will help you get Lineage on your 6T if thats what you want to do. It's the same process LOS 17 or 16. Just make sure if you are doing LOS 16, start with OOS 9.0.17, if you are doing LOS 17, start with 10.3.2 (latest OOS). Don't mix Android 9 and 10. When booting TWRP from fastboot boot the correct TWRP img, Pie for Android 9, Q for Android 10. The installer works for either.
At this stage you will need to restore your phone. Replacing the boot partition would likely make it boot again. Some people have posted this. I would go this route if you need to get data off of it. If you don't care about data (hopefully you backed up already) I would use the fastboot ROM at this point to start over. OnePlus 6T Fastboot ROM thread.
Once you have that, install TWRP. Funk Wizard's guide's are always good for this stuff. It's basically boot the TWRP img from fastboot, then run the installer, reboot to recovery, install Magisk if running OOS (otherwise TWRP will be replaced on boot). Magisk Link
Any questions ask.
Click to expand...
Click to collapse
Dear OhioYJ, thank you very much.
Before starting the flashing process, I want to ask a few questions.
1. While running the adb& fastboot setup, the interface (the blue one) said that 0 files were copied. In a YT video I saw the same programm, but 4 files were copied in the video. Will adb and fastboot be disturbed by that?
2. after rebooting the phone (and editing my first post), I made a factory reset in the setting of OOS. Does this change anything?
3. in Funk Wizard´s source for downloading the TWRP image (official TWRP site) i can find only a few versions of the img and the Zip, but there are no specifications if they are made for Pie or Q, as OhioYJ mentioned in his answer. Is there any ploblem?
4. for installing Magisk, I visited the Thread and downloaded the latest stable version. Is that correct (no specific version for the device or something, I just want to make sure not to mix the whole thing up again)
thank you for your help

MedusaGnom said:
1. While running the adb& fastboot setup, the interface (the blue one) said that 0 files were copied. In a YT video I saw the same programm, but 4 files were copied in the video.
Click to expand...
Click to collapse
As long as the files are copied, I guess it doesn't matter. You can see the image below I did as an example just now for this post, but I'm used to a count as well. I use Linux though. As long as the files move, don't worry about it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MedusaGnom said:
2. after rebooting the phone (and editing my first post), I made a factory reset in the setting of OOS. Does this change anything?
Click to expand...
Click to collapse
No. In fact when going between AOSP, like LOS, and OOS you'll have to use OOSs recovery to to do a factory reset to get the phone to boot.
MedusaGnom said:
3. in Funk Wizard´s source for downloading the TWRP image (official TWRP site) i can find only a few versions of the img and the Zip, but there are no specifications if they are made for Pie or Q, as OhioYJ mentioned in his answer. Is there any ploblem?
Click to expand...
Click to collapse
Glad you asked. Don't use the official version. It's out of date and will cause problems. This is the official maintainers thread. Download the main versions there. The install guide talks about installing to recover ramdisk, which you can do, but it's still perfectly fine to boot the image, and run the installer like normal. Using the installer is what I always do as it's easier.
MedusaGnom said:
4. for installing Magisk, I visited the Thread and downloaded the latest stable version. Is that correct (no specific version for the device or something, I just want to make sure not to mix the whole thing up again)
Click to expand...
Click to collapse
You are correct. 20.3 is the latest stable version. That's all you need. 20.3 will also install Magisk Manager 7.5.1 the latest version of the Manager as well so you don't even need to download that. I will recommend two additional things:
MagiskHide Props Config
UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip (In the first post, required for the MagiskHide Props to work)
MagiskHide Props Config will make it so you pass safetynet and still come up certified in the play store. You will need a terminal emulator to activate the props module. You can use anyone you prefer, I personally use this one.

I need an advice
OhioYJ said:
As long as the files are copied, I guess it doesn't matter. You can see the image below I did as an example just now for this post, but I'm used to a count as well. I use Linux though. As long as the files move, don't worry about it.
No. In fact when going between AOSP, like LOS, and OOS you'll have to use OOSs recovery to to do a factory reset to get the phone to boot.
Glad you asked. Don't use the official version. It's out of date and will cause problems. This is the official maintainers thread. Download the main versions there. The install guide talks about installing to recover ramdisk, which you can do, but it's still perfectly fine to boot the image, and run the installer like normal. Using the installer is what I always do as it's easier.
You are correct. 20.3 is the latest stable version. That's all you need. 20.3 will also install Magisk Manager 7.5.1 the latest version of the Manager as well so you don't even need to download that. I will recommend two additional things:
MagiskHide Props Config
UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip (In the first post, required for the MagiskHide Props to work)
MagiskHide Props Config will make it so you pass safetynet and still come up certified in the play store. You will need a terminal emulator to activate the props module. You can use anyone you prefer, I personally use this one.
Click to expand...
Click to collapse
Dear OhioYJ,
thank you for your help.
Right now i´m looking for the files you recommended in your fourth answer, but i can´t find MagiskHide Props Config. (could you give me a download link?)
Since my device decided to work again and even the Playstore started downloading, I am not sure if I want to risk new problems , than´s why I need an advice: is Lineage OS worth the risk? What could go wrong and is there a possibility to brick the phone irretrievable?
Is there a way just to get twrp and Lineage without rooting the device permanently, installing magisk etc? I need to use some banking apps, so i would have to unroot the phone after installing Lineage.
Is it dangerous to lock the bootloader again?
I´m sorry for my questions, but i do not have much experiece with this stuff, I only installed Lineage OS on the oneplus 1 and 2, what was very easy. Thank you very much.

MedusaGnom said:
Right now i´m looking for the files you recommended in your fourth answer, but i can´t find MagiskHide Props Config. (could you give me a download link?)
Click to expand...
Click to collapse
It's at the bottom of his first post. It's attached to the post.
MedusaGnom said:
wrong and is there a possibility to brick the phone irretrievable?
Click to expand...
Click to collapse
Highly unlikely, but anything is possible I guess. With OnePlus devices you have the MSMTool, which while I've frequently on here said should be a last resort, works very well. This will work without recovery or fastboot. While you have a working phone though, make sure you use FunkWizard's guide to backup your modem. <-- This is key if you are going to play with your phone, and install ROMs and such. Odds are you are never going to need them, but its the one unique thing to your device and it will save you if you ever happen to actually mess that up. Back these up some where safe (not on the phone).
MedusaGnom said:
than´s why I need an advice: is Lineage OS worth the risk?
Click to expand...
Click to collapse
Everyone must form their own opinion, tolerance level. The OS is very stable. Personally I don't own or buy a device that doesn't have LOS support (Before LOS it was CM). I don't even give a device to my son that doesn't have LOS on it. It gives me much more control over my privacy, data, and information. Even my battery life has been great, typically averaging 7-8 hours of SOT over 48 hours.
MedusaGnom said:
Is there a way just to get twrp and Lineage without rooting the device permanently, installing magisk etc? I need to use some banking apps, so i would have to unroot the phone after installing Lineage.
Click to expand...
Click to collapse
You don't have to root to have Lineage. Depends on the banking app, but some won't work without hiding the fact your bootloader is unlocked anyways. So you may not be able to run your app just running Lineage unrooted anyways. Only one way to find out I guess. I generally have as few apps as possible. I do know the few times I've used my banking app, it's worked with Magisk and that Module I've linked to above.
MedusaGnom said:
Is it dangerous to lock the bootloader again?
Click to expand...
Click to collapse
If you phone isn't completely stock, yes. If you are absolutely sure everything is stock, then it's not a problem. MSM Tool will put everything back as it was out of the box and relock the bootloader for you. Relocking / Unlocking the bootloader wipes the phone. Back everything up.
MedusaGnom said:
I only installed Lineage OS on the oneplus 1 and 2, what was very easy.
Click to expand...
Click to collapse
It's not that bad once you get it down, and get it converted over. It's just not like the "old days" where many devices were similar wipe caches, it was ok to wipe system, flash ROM, etc. I have a new tablet and you can't flash the those modules above in TWRP otherwise it refuses to boot again. Every device has something different. Once you're running LOS, updating is pretty straight forward:
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean instal)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.

my plan
OhioYJ said:
It's at the bottom of his first post. It's attached to the post.
Highly unlikely, but anything is possible I guess. With OnePlus devices you have the MSMTool, which while I've frequently on here said should be a last resort, works very well. This will work without recovery or fastboot. While you have a working phone though, make sure you use FunkWizard's guide to backup your modem. <-- This is key if you are going to play with your phone, and install ROMs and such. Odds are you are never going to need them, but its the one unique thing to your device and it will save you if you ever happen to actually mess that up. Back these up some where safe (not on the phone).
Everyone must form their own opinion, tolerance level. The OS is very stable. Personally I don't own or buy a device that doesn't have LOS support (Before LOS it was CM). I don't even give a device to my son that doesn't have LOS on it. It gives me much more control over my privacy, data, and information. Even my battery life has been great, typically averaging 7-8 hours of SOT over 48 hours.
You don't have to root to have Lineage. Depends on the banking app, but some won't work without hiding the fact your bootloader is unlocked anyways. So you may not be able to run your app just running Lineage unrooted anyways. Only one way to find out I guess. I generally have as few apps as possible. I do know the few times I've used my banking app, it's worked with Magisk and that Module I've linked to above.
If you phone isn't completely stock, yes. If you are absolutely sure everything is stock, then it's not a problem. MSM Tool will put everything back as it was out of the box and relock the bootloader for you. Relocking / Unlocking the bootloader wipes the phone. Back everything up.
It's not that bad once you get it down, and get it converted over. It's just not like the "old days" where many devices were similar wipe caches, it was ok to wipe system, flash ROM, etc. I have a new tablet and you can't flash the those modules above in TWRP otherwise it refuses to boot again. Every device has something different. Once you're running LOS, updating is pretty straight forward:
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean instal)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
Click to expand...
Click to collapse
Thank you very much!
I will write down what i´m going to do, would be great if you would give it a savety check.
Status:
- I unlocked the bootloader and enabled usb debugging and advanced reboot
-I installed the OP drivers and adb and fastboot on my pc
- I downloaded the the fajita twrp image and the twrp installer by mauronfrio, Magisk-v20.3 , UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip and MagiskHidePropsConf-v5.2.4 on my pc
- I downloaded the official Lineage Os 17 for fajita on my pc
next steps (assuming)
- download gapps
- set swipe to unlock the phone
- store the twrp image, installer, Magisk, magisk hide , UPDATE-Busybox.Installer.v1.31.1-ALL-signed.zip, gapps and the lineage zip on my internal storage
- boot into fastboot mode
- fastboot flash twrp image
- fastboot boot into recovery
- flash (now in twrp) twrp installer
- reboot recovery
- create nandroid backup
- flash magisk and the other 2 files relating to magisk
- gain root access
- reboot recovery
- wipe system partition
- flash lineage os 17
- flash twrp installer
- flash gapps
- create a backup
- reboot system
further targets: undo root
optional: clean install gapps
Thank you very much

OhioYJ said:
Wow... It's scary how wrong those instructions are. Those need to be changed. Don't follow those. They will not work for this device.
These instructions will help you get Lineage on your 6T if thats what you want to do. It's the same process LOS 17 or 16. Just make sure if you are doing LOS 16, start with OOS 9.0.17, if you are doing LOS 17, start with 10.3.2 (latest OOS). Don't mix Android 9 and 10. When booting TWRP from fastboot boot the correct TWRP img, Pie for Android 9, Q for Android 10. The installer works for either.
At this stage you will need to restore your phone. Replacing the boot partition would likely make it boot again. Some people have posted this. I would go this route if you need to get data off of it. If you don't care about data (hopefully you backed up already) I would use the fastboot ROM at this point to start over. OnePlus 6T Fastboot ROM thread.
Once you have that, install TWRP. Funk Wizard's guide's are always good for this stuff. It's basically boot the TWRP img from fastboot, then run the installer, reboot to recovery, install Magisk if running OOS (otherwise TWRP will be replaced on boot). Magisk Link
Any questions ask.
Click to expand...
Click to collapse
Thank you so much for covering this topic properly. I'm just now rejoining the Android world after having to use iPhone for over a year. Still had my 6t floating around, almost brand new and trying to quickly Google my way to getting TWRP and Lineage installed. The install instructions on the Lineage site are incredibly wrong. After going to that link and tweaking a bit it installed perfectly.

Related

Unable to root Redmi 7A - with MIUI 11.0.6

Got a second Redmi 7A, I'm 99.99% certain it came with *global* 10.2.5 PCMMIXM (it was what ordered, and saw it too, pretty certain), decided to let it upgrade OTA, it picked 11.0.6 OTA, and it came to:
MIUI Global 11.0.6 PCMEUXM (notice the EU there), which, I'm assuming from this url: https://mirom.ezbox.idv.tw/en/phone/pine/
to be this one:
Code:
Redmi 7A – EEA Stable ROM
Lstest V11.0.6.0.PCMEUXM(History)
MIUI 11
Android 9.0
Update at 2019-10-31 19:05:57
Changelog Expand Official Link
Recovery miui_PINEEEAGlobal_V11.0.6.0.PCMEUXM_bcc90ca1df_9.0.zip
Filesize 1.5G
MD5 bcc90ca1df89a4f3d8cc7b9705a70d83
which is a bit confusing, it says Global, but has "EU" in the name.. in any event, flashed TWRP as per:
https://xiaomifirmware.com/guides-and-tips/how-to-install-twrp-and-magisk-root-on-redmi-7a/
choose the LRTeam version:
Code:
2a3296af05267160cba2891bff446203 TWRP-3.3.1-1003-REDMI7A-CN-wzsx150.img
seemed newest, all is great, it boots into TWRP recovery.. Next, trying to get Magisk on it, got the manager apk installed 7.4 all fine, it says 20.1 needs to be installed so...
unzipped the boot.img from above zip file, it has this md5, this is original , unmodified boot.img:
Code:
036d1b6c5a99e9417f8d3e98d5718368 boot_Global_V1106PCMEUXM.img
following this guide: https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
Magisk successfully patched the boot.img on the same phone (running 11.0.6) and got this file:
Code:
dad219422c9302a460d4d2370adafb4f magisk_patched_Global_V1106PCMEUXM.img
transferred to PC, attempted to flash:
Code:
c:\XiaomiADB\bin>fastboot flash boot magisk_patched_Global_V1106PCMEUXM.img
target reported max download size of 535822336 bytes
sending 'boot' (14914 KB)...
OKAY [ 0.470s]
writing 'boot'...
OKAY [ 0.190s]
finished. total time: 0.665s
c:\XiaomiADB\bin>fastboot reboot
rebooting...
finished. total time: 0.003s
Phone boots fine, however, magisk still says it needs to be installed...
in developer's options, the USB debugging is enabled, and boot loader is definitely unlocked, it says on splash screen and the OEM Unlocking is greyed out and says "bootloader already unlocked".
Also, attempted to flash boot image from within TWRP, selecting the above boot.img file and selecting the boot partition, flashes OK, however, after normal reboot, as if nothing happened, phone boots, but magisk is NOT installed (no root).
Is there anything missing in these steps? does anyone have a correctly patched 11.0.6 image with magisk in it from an 7A phone?
Only thing that appears as an "error" are these family of cmds to unlock boot loader:
Code:
fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
however, i think that is normal/expected, since the bootloader is already unlocked.. able to flash twrp, etc.
Thanks so much for any ideas...
Stormy.
Forgot to mention that attempted to install Magisk 20.1 zip file downloaded by the app, from within TWRP, attached screenshot of how that looks like all seems okay but after reboot it still says that magisk needs to be installed... Very strange..
Appreciate any thoughts..
Stormy
noticed in above screenshot that it detected a patched boot image so decided to try installing the
v20.1 Magiskk zip file with the stock Boot, the install results in a screenshot, after reboot it still says that magisk has to be installed.!
also attaching screenshots showing the device is unlocked as well as USB debugging and OEM unlocking are all there.
Should this be posted in The magisk forum or is this something specific to the 7A? Or my steps?
How to debug further?
Attempted with the other TWRP image TWRP_v3.3.1-1_all.img, same results also reinstall the magisk manager 7.4 and same results....hmm.. maybe the OTA update took wrong ROM version. (EU and not pure Global)?...
Digging a bit more, found this pretty cool tool: https://www.xiaomitool.com/V2/latest called: "XiaoMiTool V2 ", which basically automated (almost) Everything !! Tried to do TWRP, as well as Magisk, it too followed similar steps I did, all automatically, rebooting, patching, etc. but outcome is still same, when phone boots normally, Magisk Manager says that Magisk 20.1 needs to be installed...
Then tried to flush miui_PINEGlobal_V11.0.4.0.PCMMIXM_674ed79f0b_9.0.zip using that tool, it said all is OK, phone rebooted , wiped all, but it still runs the EU version for some reason.. Now trying to find the path to "downgrade" from 11.0.6 to 11.0.4, or switch from EU to Global.. maybe that's the source of all issues, not sure what else to try
Reporting progress, to keep track of what was attempted. So, decided to WIPE all and start with 11.0.4 Global fresh, from TWRP, wiped everything, to the point it said "no OS installed, are you sure u want to reboot" it rebooted into fastboot, then downloaded the 11.0.4 Global .tgz and flashed, phone booted OK this time into 11.0.4 Flashed TWRP, and then attempted to flash Magisk via both routes, one by patching the boot.img from the .tgz and flashing, all using the Phone (to avoid any PC/driver/adb issues). The flashing worked fine, but upon reboot, Magisk Manager claimed that Magisk is not installed. Second try was to flash the stock boot.img, then flash magisk zip file, did that for v20.1, v19.4 and 19.3, each time from stock boot.img, and reboots to test, none of them showed that magisk is installed...
all this time, usb debugging is enabled despite most work done on the actual redmi 7A phone itself.
Then uninstalled magisk manager 7.4, and tried with 7.2, but that doesn't change much since any action there wants to update to v7.4..
next step will wipe again, and go for the Global 10.2.5... if that doesn't work then I really don't know what can be going on...
If anyone does have a 7A with MIUI 11 with a properly patched boot.img, would love to try it... all my patching attempted booted fine, but none showed that Magisk is installed... finding it hard to think it's a magisk bug, more likely some MIUI 11, lets see how 10 works out...
Stormy
OK, some success! so, wiped ALL again, to the point of no-OS installed; phone only boots into fastboot (brick), using flash_all.sh from 10.2.5 fastboot Global ROM flashed entire phone and it booted OK.
btw, not easy to find 10.2.5 now, as places already updated links to 11.0.x..
Once in 10.2.5, tried to patch Magisk in all possible ways (twrp or patching boot.img on phone the flashing from Windows10/PC) as also described in this thread few weeks ago:
https://forum.xda-developers.com/showpost.php?p=80498891&postcount=179
but it did NOT work, well, the procedure appeared OK, no errors and when booting, it says magisk needs to be installed.
The only thing that works is the provided boot global .img file [size 14.5 MB (15,269,888 bytes)], as soon as this one is flashed, via phone/twrp or PC, then the magisk is correctly detected.
Very mysterious, why only that boot.img is working on my 7A phones.. maybe there's an additional step, to "sign" or fix the boot.img before it can be flashed?
now took a full TWRP backup, and will try to move to 11.0.4 see if magisk is retained, and if not, if possible to re-gain it.. if not, then, will restore from TWRP backup.
Any thoughts welcomed..
Stormy.
Did not manage to get it working with MIUI 11 yet, so backed to MIUI 10.2.5.. all is fine there.
Noticed that TWRP did not "stick", flash but after normal boot, it came back to original recovery. I think this is b/c of Verify Boot in android Pie/9.. so I *think* what helped here is to flash a vbmeta.img from first post of this thread:
https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820
Even after flashing this, and even in 10.2.5, patching the STOCK 10.2.5 from the phone using Magisk 20.1 and installing using TWRP did not work, not sure if this is a bug in magisk or what, but only way to get root was using the provided boot.img as described above. I'll keep using 10.2.5 for now. feel free to add any ideas here , maybe one day will get more time and a spare phone to try MIUI 11
Stormy.
hey , I have the same problem. I noticed you mentioned 'sign', what should I sign what things? and how to sign?
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
depaul9999 said:
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
Click to expand...
Click to collapse
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible.
Click to expand...
Click to collapse
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
depaul9999 said:
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
Click to expand...
Click to collapse
I've read that the 16GB version of the Redmi 7A is possible to put a micro SD card and format it as internal storage and that was the reason I've bought it, although I'm not yet sure because I'm waiting to buy a microSD card, it's still on the way.
I want to root it because of privacy reasons and that's the only reason. For now I'm using a VPN to block 99% of the google and xiaomi apps, etc. to the internet this way I got some privacy. I have unlocked the phone too so I did uninstalled several apps from the system using the PC.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
Click to expand...
Click to collapse
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
stormy1777 said:
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
Click to expand...
Click to collapse
Well, if you say so... If you're right then I got the wrong Redmi 7A model. It came with the EU version of the miui.
I already knew the tutorial in the link you gave, but that seems very complicated and I do not really know what's going on there so it's better I do not try it. And if I followed that tutorial I would have to flash the phone again with the miui 10, because I have the 11 now. I already wasted many hours trying to root the phone and I had to flash the rom about 4 times because the phone became bricked. Anyway the tutorials I've followed were not the one in the link above and all the other ones I've tried did not work and yet they claim it does, specially using magisk only, without TWRP.
I'll wait for an easier method than the one you shared, if that will ever happen. For now I just use a VPN, it's the closest thing to root I have found, to deny system and apps permission to the internet.
Thank you
In case you're not aware, there are scripts to flash the entire phone automatically, I've done that 10's of times BEFORE putting the phone into "production" use, root was a _must-have_,phone's now heavily used, so can't toy with it much, unless forced to (see below), i may get another phone to play with, but not much TIME to justify it...
Was getting tired of typing:
Code:
:/ # pm list packages|grep xyz
followed by:
:/ # pm uninstall -k --user 0 com.google.android.apps.tachyon
Success
Decided to give some "highly-rated" app a try, it claims to be able to remove system apps: "System app remover (root needed)":
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_US
Took a full TWRP backup, installed, all seems great.. remove, goes to recycle bin, ok.. now, lets REBOOT..
Opps.. phones goes into FASTBOOT... OK!! that's what the backup is for.. go into TWRP, flush SYSTEM, CACHE, DATA, reboot, again, we're in Fastboot, and this time no RECOVERY boot is possible, just goes into FASTBOOT directly.. much like i've described in this thread:
https://forum.xda-developers.com/showpost.php?p=80509823&postcount=111
so, TWRP on phone doesn't help much, took the TWRP backup from SD Card to PC (since phone can only do fastboot at this point), thought it would be easy/possible to fastboot flash all the TWRP into the phone from PC, however, that is NOT simple, since TWRP breaks files, one must concatenate them before flashing..
I was not in the mood, nor did i think a huge change took place, it was just something silly that app did. hmm.. here, i can't exactly explain what took place, but a sequence of flashing of boot.img recovery.img and vbmeta.img all from STOCK and the TWRP backup, was "all it took" to recover the phone fully..
After about 30+ flashes and reboots it came to life much like the last boot, went into that APP again, tried to RESTORE the apps, it failed, and a reboot again, went into FASTBOOT! twrp was there, again, tried recovery, this time only SYSTEM, again, phone lost recovery, and went into, fastboot only... and.. again, sequence of flashing from fastboot, i can tell that vbmeta (Verify Boot) takes a *major* role in this version/device, if something is not right, it just reverts things or decides to go into fastboot.
I saw it work once, so was not going to give up and wipe/start fresh.. kept trying..
I think the app somehow made "direct" modifications to the system partition without proper interface, and thus ruined the "signature" or encryption, otherwise not sure how it could trash the phone so badly..
in any event, after long struggles, flashing the LATEST did _not_ work, it's almost as if the phone had to be taken back to original setting, let it boot into recovery, then reboot again, and flash things in steps, not all at once, at least based on this experience. I know it's silly, b/c in Android 6 I've restored/cloned phones all the time using TWRP directly from phone.. not sure, it does not work on my 7A's...
eventually, phone booted, with 10.2.5 magisk/boot.img (no root, since it did not recognize magisk), then fastboot flashed the canary boot.img, and got root.
anyways, point is, it was pretty ugly, and I'm not complaining, just saying this is pretty complicated stuff, it's a miracle that this even works
keep up the great work everyone, if i can help in any way, let me know...
All this is on Global phone, I don't have an EU/ROM/phone, so can't help u directly, but someone may have a root boot.img EU boot, that's really the key, and the vbmeta.img of course as for MIUI11? so what if that's what you have, it can be flashed, it's a matter of choice, flash to miui 10.2.5 and get root, or try to do it on MIUI11, or, let it be and use w/o root.. which was not an option for me
good luck.
Stormy.
btw, the magisk/patching boot.img did not work for me, and was reported in that same thread:
https://forum.xda-developers.com/showpost.php?p=80560039&postcount=206
MDV106 said that both EU and global boot.img were posted in that thread, and i agree i used one of them, not sure exactly which, but definitely it was the Global, not the EU. and i think it's not goot to mix up.. if u have an EU, stick with it, it might impact Wifi or similar "regional" things..
Same problem, but it works on mokee
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
boody shaban said:
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
Click to expand...
Click to collapse
Thanks for this data point, yeah, root was/is also possible with MIUI 10.2.5, I'm sure other ROMs can root pretty easily.. the "goal" of this thread is to somehow figure how to do it on MIUI 11 so we can take the security updates and still retain rootness
working root redmi 7a
Working root for Redmi 7a
thank you stormy1777 - it is your tutorial, I only put it together. It is the only tutorial that works
links unavailable due to site rules:
google for: ROM v10.2.5. global V10.2.5.0.PCMMIXM/pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global_efb78ff9c3.tgz
google for: patched boot v10.2.5. under: xiaomifirmware (dot) com how-to-install-twrp-and-magisk-root-on-redmi-7a
google for: TWRP: under: androidweblog(dot)com xiaomi-redmi-7a-root-install-twrp-recovery I took the version 3.3.1.-0
google for Magisk: Magisk-v20.1.zip
Install in fastboot mode and with Mi Flash Tool
flash: pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global
option: clean all
wait until the mobile phone is fully installed (will reboot automatically)
copy Magisk into the root directory on your phone
restart in fastboot mode (volume down + power button)
on PC:
rename twrp file to recovery.img
rename boot file to boot.img
copy boot.img and recovery.img on the PC in the directory, where adb drivers are
open power shell on the PC in the directory, where adb drivers are
type in the power shell window:
fastboot flash recovery recovery.img
Enter
then type in the power shell window
fastboot flash boot boot.img
Enter
then hold volume up + power button until it 2x starts and vibrates, then wait, it opens in TWRP
type install, find Magisk.zip in the phone root directory a flash
restart into system
done

Fresh 6T on Pie. Flashed Lineage 16 and TWRP; cannot get past encryption for GApps

Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Next Steps...
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
NoBodyUKnow said:
OK, finally getting back to this...
Click to expand...
Click to collapse
Your version of TWRP could be part of the problem. This is the thread for the official maintainer, use these builds of TWRP even though they say "unofficial." Q is for Android 10, Pie is for Android 9. For LOS 17, download the 3.3.1-32 versions. Remember you are booting the img files, the Q version, you use the same installer for both versions of Android.
To go to LOS 17 you need Android 10 on both slots. Doesn't matter how you get there. 10.3.1 is the latest version from OP, so there is technically a newer version than what you downloaded.
Fastboot ROM page.
You have a few options:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
- Use the fastboot ROM. Again as above this will require TWRP installation, etc.
- My least favorite, the MSMTool. My opinion, is the MSMTool should always be a last resort as it locks your bootloader. You can unlocking afterwards again, but if something goes wrong, it could be a bad thing. I just always try every other option before jumping to this one.
As for Gapps, I just use OpenGapps. At this point you don't even have to mess with their test or beta folders anymore. You can just select it from their homepage, and download Android 10 gapps. OpenGapps page, the 6T is Arm64, LOS17 is Android 10, I always use Nano
As for Magisk, yes 20.3. The uninstaller you don't really need as this will essentially be a clean install. The 20.3 zip will also install the Magisk Manager app.
Hopefully that clears some things up?
NoBodyUKnow said:
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
Click to expand...
Click to collapse
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
NoBodyUKnow said:
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
Click to expand...
Click to collapse
OhioYJ said:
Your version of TWRP could be part of the problem. This is the thread for the official maintainer, use these builds of TWRP even though they say "unofficial." Q is for Android 10, Pie is for Android 9. For LOS 17, download the 3.3.1-32 versions. Remember you are booting the img files, the Q version, you use the same installer for both versions of Android.
To go to LOS 17 you need Android 10 on both slots. Doesn't matter how you get there. 10.3.1 is the latest version from OP, so there is technically a newer version than what you downloaded.
Fastboot ROM page.
You have a few options:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
- Use the fastboot ROM. Again as above this will require TWRP installation, etc.
- My least favorite, the MSMTool. My opinion, is the MSMTool should always be a last resort as it locks your bootloader. You can unlocking afterwards again, but if something goes wrong, it could be a bad thing. I just always try every other option before jumping to this one.
As for Gapps, I just use OpenGapps. At this point you don't even have to mess with their test or beta folders anymore. You can just select it from their homepage, and download Android 10 gapps. OpenGapps page, the 6T is Arm64, LOS17 is Android 10, I always use Nano
As for Magisk, yes 20.3. The uninstaller you don't really need as this will essentially be a clean install. The 20.3 zip will also install the Magisk Manager app.
Hopefully that clears some things up?
Click to expand...
Click to collapse
It did clear some things up, thank you. However, I still end up at the Qualcomm CrashDump Screen of Death. this happens at the very end of the process, after the second load of LOS 17 and TWRP Installer, while rebooting to recovery from the TWRP .img. I'm going to list every step I take and all of the files I use. There are a couple of places where I'm not sure I'm doing the right thing, and/or the outcome of that step is not as expected.
1. Download all of files:
TWRP Q .img
TWRP Installer
OP OS 10.3.1 Fastboot ROM
lineage-17.1-20200223_133843-UNOFFICIAL-fajita.zip
First step is to flash Oxygen 10 and TWRP Recovery to both slots. I unpack the OOS Fastboot ROM zip on my laptop, boot to my 6t's bootloader and connect that to my laptop. After making sure ADB/Fastboot sees the device, I run "flash-all.bat" by clicking on it. This seems to load OOS just fine. The phone boots to OOS and I turn the phone off.
(I've done all of this several times and there are variants: I've tried becoming a developer and turning on the advanced boot options in OOS 10, but I don't think that matters, as long as I can get back to the bootloader or recovery. Let me know if that is incorrect).
At this point, your instructions say
"reboot to recovery, flash the OTA zip again."
I've tried moving the OOS fastboot zip file to my phone and flashing from TWRP, but that doesn't work. I get an error complaining of wrong format. It seems to me, a Fastboot ROM can only be flashed from adb/flashboot. Is that correct?
Therefore, I have been going back to the bootloader and re-flashing OOS 10 from adb fastboot again. After this step, contrary to your guidance above, the phone does indeed boot directly to OOS.... A loooong, what seems to be initial boot. I then turn off the phone.
I reboot to recovery again - and it is now the stock recovery - so I follow your guidance to factory reset from there. It does boot into OOS, and it is another looonnng boot. I then turn off the phone, return to the bootloader, flash the TWRP .img, install the TWRP installer and move on to the LOS 17 process linked to above.
Though I'm not sure it's necessary, I follow these steps from the beginning of he process:
Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
Everything seems to work well, so I follow these steps, all from TWRP:
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
I do all of the steps below, with no problems:
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
Just a note at this point, to highlight that this is done from TWRP, as opposed to using adb fastboot as with OOS10. This is what I've done with ROM's in the past; the fastboot ROM thing is new to me.
Next, I
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery
This is where things go bad. In this reboot to recovery, the TWRP splash screen sits there for a long time, and then the Qualcomm CrashDump Screen of Death (QCDSoD) appears. If I hold the power button down for long time, the QCDSoD disappears and the phone reboots and starts to load LOS. Then, it switches to TWRP splash screen, and as before, end with the QCCDSoD.
I've been through this entire process maybe three times. Always the same outcome (you know what they say, about doing the same things and expecting different results...)
I did note, that on the OS Fastboot ROM page, there was some discussion of "Branded" phones, specifically T-Mobile phones. When I first got this phone, after loading TWRP, I swapped active slots. On the new, active slot, I booted the phone, and it was to a T-Mobile ROM. Not sure if that plays any part in all of this.
Appreciate your hanging with me. I'm going to rest my fingers
Is this a TMobile 6T?
NoBodyUKnow said:
OK, finally getting back to this...
I currently have LOS 16 and twrp fajita 3.2.3-2 onboard, as well as Magisk Manager (but not magisk - shows red question mark and "magisk not installed" in Magisk mgr.).
I want to go to LOS 17, load gapps and root to remove redundant apps.
First, I need to I need to get back to stock ROM before anything else, right? I've downloaded 10.0.1-OnePlus6TOxygen_34_OTA_041_all_1911142208_af338-FASTBOOT.zip
I'll also need LOS 17.X, correct? I have this: lineage-17.1-20200104_020517-UNOFFICIAL-fajita.zip
I'll need the Q version of TWRP, right? Still looking for that. Is this version of TWRP specific to the OP 6T, or specific to Android 10? Other?
I'll need the ARM64 , Android 10 version of mindthegapps (mindthegaps supports A/B architecture, right?). Still looking for that. I've found "GApps", but not "mindthegapps". There's also "bitgapps". Should I consider this?
I'll need magisk manager. magisk uninstaller and magisk, correct? I have MagiskManager-v7.5.1.apk, Magisk-v20.3.zip and Magisk-uninstaller-20200110.zip. Not sure if these are the right ones..
I think the main thing I need help with is getting back to the stock ROM. Guessing that would be OOS10. Once I get there, there are lots of instructions around on how to get to LOS 17.
Thank you!!
Click to expand...
Click to collapse
OhioYJ said:
It's like that because you didn't format data. Also you can't have OOS on one slot, and an AOSP ROM on another slot.
Here's the LOS install instructions I've been posting / using for clean / first installs.
Note the part in the begining about using 9.0.17 or 10.3.1 depending on which version of LOS you are using. Don't mix Android 10 and 9. Any questions ask.
Also note when Magisk is flashed those instructions. You're close, just missed a couple steps.
Click to expand...
Click to collapse
NoBodyUKnow said:
Hello All,
I picked up a OP 6T from Amazon and would like to run Lineage 16.0 and load GApps, along with a number of other apps. I have TWRP Fajita (bluespark) installed and can boot to it. I also have Lineage 16 flashed as my ROM on Slot A, to which I can also successfully boot. I have Mind the GApps .zip ARM64 version on internal storage root.
Prior to flashing Lineage, I also loaded Magisk, which is still there as an app.
In trying to load MtheGApps, I cannot get past encryption in TWRP. TWRP prompts for a password, but I have no idea what that might be. I've read (somewhere) that the password is the pin I defined for my opening screen in Lineage, which I know. That does not work. I also have fingerprint enabled and have defined a print. The pin and finger get me into lineage without any trouble.
All of this is on slot A. Slot B seems to holds an older T-Mobile ROM, which I booted at some point. Not really interested in that, so eventually, I'll want to know what to do with that slot. I'll also want to root Lineage.
Maybe I should start from scratch? ( not sure how to get back there). Any guidance greatly appreciated!
Click to expand...
Click to collapse
OhioYJ said:
Is this a TMobile 6T?
Click to expand...
Click to collapse
After a little research, it appears that it is a T-Mobile variant: the A6013. And, well.... I guess this may be a clue...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing this is the source of my problem. Do you agree?
My research suggests the T-Mobile variant can be converted to "Global", but I'm wondering if it may just be more efficient to return this phone to Amazon with OOS 9 or 10 on it and buy the Global variant (A6010?)
NoBodyUKnow said:
I'm guessing this is the source of my problem. Do you agree?
My research suggests the T-Mobile variant can be converted to "Global", but I'm wondering if it may just be more efficient to return this phone to Amazon with OOS 9 or 10 on it and buy the Global variant (A6010?)
Click to expand...
Click to collapse
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
OhioYJ said:
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
Click to expand...
Click to collapse
Thanks! I like the 6T, so I guess I'm gonna get a Global. I'll get back to this, when I have that phone in-hand. Will slowly chug away on my Moto G6 until then. More to come...
Oh... Should I have any trouble putting an Oxygen 9 ROM ( or 10) on both slots without TWRP, before sending it back? Guess I'll need to re-lock the bootloader too.
NoBodyUKnow said:
Oh... Should I have any trouble putting an Oxygen 9 ROM ( or 10) on both slots without TWRP, before sending it back? Guess I'll need to re-lock the bootloader too.
Click to expand...
Click to collapse
You could always use a T-Mobile MSM Tool ?
Link
MSM Tools are usually my last resort as they relock the bootloader, but in this case, it's what you are after.
OhioYJ said:
Yeap, you have a TMobile 6T. A TMobile 6T is not a Global 6T, and even a "converted" TMobile 6T is not a Global 6T. They still require special instructions at points, and do different things. The instructions above will work perfect for a Global 6T. They (TMobile 6Ts) tend to be cheaper, but tend to have some gotchas with them.
Click to expand...
Click to collapse
NoBodyUKnow said:
Thanks! I like the 6T, so I guess I'm gonna get a Global. I'll get back to this, when I have that phone in-hand. Will slowly chug away on my Moto G6 until then. More to come...
Click to expand...
Click to collapse
OK... Back this this!
This is the what I ordered to replace the T-Mobile variant I had. It arrived yesterday. Is this the "global" model, or did I again purchase the wrong phone?
This phone is a dual sim, so it is definitely different from the one I had. Model number from System Info is A6010_41_200115.
Behavior is exactly as before. First, I'm loading the Android 10 version of the OP Oxygen Rom. After the second install of the OTA as advised below...
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
...rather than going directly to stock recovery, the phone DOES boot to OOS. To get to recovery, I go through the minimal necessary setup steps to access the settings, so I can activate developer mode, enable advanced reboot and enable USB debug. Then I reboot to recovery (stock), perform the wipe and reset. I then reboot to Fastboot and flash the TWRP .img using adb/fastboot on my PC. I then txfr the TWRP install .zip to root and install that. All of this SEEMS to go well, but again, there's that unexpected reboot to OOS as highlighted above.
Next, I move on to the LOS 17 load.
This goes well, until I complete the second load of TWRP Installer and reboot to recovery. When I execute that step, the TWRP splash screen appears and stays there for 30-45 seconds, and then turns to the QualComm CrashDump Mode Screen.
:crying:
I guess the first thing is to determine, If I have the correct phone ....
NoBodyUKnow said:
OK... Back this this!
This is the what I ordered to replace the T-Mobile variant I had. It arrived yesterday. Is this the "global" model, or did I again purchase the wrong phone?
This phone is a dual sim, so it is definitely different from the one I had. Model number from System Info is A6010_41_200115.
Behavior is exactly as before. First, I'm loading the Android 10 version of the OP Oxygen Rom. After the second install of the OTA as advised below...
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
...rather than going directly to stock recovery, the phone DOES boot to OOS. To get to recovery, I go through the minimal necessary setup steps to access the settings, so I can activate developer mode, enable advanced reboot and enable USB debug. Then I reboot to recovery (stock), perform the wipe and reset. I then reboot to Fastboot and flash the TWRP .img using adb/fastboot on my PC. I then txfr the TWRP install .zip to root and install that. All of this SEEMS to go well, but again, there's that unexpected reboot to OOS as highlighted above.
Next, I move on to the LOS 17 load.
This goes well, until I complete the second load of TWRP Installer and reboot to recovery. When I execute that step, the TWRP splash screen appears and stays there for 30-45 seconds, and then turns to the QualComm CrashDump Mode Screen.
:crying:
I guess the first thing is to determine, If I have the correct phone ....
Click to expand...
Click to collapse
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
DarthVader said:
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
Click to expand...
Click to collapse
He's got the China version this time, which I believe is minus a couple LTE bands (not a deal breaker necessarily, but not ideal). Does this change his install process since it would have originally had HOS on it?
Yes, but...
DarthVader said:
So if I get this right, you're trying to install LOS 17 on your OnePlus 6T which is running OOS 10? Also you have the international variant.
Click to expand...
Click to collapse
Yes, my goal is to have Lineage OS 17 (Android 10/Q) on a OnePlus 6T. Hopefully on the phone I have now, but on whatever 6T variant I need to get. I like the phone.
I tried before with a T-Mobile version of the A6013, and I could not get there. @OhioYJ offered some assistance and suggested the problem was the phone being a T-Mobile variant; that I needed a "Global" version. Therefore, I returned that phone and purchased an "International" A6010_41_200115. Is this the Global variant?
I've followed the processes detailed above on both phones and wound up at exactly the same place: The QUALCOMM CrashDump Mode screen. This happens after the second install of TWRP, when I reboot to Recovery.
In both cases, the phones came with OOS 9, and I'm updating to OOS10 via the Fastboot ROM before proceeding to LOS 17.
Is it possible to get to LOS 17 on the phone I have now?
Thanks!!!
OhioYJ said:
He's got the China version this time, which I believe is minus a couple LTE bands (not a deal breaker necessarily, but not ideal). Does this change his install process since it would have originally had HOS on it?
Click to expand...
Click to collapse
This would be the global variant, wouldn't it? An A6013 with both GSM and CDMA...?
Mine is an A6013, I checked the phone and original box. I bought mine straight from OnePlus. TMobile ones will only have a single IMEI. The "Real" 6T will be dual sim and have two separate, unique IMEI numbers.
NoBodyUKnow said:
This would be the global variant, wouldn't it? An A6013 with both GSM and CDMA...?
Click to expand...
Click to collapse
Do this. Download the latest OOS 10.3.2 from OnePlus's Website. As well as latest Unofficial TWRP Image and Installer. Grab the Q Image, not the Pie one. The latest TWRP version as of now is 3.3.1-32. Now Boot to TWRP. Flash the OOS ZIP File and then TWRP Installer. Reboot to Recovery and again flash the OOS ZIP and TWRP Installer. Once that's done, you can once again Reboot to Recovery. Now, flash the Latest LineageOS 17.1 ZIP file and TWRP Installer. Reboot to Recovery one last time and flash Gapps. After that Format Data and Reboot System. You should now hopefully boot into Android.
DarthVader said:
Do this. Download the latest OOS 10.3.2 from OnePlus's Website. As well as latest Unofficial TWRP Image and Installer. Grab the Q Image, not the Pie one. The latest TWRP version as of now is 3.3.1-32. Now Boot to TWRP. Flash the OOS ZIP File and then TWRP Installer. Reboot to Recovery and again flash the OOS ZIP and TWRP Installer. Once that's done, you can once again Reboot to Recovery. Now, flash the Latest LineageOS 17.1 ZIP file and TWRP Installer. Reboot to Recovery one last time and flash Gapps. After that Format Data and Reboot System. You should now hopefully boot into Android.
Click to expand...
Click to collapse
@OhioYJ
I did as you suggested. As with my first phone (a T-Mobile variant), when I perform the reboot to recovery after flashing LOS 17 and TWRP, the TWRP intro screen appears for a long time ( 30 seconds + ). When it finally disappears, the Qual. Crash Dump Screen appears. By holding the power button for about 10 seconds, the phone reboots to LOS. After booting, I can navigate within LOS, but a warning flashes for a few milliseconds, about every ten seconds. I was able to capture a screenshot of the warning from the video I just linked to:
This continues to occur: if I try to reboot to recovery, the TWRP screen appears, lingers and then changes to the Qual Crash Dump screen. At this point, when I hold the power button for about 10 seconds, the phone boots to LOS. When LOS is running, the warning continues to appear at regular intervals.
Thinking I may just go for another phone, preferably one that supports GSM and CDMA, but at least a US, non-T-mobile phone with all of the GSM Bands. They are a little pricey though.
Happy to try other things with this phone though, if it might help further understanding of these phones.
Looking for w Breakthrough...
@OhioYJ @DarthVader
Gentleman,
I hope this update finds you and your loved ones safe, in this scary time.
I am still trying to get LOS 17 on my OP 6T, and I Keep ending up at the same place.: Qualcomm CrashDump Screen. l'm using the fastboot ROM's, and using those does not completely align with this part of OhioYJ's instructions:
- You can also update using TWRP, and flashing the OTA full ZIP. Just be aware, you need to flash the OTA zip, flash the TWRP installer, reboot to recovery, flash the OTA zip again. Reboot. At this point the phone won't boot, it will just go to stock recovery, wipe data (factory reset), and it should boot up into OOS. Then boot your TWRP img, install TWRP, boot to recovery, start the LOS install I linked to above.
OhioYJ mentions "flashing the OTA Full .zip". The Fastboot ROM's have "OTA" in their labels and they are .zip files, but they will not flash in TWRP. They error out. They do run - and flash - from the bootloader, and this is what I've been doing. I'm guessing there are other, TWRP flasheable .zip files for the 6T. Maybe I should try those? Can't seem to find them. If so, can you point them out to me, please?
I humbly ask that you review this thread, looking closely at your guidance and my responses. I keep ending up at the same place - the Qualcom CrashDump Mode Screen.
Thanks!
NBUK

I keep loosing root after reboot, Pls help.

Hey guys,
first time posting here so i dont kow how to style the text, so sorry about that.
last time i rooted a phone was on my sony xperia sp , where all i had to do was to go to towelroot .com and click to root.
I tryed to root my OP6T yesterday, after some setbacks i managed to sucessfully do it.
I did it like this:
1. Downloaded full ROM of OOS 10.3.2,
2. copied the payload to a program called payload dumper that extracted the boot image.
3. Copied the boot image to the phone
4. opened Magisk manager and selected install from source where i chose the boot.img
5. it created a copy called magisk_patched.img
6. booted in fastboot
7. on my pc used the command prompt to "fastboot boot magisk_patched.img"
booted normally and i had root.
but then problem appeared
#Problem 1
everytime i rebooted my phone i would loose root and it would say Magisk not installed. To get it back i would need to perform step 7 again and it was not ideal to do that everytime i turned off my phone.
#Problem 2
While tryng to solve problem 1 i read that i needed to open magisk manager and "Install to Inactive Slot (After OTA)."
After doing that it rebooted but now it wont boot at all, even if i try to "fastboot boot magisk_patched.img" the cmd gives me error:
fastboot boot magisk_patched.img
downloading 'boot.img'...
OKAY [ 0.838s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.845s
now my phone is just sitting there i dont want to reset it again. it would be the 4th time that i need to set up my phone in 2 days, so im trying to see if there are alternatives.
If reset is really the only way, i read that with root you can make a full backup of your phone and then restore it. How to do that? can i do it in the situation im in?
How can i root my OP6T running OOS10.3.2, and keep it? Whats the right method bc the one i followed seemed flawed.
I also tried one that had TWRP but maybe i did something wrong bc it didnt work., also there is no official one working for 10.3.2.
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
OhioYJ said:
What is happening is normal with those instructions (they aren't right).
All you need to do is install TWRP. Do not use the official one, it is out of date. Use TWRP from this thread Link here. The TWRP from that thread is from the official maintainer. It works fine with OOS 10.
- You need to get the phone in fully working order again. Which may mean you need to use the fastboot ROM, as you've probably "goofed" something up at this point. (no offense meant). Make sure your phone boots and such after this.
- For OOS 10 with the phone in fastboot, fastboot boot recoveryimgfilename.img (<-- For OOS 10 you will need TWRP 3.3.1-32 Q Unofficial by mauronofrio from the thread I linked to above) This will boot to TWRP.
- Now run TWRP 3.3.1-32 Unofficial Installer by mauronofrio this will install TWRP. The installer is the same for Android 9 and 10, doesn't matter.
- Once the installer runs, click back, choose reboot to recovery. If you boot to the system, you have to start over. Reboot to recovery!
- Install Magisk 20.3 <-- The current version. The official download page. After that you can reboot to the system. You should now have a rooted, phone with Magisk, and TWRP installed.
Any questions ask.
Click to expand...
Click to collapse
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Davide1713 said:
So getting it straight, i need to first reset my phone and then do the steps you described.
Can i backup the data first with TWRP to restore it later and avoid setting up everything again?
Click to expand...
Click to collapse
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
OhioYJ said:
Supposedly. I've never used that function of TWRP. Some people have luck with, some people restore things that shouldn't be restored and end up having to wipe the phone again. Personally I just use TitaniumBackup like I always have. I would search for information on that in the TWRP thread if you want to try method. I don't know enough on that to provide solid information.
Click to expand...
Click to collapse
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Once again thank you so much
Davide1713 said:
Hey man,
Thank you so much. It worked and i stay rooted even after reboot.
May i ask how you use the Titanium Backup, i think back in the days all i used it for was uninstalling system apps. Or if you know some nice guides. If you know other good things to checkout now that i have root i would appreciate it, i have been far away from rooting for too long.
Click to expand...
Click to collapse
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
OhioYJ said:
I use it to back up app and app data primarily. It allows me to restore data to apps after a clean install. Since I have the Pro version it's just a batch action (one click essentially). There is also a way to create a flashable .zip you can use in TWRP, although I haven't tried that method, as I'm typically not restoring apps, just data. I also use it remove apps from time to time.
Click to expand...
Click to collapse
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Davide1713 said:
Hey man, im sorry i am once again in need.
Idk why but at first i can reboot the system normally without issues. but after a while once i set up everything it just doesnt boot anymore. Am i missing something? do i have to do anything with magisk? download a module or something?
Could it be that google security update is the fault?
Click to expand...
Click to collapse
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
OhioYJ said:
When you installed everything originally did you fix everything with a clean install? Both slots are the same version of Android? (Like you don't have something weird going on like Android 9 on one and Android 10 on another?)
You definitely have something abnormal going on. There shouldn't be anything in Magisk that you have to do, at least not to prevent crashing. I normally hide it, but that has to do with keeping apps from detecting root.
Click to expand...
Click to collapse
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
GuestD2272 said:
I got it to boot by uninstalling magisk,
I am 100% sure i dont have two different version of android in different slots, bc yesterday i was in big trouble and nothing was working and i flashed on both slots the same version of android 10(dont remember exactly wich one as i tried a couple, but they were the same).
Today when i couldnt boot anymore i went into stock recovery, factory reset -> when it booted i placed the stockOS.zip file in the phone and applied update from local file -> after that i factory reset again from the system settings, so i think the phone should have installed it properly.
Only after that i did what you told me and installed TWRP and Magisk. and as i said it worked and i could restart my device etc..
After a while when i restarted i couldnt boot anymore and went to bootloader. Removing Magisk fixed it,apperantly on install magisk creates a copy of the boot.img that it restores on uninstall, and i booted to system.
Now i can use my phone but dont have root.
Im very thankful for you being there and helping me out trough this, i cant thank you enough
Click to expand...
Click to collapse
Not sure if you're still having this issue but I'll post the solution just in case anyone gets stumped, does a google search, and comes across this post. You were using the wrong command.
"fastboot boot" just lets you boot with the img so you can verify that root works.
"fastboot FLASH boot" will flash it and root will stick after reboot.
No need to jump through hoops with TWRP and such.

[Help] I can no longer access wifi after flashing TWRP

So i've exhausted almost every xda thread I can find, and finally decided to make a post myself. This is maybe the 6th or 7th time I've had to MSM tool my phone because I softbricked and could only access bootloader. I'm a newbie so you may need to go in detail in what I should do. All help is very appreciated.
I'm trying to flash a new ROM to my phone, the one in question is the latest nightly build of LineageOS: lineage-17.1-20200806-nightly-fajita-signed.zip, the ROM itself works fine, however, flashing TWRP after flashing this rom (even if I wipe dalvik/cache) I no longer am able to access wifi). I've flashed stock and started over about 5-6 times (from the very very beginning, including unlocking the bootloader) and I'll always end up with a wifi issue or a bootloop.
I've tried multiple different versions of twrp, including the unofficial 3.3.1-32 Q unofficial builds from this guide and both 3.4.0-0 and 3.4.0-1 from the official website, both leading me to the same results. (the unofficial build wouldn't decrypt, so I failed with that one).
I'll go through the steps I do in detail, and if anyone sees an issue with my process, please correct me.
1- enabled developer options
2- enabled usb debugging and oem unlocking in developer options
3- booted into bootloader with
Code:
adb reboot bootloader
4- checked to see if phone is connected and unlocked the bootloader with
Code:
fastboot oem unlock
5- set up my phone again, enabled dev options, and enabled usb debugging again.
6- booted into bootloader again
7- typed this into the terminal to temporarily boot TWRP
Code:
fastboot boot <recovery_twrp>.img
7.5- flash copy-partitions.zip from the LineageOS install guide
8- went to advanced>adb sideload>swiped then went on adb terminal to sideload TWRP installer
Code:
adb sideload <twrp-installer>.zip
9- went to menu>reboot>recovery
10- after rebooting went to wipe>factory reset slide>swiped slider
11- went back to menu>advanced>adb sideload>swiped then went on adb terminal to sideload (while checking wipe cache/dalvik)
Code:
adb sideload <lineageOS-rom-nightly>.zip
12- tapped reboot system
this is where things begin to go wrong:
- i notice that I can't boot into lineageOS, lineageOS claims android data is corrupted and needs to factory reset
- factory reset phone
- boots up fine, go through set up process (wifi works right now, only problem I notice is that within build settings, it shows a completely different phone number on my SIM card rather than the phone number I actually have, but it doesn't look broken or corrupted), enable usb debugging again, boot into bootloader
- type
Code:
fastboot boot <recovery-twrp>.img
- twrp loads up fine
- go to menu>advanced>adb sideload>swipe to begin sideload then type
Code:
adb sideload <twrp_installer>.zip
- reboot system
- boot process takes forever, (restarts 3-4 times) phone feels sluggish, and wifi will no longer work (data works fine)
- i give up and I MSM tool my phone.
I genuinely think this is because of TWRP, I read through a few xda threads claiming that the official 3.4.x builds had many issues, and therefore would reccomend using 3.3.x builds. I tried both from the official website and the unofficial TWRP by mauronofrio, where i get decryption problems on both of them. only 3.4.0-x TWRP builds would get me as far as flashing the rom. I've tried this process on both android 10.3.0 and 10.3.5
I genuinely would like some help. this phone is my daily driver and not being able to use TWRP (let alone properly flash a ROM) is a big problem that destroys what I loved about my phone in the first place. Thanks in advance.
I'm assuming this is not a TMobile 6T. With that assumption.
Try my LOS install guide. Note I couldn't get the 10.3.5. fastboot ROM to work. However if you are already on 10.3.5 stock, you are fine, just go with it. I updated manually to 10.3.5 using TWRP, and then used the latest weekly build and everything has been fine. Just go straight to the TWRP step. Other wise use the 10.3.4 fastboot rom. Cliff notes version in the second post.
https://forum.xda-developers.com/on...ash-magisk-t4022157/post81248271#post81248271
Follow this thread. If you're losing WiFi in stock from flashing twrp, there's way to prevent it
Extreme_Ninja2099 said:
https://forum.xda-developers.com/on...ash-magisk-t4022157/post81248271#post81248271
Follow this thread. If you're losing WiFi in stock from flashing twrp, there's way to prevent it
Click to expand...
Click to collapse
Im not rooted, im coming from unrooted 10.3.5
OhioYJ said:
I'm assuming this is not a TMobile 6T. With that assumption.
Try my LOS install guide. Note I couldn't get the 10.3.5. fastboot ROM to work. However if you are already on 10.3.5 stock, you are fine, just go with it. I updated manually to 10.3.5 using TWRP, and then used the latest weekly build and everything has been fine. Just go straight to the TWRP step. Other wise use the 10.3.4 fastboot rom. Cliff notes version in the second post.
Click to expand...
Click to collapse
this worked!! thank you so much for such a great guide!
I did one thing differently though, instead of using the fastboot rom or running it through scripts, I used the copy-partitions.zip file available on LineageOS' fajita install guide to make both partitions appear the same. I realized my mistake when I didn't flash the rom twice, as that's mandatory when it comes to A/B partitioned phones
Everything works smoothly! thanks!

[GUIDE] [TB-X606F] [Lenovo M10 Plus FHD] How to flash TWRP, Generic System Image (Android 11, Android 12), and Root with Magisk

Hi, I'm a long-time lurker on these forums but recently had some success flashing a GSI and rooting the Lenovo Tab M10 Plus (FHD) (X606F) with TWRP, and wanted to share my exact steps here. This device is awesome for the price point but unfortunately not popular enough to have many guides available. The tablet is Project Treble compatible and uses A/B roms (although it is not an A/B device in terms of OTA updates). You can use the Treble Info app to confirm that the devices uses an ARM64 A/B operating system. This was tested with the CAOS 11 GSI based on Android 11; it may work on other GSIs and other Android versions but I have not tested those (NOTE: user below confirms working on Android 12). I've written this guide at a bird's-eye-view meant for users familiar with flashing.
A couple useful notes before we begin:
- Hardware force off: hold down both volume buttons + power button
- Hardware boot into bootloader: while powered off, hold volume down + power button
- Hardware boot into recovery: hold down both volume buttons + power button
- While in fastboot mode, the command `fastboot reboot recovery` does not work for me on this device. You may have to hardware boot into recovery using the hardware steps above (power off completely then hardware boot). [This command may work for some people. It does not work for my device.]
Obviously, make sure your bootloader is unlocked before starting.
1. I used Ubuntu since Windows was having trouble recognizing the device in fastboot mode; linux drivers seem to be better developed for this particular device. I used `sudo apt install android-sdk` to get the drivers. Much easier than the nonsense that you have to do on Windows to get this device to work. Unfortunately, the Lenovo rescue app is available only for Windows, so you'll need access to Windows to gain access to vbmeta.img for installing TWRP (below).
2. Install TWRP following this guide: https://forum.xda-developers.com/t/...rp-3-5-x-for-lenovo-tab-m10-fhd-plus.4222887/. It is important that you follow all these steps. After flashing the recovery, you must reboot into recovery to ensure that TWRP permanently installs. If the `fastboot reboot recovery` command does not work for you, hold down the power button to power off the device, then hardware boot into TWRP by holding down both volume buttons + power button to boot into TWRP. If you do not perform this step, the device will boot normally and TWRP will be erased. After booting into TWRP, wipe -> format data.
3. In TWRP, flash CAOS 11 GSI: https://forum.xda-developers.com/t/official-aosp-r-mod-caos11.4265059/. You can try with other GSIs - it will probably work - but I've only tested this particular one, and can attest for the stability of CAOS 11 on this device. The image you'll want is named with -arm64-bgZ. If you use another GSI, make sure to use the A/B arm64 image. CAOS 11 has gapps included, so no need to flash here; if you use another GSI that does not have, you'll need to flash the appropriate gapps yourself. You can also opt for the non-gapps download if you don't want Google spying on you.
4. (Optional/No longer necessary) In TWRP, flash to disable dm-versity: https://zackptg5.com/android.php#disverfe.
5. (Optional - many GSIs come with root) In TWRP, flash standard Magisk.zip: https://github.com/topjohnwu/Magisk. I didn't need to use Magisk-Phh.
6. Reboot system.
7. You may or may not get errors from Google Play saying that the device is not certified. Follow these steps:
- Sign into Google account on device via settings
- Download and install the Get ID app: https://f-droid.org/en/packages/makeinfo.com.getid/
- Open the app and Copy Google Service Framework Key
- Go to https://www.google.com/android/uncertified/
- Sign in and paste the copied value to it, register
- Reboot (this actually took me a few tries to get working, I believe the key is to make sure you're signed into your Google account)
- Google Play should be working
Feel free to ask any questions here.
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
dpn982 said:
I got this working with the PHH android 12 pre-release version. So far everything seems to be working. There are a couple things I have to sort out still like it passes safetynet but some apps still don't show up in the play store.
Click to expand...
Click to collapse
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
shnioob said:
Good to know that Android 12 works. What apps aren't showing up for you? Maybe they are simply incompatible with Android 12.
Click to expand...
Click to collapse
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
dpn982 said:
Netflix is one, maybe Disney plus too. It could be that I just need to restart cause I haven't done that since I got safetynet passing. I was waiting for the bulk of the apps to restore first.
Click to expand...
Click to collapse
I think this tablet has always had an issue with Netflix due to lack of DRM or something of that nature - I wasn't able to get Netflix on the stock version. Disney+ is probably the same issue.
If you have some free time, it would be great if you can outline your steps for getting safetynet to pass. I haven't bothered with it.
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
emilio666 said:
Thanks!
By the way, about point number 7, which roms are like this? I have tried: Phhusson Android 12 latest version, PE 12 latest version and Lineage OS by AndyYan, all with gapps but I get the error
Click to expand...
Click to collapse
NEVERMIND, it got solved by just waiting a couple of hours after using the Google website: https://www.google.com/android/uncertified/
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
Thanks for the clarifying info, updated the OP a bit. And thanks for providing us with a TWRP to make this possible. Otherwise this awesome tablet would be stuck on Android 10 forever.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Happy to help, glad it worked for you. I tried installing some other GSIs with and without flashing Magisk - LineageOS 12 boots but is very buggy, after reboot I was unable to get past the lockscreen. PixelExperience 11 and 12 cause a bootloop. If anyone has had success with PixelExperience I would love to get your input.
Yahoo Mike said:
Nice thread. Here's some thoughts to help make this process simpler.
Following the numbering in the OP:
If you are using Windows, just make sure you have the latest OEM drivers from Mediatek (MTK).
after flashing TWRP and vbmeta, you can try fastboot reboot recovery to boot to twrp. I know the OP says it doesn't work, but it works on my TB-X606FA.
..and it's also a good idea to format data, especially if you're upgrading to a new OS level. This will delete everything on the data partition.
phhusson keeps a list of GSIs based on his work.
this step is now optional. TWRP (v3.6.0) has been patched to handle the A12 keymaster.
many GSIs come with root as standard. If yours does (or if you installed Magisk-Phh), then you can use the Magisk app as a root manager, but be aware that updating Magisk from inside the app might break the GSI.
-
some of the latest GSIs have fixed this issue and the integrated gapps should just work.
Click to expand...
Click to collapse
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
jebise101 said:
So i can flash the official google GSI using these steps?
Branch Grid
ci.android.com
I don't need root and want to be stock as possible.
Click to expand...
Click to collapse
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
shnioob said:
Give it a try and let us know. I think some GSIs are more stable than others. I've had trouble with LOS and PE on this device.
Click to expand...
Click to collapse
How do you go back to stock in case this does not work?
Is there a factory image?
jebise101 said:
How do you go back to stock in case this does not work?
Is there a factory image?
Click to expand...
Click to collapse
you can download the stock ROM from LMSA
I also have Lenovo tab m10 fhd plus but it is tb-x606v. Can I flash x606f rom on this device and flash twrp after.i don't want my device to be bricked.
vladilog said:
Thanks a lot for this guide.
I just installed the latest Phh AOSP 12 GSI (system-squeak-arm64-ab-vndklite-gapps.img.xz) without problems by following your recommendations. I used the lastest twrp_X606FA_11. Flashing dm-verity or Magisk was not required for this GSI to work (it's already rooted). I did have to register my device to solve the "Google Uncertified" issue.
Click to expand...
Click to collapse
Hi, I'm trying to follow what you did, but I'm having issues with the Gapps, do you have some pointers to solve it? Thank you in advance
Hello everybody!
I finally installed CAOS 11 and it's working like a charm. Gapps are definitely working as excpected and system seems to be stable as possible.
I have two question to those that installed it to :
Is anyone kow why some widgets on X606F are not clickable, an do not actualize till reboot?
Am I the only one that lost double tap to wake on CAOS?
Thank you all
I tried AOSP V412 12L too, we lost fingerprint sensor and face unlock, widevine DRM. There is some troubles on wifi, beside of this it is pleasant. Of course this not as smooth as android 10. I do not recommend it for daily basis.
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
garconblair said:
I have tb-X606X. I’ve tried AOSP 11 and AOSP 12, Pixel Exp 11 and 12, LineageOS 11 and 12, but finally I stay with CAOS11, which is from all I tried, the most stable, smooth and bug free.
Btw, I do not have any issue with widgets on CAOS.
And yes, the double tap to wake is lost. I think it is not because of CAOS, it is because of Android 11 and above.
Click to expand...
Click to collapse
Thanks for the feedback. What about Widevine L1 and SafetyNet test with CAOS11? Are you able to play content at 1080p resolution with the Netflix App?

Categories

Resources