Database Users

4.2.2 Update / TWRP problem

Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?

The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.

MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
Maybe before you even answer, I'm sure I'll find a link on here to show me how?
One issue I have though, is that when I manually updated to 4.2.1 on my Nexus 7, I still got an OTA update a few days later, that actually ran.
I don't ever plan on flashing roms to any of my devices. Do I need to keep a custom recovery on my Nexus 4 or 7? If not, how to I revert back to the stock recovery?

If you saved the offical stock 4.2.1 images, to revert back to stock recovery, just use the 'fastboot flash recovery recovery.**************.img' command. If you haven't, you might have to flash the whole 4.2.2 rom which you can find on the google dev website. After this, if you only want to root then you don't need to flash a custom recovery, just use the 'boot' command instead of the 'flash' one.

MacHackz said:
The OTA update requires stock recovery in order to be flashed. I recommend you just flash the update manually using fastboot, and you won't lose data.
Click to expand...
Click to collapse
I flashed the OTA sideload file through TWRP and it installed succesfully.

jvbferrer said:
I flashed the OTA sideload file through TWRP and it installed succesfully.
Click to expand...
Click to collapse
How did you do that? Did you sideload wrinkle's file from this thread: http://forum.xda-developers.com/showthread.php?t=2145848?
I should let you know, that while I'm not afraid to install via the custom recovery, it doesn't mean I've done it via commands. I've always used toolkits, or one click methods of rooting and installing custom recoveries.

Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.

wvcadle said:
Well, this is crazy (weird?). I tried to flash it via TWRP by downloading the zip file in the thread referenced above, and it failed. By flashing, I mean, I chose 'Install' and pointed to the zip after moving it to my phone. After failing, I wiped the Dalvik cache and rebooted, and it's telling me 'Android is upgrading'. If it means it updated, so be it. But can anyone explain? Feeling a little confused here.
Edit: Ok, so it said it was upgrading, but it's still 4.2.1.
Click to expand...
Click to collapse
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?

MacHackz said:
It 'upgrades' when you wipe the cache. It just means it's rebuilding the cache. Are you running an unmodified stock rom? Custom kernel?
Click to expand...
Click to collapse
Yes, stock rom, rooted and unlocked. I did install Beats today. Could this be the problem? If so, I found a revert zip that I'm assuming is supposed to revert me back to stock audio codecs.

I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.

MacHackz said:
I don't think added files matter, but I'm guessing the Beats mod has overwritten something in system, so flash the revert zip, then try again.
Click to expand...
Click to collapse
Flashing the revert zip failed. I'm starting to think that flashing anything with TWRP will fail.
How about this. I made a backup of all system data + apps with Titanium earlier today. Could I just reset my phone back to factory defaults, restore my apps + some system data, then re-root (*without a custom recovery*) and wait for the update again? Or will it come again?
Also, I've used Wugfresh's Nexus Toolkit. I don't remember checking the custom recovery button, but ended up with TWRP anyway. What's the easiest way to root without installing a custom recovery?

You could try that, and the update will come straiht away. You can root without flashing a custom recovery, just use the 'boot recovery' instead of 'flash recovery'

MacHackz said:
flash cwm and see if there's any difference
Click to expand...
Click to collapse
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?

wvcadle said:
How do I do that with TWRP? Can I do it with Wug's Nexus toolkit?
Click to expand...
Click to collapse
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot

MacHackz said:
I'm not familiar with any toolkits, I would recommend flashing cwm using fast boot
Click to expand...
Click to collapse
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.

wvcadle said:
Ok, I'm surely not afraid to use the command prompt. Any tutorials you can point me to? I probably already have all of the drivers I need, as the toolkit had to download install them.
Click to expand...
Click to collapse
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440

MacHackz said:
Check out this thread. Use flash to flash and overwrite TWRP, or boot just to test. http://forum.xda-developers.com/showthread.php?t=1995440
Click to expand...
Click to collapse
Where in that thread does it show me how to flash the stock recovery back onto my device?

wvcadle said:
Hello. I just received my OTA notification, but when I clicked it, it rebooted and landed my on the TWRP recovery screen. Not knowing what to do, I just told it to reboot to the system.
Once rebooted, I was still on 4.2.1, and there was no update.
Any ideas why it booted to TWRP?
Click to expand...
Click to collapse
The same thing happened to me. I was rooted running stock ROM with TWRP recovery (used wugfresh toolkit). The problem was I forgot I was using a modified kernel (for color correction) by molesarecoming. I flashed the stock kernel back, downloaded and flashed the OTA file from the help desk thread (http://forum.xda-developers.com/showthread.php?t=2145848&highlight=beats), and it worked. Oh, and I flashed the Superuser file immediately after the OTA did it's thing (while still in TWRP) to regain root. I didn't really like how after the initial failed install of the OTA, it took my into TWRP with no error message showing or anything.
I don't think TWRP is your problem -- I think beats is your problem. It may have modified something. Try searching the above-linked thread for answers. Honestly, there's no rush to get 4.2.2, so take your time finding the answer. It's better than wiping the phone just to install a small android update and having to redo everything on your phone again.

Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.

wvcadle said:
Ok, it must have been the Beats audio drivers. I restored a Nandroid backup from right before installing the beats audio drivers, then flashed the zip and it worked. Now running 4.2.2.
I would like to know, however, how to use fastboot via commands, so that I can learn how to flash TWRP, CWM, Stock recovery, etc.
Click to expand...
Click to collapse
I need some help here - I have nexus 7 with 3G and Google (takju) with 4.2.1 installed.
I had it 'rooted" and installed TWRP .
AT the time I followed instructions to chand extension of some file to .bak - to prevent 'unrooting"
I do not remember which file I unfortunately changed.
Now I cannot install the 4.2.2 upgrade - the OTA fails because it boots into TWRP and after that I rrid several selections from TWRP screen (flash, reboot, etc) - but all attempts failed.
I have the upgrade files (bot .tar and .zip) on /sdcard directory but have no idea how to update to 4.2.2.
Tried manual flashing using adb command - all fails.
I do not have beats drivers installed
Can someone tell me how to uninstall TWRP? If the CWM recovery works with this upgrade, I would like to change from TWRP to CWM.
Or any other suggestion wold be appreciated.
I am really struggling with Android operating system the way it configured on Nexus 7 by Google - any simplest is a major pain!
Hope I can get out of this and operate the device instead of continuously meddling with operating system.
Thanks in advance
[email protected]

[Q] HELP! Stuck in a boot loop :(

*RESOLVED*
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.

wipe data then reflash your rom

benblb said:
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.
Click to expand...
Click to collapse
If you have unlocked bootloader, download Nexus 4 image from here, unzip it to get the various factory images and then flash using fastboot. If you have locked bootloader, you will have to unlock it using
Code:
fastboot oem unlock
.
CAUTION: This will wipe all data.
Follow this guide to re-root and install CWM.

simms22 said:
wipe data then reflash your rom
Click to expand...
Click to collapse
Is there any way for me to keep my data? How do I cleanly do it? If I do need to wipe data, what do I do? Do I just go into CWM and tell it to wipe the data and then flash the operating system? I saw some instructions that had me flashing all sorts of stuff (i.e. radios etc). Sorry for all the questions.

rhoadster91 said:
If you have unlocked bootloader, download Nexus 4 image from here, unzip it to get the various factory images and then flash using fastboot. If you have locked bootloader, you will have to unlock it using
Code:
fastboot oem unlock
.
CAUTION: This will wipe all data.
Click to expand...
Click to collapse
My bootloader is unlocked. What exactly do I flash from the 4.2.2 image? Do I need to wipe my data first or is my data just wiped in the process?

benblb said:
Is there any way for me to keep my data? How do I cleanly do it? If I do need to wipe data, what do I do? Do I just go into CWM and tell it to wipe the data and then flash the operating system? I saw some instructions that had me flashing all sorts of stuff (i.e. radios etc). Sorry for all the questions.
Click to expand...
Click to collapse
yes, in cwm. wipe data then flash the rom. you can try just reflashing your rom first, without wiping data. if it still bootloops, then wipe data and reflash. flashing the system img via fastboit will wipe everything.

benblb said:
I tried to update to 4.2.2 manually and got stuck in a bootloop. The first time, I got an error message (attached) and rebooted, so I went into Voodoo Root protector and deleted my backup of SU thinking that could be the problem. I tried again, got the same error, and now I'm in a bootloop. I am on stock Android 4.2.1 and using Franco Kernel r72. Please help me.
Thanks.
Click to expand...
Click to collapse
Since you aren't running the stock kernel, one of the kernel modules failed an md5sum check for a patch and the install stopped before attempting to patch a file that wasn't equal to what it was expecting.

a wipe data/factory reset in Recovery Mode can solve this bootloop, especially after you have just flashed a ROM.

benblb said:
My bootloader is unlocked. What exactly do I flash from the 4.2.2 image? Do I need to wipe my data first or is my data just wiped in the process?
Click to expand...
Click to collapse
Flashing from fastboot will automatically clear all data. There should be a system.img file. Flash it using
Code:
fastboot flash system system.img
But to make a clean install, I would recommend you flash all the factory images. Refer this for more detail.

JaiaV said:
Since you aren't running the stock kernel, one of the kernel modules failed an md5sum check for a patch and the install stopped before attempting to patch a file that wasn't equal to what it was expecting.
Click to expand...
Click to collapse
So I can just re-flash my kernel and be fine? I can't get the kernel to flash though.

benblb said:
So I can just re-flash my kernel and be fine? I can't get the kernel to flash though.
Click to expand...
Click to collapse
reflash the rom. franco kernel isnt flashable in recovery, you need to flash it via fastboot(.img file not a .zip).

simms22 said:
reflash the rom. franco kernel isnt flashable in recovery, you need to flash it via fastboot(.img file not a .zip).
Click to expand...
Click to collapse
I'm on stock. What file do I flash? Thanks for all your help.

benblb said:
I'm on stock. What file do I flash? Thanks for all your help.
Click to expand...
Click to collapse
look in the development section, there are a few rooted stock roms available.

simms22 said:
look in the development section, there are a few rooted stock roms available.
Click to expand...
Click to collapse
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?

benblb said:
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?
Click to expand...
Click to collapse
Flashing the factory images will have restored the stock kernel.

If you are going to flash a factory image or anything like that, watch this: http://forum.xda-developers.com/showthread.php?t=2039162
after you flash that ROM, if your phone stucks in a bootloop, then go to Recovery, wipe cache and reset factory will solve the problem.

benblb said:
I just flashed stock. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2010312
Do I also need to flash a kernel? If so, where do I get the download for stock?
Click to expand...
Click to collapse
na, the kernel is always included in the rom. you flash a kernel if you want to use a different kernel(trinity is great with stock).

Hi everyone,
Thanks for your help. I have flashed stock 4.2.2 to my phone and have finished setting everything up. I really appreciate the quick responses and dedication to my issue. It means a lot to me that you guys helped me in my time of need. Thanks again.
Cheers,
Ben

Stuck on Google at Boot, not sure how to recover. :(

Sooo... Where to begin? I was previously on the latest Paranoid but decided I just couldn't wait so as soon as the stock 4.3 images were available, I wiped and went to 4.3. Used the updated SuperSU (chainfire's) and restored some apps from Titanium and all was well... Stock, rooted, and moving along. Then I see an amazing boot animation someone made for the N4 so I just had to have it. Downloaded it, rebooted into TWRP and flashed it and BOOM device no longer boots. I tried every which way from Sunday to get it to boot and to no avail it no boot. So I said screw it, I'll just wipe and start over. I formatted cache, flashed bootloader, boot.img, and system.img (didn't think there was any point to reflash radio) and still no boot... I'm stumped. Am I forgetting something blatantly obvious here? I mean I flashed, bootloader, boot image, and system image... I should basically be at a brand new device. I'm really trying not to format user data unless I have to, and I don't see how anything in user data would be preventing me from booting as it really only reads that stuff at started and not necessarily at 'boot' right? I'm hanging at the Google screen and never even make it to the Nexus X animation portion of boot. What am I missing?

itpromike said:
Sooo... Where to begin? I was previously on the latest Paranoid but decided I just couldn't wait so as soon as the stock 4.3 images were available, I wiped and went to 4.3. Used the updated SuperSU (chainfire's) and restored some apps from Titanium and all was well... Stock, rooted, and moving along. Then I see an amazing boot animation someone made for the N4 so I just had to have it. Downloaded it, rebooted into TWRP and flashed it and BOOM device no longer boots. I tried every which way from Sunday to get it to boot and to no avail it no boot. So I said screw it, I'll just wipe and start over. I formatted cache, flashed bootloader, boot.img, and system.img (didn't think there was any point to reflash radio) and still no boot... I'm stumped. Am I forgetting something blatantly obvious here? I mean I flashed, bootloader, boot image, and system image... I should basically be at a brand new device. I'm really trying not to format user data unless I have to, and I don't see how anything in user data would be preventing me from booting as it really only reads that stuff at started and not necessarily at 'boot' right? I'm hanging at the Google screen and never even make it to the Nexus X animation portion of boot. What am I missing?
Click to expand...
Click to collapse
boot animation goes into splash partition doesn't it? Still how many times do you see the splash screen on your device a day when you are not flashing systems?

