Related
Hello! I got a huge problem, i cant activate the wifi or the mobile functions on my phone after flashing it. Also in abote phone it says its a oneplus 7t (not pro)
May i have flashed a oneplus 7t firmware? I have tryed the volte fix with no ressults.. When i bricked the phone i did an flashall using fastboot, but culdent flashs system and vendors. Please help me!
I did the same thing as well. I ended up using the msm tool to flash the 9.5.3 gmba software then downloaded and updated to the 10.0.3. after that finished I downloaded the 10.3 global update and went smoothly. Then go to bootloader and flash twrp and root. First time you flash twrp make sure you check the box for ramdisk otherwise recovery won't stay as twrp, it will just keep going back to stock recovery. Also before you restart your device you have to flash magisk otherwise your phone will not boot. Also if you restart and their is no cell reception or cannot turn on wifi you will either have to go back and uninstall magisk then reinstall or do the process all over again. I did the 9.5.3 because I tried others and failed to reflash. The 9.5.3 seems to always work for many people
Knorrigbollen said:
May i have flashed a oneplus 7t firmware?
Click to expand...
Click to collapse
Impossible to tell what you've done. You haven't given sufficient info. Only you know what has been done to the phone so far. Where did you get the file, what is the file named, etc.
You have 3 threads going, none of which have sufficient info for anyone to provide proper help. Making multiple threads is not the right way to get help. Just confuses those trying to help you, and will make the situation worse. Stick to one thread, and give as much specific info as possible, as I've noted here: https://forum.xda-developers.com/on...ease-soft-bricked-phone-t4044311#post81668605
Im sorry im panicing
I tryied to flash the stock rom from this site after failed to root. THe fastboot one, when flashing it fails to flash system a and b, says partion not found
Hello again!
Ive been trying the msm tool, i downloaded it from here
https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909
It says it shuld support my version (hd1913) but MSM tool says "unsupported Target EU)
HOw can i fix this?
Also, ive flashed a oneplus 7t image, shuld i flash a new image and brick it then use msm tool?`
now it says Devices not match image. The post says it shuld support my model.
Hello,
So, to start off, I genuinely hate asking for help because it makes me feel like a failure but.... I'm desperate.
Preface; I got my token today to unlock this and I thought it was going to be as simple as it was with my 6 to root or whatever. well...
Cut to me thinking I remembered how to do it, only to get myself into a whirlwind of anxiety because it's been 8 hours now and I am at a loss.
Not sure if I'm just not grasping what I need to do, if my computer has something to do with it, if I'm using the wrong files, etc.
So, I was trying to just root the OOS because I genuinely like that... well some how I ended up installing lineageOS because I kept getting the QualCom error screen, and it wouldn't do anything.
Then, when I finally got lineageos to work, nothing on the phone actually worked. I've tried a million roms now and a dozen or two different version of the OOS... to no avail. I can't even turn the phone on now, it just goes to fastboot immediately.
I just want my tmobile oos back with magisk :'(
-sobs quietly-
Any help is appreciated. I've followed dozens of tutorials and guides and used that MSM thing and absolutely nothing is working. I feel like a complete idiot because all of my previous phones were so smooth to deal with. This, I want to legit throw it through the wall :/
Please help
EDIT: Update! Resolved!
After nearly pulling me hair out for two days... I decided to completely uninstall all my ADB Drivers and Qualcom drivers... Reinstalled everything from SDK AND I used the drivers at the bottom of https://onepluscommunityserver.com/list/Unbrick_Tools/
Those seem to be the only qualcom drivers that worked for me... I've tried probably 10 different ones and these are the ones that work. Follow the instructions that come with it, it's pretty basic but holy hell, it finally let me use MSM and it immediately started installing on the MSM program.
MSM should work.
I have a TMob 8T+5G as well and soft bricked it as well on my first attempt to take OTA after rooting.
MSM tool saved my bacon.
Would you please expand on the MSM efforts?
It should restore the SoC without any regard for the state of the partitions as long as there is no hw failure.
parakleet said:
MSM should work.
I have a TMob 8T+5G as well and soft bricked it as well on my first attempt to take OTA after rooting.
MSM tool saved my bacon.
Would you please expand on the MSM efforts?
It should restore the SoC without any regard for the state of the partitions as long as there is no hw failure.
Click to expand...
Click to collapse
Thanks for the reply!
I have been trying to use MSM all day and I can't get my phone to show up when putting it into EDM. I've fixed the drivers and when in fastboot, it shows up on my device manager as the correct qualcom device, but in the MSM program it shows the COM port that the phone is plugged in to, it just doesn't show the phone, just says waiting for device.
I'm at my wit's end lol. I have tried different cords, different USB ports, etc. x.x
Resolved! See OP!
Ive uploaded signed Qualcomm driver's I found that install on windows and don't turn on test mode. These work. Then afterwards toggle USB options with device plugged in PC ,change from charging to PTP and let it automatically install drivers. Rebooted and opened msm tool and Is connecting and now showing 2 ports. Hope this works for anyone having trouble ; as earlier I had no Qualcomm driver's installed and no ports showing on msm tool after many attempts to install drivers. I'm now ready when something comes along to flash. After rebooting PC use cmd window adb reboot edl. Will then show up on msm tool as connected. When installing Qualcomm driver's choose first option Wwan is not used to get Ip address. If this works for you hit the like button "it's free". I've seen many people complaining they can't connect to msm tool. This fixed my issues. Tested on windows 10 pro
Driver's. https://drive.google.com/file/d/1AOeuMj6D5f6H4yhAC1QKGN437qV9YmJs/view?usp=drivesdk
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
XNine said:
Do these overwrite existing drivers (used for rooting), or just add additional drivers to Windows?
Click to expand...
Click to collapse
No additional driver's need to make Qualcomm devices/one plus phones to connect to msm tool.
illusiveairforce said:
Mattie69 can you explain how to work the MSMTool to me? It wants a login and i dont understand exactly what to do.
Click to expand...
Click to collapse
You don't use the factory one use the one above or below. It's a tool that relocks bootloader and flashes device to original firmware that it was shipped with. It's an anti-brick tool so to speak.
I still cant get it to work. the driver looks to be working and MSM identifying it
but no matter what i do it wont progress. i cant adb reboot because adnb nor fastboot are responsive. the phone just disconnectes and reconnects USB over and over and thats it. no button combo of volume keys and power being held for along time seems to work either.
I finally got it functional and now at "Image does not match" tried on 3 other machines with 3 seperate MSm installs.
9 5G LE2115 is my phone I bought directly form OnePlus. Idk what to do from here.
Usually kicks up that warning if your trying to use the wrong msm tool.?
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
applyscience said:
i tried this one, the one from reddits backup area and the offical one linked to me by the angriest technician alive. it just boots and reboots and reboots. no matter the cable, version, cord. port, usb standard, serial setting or any combination of drivers form signed, unsigned and official, everything always leads to that same error.
its insane. the tech said "i didnt say run that (MSM he linked me) , were not liable to what it did"
I replied with " it didnt flash anything, thats why im contacting you and its qualcomms software, youre the company official making customers download altered /unofficial builds of another companies intellectual property. Im sure theyll be so happy to find out what you are doing"
he just logged after that. The balls on that guy. They Qualcomm didnt incorporate region based logins and VM Protect into MSM because its fun.
So yeah, hopefully i fix it before qualcomm returns my my emails.
Click to expand...
Click to collapse
What about that global fastboot rom I linked you to?
mattie_49 said:
What about that global fastboot rom I linked you to?
Click to expand...
Click to collapse
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
applyscience said:
man, sorry super tired. yeah no fastboot at all.no screen activity ever, all i get is usb plug in and out sounds every 3 seconds on my computer.
no fastboot, no adb. nothing.
Click to expand...
Click to collapse
You were able to get back from aospa though right? Via msm
mattie_49 said:
You were able to get back from aospa though right? Via msm
Click to expand...
Click to collapse
i always had fastboot access during that, i just was too stupid to extract my own img files form the paylod dumps (theres so many guides online, i just suck with it) anyhow, after you hooked me up with download i just ran the the imgs in a flash-all bat file to clean up both slots of the phone and it was wonderful. as soon as i went to the unofficial lineage my phone just gave up. 2 reboots later.
im not sure what im going to do. its been a long day and not too pleased with myself so im trying to just procrastinate it till tmw or sunday.
[17784][07-04 07:23:08.893]<4> [3] [CSerialCommHelper] No data in buffer to be sent 0
[17784][07-04 07:23:11.061]<4> [3] [SP][195] Check cmd done status failed. 1
this is the 2 lines in the log that have ruined my weekend.
I'm investigating possible solutions to common MSM errors that prevent flashing.
See the following thread and feel free to try the steps outlined if you're brave enough.
Please report back your findings.
[ADVANCED] [UNTESTED] Possible Fix - MSM Errors (Sahara, Param info, etc)
WARNING: THE FOLLOWING IS FOR INFORMATIONAL PURPOSES ONLY AND MAY FURTHER DAMAGE YOUR DEVICE. EXERCISE EXTREME CAUTION. USE ONLY AS A LAST RESORT. This was tested with a Global OnePlus 9 LE2115 Overview So I was encountering an error with MSM...
forum.xda-developers.com
Can you re-up these? I'm getting a 404 on the google drive link.
Ethanadams642 said:
Can you re-up these? I'm getting a 404 on the google drive link.
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
So I have been testing out a number of different custom ROMs without having any issue until I flashed Lineage 19.1 and decided I didn't like it. I tried to move to StagOS and everything just went south. The recovery refused to boot after being flashed. I tried it multiple times and it would just bring me back to fastboot after a black screen and the device giving a vibration. In this process I lost the installed ROM too because at one point I tried to reboot and see if it would boot normally (I had a feeling that it wouldn't but it was already late and I wanted to get a working device again and go back to bed so I tried it) and had to fuss around with the phone quite a bit to get it to boot into fastboot so I could shut it off and put it in EDL mode because if I didn't get the timing right, the force reboot dropped me right back to the black screen and then the phone went unresponsive for a bit again.
Went and ran the MSM Tool to get it back to stock global ROM. That worked fine. Updated to 11.2.10.10 which also worked fine. Unlocked bootloader, device wiped itself, rebooted and the device failed to boot. It dropped me to fastbootd. Tried to reboot and it just kept going back to fastbootd.
Okay, let me try this again. MSM a second time. Worked fine. Updated to 11.2.10.10. Worked fine. Unlocked bootloader, device wiped itself, rebooted aaaand... device dropped me back to fastbootd again. Tried to do the manual recovery with fastboot and it failed to flash a bunch of files with some saying that protected partitions can't be flashed and some saying the partition doesn't exist despite me following the entire process exactly, including the reboot in the middle. Okay, guess it's MSM time again.
So now I ran MSM the third time and decide maybe it's an issue with 11.2.10.10 (even though I swear I was able to unlock the bootloader just fine when I did this exact process the last time when I was first downgrading from OOS 12 to install a custom ROM for the first time last week) so I go to unlock right after MSM before updating. That works perfectly. I guess I must have been wrong about the way I did it the first time? Hmm.
I have to say that I have never actually had such difficulty with any device before and as you can see from my signature, I have had a ton of them. When I first got this thing and started reading in the forum, I thought it was weird seeing so many people with bricked devices. Yeah I don't feel that way anymore. It's a good thing that we have the MSM Tool because for some reason, it's just really easy to wipe these things out.
I was able to get StagOS back up and running with no problem after updating to 11.2.10.10 by using the same recovery I was trying to flash that didn't work before so I have no clue what the issue was that broke everything and I'm also not sure why I was unable to unlock the bootloader on 11.2.10.10 but all's well that ends well.
Now I'm going to set up Signal and Google Voice and go to bed. It's almost 4AM here.
Y'know, I went through pretty much the same thing yesterday trying to install Stag. Currently stuck in EDL and I cant flash due to param preload if using lite firehouse or sahara error if not. Any chance you could send a link to the exact MSM tool and ROM?
EDIT: This is only a few minutes later but I am now flashing the India OP9 Pro rom and it seems to be working without giving me error. Fingers crossed though.
EDIT2: IT BOOTS, I am so ready to refuck everything up : )
Soldre said:
Y'know, I went through pretty much the same thing yesterday trying to install Stag. Currently stuck in EDL and I cant flash due to param preload if using lite firehouse or sahara error if not. Any chance you could send a link to the exact MSM tool and ROM?
EDIT: This is only a few minutes later but I am now flashing the India OP9 Pro rom and it seems to be working without giving me error. Fingers crossed though.
EDIT2: IT BOOTS, I am so ready to refuck everything up : )
Click to expand...
Click to collapse
I have a global NA variant OnePlus 9 and this is the one I use.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
I don't know why I had so many problems. I'm not new to this, my device list is in my signature and I put custom ROMs on most of them and never had an issue like that before, but at least I managed to figure it out and get it working again lol. Gonna stick with Stag, never would have left if I didn't need Verizon support temporarily.
EtherealRemnant said:
I have a global NA variant OnePlus 9 and this is the one I use.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
I don't know why I had so many problems. I'm not new to this, my device list is in my signature and I put custom ROMs on most of them and never had an issue like that before, but at least I managed to figure it out and get it working again lol. Gonna stick with Stag, never would have left if I didn't need Verizon support temporarily.
Click to expand...
Click to collapse
None of the ROMS I've tried have supported verizon, stag is supposed to get it in the next update. Gonna have to find a way to MSM the stock op9 ROM bc right now I can only get op9 pro MSM to work :C
Is your phone a le2110 ? Is le2115? Mine le2110 Chinese variant , I had flash with Chinese ROM , then flashed it with the global ROM , that cleared my software issues , got drivers msm tool of OP remote team including ROM
jab5555 said:
Is your phone a le2110 ? Is le2115? Mine le2110 Chinese variant , I had flash with Chinese ROM , then flashed it with the global ROM , that cleared my software issues , got drivers msm tool of OP remote team including ROM
Click to expand...
Click to collapse
It's LE2115.
If I have to use the MSM again I'll just have to remember not to upgrade to 11.2.10.10 until after I unlock the bootloader because that worked fine, it seems like there's something broken in the unlock process for global 11.2.10.10. Been running StagOS without issues since.
EtherealRemnant said:
It's LE2115.
If I have to use the MSM again I'll just have to remember not to upgrade to 11.2.10.10 until after I unlock the bootloader because that worked fine, it seems like there's something broken in the unlock process for global 11.2.10.10. Been running StagOS without issues since.
Click to expand...
Click to collapse
I always unlock bootloader immediately after msm when I'm on firmware 11.2.4.4 always have and zero issues.
mattie_49 said:
I always unlock bootloader immediately after msm when I'm on firmware 11.2.4.4 always have and zero issues.
Click to expand...
Click to collapse
Yep was exclusively an 11.2.10.10 issue.
I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9
Flash by edl if you can't do it then pm I'll fix it by tv
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.
I had this problem because I flashed a custom kernel on a custom rom today
SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.