Related
Ive downloaded TWRP.img from official site
unlocked BL > fastboot boot twrp.img
i get this error
"failed (remote: 'unknown command')
any ideas?
ive even used the MSM tool to go back to 9.5.3
unlocked BL
rebooted BL and tried "fastboot boot twrp.img" with the same error.
i think if you update to 9.5.8 the bootloader no longer accepts fastboot boot commands.
virtyx said:
Ive downloaded TWRP.img from official site
unlocked BL > fastboot boot twrp.img
i get this error
"failed (remote: 'unknown command')
any ideas?
ive even used the MSM tool to go back to 9.5.3
unlocked BL
rebooted BL and tried "fastboot boot twrp.img" with the same error.
Click to expand...
Click to collapse
9.5.3 does not have that capability, update to 9.5.4
Bradl79 said:
9.5.3 does not have that capability, update to 9.5.4
Click to expand...
Click to collapse
i have updated to 9.5.8 via fastboot same problem
ill try 9.5.7 via local updater.
Confirmed working on 9.5.4.
Not sure about others yet.
virtyx said:
i have updated to 9.5.8 via fastboot same problem
ill try 9.5.7 via local updater.
Click to expand...
Click to collapse
slayerh4x said:
Confirmed working on 9.5.4.
Not sure about others yet.
Click to expand...
Click to collapse
ok works on 9.5.7 via local updater
ill try 9.5.8 i think the fastboot updater breaks this functionality somehow because i fastbooted 9.5.7 and it didnt work earlier. but doing it via local updater works.
virtyx said:
Ive downloaded TWRP.img from official site
unlocked BL > fastboot boot twrp.img
i get this error
"failed (remote: 'unknown command')
any ideas?
ive even used the MSM tool to go back to 9.5.3
unlocked BL
rebooted BL and tried "fastboot boot twrp.img" with the same error.
Click to expand...
Click to collapse
Are you typing in 'twrp.img' or dragging and dropping the actual file into adb?
I tried the command with 9.5.8 and it works well with both CMD and Powershell using minimal ADB files. Looking well, not sure if twrp official is able to boot that way or is meant to be used for just flashing. maybe the one in the guide twrp-3.3.1-29, 30,31 etc-guacamole.img are the ones you should use.
GUGUITOMTG4 said:
I tried the command with 9.5.8 and it works well with both CMD and Powershell using minimal ADB files. Looking well, not sure if twrp official is able to boot that way or is meant to be used for just flashing. maybe the one in the guide twrp-3.3.1-29, 30,31 etc-guacamole.img are the ones you should use.
Click to expand...
Click to collapse
Just tested and I agree. Try the latest Unofficial TWRP
Bradl79 said:
Just tested and I agree. Try the latest Unofficial TWRP
Click to expand...
Click to collapse
Doesn't work if you flash the rom via fastboot for some reason, flashed via local update and it worked
virtyx said:
Doesn't work if you flash the rom via fastboot for some reason, flashed via local update and it worked
Click to expand...
Click to collapse
I think this has something to do with slot A/B. I saw other folks having problems with "fastboot boot" for TWRP not working, until they switched slots.
redpoint73 said:
I think this has something to do with slot A/B. I saw other folks having problems with "fastboot boot" for TWRP not working, until they switched slots.
Click to expand...
Click to collapse
hmm maybe
i just flashed zip in local updater and it worked again.
hi guys , how to flash using local updater ? i have the same case i am new
Guys , I am new here , I had a stuck in fastboot then using msm tool back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
flash stock rom using fast boot
new_world_2006 said:
Guys , I am new here , I had a stuck in fastboot then using msm tool back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
Click to expand...
Click to collapse
I just got my phone 2 days ago. So I started on 9.5.3 or something. Upgraded to 10 and rooted it by following a guide which is just the usual root method for me but I didn't want to screw anything up.
So I suggest just stay unrooted and upgrade to A10. Then root like normal (fastboot boot twrp, flash twrp zip, flash magisk). That's all I did and I'm having no issues on my phone.
I flashed International Firmware
I flashed DP3
OEM UNLOCKED (No Service--- Expected)
Ok now I need to flash a custom rom to get service back which means... flashing TWRP....
Try booting TWRP img nope doesn't work
I talk to people in TWRP they said its because fastboot commands arn't present on DP3 and to download magisk manager and patch a stock boot img.
Grabbed stock IMG from 9.5.10: https://androidfilehost.com/?w=files&flid=294812
moved to Phone, Patched with Magisk Manager, Moved back to pc
adb reboot fastboot
fastboot boot magisk_patched.img (FAILED)
fastboot flash boot magisk_patched.img (Successful)
fastboot reboot
Bootloader (select start option)
Loops into bootloader
Select Recovery
Loops into bootloader
I am literally losing my mind.
I've been trying to get TWRP/ROOT for almost 4 hours I'm starting to Crack someone please dear god help me.
Did you try msm back to stock and start over?
Its a bit of extra work, but it usually works for a non-expert like me when I'm beyond my knowledge.
Also, iirc there's no reason to flash magisk if you're going to flash twrp cuz twrp unroots the device?
I would try msm back to international > unlock bootloader > fastboot flash boot twrp.img > flash twrp installer in twrp > flash magisk in twrp > flash your new rom in twrp.
sydsick42069 said:
Did you try msm back to stock and start over?
Its a bit of extra work, but it usually works for a non-expert like me when I'm beyond my knowledge.
Also, iirc there's no reason to flash magisk if you're going to flash twrp cuz twrp unroots the device?
I would try msm back to international > unlock bootloader > fastboot flash boot twrp.img > flash twrp installer in twrp > flash magisk in twrp > flash your new rom in twrp.
Click to expand...
Click to collapse
You can't flash TWRP from adb on DP3
:/ gives error command
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
So as said before use the msm download tool and start over
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
Right, that's why I was suggesting you msm back to international which would put you on 9.5.3(?)
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
sydsick42069 said:
Right, that's why I was suggesting you msm back to international which would put you on 9.5.3(?)
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
Click to expand...
Click to collapse
Unless your using DP3
so even though I can be on international, Without DP3 you can't bootloader unlock.
You can't unlock the bootloader on T-Mobile phones.
Virus1x said:
Unless your using DP3
so even though I can be on international, Without DP3 you can't bootloader unlock.
You can't unlock the bootloader on T-Mobile phones.
Click to expand...
Click to collapse
I'm not sure where you got that info, but it's definitely wrong.
Tmobile has a standard unlocking procedure, or you can utilize something like this or this if your device is not paid off yet.
However... if you are attempting the dp3 unlock method found here, and as of right now you are still locked, its because you skipped the actual unlock procedure. Which is literally steps 1 & 2 in this guide, attached in the previous dp3 unlock guide.
https://forum.xda-developers.com/on...obile-one-plus-7-pro-msm-tool-revert-t3936528
Step 1- Download the file in the original post, create a folder somewhere you know where it is and extract the downloaded files to that folder
Step 2-Turn off your OP7 Pro
Step 3-Open the folder you created and right click on MsMDownloadTool V4.0.88.exe and select run as administrator, Once open uncheck sha256 check.
Step 4-Plug the Original USB cable that came with your phone into the phone.
Step-5-Hold the Power/Volume up/Volume down button until you see Connected in MsMDownloadTool, the instant you see Connected press start. You only have 5 seconds before it's too late so be quick.
Step-6 Once you see "Download Complete" in green in the Status of Communication box in MsMDownloadTool the phone will automatically reboot and you should have the TMobile splash screen and be able to set the phone up through the set up Wizard.
If you want to use Android 10 with service working on your T-Mobile 7 Pro you NEED to be SIM unlocked.
sydsick42069 said:
From there you can unlock your boot loader, flash twrp and magisk, and then flash your rom
Click to expand...
Click to collapse
That process doesn't work for Android 10 (OB1 and OB2). With OB1/2 the fastboot boot command doesn't work yet (similar to all the 7 Pro devices when it was first released). As the top poster already mentioned the correct method to get TWRP on the device is to flash a patch boot image. Form there, he can flash TWRP within Magisk.
redpoint73 said:
That process doesn't work for Android 10 (OB1 and OB2). With OB1/2 the fastboot boot command doesn't work yet (similar to all the 7 Pro devices when it was first released). As the top poster already mentioned the correct method to get TWRP on the device is to flash a patch boot image. Form there, he can flash TWRP within Magisk.
Click to expand...
Click to collapse
"From that point" would have been 9.5.3 international not 10, and I was assuming he was already carrier unlocked.
Virus1x said:
You can't flash TWRP from adb on DP3
:/ gives error command
Click to expand...
Click to collapse
Right. What you need to do now is download the full latest ota, put it on root of storage. Do local upgrade. After it will boot into stock recovery do a full wipe. Reboot. Then you can install twrp, magisk..ect
This way worked for me ^
(I'm not sim unlocked btw)
If you use msm it will relock your bootloader!
JWnSC said:
Right. What you need to do now is download the full latest ota, put it on root of storage. Do local upgrade. After it will boot into stock recovery do a full wipe. Reboot. Then you can install twrp, magisk..ect
This way worked for me ^
(I'm not sim unlocked btw)
If you use msm it will relock your bootloader!
Click to expand...
Click to collapse
Is there some benefit to keeping the sim locked? Getting the sim unlocked is so easy. Then you don't have to worry about the bootloader relocking, cuz you can just fastboot unlock it.
sydsick42069 said:
Is there some benefit to keeping the sim locked? Getting the sim unlocked is so easy. Then you don't have to worry about the bootloader relocking, cuz you can just fastboot unlock it.
Click to expand...
Click to collapse
No, no benefit. Less headache actually, no need to flash dp3 if sim unlocked already
JWnSC said:
No, no benefit. Less headache actually, no need to flash dp3 if sim unlocked already
Click to expand...
Click to collapse
Exactly, like why go through the trouble of using certain methods of upgrading, etc. to avoid relocking If you can just go to one of the unlocking threads on xda, or just talk to TMobile support on Twitter and get sim unlocked. Like the whole process took me 30 minutes and now I don't have to worry about it because it's officially unlocked. Like, I've had my **** in a boot loop a few times, and being able to msm all the way back to stock and reunlock etc is extremely useful.
Virus1x said:
I flashed International Firmware
I flashed DP3
OEM UNLOCKED (No Service--- Expected)
Ok now I need to flash a custom rom to get service back which means... flashing TWRP....
Try booting TWRP img nope doesn't work
I talk to people in TWRP they said its because fastboot commands arn't present on DP3 and to download magisk manager and patch a stock boot img.
Grabbed stock IMG from 9.5.10: https://androidfilehost.com/?w=files&flid=294812
moved to Phone, Patched with Magisk Manager, Moved back to pc
adb reboot fastboot
fastboot boot magisk_patched.img (FAILED)
fastboot flash boot magisk_patched.img (Successful)
fastboot reboot
Bootloader (select start option)
Loops into bootloader
Select Recovery
Loops into bootloader
I am literally losing my mind.
I've been trying to get TWRP/ROOT for almost 4 hours I'm starting to Crack someone please dear god help me.
Click to expand...
Click to collapse
Download something called "minimal adb and fastboot" (don't have the link handy) and use that fastboot to do the following:
fastboot getvar current-slot
Whichever slot it shows, a or b, you want to switch to the other. So if it says the current slot is A, you would type
fastboot --set-active=b
And if it says slot B, then you want to set A as active slot. Then after it successfully changes slots
fastboot reboot-bootloader
Now when you're back to the fastboot screen after your phone reboots, the fastboot boot command on your twrp img should work fine.
Sent from my OnePlus7Pro using XDA Labs
This Guide is used to Unlock the Bootloader of Nokia 3 [NE1] for all the "TA" variants & also applicable on Android 7.X Nougat, Android 8.1 Oreo, Android 9.0 Pie.
Please follow the below steps carefully to unlock the handset succesfully.
First of all we need to convert our phone SN (Serial Number) to MD5 hash
For checking the SN dial *#06# OR Go to the settings > About Phone
MD5 HASH CHECKSUM
The output will be looks like
8AE2A2B4F0D939819F762798F14A4D34
Code:
fastboot oem alive
After executing this command connect the USB cable, your device will boot into Fastboot mode/Download mode.
Code:
fastboot devices
To Check wheather your devices connected or not, if connected you will find the device SN
Example: NE1GAMXXXXXXXXXX
Code:
fastboot oem key <Your MD5 hash checksum>
Input your MD5 hash checksum that you've generated by device SN
Code:
fastboot oem key 8AE2A2B4F0D939819F762798F14A4D34
Just taking as an example (How you need to put the MD5 key see above command)
Code:
fastboot flashing unlock
After executing this command you will see the warning message on the screen
Now press Volume + button to continue the unlocking process.
Code:
fastboot reboot
All Done!!
Device Bootloader Unlocked Succesfully.Required files:
Platform Tools by Google (Make sure your device got installed with adb/fastboot driver)
Nokia Driver (Required before executing the fastboot commands, otherwise the output will be NIL.
Please like the thread if its helpfull to you- CRUECY
Comment down if you've any queries regarding this.
Serial number (?
WORKED! Thanks brou
Bro it's not working please help me out
It is showing failed
---------- Post added at 09:25 AM ---------- Previous post was at 09:19 AM ----------
I have tried all the methods to root my nokia 3 given here but it's not working Every time i try to unlock Bootloader Using Command Fastboot oem unlock it doesn't work then I used Fastboot flashing unlock then new window comes in my phone saying press Volume up to unlock Bootloader when I press volume up button it shows failed and a msg comes in my command window that unlock not allowed then I tried with MD5 hash key still not working
My Oem unlock is on
My usb debugging is on
But still not working plzz help me out
Vishwas_shaji said:
Bro it's not working please help me out
It is showing failed
---------- Post added at 09:25 AM ---------- Previous post was at 09:19 AM ----------
I have tried all the methods to root my nokia 3 given here but it's not working Every time i try to unlock Bootloader Using Command Fastboot oem unlock it doesn't work then I used Fastboot flashing unlock then new window comes in my phone saying press Volume up to unlock Bootloader when I press volume up button it shows failed and a msg comes in my command window that unlock not allowed then I tried with MD5 hash key still not working
My Oem unlock is on
My usb debugging is on
But still not working plzz help me out
Click to expand...
Click to collapse
Hi, bro. I tried yesterday this method and worked for me.
Boot your phone to bootloader.
In adb/fastboot type this command: fastboot devices
Then it will show you the serial number of the device.
Copy it and go to the generator page, paste it there and now you have the key.
Now you just have to type the command: fastboot oem key "Here your MD5 hash key"
Now go further.
Now My nokia 3 Bootloader is unlocked and is showing orange state your device is unlocked and cannot be trusted and will boot in 5 sec
After that I tried to install twrp recovery it shows finished in my cmd window but when I try to boot to twrp recovery using command fastboot boot twrp.img my system doesn't boots into twrp recovery after that I tried to poweroff and boot to twrp recovery using volume and power buttons then also it doesn't boot to twrp recovery
Please give me a solution for this
Hello, your post is for TA-1032 for Android 9, I have TA-1020 Android 8.1.0, but I tried this and nothing changed, it just fails the unlock, even after I put the oem key.
You seem like you're good and you know what you're doing, can you please help me? https://forum.xda-developers.com/nokia-3/help/rooting-nokia-3-ta-1020-android-8-1-0-t4077501
Thank you so much.
It worked!
Thanks for the help. Still works in april. To clarify for others - the number that you need to put in the hash generator is the number that you get when you type *fastboot devices*.
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
quanghung123 said:
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
Click to expand...
Click to collapse
I haven't tried it yet in fear of bricking my device. What do you mean you got it installed? Can you boot into it at least once before it gets replaced with the stock recovery? Cus if you want twrp to be permanent, you need to flash root on your device. Also if you can't get it working on pie try downgrading as there are many threads for previous versions.
Not working, adb device in fastboot shows blank. nokia 3 drivers are installed, oem unlock enabled. Nokia 3 - 1032, Android 9.
quanghung123 said:
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
Click to expand...
Click to collapse
I have unlocked bootloader, TWRP, Magisk & removed encryption on Android 9.0 April security patch succesufuly. I tried to flash TWRP with SP Flash Tools but it just reverts back to stock recovery with No Command screen like you said. To install TWRP, use fastboot instead with fastboot command "fastboot flash recovery twrp.img". It works. To remove encryption, first format data than flash this in TWRP: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 This also solves issue with TWRP when TWRP can't read Internal storage. After that flash Magisk. That's it.
quanghung123 said:
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
Click to expand...
Click to collapse
You need to patch the boot.img by magisk then flash the twrp.img it will work...
In the version of Android 8.1 Oreo and 9.0 Pie boot.img patched required to boot Custom recovery TWRP....
Константинос said:
I haven't tried it yet in fear of bricking my device. What do you mean you got it installed? Can you boot into it at least once before it gets replaced with the stock recovery? Cus if you want twrp to be permanent, you need to flash root on your device. Also if you can't get it working on pie try downgrading as there are many threads for previous versions.
Click to expand...
Click to collapse
To install twrp in Nokia 3 Android 9 pie you must patch the boot.img by rooting with Magisk... after that twrp will successfully flash in your phone...
Thanks
blubbbb said:
Not working, adb device in fastboot shows blank. nokia 3 drivers are installed, oem unlock enabled. Nokia 3 - 1032, Android 9.
Click to expand...
Click to collapse
use Platform Tool by Google
Thanks
quanghung123 said:
Do you have TWRP for Nokia 3 on Pie, I got it installed on mine but when I reboot into recovery mode it's show the No Command screen. I wonder do you get TWRP on your device?
Click to expand...
Click to collapse
My man if u get the no command screen press the power button and volume up key simultaneously
Hey there,
You think it'll work in a Nokia 3 TA-1028 with android 9ie?
caterham1888 said:
Hey there,
You think it'll work in a Nokia 3 TA-1028 with android 9ie?
Click to expand...
Click to collapse
Yes This method is applicable for TA-1020, TA-1028, TA-1032, TA-1038
What is MD5
Bro actually I am new in bootloader unlocking and root so I wanted to know what is MD5 key
My Nokia 3 TA-1032 failed to unlock with "fastboot flashing unlock" & "fastboot oem unlock". Anybody have some tipp about how to then? Thank you very much
Yestaday I upgrade Oneplus 8 IN2010 OxygenOS International to 11 and working just fine
But I regret it because there is no root
So I flash official rollback package from:https://forums.oneplus.com/threads/oxygenos-11-for-the-oneplus-8-pro-and-oneplus-8.1312654/
After local package flash,I reboot my phone and this thing happened
When it displays the oneplus logo, it becomes a black screen instead of a boot animation
I tried using twrp to flash OxygenOS,no error but still black screen
I tried many different versions with MSM tool
But there is no way to solve my problem
I tried to talk to oneplus service staff online
But because I was in Taiwan, they couldn’t perform the session with China region?
Taiwan is not even part of China!(Digress
Anyway, I regret disappointed and sad now
I really hope I can save my phone :crying:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
djmcnz said:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
Click to expand...
Click to collapse
Thanks for your help but MSM tool locked my bootloader
I don't know what to do now
Maybe wait for OxygenOS 11 MSM tool have the opportunity to fix it
oliver802 said:
Thanks for your help but MSM tool locked my bootloader
I don't know what to do now
Maybe wait for OxygenOS 11 MSM tool have the opportunity to fix it
Click to expand...
Click to collapse
Can you access fastboot? If so...
Code:
command: [I]fastboot oem unlock[/I]
First of all there is root on oos11, there is a magisk guide here on the forum, i did it myself & flashed magisk & was able to gain root access & installed custom kernel too
luscharsch said:
First of all there is root on oos11, there is a magisk guide here on the forum, i did it myself & flashed magisk & was able to gain root access & installed custom kernel too
Click to expand...
Click to collapse
I know but too late
djmcnz said:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
Click to expand...
Click to collapse
Thanks, I can boot to slot b and have crash dump on slot a, can't recognise in MSM and reluctant to use it after doing the rollback from A11 as afraid to lock the bootloader without successfully restoring as happened to OP
xdtyui said:
Thanks, I can boot to slot b and have crash dump on slot a, can't recognise in MSM and reluctant to use it after doing the rollback from A11 as afraid to lock the bootloader without successfully restoring as happened to OP
Click to expand...
Click to collapse
If you can boot for either slot you're fine, don't worry about the other, if you have a bootable slot you can recover to a factory image from it, you don't need to rely on the other (non-bootable) slot.
djmcnz said:
Can you access fastboot? If so...
Code:
command: [I]fastboot oem unlock[/I]
Click to expand...
Click to collapse
FAILED (remote: 'Flashing Unlock is not allowed')
djmcnz said:
If you can boot for either slot you're fine, don't worry about the other, if you have a bootable slot you can recover to a factory image from it, you don't need to rely on the other (non-bootable) slot.
Click to expand...
Click to collapse
Yeah thanks, I have a factory image on b so is it alright that a boots to crash dump? Could that be a problem in the future?
xdtyui said:
Yeah thanks, I have a factory image on b so is it alright that a boots to crash dump? Could that be a problem in the future?
Click to expand...
Click to collapse
That's okay. Often the alternative slot is unbootable. The next time you do a system update it will make the alternative slot bootable and boot from there.
---------- Post added at 12:59 ---------- Previous post was at 12:56 ----------
oliver802 said:
FAILED (remote: 'Flashing Unlock is not allowed')
Click to expand...
Click to collapse
Okay, if you can't unlock the bootloader, can't get into EDL mode and you can't use ADB then you need to chat with OP technical support again and hope they can help.
djmcnz said:
That's okay. Often the alternative slot is unbootable. The next time you do a system update it will make the alternative slot bootable and boot from there.
---------- Post added at 12:59 ---------- Previous post was at 12:56 ----------
Okay, if you can't unlock the bootloader, can't get into EDL mode and you can't use ADB then you need to chat with OP technical support again and hope they can help.
Click to expand...
Click to collapse
I can get into EDL mode and no error on MSM tool
But I have tried flashing with MSM tool, it shows that the flashing is successful and the Bootloader is also locked.
But I still can’t enter the system
In addition, flashing the version before instantnoodle_15_O.20_200716 will enter Qualcomm Dump mode
I used to suffer like you on oxygenos 11. Maybe you haven't installed Qualcomm HS-USB correctly. You should reinstall many times to wish you success.
Make sure it's latest MSMtool, that was the issue for me. Also can you get to the other slot? If so you can boot there and enable OEM unlocking from there, than unlock in fastboot.
greendragon527 said:
Make sure it's latest MSMtool, that was the issue for me. Also can you get to the other slot? If so you can boot there and enable OEM unlocking from there, than unlock in fastboot.
Click to expand...
Click to collapse
Unfortunately, because the bootloader of my device is locked by MSMtool, I can't switch partitions
Not sure if this is helpful, but I had trouble getting MSM to work after upgrading to OOS11 because I couldn't get into EDL mode. Something changed with boot in OOS11 so the normal up+down key combination didn't work it just always put me into fastboot. 'adb reboot edl' didn't work either it just went into fastboot. What I finally found that worked was a patched version of fastboot.exe that has the reboot-edl command. After that I was able to MSM successfully.
Here's the patched fastboot I used: https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
I used the MSM tool of OxygenOS 11 to successfully repair my device
Thanks to everyone who helped me
oliver802 said:
I used the MSM tool of OxygenOS 11 to successfully repair my device
Thanks to everyone who helped me
Click to expand...
Click to collapse
Can you share the lino to MSM for 11 please
firoz3321 said:
Can you share the lino to MSM for 11 please
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
I'm having same issue only fastboot and crashdump mode lol msm don't spot my phone probably too many other drivers I hold volume up and down for crash dump any ideas I've tried 11 no luck I updated to 11 using the oxygen updater
hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help
Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.
https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide
One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader