yes doing that now, will update after i am done. do you think usb 3.x can be culprit?
Tried the process altogether from step 1, did step 2 via unlock.bin file from oneplus.
Sorry for the late reply you should not do anything when it restarts again and the terminal says "waiting for device" the flashing process with resume automatically when it boots up again and goes to recovery modeTried the process altogether from step 1, did step 2 via unlock.bin file from oneplus.
Flashed european fastboot rom, initial steps succeeeded like before, but then it said rebooting to fastboot, it rebooted to recovery instead, from there i selected fastboot after that errors started popping up in the flash all script majorly, "flashing is not allowed for critical partiitions", "partition not found" and eventually device rebooted, but i dont have any cellular signals or wifi, sound etc. Kindly have a look at the attached screenshots, what exactly am i doing wrong, i really dont understand, please help
You used Europe fastboot rom (which is in this thresd) to convert?right, but i used the europe fastboot rom linked by OP, yet still it went to crashdump mode, any idea why?
You used Europe fastboot rom (which is in this thresd) to convert?Unlocked bootloader, now Using the fastboot rom mentioned by OP, the european rom, but now i cant flash fastboot rom, after running flash_all.bat in fastboot mode, it did a few steps formatting etc then says on the cmd, rebooting to fastboot but it went to crash dump mode, am i doing something wrong?
You not need t.moblie sim neither to be in USI don't have T-Mobile sim and not in the US. How would I go about this?
This is a reference for anyone unbrick his device as l want to write what happened to me but l found someone wrote his story like meOh my friggen god, so super duper incredibly happy! Thanks to OP and people on here I now not only have EVO X 7.5 with dual sim on my TMO OP8 but I unbricked what I thought was a hard bricked OP8.
For anyone who had the absolute misfortune of a crashdump due to misflashing the wrong .ops file, there's hope. I had that, the DIAG 900E only driver, alongside zero fastboot and recovery. It seemed hopeless, but being desperate and in lieu of the advice above and from other sites I kept trying and finally the following revived my phone:
1) I had to use a usb 2.0 port. It can be inbuilt or it can be from a hub but you really need usb 2.0.
2) I had to use a different cable than the one from oneplus. I ended up using the one used to charge my wireless headphones.
3) You should try windows 10 and above. Others may have had luck with windows 7 and native usb 2.0 but not in my case.
I had both the msm download and device manager open and ready. I kept the usb port in the system, then while holding down both volume buttons and power, quickly connected the usb C end into the phone. You can try without the power button but regardless you need to see 9008 pop up under ports in device manager. If the phone under device manager still remains as 900E then you have to start the process over again until it shows EDL (9008). If it shows bulk you need to reinstall your drivers.
On MSM immediately ENUM and Start.
If the above doesn't work, look for resources as if it showed issues only after msm there's still a good chance you can save it.
thank you for your reply, i tried waiting for it for about a two minutes or more, it felt like it wasnt proceeding at all. should i wait more? kindly let me know if thats the case or whatever i am doing wrong, any help is appreciatedSorry for the late reply you should not do anything when it restarts again and the terminal says "waiting for device" the flashing process with resume automatically when it boots up again and goes to recovery mode
Yes, i used the europe rom mentioned by OP in this thread, version was 10.5.9, yet still its not working, crash dump is not occuring now but when i run flash all, it does some flashing and says rebooting to fastboot and then never reboot to fastboot, it just reboots to stock recovery and stays there, and if i reboot to fastboot manually from there, flash all script starts giving errors, "flashing is not allowed for critical partition", I have literally no idea where i might be going wrongYou used Europe fastboot rom (which is in this thresd) to convert?
Try one of these OnePlus fastboot romsYes, i used the europe rom mentioned by OP in this thread, version was 10.5.9, yet still its not working, crash dump is not occuring now but when i run flash all, it does some flashing and says rebooting to fastboot and then never reboot to fastboot, it just reboots to stock recovery and stays there, and if i reboot to fastboot manually from there, flash all script starts giving errors, "flashing is not allowed for critical partition", I have literally no idea where i might be going wrong
Why you not follow the steps just confirmall drivers installed then start from step 1 with msm A10 not A11 then step two then use eu 10.5.9 fastboot rom not use eu 11 i as A11 always above 95% get crash dumpright, but i used the europe fastboot rom linked by OP, yet still it went to crashdump mode, any idea why?
i followed every step as mentioned. I have drivers installed and i am using msm 10 not 11, but with step two i couldnt unlock bootloader with the method mentioned so used unlock.bin from oneplus and used that to unlock bootloader but with step three, used eu 10.5.9 not 11, but i am not encounterring crashdump now, it probably went to crashdump because i updated my system a bit from wifi.Why you not follow the steps just confirmall drivers installed then start from step 1 with msm A10 not A11 then step two then use eu 10.5.9 fastboot rom not use eu 11 i as A11 always above 95% get crash dump
tried again, even tried waiting for 10 minutes or so but nothing, until i manually go to fastboot mode myself and then it starts saying "flashing is not allowed for critical partition"Sorry for the late reply you should not do anything when it restarts again and the terminal says "waiting for device" the flashing process with resume automatically when it boots up again and goes to recovery mode
fastboot flashing unlock_critical
Simple step put the device in fastbootd and show if pc recognizes it or no ,then tell metried again, even tried waiting for 10 minutes or so but nothing, until i manually go to fastboot mode myself and then it starts saying "flashing is not allowed for critical partition"
I read in another forum regarding the unlock_critical:
Running the above command gives "Device Already : Unlocked !"Code:fastboot flashing unlock_critical
As of right now i have tried a lot of possibilities, even used differnet roms, 10.5.12 global as well but every rom just after an inital flashing goes to fastbootd and never progresses afterwards
Strange, it still works for me. Are you outside of US ? I do see that you got the steps to request the unlock token from OnePlus and proceed.
yep pretty strange, it wasnt working before, finally it started working when it redirected to us site, for anyone having issues with that, this is the linkStrange, it still works for me. Are you outside of US ? I do see that you got the steps to request the unlock token from OnePlus and proceed.
i ran the following commandSimple step put the device in fastbootd and show if pc recognizes it or no ,then tell me
adb reboot fastboot
Thank you so much for the hint, that was the issue, i didnt had any google drivers installed for fastbootd mode, i have flashed the fastboot rom successfully, again thanks a lot.Simple step put the device in fastbootd and show if pc recognizes it or no ,then tell me
thanks, i tried it, and successfully installed. I never thought i can use custom rom on this phone. very nice custom rom.
some phones do this you need their unlock token from oneplusI successfully converted 2 phone by this method but my 3rd phone is getting stucked in bootloop by this process ( it is unlocked at oem unlocking enabled) when I flash unlockops it starts to reboot to fastboot mode ( device is corrupted is not showing) when I run fastboot flashing unlock is say it is not allowed any solution or other way to unlock bootloader
bcdedit.exe /set nointegritychecks off
bcdedit.exe /set testsigning off
adb reboot edl
fastboot devices
fastboot flashing unlock
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
fastboot flashing lock
Sorry for spamming the board today, but I think I figured it out.I tried again, MSM to 10.5.7, unlocked bootloader, rebooted to bootloader, flash-all.bat, and I'm still getting errors on the critical partitions. And I can't figure out how to unlock the critical partitions (probably not allowed in TMo firmware).
I'm going to MSM to 10.5.22 and see if that makes any difference.
EDIT: No dice. 10.5.22 made no difference. The issue is the locked critical partitions. If anybody has any solutions please tag me.
IN2017 is Tmobile version of the phone and updates are late and you cant sideload an update because it is not available on carrier versions of the phone. Converting it to International version gives access to the latest updates, and some other features that weren't available to Tmobile version. If you do this method, you will lose Safetynet which is the ability to use bank apps and etc. So after converting you have to lock the bootloader if you wish to do anything related to banking.Thanks for the guide!! I just submitted my request to T-Mobile to unlock my boot loader so now I play the waiting game...
In the meantime, can someone please clarify what does converting from IN2017 to International achieve? Ultimately my goal is to flash a custom ROM - not sure if I can do this directly after unlocking my boot loader.