boot animation goes either into /system/media/ or /data/local/ btw.
simply reflashing your rom without wiping anything would have resolved your issue. you are going to have to wipe data now most likely.
---------- Post added at 10:40 PM ---------- Previous post was at 10:28 PM ----------
did you make a nandroid backup in your recovery?

simms22 said:
boot animation goes either into /system/media/ or /data/local/ btw.
simply reflashing your rom without wiping anything would have resolved your issue. you are going to have to wipe data now most likely.
---------- Post added at 10:40 PM ---------- Previous post was at 10:28 PM ----------
did you make a nandroid backup in your recovery?
Click to expand...
Click to collapse
I didn't make a nandroid but its fine now. I finally decided to wipe the data and it booted. I wasn't actually running a custom ROM at this point though. Just stock and rooted. You think reflashing stock without wiping anything would,d have done the trick?

itpromike said:
I didn't make a nandroid but its fine now. I finally decided to wipe the data and it booted. I wasn't actually running a custom ROM at this point though. Just stock and rooted. You think reflashing stock without wiping anything would,d have done the trick?
Click to expand...
Click to collapse
if the zip puts the bootanimation.zip into /system/media/ then yes(it most likely does, you can look into the zip and see). if it puts the bootanimation.zip into /data/local/ then no, because just reflashing the rom wouldnt clear out that folder. btw, if you ever want a boot animation to stick between flashing roms, put it into /data/local/. you can do this manually, with a root file explorer, without the need to flash anything.

