So I have Android 11 update on my oneplus7 pro waiting to download.Can someone please help me? I was trying to root my 7 Pro with fastboot since I have oos11, and the device went to the Qualcomm CrashDump mode. I was able to get back to fastboot and tried to flash the stock images but it wouldn't let me flash many of them because they are critical partitions. After that the OS still wouldn't boot so I went to stock recovery and wiped the device to try to flash the stock images again. BUT NOW, fastboot will not work, I guess becuase Debugging is not on anymore, but there's no way for me to boot the device to turn it on, and I'm not having much luck using MSM tool because it's not easy to use because of all of this driver BS. What the hell do I do?
EDIT: LOL Nevermind I just needed the Oneplus Drivers.
Well since, there is no TWRP that works with A11 yet. Your safest bet would be to install the update, DONT REBOOT, install Magisk to inactive slot. Disable or remove modules from Magisk. Reboot , done.So I have Android 11 update on my oneplus7 pro waiting to download.
How would you recommend me upgrading my phone with root?
What I've done in the past with andriod 10 was download the update, install it, then fastboot with twrp & install the lastest version on Magisk.
Try this ...I am on Lineage OS 18.1 with stock Lineage recovery. I want to go back to stock Oxygen with locked bootloader. Can I use this method to do this? If not can someone please link me to the appropriate thread. Thank you
Same problem here, it went disasterously wrong for me too on my OnePlus 7 Pro LineageOS 17.1 to 18.1 except I even ended up having to use MSM tool to unbrick because it kept rebooting to bootloader even after other stuff like flash-all.bat etc.I tried updating to LineageOS 18.1 using the instructions at https://wiki.lineageos.org/devices/guacamole/upgrade and it was a disaster.
From the fastboot mode menu, 'Recovery mode' was not booting into recovery so I tried flashing the 18.1 recovery image. That was booting but not consistently. Anyway, when I tried to sideload the new version of LineageOS nothing happened and it was stuck in a fastboot loop.
Try the following and stick with a 17.1 version of recovery for LineageOS 18.1 (this works for me anyway).
To get out of this fastboot loop:
Note:
- Go to https://sourceforge.net/projects/fastbootroms/files/OnePlus 7 Pro/
- Download and find images.zip
- In fastboot mode, run 'fastboot update images.zip'
- Be prepared for weird stuff to happen but try to get into fastboot mode to flash a known working recovery image which will probably be a 17.1 version
- From there it should be like a standard install
- Boot into recovery
- Sideload LineageOS 18.1
To poweroff from the 'the bootloader is unlocked' splash screen (or the new Crashdump Mode):Hold power, volume-up, and volume-down buttons for ~3 to ~10 secondsWhen powered off:Always start with USB unpluggedTo enter recovery mode:Hold power and volume-down buttons for ~5 to ~ 10 secondsTo enter fastboot mode:Hold power, volume-up, and volume-down buttons for ~3 seconds
I hope this helps someone. Cheers
Just want to confirm that we can flash the international ROM to a T-mobile variant. Did you get dual sim? Thanks!Although it said not for branded devices I used this on a T-Mobile variant with an unlocked bootloader that I had previously converted to international firmware. I was stuck in the bootloader and my phone would not boot into anything else. The MSM tool wasn't working either. This tool revived my device. Thank you! Everything works fine and I have noticed no issues whatsoever.
I've got a TMO OP7P that I converted to INternational. All was fine on Android 10, but after upgrading to international Android 11, I had crazy screen issues when it would sleep/wake/switch to and from 60hz and 90hz refresh rates. Putting it back on the TMO software seems to have helped. YMMVJust want to confirm that we can flash the international ROM to a T-mobile variant. Did you get dual sim? Thanks!
9.5.7 for those that want it
OOS 9.5.7 GM21AA International version
This is only meant for GM1915 converted OnePlus 7 Pro or GM1917 actual international version from OnePlus direct. Thanks.
You will need to apply it locally and re-root and flash twrp again from magisk then flash magisk from twrp in recovery mode.
I have the same issue.My phone is stuck in a bootloop after falling the "Flash-all.bat" (It goes from logo back to "bootloader is unlocked". I can still enter and execute commands in fastboot. Should I have used the Flash- al partitions. bat?
Any tips to help?
Try rebooting into stock recovery after flashing the fastboot rom and reset/factory reset. That always worked for me.Hello!
please, I really need help!
I got Oneplus 7 Pro, Model GM1913, Build: ...GM21BA. I flashed via flash-all.bat, I used this "
10.0-GM21BA-OnePlus7ProOxygen_21.E.20_OTA_020_all_1909172050_2ce34409-FASTBOOT.zip" and after flashing, I get "Qualcomm ChrasDump Mode: dm-verity device encrypted Force Dump kernel_restart"
"
Please please please, what can I do? Any help is really appreciated!!
View attachment 5382893
Sadly, that's doesn't work work me :/Try rebooting into stock recovery after flashing the fastboot rom and reset/factory reset. That always worked for me.
You saved my phone! Thank you sooo much!Use the MSM tool to reset factory your OnePlus 7pro and then do all the update to last Android 11.0.2
=> https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
What android number are you on that makes a significant differenceTry rebooting into stock recovery after flashing the fastboot rom and reset/factory reset. That always worked for me.
You may have to do it manually and go through all of the images and Flash manually but the boot image and recovery image are the main two that you have to have right rightWhat android number are you on that makes a significant difference
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
fastboot flash persist persist.img
fastboot boot TWRP.img
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
I know you said not for branded devices, are the partitions different for these devices?