Database Info

Weird Soft-Brick, Need Help!!!

Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!

akn4497 said:
Hi all,
I started out on TWRP version 2.7.1.0, and I wanted to flash the latest TWRP recovery (2.8.7.0), so I used the app that was linked by the TWRP site (TWRP Manager). So I tried to flash the latest update, and then a message pops up telling me to check if this was the right partition. I was careless and I didn't check it, and went ahead and installed it. It said it failed, but next thing I know, every time I tried to reboot(into the system/OS) I just boot right into TWRP (version 2.8.7.0). Then from TWRP (2.8.7.0) I tried to reboot into recovery, and it rebooted into TWRP, except that it was version 2.7.1.0, where I started.
So, when I hit boot into system, I got TWRP (2.8.7.0), and when I hit boot into recovery, I got TWRP 2.7.1.0. I was completely confused, so I wiped the OS, and then booted into fastboot to fastboot flash TWRP(2.8.7.0) in my recovery (It worked). Right now, I'm soft-bricked so I don't have an OS, but I have TWRP(2.8.7.0) as my recovery. Except now, I still get TWRP when I try to boot into system, and fastboot flashing, adb sideloading, and regular TWRP flashing is not working...
Any help is very appreciated, I need my phone to just be working!!! Except, if anyone can help me update it to 5.1 while they're at it, that would be awesome!
Click to expand...
Click to collapse
I would flash the new RUU.

andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.

akn4497 said:
Thanks for the reply!
I have already tried to flash the RUU for 4.4.4 but the recovery flash method gave me an error, and the fastboot flash method gave me
FAILED...(remote: not allowed)
I will try again in the morning and let you know how it goes, but I have a feeling it will end the same way.
Click to expand...
Click to collapse
Why not use the new 5.0.1 RUU?

andybones said:
I would flash the new RUU.
Click to expand...
Click to collapse
andybones said:
Why not use the new 5.0.1 RUU?
Click to expand...
Click to collapse
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4

akn4497 said:
Yup that's what I meant I'll try 5.0.1 in the morning. Just wondering, will I need the firmware for it? Because I am coming from 4.4.4
Click to expand...
Click to collapse
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU? Fastboot flash zip nameofRUU.zip

andybones said:
The firmware is apart of the RUU, did you use cmd
fastboot oem rebootRUU
Then flash RUU?
Click to expand...
Click to collapse
Oh shoot, I feel dumb. I'll let you know, thanks!

The RUU worked! I used the exe and I'm up and running. Thanks!!

akn4497 said:
The RUU worked! I used the exe and I'm up and running. Thanks!!
Click to expand...
Click to collapse
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.

cntryby429 said:
When you go to flash your custom recovery, use fastboot rather than twrp manager. If you MUST use such a shortcut, I might recommend flashify.
Click to expand...
Click to collapse
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks

akn4497 said:
Yeah I think I'll just stick with fastboot flashing recoveries from now on! Thanks
Click to expand...
Click to collapse
Glad to hear you're up and running my friend.

Root for NOF26W?

Is there a guide for rooting the Rogers Pixel on 7.1.1??
Sent from my Pixel using XDA-Developers Legacy app

christanya99 said:
Is there a guide for rooting the Rogers Pixel on 7.1.1??
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886 disregard anything about verizon as you do not have that model.
its for the XL but the exact same method applies, just make sure you get the TWRP RC1 zip and image from here
root is here 2.79 SR3

Great, thanks a ton!
Sent from my Pixel using XDA-Developers Legacy app

k.s.deviate said:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886 disregard anything about verizon as you do not have that model.
its for the XL but the exact same method applies, just make sure you get the TWRP RC1 zip and image from here
root is here 2.79 SR3
Click to expand...
Click to collapse
I just rooted successfully but didn't install TWRP. Can I just boot back in through fastboot and install it now?

christanya99 said:
I just rooted successfully but didn't install TWRP. Can I just boot back in through fastboot and install it now?
Click to expand...
Click to collapse
Yes, put the zip on your internal storage and boot into fastboot and then boot into the TWRP image and flash the zip.