simms22 said:
if the zip puts the bootanimation.zip into /system/media/ then yes(it most likely does, you can look into the zip and see). if it puts the bootanimation.zip into /data/local/ then no, because just reflashing the rom wouldnt clear out that folder. btw, if you ever want a boot animation to stick between flashing roms, put it into /data/local/. you can do this manually, with a root file explorer, without the need to flash anything.
Click to expand...
Click to collapse
Ahhh thanks for the tip mate. Didn't know that. Now it seems I have another problem. My phone seems to think it only has 8GB of storage when it has 16GB... this can't be good. Wonder how I would go about diagnosing and fixing this or maybe I should start another thread?

itpromike said:
Ahhh thanks for the tip mate. Didn't know that. Now it seems I have another problem. My phone seems to think it only has 8GB of storage when it has 16GB... this can't be good. Wonder how I would go about diagnosing and fixing this or maybe I should start another thread?
Click to expand...
Click to collapse
First try wiping the cache and Dalvik cache and reboot. If your phone still sees only 8GB of storage, perform a factory reset and reboot.
Finally, if your phone does not see 16GB of storage, follow the guide at http://forum.xda-developers.com/showthread.php?t=2033692.

[Q]Wont boot after failed 4.4 OTA Update (Bootloader Unlocked, CWR)

