Related
Hi,
I recently flashed a custom ROM(Lineage OS 15.1) using this tutorial. Didn't like it so decided to switch back to stock. Trouble is I didn't have Stock ROM. Found one here and flashed it. It worked, sorta. My IMEI numbers were cleared. I have them on my box but no .bak file. Read somewhere that some apps can write IMEI but needed root and Xposed Framework.
Rooted my device using this tutorial and tried to install Xposed using this tutorial.
However,this caused my phone to get stuck in a bootloop.
Tried reset from stock recovery. Even though it says reset success, still stuck in bootloop. Also cleared Cache.
Tried flashing stock ROM and Lineage OS using fastboot flash system ***.img,
Code:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/7 (456507 KB)...
OKAY [ 19.324s]
writing 'system' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 19.402s
I can't seem to flash recovery or system.
Have I bricked it? Please help me out.
HarryPotterWannabe said:
Hi,
I recently flashed a custom ROM(Lineage OS 15.1) using this tutorial. Didn't like it so decided to switch back to stock. Trouble is I didn't have Stock ROM. Found one here and flashed it. It worked, sorta. My IMEI numbers were cleared. I have them on my box but no .bak file. Read somewhere that some apps can write IMEI but needed root and Xposed Framework.
Rooted my device using this tutorial and tried to install Xposed using this tutorial.
Now,
My phone is stuck in a bootloop.
Fastboot opens, but FRP is locked. (PHONE Unlocked).
all fastboot commands FAILED (remote: Command not allowed), except
fastboot devices, which shows my device.
I can't flash recovery or system.
Have I bricked it? Please help me out.
Click to expand...
Click to collapse
Can you still go into erecovery?
Sent from my HUAWEI BKL-L09 using XDA Labs
youtuber123 said:
Can you still go into erecovery?
Sent from my HUAWEI BKL-L09 using XDA Labs
Click to expand...
Click to collapse
Yes. attempted factory reset and cache. succeeds both, still stuck in boot loop
HarryPotterWannabe said:
Yes. attempted factory reset and cache. succeeds both, still stuck in boot loop
Click to expand...
Click to collapse
I'm not asking for the recovery but the Erecovery
The one who should help you in this situation
Sent from my HUAWEI BKL-L09 using XDA Labs
youtuber123 said:
I'm not asking for the recovery but the Erecovery
The one who should help you in this situation
Sent from my HUAWEI BKL-L09 using XDA Labs
Click to expand...
Click to collapse
Yes, it boots into erecovery. I don't have twrp, and can't seem to flash one because if command not allowed error.
I have followed this guide to a T (https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/).
And I am encountering 2 issues.
First - I flash everything as describe Magisk, TWRP. When I reboot I don't have root and magisk isn't installed. When I download the zip through magisk it says it failed to "unable to unpack image...' I have no root, no magisk.
Second - If I try to just do a flash the TWRP img from ABD while in bootloader. Then go in to TWRP and flash magisk and not do the option to flash TWRP zip my phone wont' boot back to system.
I have tried to sideload the magisk zip as well and that hasn't working.
I am on the Dec security patch.
zrex said:
I have followed this guide to a T (https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/).
And I am encountering 2 issues.
First - I flash everything as describe Magisk, TWRP. When I reboot I don't have root and magisk isn't installed. When I download the zip through magisk it says it failed to "unable to unpack image...' I have no root, no magisk.
Second - If I try to just do a flash the TWRP img from ABD while in bootloader. Then go in to TWRP and flash magisk and not do the option to flash TWRP zip my phone wont' boot back to system.
I have tried to sideload the magisk zip as well and that hasn't working.
I am on the Dec security patch.
Click to expand...
Click to collapse
At this point flash the stock boot image to both partitions with fastboot. And make sure you have the latest sdk platform tools, r28. Then boot twrp.img with fastboot. Once in twrp install the twrp.zip. Then boot back into recovery, it should be twrp. Then install the magisk zip.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
At this point flash the stock boot image to both partitions with fastboot. And make sure you have the latest sdk platform tools, r28. Then boot twrp.img with fastboot. Once in twrp install the twrp.zip. Then boot back into recovery, it should be twrp. Then install the magisk zip.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Do you know where I could find those boot images and how to install them? I have looked, but am only finding stock roms.
zrex said:
Do you know where I could find those boot images and how to install them? I have looked, but am only finding stock roms.
Click to expand...
Click to collapse
Download the factory image, it's a zip file. Extract the zip. Inside is another zip file, extract that one too. In there you'll find the boot.img
Sent from my [device_name] using XDA-Developers Legacy app
Do not flash twrp, only boot to twrp using fastboot commands
jd1639 said:
Download the factory image, it's a zip file. Extract the zip. Inside is another zip file, extract that one too. In there you'll find the boot.img
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I got back to factory, thank you. Still struggling to get root and magisk.
acidspider said:
Do not flash twrp, only boot to twrp using fastboot commands
Click to expand...
Click to collapse
so just use the img for TWRP, then install the Magisk?
acidspider said:
Do not flash twrp, only boot to twrp using fastboot commands
Click to expand...
Click to collapse
Okay, I have just flash the twrp img using the fastboot commands. I installed the Magisk zip and reboot the system. Now it is just looping from the G logo, then it loops twice and then just prompts me to factory reset. I can get back to normal by flashing the stock boot images.
Because you are flashing twrp, do not use the flash twrp command, use the boot twrp image
acidspider said:
Because you are flashing twrp, do not use the flash twrp command, use the boot twrp image
Click to expand...
Click to collapse
+1. OP, you need to boot twrp, not flash it. Use the command, "fastboot boot twrp.img" (use the full name of your twrp image file) But before you do that flash the stock boot.img to both slots again. fastboot flash boot_a boot.img. Then do the same for boot_b.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
+1. OP, you need to boot twrp, not flash it. Use the command, "fastboot boot twrp.img" (use the full name of your twrp image file) But before you do that flash the stock boot.img to both slots again. fastboot flash boot_a boot.img. Then do the same for boot_b.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I am having the same problem as OP, and spent 6 hours trying to solve it. I was hoping my problem was as simple as using "flash boot" instead of "fastboot boot" but, I just tried this now to no avail.
Any other advice?
mellerad said:
I am having the same problem as OP, and spent 6 hours trying to solve it. I was hoping my problem was as simple as using "flash boot" instead of "fastboot boot" but, I just tried this now to no avail.
Any other advice?
Click to expand...
Click to collapse
I always ask to make sure you have the latest sdk platform tools? You need r28. Start with that.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I always ask to make sure you have the latest sdk platform tools? You need r28. Start with that.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have triple-checked this as well and am on the latest set of Platform Tools.
I've read that some newer USB-C cables could cause an issue? I'm using a Thunderbolt 3 cable to a Thunderbolt 3 port on my PC, but not getting any flashing errors.
I also haven't re-flashed the Dec 5 update yet, but because I was coming off a clean reset (due to bootloader unlocking) I didn't think it would be necessary.
mellerad said:
I have triple-checked this as well and am on the latest set of Platform Tools.
I've read that some newer USB-C cables could cause an issue? I'm using a Thunderbolt 3 cable to a Thunderbolt 3 port on my PC, but not getting any flashing errors.
I also haven't re-flashed the Dec 5 update yet, but because I was coming off a clean reset (due to bootloader unlocking) I didn't think it would be necessary.
Click to expand...
Click to collapse
Usb c to c seems like it's not working well. If you have an a/b to c try that. Are you able to flash the stock boot.img and have the device boot?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Usb c to c seems like it's not working well. If you have an a/b to c try that. Are you able to flash the stock boot.img and have the device boot?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes flashing a stock boot.img works and I'm able to use the phone as normal. I can also flash the TWRP.zip from the TWRP.img. I just can't get Root to take hold with either method of flashing Magisk (zip from TWRP or patched_boot.img from Bootloader).
I'll try a USB-A to USB-C cable and see how that goes.
mellerad said:
Yes flashing a stock boot.img works and I'm able to use the phone as normal. I can also flash the TWRP.zip from the TWRP.img. I just can't get Root to take hold with either method of flashing Magisk (zip from TWRP or patched_boot.img from Bootloader).
I'll try a USB-A to USB-C cable and see how that goes.
Click to expand...
Click to collapse
Also, when you boot into twrp run the magisk uninstaller, then the magisk install zip. If you're going to have twrp permanently, install the twrp zip and boot back to recovery before the magisk zips.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Also, when you boot into twrp run the magisk uninstaller, then the magisk install zip. If you're going to have twrp permanently, install the twrp zip and boot back to recovery before the magisk zips.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Followed all these steps, and USB-A to USB-C is still a fail.
I have no idea why this isn't working and it's driving me absolutely crazy
mellerad said:
Followed all these steps, and USB-A to USB-C is still a fail.
I have no idea why this isn't working and it's driving me absolutely crazy
Click to expand...
Click to collapse
When you boot twrp with fastboot can you boot to recovery (twrp) from within twrp? Also, before you try to boot twrp flash the stock boot.img to both slots. And make sure the boot image is from the same pie update as you currently have on your device, ie if you have the Dec update user the boot image from that factory image.
Edit, also, just make sure, when you boot into the bootloader run the command fastboot --version. I was sure I had updated the sdk tools but when I copied fastboot and adb to the folder I use the old ones where still there. I spun my wheels on that for awhile.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
When you boot twrp with fastboot can you boot to recovery (twrp) from within twrp? Also, before you try to boot twrp flash the stock boot.img to both slots. And make sure the boot image is from the same pie update as you currently have on your device, ie if you have the Dec update user the boot image from that factory image.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
1) Yes I can boot to TWRP Recovery from TWRP.img after installing the TWRP.zip
2) My stock boot.img is from the Dec 5 Factory Image, which is the version of Android I'm currently running.
Going to try flashing the entire December 5 Factory Image now and then attempting Magisk installation again.
mellerad said:
1) Yes I can boot to TWRP Recovery from TWRP.img after installing the TWRP.zip
2) My stock boot.img is from the Dec 5 Factory Image, which is the version of Android I'm currently running.
Going to try flashing the entire December 5 Factory Image now and then attempting Magisk installation again.
Click to expand...
Click to collapse
Good. That was going to be my next suggestion, flashing the factory image. Time to start from a clean piece of paper.
Sent from my [device_name] using XDA-Developers Legacy app
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
You haven't given enough info, tell us step by step how your "Bootloader is unlocked".
We would need to know if you did it properly, you probably need to go into the recovery and perform a "Full wipe". Unlocking the bootloader usually does that anyway.
The normal method is:
Enabled developer settings by pressing the version number in the about section 7 times and entering your pin
Copy the adb developer folder from the mounted OnePlus driver partition you usually get on your computer when attaching the phone, into a folder on your hard drive, and enable adb in developer settings.
In developer settings enable "OEM unlocking"
Reboot into fastboot mode
Open a command window (with admin privileges) in the folder you copied to your hard drive (In Windows, hold down shift and right click inside the folder, then click "Open Command Window..."
Run the command "fastboot oem unlock"
Accept the prompt shown on the phone
This will wipe the phone back to factory reset so ensure you have backed up your data, although you should be doing that before you even start.
Flash the appropriate TWRP recovery partition (which afaik isn't even available yet so I'm not sure why you would unlock the bootloader so soon to be honest
If you didn't perform those steps or performed them in the wrong order then you've done it wrong.
Performing a factory reset in the recovery partition may get it booting again but it's hard to know with the minimal information you've provided.
Although again, why are you unlocking the bootloader when there hasn't been a TWRP version released yet? You won't be able to flash anything, not even Magisk.
I've unlocked bootloader by command of OEM unlocking.
After than the unlock, I rebooted it's again And installed some Magisk file, which made it stuck at fastboot.
I can't access the Recovery nor can restart Phone.
All I can do is switched it off And get back into fastboot again after.
Yeah, you can't flash things with the default recovery (That's just made for flashing the default builds), that's most likely why. Magisk was made to be flashed with TWRP.
Did you use the test TWRP here? If so, then go to that thread for help.
If you can get into the OnePlus recovery you could maybe grab a build from here and flash the default rom back, then start again using the guide I showed you but, tbh, I would wait until a good TWRP build is established and Magisk is confirmed to be working.
That thread also looks like it has the default recovery image too so you can flash that back on the phone with :
fastboot flash recovery filename (Just put the recovery image into the same folder as your adb.exe and fastboot.exe
Then see if you can reboot into it and flash the stock rom back on from the same thread.
How can I get things done back, all I've is fastboot.
It's a New set, please help (
dmishra639 said:
How can I get things done back, all I've is fastboot.
It's a New set, please help (
Click to expand...
Click to collapse
If you have fastboot, I've just told you how to get the default recovery back in above.
---------- Post added at 05:45 PM ---------- Previous post was at 05:28 PM ----------
Reading that thread again, flashing recovery is not as simple as it used to be due to the A/B partition model used now, so you'll need to read the instructions shown for recovery. My guess is that you didn't read them properly and flashed the recovery to the wrong partition. If you have flashed that TWRP then you need to seek support in that thread.
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
dmishra639 said:
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
Click to expand...
Click to collapse
This will sound stupid, but I had similar issues with the pixel and it was due to drivers and the port. Tried from a different machine and worked. Do you have the luxury to do so ?
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Grab this fastboot rom and flash...
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
LLStarks said:
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
Click to expand...
Click to collapse
paatha13 said:
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
dmishra639 said:
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
Click to expand...
Click to collapse
I forget the command, but change the boot slot and try to reboot.
tech_head said:
I forget the command, but change the boot slot and try to reboot.
Click to expand...
Click to collapse
Fastboot flash boot C://path/to/recovery.img
SysAdmNj said:
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
Click to expand...
Click to collapse
You can read over here on 6T device details of how thing work with A/B partition.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
https://twrp.me/oneplus/oneplus6t.html
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Also follow this thread about 7 Pro situation and how well work over time
[RECOVERY][3.3.1-2][guacamole]Unofficial TWRP recovery for OnePlus 7 Pro(Testing)
Sent from my iPad using Tapatalk Pro
joemossjr said:
Fastboot flash boot C://path/to/recovery.img
Click to expand...
Click to collapse
Man, thank you so much
You literally made my day,
Wht I've did wrong in a flow was I had given the command: fastboot flash boot and the magisk location.
That was a stupidity, all I forgot was the command.
Now I used the same command and then used oxygen os fastboot flashable all bat file, as suggested by a member.
And here's my phone back. )
Thanks
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
dmishra639 said:
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
Click to expand...
Click to collapse
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Robert235 said:
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Click to expand...
Click to collapse
Man I've a 2gb daily add on (for 3 months), which will only gonna work with my previous device (Redmi note 5 pro).
So, I've to change OnePlus as Note 5 Pro as same.
I've did that tons of time on my past phone,it never did a brick TBH.
Hi,
I have unlocked my Note 7 Pro and I was trying to install twrp via fastboot. Fastboot devices command showed the device and so I went ahead with fastboot flash recovery command. Executing the command recognized the recovery image but it didn't flash. the command finished in 2 seconds. So then I tried fastboot -w to erase userdata. Since then it has stop loading.
I am unable to flash the recovery and I am unable to boot into the phone but I can boot into fastboot. Please help me get out of this mess.
From fastboot reinstall twrp. Then proceed.
Sent from my Redmi Note 7 Pro using Tapatalk
newtonc said:
From fastboot reinstall twrp. Then proceed.
Sent from my Redmi Note 7 Pro using Tapatalk
Click to expand...
Click to collapse
Thanks. Formatting from TWRP solved my issues.
No matter what I do, or which tool I use, I am unable to install TWRP in my Oneplus, GM1913 running Oxygen OS Open Beta 10, had the same issue running OOS 10.0.4.
Whenever I try to "fastboot boot twrp.img" it just leads to the fastboot screen and stands like that not doing anything.
If I go and "fastboot flash recovery twrp.img" it brings me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.631s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.640s
Which leads me nowhere as everything's the same.
Can anyone please help me? It's driving me nuts and I can't seem to find any answere online. I'm using the original cable, tried multiple USB ports (2.0/3.0) and I'm using the latest Guacamole version of both .img and .zip installer.
Thank you very much for your help.
All you gotta do is go to fastboot mode then type in fastboot boot TWRP 3.3.1-79 Unified Unofficial Q by mauronofrio then it'll redirect you to twrp and all you need to do is download the most recent twrp update and install it using adb sideload
Sent from my OnePlus 7 Pro using Tapatalk
AxxPyrtlexx20 said:
All you gotta do is go to fastboot mode then type in fastboot boot TWRP 3.3.1-79 Unified Unofficial Q by mauronofrio then it'll redirect you to twrp and all you need to do is download the most recent twrp update and install it using adb sideload
Sent from my OnePlus 7 Pro using Tapatalk
Click to expand...
Click to collapse
You didn't follow me there, that's the TWRP version I'm using, that takes me to fastboot mode and doesn't go anywhere.
jpedrojesus said:
You didn't follow me there, that's the TWRP version I'm using, that takes me to fastboot mode and doesn't go anywhere.
Click to expand...
Click to collapse
Have you tried previous versions? Like 76? I haven't tried 79 myself so maybe it's broken.
Sent from my OnePlus 7 Pro using Tapatalk
AxxPyrtlexx20 said:
Have you tried previous versions? Like 76? I haven't tried 79 myself so maybe it's broken.
Sent from my OnePlus 7 Pro using Tapatalk
Click to expand...
Click to collapse
Well, 76 worked, thank you for the advice! cheers
jpedrojesus said:
Well, 76 worked, thank you for the advice! cheers
Click to expand...
Click to collapse
No problem!
Sent from my OnePlus 7 Pro using Tapatalk