k.s.deviate said:
Yes, put the zip on your internal storage and boot into fastboot and then boot into the TWRP image and flash the zip.
Click to expand...
Click to collapse
Uh oh! Just did this now it's booting straight to TWRP...

christanya99 said:
Uh oh! Just did this now it's booting straight to TWRP...
Click to expand...
Click to collapse
Put the TWRP RC1 zip on the internal storage
Fastboot boot TWRP RC1.img
*Might have to do that a couple times for TWRP to properly decrypt.
Flash TWRP RC1 zip to apply it
That's how to get TWRP.
Your saying you did this and when you reboot system from TWRP it just reboots to TWRP?

k.s.deviate said:
Put the TWRP RC1 zip on the internal storage
Fastboot boot TWRP RC1.img
*Might have to do that a couple times for TWRP to properly decrypt.
Flash TWRP RC1 zip to apply it
That's how to get TWRP.
Your saying you did this and when you reboot system from TWRP it just reboots to TWRP?
Click to expand...
Click to collapse
Exactly. I can't boot into the system anymore. Google logo pops up and then straight to TWRP every time.

christanya99 said:
Exactly. I can't boot into the system anymore. Google logo pops up and then straight to TWRP every time.
Click to expand...
Click to collapse
Almost sounds like you fastboot flashed TWRP instead of fastboot boot TWRP. Either way, I believe you will have to flash the factory image and start over. You could try fastboot flashing the stock boot image first to see if that helps.

k.s.deviate said:
Almost sounds like you fastboot flashed TWRP instead of fastboot boot TWRP. Either way, I believe you will have to flash the factory image and start over. You could try fastboot flashing the stock boot image first to see if that helps.
Click to expand...
Click to collapse
Ok, thanks! Will give it a try.
That did it. All is good now. Thanks!

Anyone please let me know the OOS 10 and TWRP/Magisk Situation...

I am currently on OOS 10 OB2/31 and can't seem to find a way to install TWRP and Magisk. Found ways to install TWRP and Magisk via patched boot images on OOS 10 stable but not for OB2/31.... anyone know why it's not as simple as flashing TWRP via fastboot?

I also have a problem
'OOS10beta31' Root

XcutionerX said:
[...] anyone know why it's not as simple as flashing TWRP via fastboot?
Click to expand...
Click to collapse
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.

adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
Thank you for your help, gonna try following those. Hopefully I don't f up and have to do a msm restore. But why would they disable that command?... Just to make everything complicated? Guess I will not stick to Oneplus next year.

XcutionerX said:
But why would they disable that command?
Click to expand...
Click to collapse
Security? Deprecated or soon-to-be-deprecated command? Dunno really, lol.
XcutionerX said:
... Just to make everything complicated?
Click to expand...
Click to collapse
To be fair, the only difference between this method and the old method is just one word and manually rebooting to recovery. You still have to flash the twrp.zip after flashing from bootloader file to install TWRP, so it's not too radically different.

this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332

adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
I have successfully installed TWRP and Magisk with the help of those links. Thank you again for your help.

quizzina said:
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
Click to expand...
Click to collapse
Thank your for the in-depth explanation.

Just download oxygen updater and install 10.0.1 and be done with it

flashed TWRP over boot slot B

I ended up flashing TWRP over my boot slot (B) and now I just boot into TWRP. I have already installed TWRP on boot slot (a). I can't remember which version of oxygenOS I have installed and couldn't find a way to confirm. How can I fix this? Also want to update to latest version of oxygenOS and android. No data on phone yet. phone still connects to computer, adb sideloader and fastboot commands still work work. Thanks

Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.

redpoint73 said:
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
Click to expand...
Click to collapse
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks

doctor_whooves said:
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
Click to expand...
Click to collapse
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success

plasticarmyman said:
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
Click to expand...
Click to collapse
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.

tech_head said:
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
Click to expand...
Click to collapse
in this case the best thing to do is just unbrick using MSM

plasticarmyman said:
in this case the best thing to do is just unbrick using MSM
Click to expand...
Click to collapse
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.

doctor_whooves said:
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
Click to expand...
Click to collapse
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.

hey guys. Not able to flash oos through twrp.
getting "error flashing zip".