Hi guys,
I unlocked my Bootloader, installed Clockwork Recovery a while back. Still had Vanilla Android on it.
Today I updated it, there was an error shown in the Clockwork recovery during the update, I rebooted the device.
Now I am stuck in the 4.4 Bootscreen.
How can I get a Recovery Image on my Phone now? (Booting in Recovery works without any issues)
When I reset my device is all the data in the sdcard folder gone? If so is there a way to back some of it up now?
Thanks

acidr4in said:
Hi guys,
I unlocked my Bootloader, installed Clockwork Recovery a while back. Still had Vanilla Android on it.
Today I updated it, there was an error shown in the Clockwork recovery during the update, I rebooted the device.
Now I am stuck in the 4.4 Bootscreen.
How can I get a Recovery Image on my Phone now? (Booting in Recovery works without any issues)
When I reset my device is all the data in the sdcard folder gone? If so is there a way to back some of it up now?
Thanks
Click to expand...
Click to collapse
Its best to do a clean flash and delete all your data. Phone vs Pics? I'd take the phone. Besides, some stuff is backed up by Google servers. Follow this:
http://forum.xda-developers.com/showthread.php?t=2010312

You can't update OTA while having cwm. OTA can only be completed using stock recovery or twrp recovery. Cwm haven't had this ability yet. Just follow the guide given in a post above and flash kitkat factory images. All your problems will be solved. Or, you can use this guide ( http://forum.xda-developers.com/showthread.php?t=2527142 ) and delete the -w to save your data.
For your second question, if you factory reset using stock recovery, then yes, it will wipe clean your sd card. If you reset using cwm/twrp, then no, it won't wipe your sd card and your pics, music will all still be intact.

arffrhn said:
You can't update OTA while having cwm. OTA can only be completed using stock recovery or twrp recovery. Cwm haven't had this ability yet. Just follow the guide given in a post above and flash kitkat factory images. All your problems will be solved. Or, you can use this guide ( http://forum.xda-developers.com/showthread.php?t=2527142 ) and delete the -w to save your data.
For your second question, if you factory reset using stock recovery, then yes, it will wipe clean your sd card. If you reset using cwm/twrp, then no, it won't wipe your sd card and your pics, music will all still be intact.
Click to expand...
Click to collapse
thanks both of you i kept using this method, -w didnt seem to work properly so I wiped it comleetly now it boots up propperly
thanks again

acidr4in said:
thanks both of you i kept using this method, -w didnt seem to work properly so I wiped it comleetly now it boots up propperly
thanks again
Click to expand...
Click to collapse
How did you wipe your phone completely? I actually have the same problem you had.

aznpro said:
How did you wipe your phone completely? I actually have the same problem you had.
Click to expand...
Click to collapse
nvm, i figured it out.

Anyone else having problems installing a backup from TWRP and it bricking your 6T?

I am on 9.0.11 rooted. I have tried installing a backup twice now from TWRP and every time it pretty much just bricks my phone. after both times it will only boot to Fastboot and acts like no recovery is installed and no OS is installed. and every time I have to go thru the process of flashing the Stock Fastboot ROM just to get the phone to work and boot again.
It makes me not want to flash anything since I can not rely on my backups and I be scared to brick the phone again.

If you have a bad magisk module, disable it using magisk manager for twrp 1st

vegetaleb said:
If you have a bad magisk module, disable it using magisk manager for twrp 1st
Click to expand...
Click to collapse
That's what I normally do, but I had two situations where I needed to restore a backup and both times my backup bricked the phone. TWRP restored the backup like normal, but after booting both times I get suck in Fastboot and have to go thru the process of wiping/restoring my phone to stock.

Fatmonk8 said:
That's what I normally do, but I had two situations where I needed to restore a backup and both times my backup bricked the phone. TWRP restored the backup like normal, but after booting both times I get suck in Fastboot and have to go thru the process of wiping/restoring my phone to stock.
Click to expand...
Click to collapse
Try to switch to the other slot, there is a fastboot command line for that but I forgot it

vegetaleb said:
Try to switch to the other slot, there is a fastboot command line for that but I forgot it
Click to expand...
Click to collapse
Did that too, first time it happened that worked, seconds time it didn't seem to do anything.

Well your last chance is to flash the fastboot version of the stock rom , it will wipe your phone so keep a backup on your PC.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

vegetaleb said:
Well your last chance is to flash the fastboot version of the stock rom , it will wipe your phone so keep a backup on your PC.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
and every time I have to go thru the process of flashing the Stock Fastboot ROM just to get the phone to work and boot again.
Click to expand...
Click to collapse
Already said that..

So I guess you don't have a choice and use this solution

Fatmonk8 said:
I am on 9.0.11 rooted. I have tried installing a backup twice now from TWRP and every time it pretty much just bricks my phone. after both times it will only boot to Fastboot and acts like no recovery is installed and no OS is installed. and every time I have to go thru the process of flashing the Stock Fastboot ROM just to get the phone to work and boot again.
It makes me not want to flash anything since I can not rely on my backups and I be scared to brick the phone again.[/QUOTE
Hi.
I have the same problem. I have backups on phone, and USB drive but whenever I try to restore a backup I soft brick my phone. I can't find any help or advice or answers.
Click to expand...
Click to collapse

Have you tried dirty flashing the full ROM, then TWRP and Magisk after doing your restore? I have been in a similar position before on a few occasions when restoring a backups and have had to reinstall some stuff again after to get it to boot again.

Are you sure you have installed the correct TWRP?
Try reflashing the one from:
https://eu.dl.twrp.me/fajita/

dj_ooms said:
Have you tried dirty flashing the full ROM, then TWRP and Magisk after doing your restore? I have been in a similar position before on a few occasions when restoring a backups and have had to reinstall some stuff again after to get it to boot again.
Click to expand...
Click to collapse
Thanks. I'll try this tonight!

Are y'all backing up the the image files, including vendor? I have had no problems restoring backups on my 6T. Unfortunately I tend to mess it up past where the backup would help ?

ZeroKool76 said:
Are y'all backing up the the image files, including vendor? I have had no problems restoring backups on my 6T. Unfortunately I tend to mess it up past where the backup would help ?
Click to expand...
Click to collapse
Thanks. I've just been backing up boot, system and data. Should I also be including system image, vendor and vendor image?
Thanks for your help. I appreciate it!

Have restored TWRP backup many times without issues.
Important is that you don't backup and restore system and vendor but system image and vendor image!

Cdneyes said:
Thanks. I've just been backing up boot, system and data. Should I also be including system image, vendor and vendor image?
Thanks for your help. I appreciate it!
Click to expand...
Click to collapse
Yes, just the images. Boot,system,vendor and data

vegetaleb said:
Well your last chance is to flash the fastboot version of the stock rom , it will wipe your phone so keep a backup on your PC.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
LMAO uh no thats not the last resort and the msmtool would be the last and smartest option to recover from a brick not a fastboot rom.
---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------
Fatmonk8 said:
I am on 9.0.11 rooted. I have tried installing a backup twice now from TWRP and every time it pretty much just bricks my phone. after both times it will only boot to Fastboot and acts like no recovery is installed and no OS is installed. and every time I have to go thru the process of flashing the Stock Fastboot ROM just to get the phone to work and boot again.
It makes me not want to flash anything since I can not rely on my backups and I be scared to brick the phone again.
Click to expand...
Click to collapse
Yeah because twrp backup and restore has had known issues like this since op6. Don't use it or you always going to have some issue like this. Just use migrate or Swift backup or something.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
vegetaleb said:
If you have a bad magisk module, disable it using magisk manager for twrp 1st
Click to expand...
Click to collapse
Um no again. There has nothing to do with it. Twrp doesn't backup magisk modules ever and never has.