FTM mode (OxygenOS 12) - OnePlus 8T Questions & Answers

DSince I have OxygenOS 12 that the FTM mode (needed to activate VoLTE) doesn't work, pressing the command just reboots for 3 seconds and starts the OS as if it were a normal reboot, Does it work for any of you, and if not, do you know of a solution?

Having the same issue as above

If you have root access, just install attached magisk module.
If you don't have it, there is a way to access engineeringmode on coloros/oos12, but it's a bit complicated.

Related

Bootloop after device got dipped in water -> Volume down button is messing around

Hey folks,
unfortunatly I am not able to boot my device properly since it fell into the bath tub. It boots into the download mode and stops after 5% saying Software install failed! That's because there is no .IMG on the SD Card I guess. Not sure what to do, I searched for a stock rom .IMG and put it on SDCARD/dload and got a good feeling that, maybe, it'll boot normally after installing this "update". So it boots into download mode and the update process is working just fine, but after the update successfully ends with 100% it reboots and starts the procedure over and over again.
I tried different button combinations to avoid booting the download modus - without success. I tried to get adb access by connecting it to the computer but just got an unauthorizised device - I never enabled usb debugging -.-
But then, somehow, it booted into safety mode and I was able to enable developer options and usb debugging. And I found the reason for the download mode bootloop. It turns out that the volume buttons are messed up. Volume up is not responding and volume down seems to be pressed all the time or repeatingly pressed in really short terms. Since my device is not rooted I installed an apk that allows me to disable the hardware buttons without root. But I found no way to run this app in safety mode. Also I have no access to the system files to change the key bindings on my own. I hoped to find a way to force normal boot out of safety mode but just got it booting up into the download mode again.
And there I am, my device is booting into download mode and nothing else. I don't know if it was just a lucky moment that the device booted into safety mode or if i did some magic that worked. But i can't get it to do something else than booting the download mode right now.
Do you have any idea what I can do without opening the device to unplug the buttons physically or to root it? If neccessary I am willing to do so but it's not the way I'd like to do.
Regards
Schmunzelhummel