tech_head said:
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
Click to expand...
Click to collapse
Doesn't TWRP back up everything including boot partitions?
Is there nothing that will take the entire internal storage and just make a 'bare metal' image of it for restoring.. the whole entire thing, byte for byte? If not, why doesn't this exist? It just seems so logical to me and would be so incredibly useful. Phone borked? No problem. Just re-image it form the archive you made. To me, that is what TWRP is all about, at least conceptually if not technically.

Stuck at TWRP splash screen

I recently updated to MIUI v12.5.1.0.RCDMIXM using a recovery zip through TWRP. A few days later I decided to flash Magisk by patching the boot.img from the same zip and flashed using fastboot.
Everything worked fine until I rebooted to recovery using the Magisk app. Now it's stuck at the TWRP splash screen, can't even reboot or enter fastboot with power and volume buttons because it will always try to boot to TWRP.
What do I need to do to fix this?
This is where I got the TWRP

Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.

VD171 said:
Just erase/format the MISC partition.
This partition holds a "go to recovery" parameter.
Click to expand...
Click to collapse
Okay, but how exactly can I do that? It's been stuck like this since last night and won't go to fastboot with vol keys..

Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.

VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?

VD171 said:
Can you use TWRP ?
If not, you need sp flash tool.
Try to flash boot.img and recovery.img.
Click to expand...
Click to collapse
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash

Reyproject said:
TWRP is stuck at the state in the picture I sent.
I'll try using SP Flash, but I think I remember that Xiaomi devices have SLA auth to prevent unauthorized flashing using SP Flash. Will your scatter file work without it?
Click to expand...
Click to collapse
Exactly.
You need to bypass EDL auth:
[GUIDE] How To bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com

Reyproject said:
I just realized that the zip file or any other version does not include a stock recovery.img...
Do you have the Global v12.5.1.0 stock recovery? Or I could just use any version like vbmeta?
The phone's battery just drained, if I try to plug it would try to boot into twrp again so I kept it unplugged since I need it to be turned off for SP Flash
Click to expand...
Click to collapse
You said "fastboot", so you need the fastboot ROM.
SP flash tool does NOT need the device to be turned off, it just need to REBOOT.
If you try to flash while a reboot to another reboot, it will works perfectly.

Which magisk did you flash? 23 is not working for 9A

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk V23.0 is the BEST MAGISK EVER !

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
It does tho, i've been using it since the first use of this phone (12 and 12.5)

Applewubs said:
It does tho, i've been using it since the first use of this phone (12 and 12.5)
Click to expand...
Click to collapse
Are you still in 12.5? Do you also use a custom recovery in that version?

Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...

yaro666 said:
Which magisk did you flash? 23 is not working for 9A
Click to expand...
Click to collapse
Magisk v23 works just fine, just patch the boot.img file of your ROM version and flash it with custom recovery or fastboot.

Reyproject said:
Are you still in 12.5? Do you also use a custom recovery in that version?
Click to expand...
Click to collapse
Theres one TWRP that doesnt have a splashscreen, in that one just block and unblock the screen while on recovery and it'll work fine. BUT your internal storage isn't going to be accesible, its encrypted and (for some reason) on 12.5 twrp cant unlock the storage, you'll have to do everything on your sdcard

Reyproject said:
Just managed to access a laptop and got to fix the situation. Turns out I can still use adb even though TWRP is stuck on the logo screen.
First tried the `fastboot erase misc` command but misc partition doesn't exist on the device.
Tried `fastboot continue` but won't let me use the command and `fastboot reboot` just makes it go to recovery and get stuck again.
I flashed Orange Fox Recovery and it was still stuck at it's splash screen. So I went back to fastboot and for some reason `fastboot reboot` worked now and booted to system, further restarts are normal now.
Now I'm curious, why won't custom recoveries work with MIUI 12.5? When I tried accessing root, every folder (ex. system) is in this format [1;34system[0m, does it have something to do with that?
Still trying to get the stock recovery, but there's no fastboot rom file for this version yet...
Click to expand...
Click to collapse
I thinks its because they cant unlock the storage, they keep trying and just keeps stuck on trying.