Rooting Help - Virgin Mobile Galaxy J3 - Volume up button unusable :(

Heya peoples, I have a problem and am hoping for some help in a work around.
I am trying to root my J3 but my volume up button does not work. I have adb installed, and the correct drivers for my phone. I can use adb command to reboot to the bootloader and it brings me to the Odin "downloading" screen. I can then use the program to install TWRP so I can root. Everything goes fine up until this point. After TWRP is installed there is a single massive problem I am hoping there is a work around for. My volume up button does not work. I can only reboot to recover using adb once the phone boots up, and I read that if you let that happen it overwrites TWRP with the stock recovery (which is what happens when I do this). I read that you have to reboot directly from the downloading screen into recovery using Vol up and home and power. But I can't do that since my Vol up doesn't work. When I am at the download screen after installing TWRP none of the adb commands work so I can't reboot directly to recovery to access TWRP the first time. I hope this all makes since, and I hope someone has some advice because as far as I can tell I can't continue passed this point without a working volume up button.
A little more info in case it matters. When using adb command prompt I have to type ".\adb" instead of "adb" as the tutorials say. When I do ".\adb devices" my device shows up as connected. After rebooting to the bootloader using adb, typing ".\fastboot devices" shows nothing is attached, and any command I try to put in results in "waiting on devices". Checking the device management at this point does not show any unknown usb devices (one guide I read said if fastboot wasn't recognizing to check to update drivers if something was showing as unknown usb".
Basically hoping there is some way of booting directly to recovery from bootloader without having to use the vol up key combination so I can access TWRP for the first time. Any help at all is appreciated. I realize having a working volume button would take all the headache out of this but unfortunately fixing it is not an option at the moment.
Edit: I have also unlocked the bootloader using the Crom Services app from samsung, and have developer options and usb debugging enable.
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
CopaseticDream said:
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
Click to expand...
Click to collapse
Can this device even be rooted? Doesn't virgin lock their devices?
In any case if you flash twrp to the boot partition (rename it to boot.img) it'll boot directly to twrp then just use twrp to flash to the recovery partition.
Reflash the stock boot.img back to the boot partition.

Phone only booting to bootloader after flashing magisk

Phone: OnePlus 7 Pro
Build number: Oxygen OS 10.3.0 GM21AA
Anndroid Version: 10
Model: GM1910
Hello Everyone,
So today I did a fresh install on my device using the latest version of O0S (10.3.0). I used the latest unofficial TWRP and flashed the latest version of magisk as well. So I installed swift installer, vanced youtube and renovate rice, had no idea ever after rebooting a few times and to install my theme.
I then installed adaway, afterwards I rebooted it in order to get everything saved correctly and everything was ok. Afterwards I decided to whitelist a website and after whitelisting and rebot this time the phone booted into bootloader.
So I flashed the magisk uninstaller and rebooted and the phone booted up without any issues. I tried rebooting and flashing magisk again and got the same issue once again. Tried uninstalled again and it booted again. So I tried flashing magisk one more time and then trying using the "magisk mod uninstaller" and it gave me an error saying that magisk wasn't installed.
Can anyone help me with this issue?
This will reset your phone to factory new. You will lose your data.
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
Some clarification:
1. Download the correct .zip and extract it.
2. Open the folder where you extracted the .zip file and run "MsmDownloadTool V4.0.exe" by double clicking it. Wait for it to load.
3. Power off your phone.
4. Connect a USB cord to your Windows based PC. Keep the other end unplugged from your phone for now but within quick reach.
5. Hold the Volume UP and Volume DOWN buttons and while holding ONLY those two buttons plug the USB cord into your phone.
6. You should see your phone appear in the application. You can release the Volume Up and Volume Down buttons when your phone appears.
7. You have 10 seconds to hit the START button in the app or you will have to unplug and go back to step 3.
The app will reset your phone to factory like new. You will have to unlock your bootloader again. Your phone should be like the day you got it.
I had an issue with Adaway and Magisk bootlooping as well.
Not sure what causes it though.
Peace.
ninrocket said:
This will reset your phone to factory new. You will lose your data.
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
Some clarification:
1. Download the correct .zip and extract it.
2. Open the folder where you extracted the .zip file and run "MsmDownloadTool V4.0.exe" by double clicking it. Wait for it to load.
3. Power off your phone.
4. Connect a USB cord to your Windows based PC. Keep the other end unplugged from your phone for now but within quick reach.
5. Hold the Volume UP and Volume DOWN buttons and while holding ONLY those two buttons plug the USB cord into your phone.
6. You should see your phone appear in the application. You can release the Volume Up and Volume Down buttons when your phone appears.
7. You have 10 seconds to hit the START button in the app or you will have to unplug and go back to step 3.
The app will reset your phone to factory like new. You will have to unlock your bootloader again. Your phone should be like the day you got it.
I had an issue with Adaway and Magisk bootlooping as well.
Not sure what causes it though.
Peace.
Click to expand...
Click to collapse
I think it is Adaway, I'm having the same problem :/ Oh well
tuff3r said:
I think it is Adaway, I'm having the same problem :/ Oh well
Click to expand...
Click to collapse
Haven't had any issues with it myself. But if you end up in a bootloop after installing a magisk module, get to twrp and navigate to /data/adb/modules in the file explorer. There you can delete problematic modules without resetting the phone.

Hard bricked OnePlus 7

My OnePlus 7 oxygenos 10.3.1 got bricked when I was trying to uninstall Magisk from an option in Magisk manager app. It showed Magisk successfully uninstalled but during reboot bootloader unlocked menu appered and screen goes blank. Power button not working nor recovery mode ( volume down + power) but when I try to fastboot it simply shows bootloader unlocked menu and screen goes blank.
I tried MSM tool but phone not detected by pc even in device manager nothing shows.
Anyone can help me plz.
Edit...
Charging not showing and not any sign of connection when try to connect with pc

OP7PRO dead (black screen, won't turn on)

I'm having issues with my OnePlus 7 Pro running Android 11 OxygenOS. It won't turn on at all, the screen is black, it's not detected by ADB.
It is my first time rooting an Android phone, I did the following to get to this result:
1. I used an handy tool called Tool All In One to unlock the bootloader https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3930862/
2. I received a notification to update OxygenOS, I did so and rebooted
3. I flashed TWRP 3.6.0 using Tool All In One
4. I used the TWRP menu on the phone to install Magisk 23, after installing I wiped Dalvik
5. After it booted, I installed the Magisk app and used it to install Magisk using the recommended “direct install” method
6. I saw a guide doing things somewhat differently, I installed the Magisk module TWRP A/B Retention Script but I didn't do anything else the guide said because I did things in the wrong order (if it was to be considered the true way)
7. I wanted to boot to TWRP but I was unsure how. I pressed “Reboot EDL” on Tool All In One to see what it does (I didn't look it up what it actually was for, I just clicked on)
8. The phone is turned off/black screen, seems dead. Pressing and holding the power button does nothing, ADB doesn't detect it.
Well don't click if you don't know :|
First thing, try to press the power button for a long time and look what happen.
I think you put your phone in Qualcomm EDL mode to completely reset the phone.
draentor said:
Well don't click if you don't know :|
First thing, try to press the power button for a long time and look what happen.
I think you put your phone in Qualcomm EDL mode to completely reset the phone.
Click to expand...
Click to collapse
I held the power button for like a minute, no dice.
I fixed it. Apparently I was too square brained to try vol up + power. It exited the EDL mode that way.

Categories

Resources