i installed the DSU package and now the phone is stuck on your device is corrupted and cannot be trusted. I can only get into fast boot mode
can someone guide me through resetting it, I dont care about anything on the phone i just want it to go back
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
If you can reach fastboot this method should work
_MartyMan_ said:
If you can reach fastboot this method should work
Click to expand...
Click to collapse
dont i need unlocked bootloader?
mattie_49 said:
[FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA
Greetings, I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a...
forum.xda-developers.com
This is flashed through fastboot
Click to expand...
Click to collapse
dont i need unlocked bootloader?
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
casualBricker said:
dont i need unlocked bootloader?
Click to expand...
Click to collapse
To flash critical partitions, yes
D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
D3G0N said:
You don't have bootloader unlocked? You might need to find your correct msm tool for your device, depending on if you got your phone from OnePlus or T-Mobile, or send it in for repair? A few people on here, including me, also was able to send it to OnePlus via 1 day airmail and have it shipped back the same way and repaired all for free. That might not be an option for you though, I don't know how much you need your phone but if it's bricked either way it might be the best option. Try the msm tool first though instead of using fastboot to flash stock.
Click to expand...
Click to collapse
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
mattie_49 said:
+1 get a remote session from OnePlus tech's. He had said earlier he tried msm already and couldn't connect and changed op
Click to expand...
Click to collapse
My bad, didn't see that he changed op. I mean if he could not connect through msm, there are a few options to try, including installing a driver manually for the qcom device. I had to fiddle with drivers and whatnot for about an hour or so before flashing was able to successfully commence. msm should help but scheduling a remote repair might take a day or so from oneplus so might as well try you know?
casualBricker said:
A phone wouldnt have an unlocked bootloader from the start right? I've never been this deep in **** with my android so this is all really out of my depth. Ill send a message to the oneplus support while the file from the other post downloads, maybe it'll work after all
Click to expand...
Click to collapse
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
D3G0N said:
No it would not, however msm tool does not use unlocked bootloader. I was informed that you tried it and it did not work and removed it from your op, but what would not work? was the device not seen on com port?
Click to expand...
Click to collapse
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
casualBricker said:
i havent used an msm? i couldnt get the com port to show up, or It was like showing up for short periods while i was doing certain inputs, but not long enough to get anything done
Click to expand...
Click to collapse
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
D3G0N said:
So you tried it though it sounds like. It requires specific steps to work. You need drivers to be installed, go into EDL mode by having the device off and holding volume up while plugging the device into your computer, and then you have to start it when the device is enumerated. Are you willing to try msm again? The only other options really are to have a remote session with oneplus, which might take a day or so to get done, or send it for free for repair?
Click to expand...
Click to collapse
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
casualBricker said:
its the holding buttons part thats a little weird but im definitely ready to try it again. The problem occurs with how my phone is powercycling by itself whatever I do while its not in fast boot mode. This makes the MSM stop detecting the phone and I have to start over.
Click to expand...
Click to collapse
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
D3G0N said:
Yeah, I have bricked my op9 so many times I know what you are talking about. With the power cycling thing I have no idea why that happens, but sometimes if I start the msm tool while it is detected, it will stay in EDL mode and stop cycling. Other times I realized that it was not really in EDL mode to begin with. Make sure that the device is completely off. Open up msmtool and get it ready. Hold volume down and up, without holding the power button, and then connect it to your pc. Once it shows up just click start. You might need to try different usb ports, and/or make sure that your drivers are installed for qcom device in edl mode.
Click to expand...
Click to collapse
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
casualBricker said:
Thank you! i think im ready to start this hell, the "qualcom something 8001ish" driver showing up(while the phone shows up in msmtool) would mean the drivers are correctly installed right?
Click to expand...
Click to collapse
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
D3G0N said:
I believe so? in device manager you should see the device and then COM... like COM4 or COM3 or something, as long as it is COM and then a number, and if it shows up in msmtool then the drivers are probably installed. The process won't work if you dont have drivers set right, so try it and if it fails make sure that it is the right msmtool and that you have drivers installed. Do not touch it while it is doing its thing, lay it down on a surface or something just to be safe. Also you might not have to do this but I have found success with msmtool by going offline like disconnecting ethernet and turning off wifi, and setting my date back to december of 2018 in windows before starting the tool, I do not know why but if it fails try that first above all else.
Click to expand...
Click to collapse
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
casualBricker said:
how do i make sure the phone is turned off, just when it goes black? and when I hold the volume buttons it goes into fast boot, does this mean I was too slow?
Click to expand...
Click to collapse
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
D3G0N said:
Yeah it should just be black screen. It goes into fastboot? You sure you aren't hitting the power button as well? In fastboot select power off. When it's off, hold only the volume buttons, and then plug it in.
Click to expand...
Click to collapse
im not touching the powerbutton, it confuses me as well. do I wait for it to vibrate before I plug in the phone?
Related
If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.
One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon
alan2500 said:
If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
yashshan said:
One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon
Click to expand...
Click to collapse
That won't work, the phone isn't turning on.
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Thanks a lot, i dont know how i did not come upon that link while trying various fixes, now i can boot the phone again
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Uh, new problem, i used the toolkit to unlock the bootloader, and i had to use the Ultimate Tool kit to get TWRP on it. When i connect the phone to the pc (windows 7) i keep getting a message saying i have to format the phone before i can use it. When i click that, it says its writing protected. When i boot up the phone, it turns on, and i can go to the home screen (some times) but after a few seconds, it just turns off it self. Sorry for asking for your help again, but do you know of this problem? Google just came up with results for people with battery problems.
Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.
alan2500 said:
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.
Click to expand...
Click to collapse
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?
Heisenberg said:
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?
Click to expand...
Click to collapse
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.
alan2500 said:
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.
Click to expand...
Click to collapse
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.
alan2500 said:
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.
Click to expand...
Click to collapse
Don't dirty flash, clean flash. Try out the Exodus ROM, great battery life and great features too.
I originally rooted my device before I updated to 9.0, but I didn't really care about rooting that much so I just let OxygenOS uninstall the recovery with the update. I couldn't play Pokemon Go so I decided to root again, but that was before I found out that TWRP doesn't work with Oneplus 6 OS 9.0. Somebody in some random thread posted about flashing the TWRP image through fastboot, which I stupidly did. Now, I'm permanently stuck on the temporary TWRP image and I get the QUALCOMM CrashDump error every time I boot up my phone. I also can't get into recovery, fastboot, etc. On top of that, I tried the MsmDownloadTool, but for some reason the trick where you hold volume up before plugging in your phone to access Qualcomm Download Mode is not recognized by my computer and it just installs the default (?) drivers every time (Qualcomm HS-USB Diagnostics 900E (COM4)).
Any idea how I can get out of this? Can I unflash TWRP? I would prefer not losing my data but I've kinda accepted at this point that I probably will. Thanks.
Are you holding volume up and power together? I think msmtool is your best bet to get things working again
klym.software said:
Are you holding volume up and power together? I think msmtool is your best bet to get things working again
Click to expand...
Click to collapse
Wow, that actually helped. Every source I've found just says to hold up and plug it in while it's off. I'll post again if I've figured it out. Thanks for the help.
@kylm.software It still doesn't work. I can get into fastboot, so I I tried to flash a flashboot rom from here: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
It worked and I don't get the error, but I just get a black screen with a blue LED when I boot into android. I can't use the MSM tool either as I still can't get the drivers but holding the up key while plugging it in. Can somebody please help me? I need my phone back ASAP
The guys on the discord helped me out with this one. I redid the Msm tool and had to manually update drivers. Thanks so much for the help everybody
zackarhino said:
The guys on the discord helped me out with this one. I redid the Msm tool and had to manually update drivers. Thanks so much for the help everybody
Click to expand...
Click to collapse
Next time use bluespark twrp not official.
This may be a simple solution, but I am completely puzzled on how to fix this.
SO i recently rooted my phone & used the twrp "twrp-3.3.1-4-guacamole". Installed magisk via that twrp and continued with my day.
I accidentally got a virus by trying to get a full free vpn, me being a terrible pirate, i accidentally got a virus! Silly me.
It was annoying me and I decided to factory reset my phone... not via twrp. I remembered after I clicked "Reset all" on oxygenos that it's not the way how to do it with a root device, and well.. it didn't exactly work.
Every time I power/reboot the phone it just brings me to the fastboot menu of "START", "POWER OFF", "RECOVERY MODE", & "RESTART BOOT LOADER". I thought since TWP is recovery mode I try to access that... no luck, it just brings me back to that fastboot menu. I tried going on CMD via adb by saying "fastboot flash boot twrp-3.3.1-4-guacamole.img". It will say it's finished and successful, but when i reboot and try to access recovery mode it just does not work.
TL;DR: Think I bricked my phone, there is no OS installed and I can only access the fastboot.
Any help? Much appreciated
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Thank you for the guap recovery as i didn't know it existed. However, what are the steps? when i go on the MSM download tool it doesn't detect my phone.
that being said, i can't access any of my files through my pc using fast boot. on MSM it's just saying "waiting for device" even when plugged in so thats annoying.
trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
MOweenSalah said:
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
Click to expand...
Click to collapse
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
A few things to note:
- Works perfectly fine for unbricking GM1917 modeled OnePlus 7 Pros.
- Use the original cable and try to plug it into a USB 2.0 port. I've found that this is the most ideal condition.
- Make sure your device is charged up. If you can't see how much charge it has, leave it charged via the 30W warp charger for 40 minutes and that should be good enough.
- In the L2 drivers folder found in the archive, navigate to the 32 or 64 folder depending on your system's architecture, and click on the file that ends in the extension ".cat". Then, click "view signature", then "View certificate", then "Install." This is IMPORTANT.
- Then, make sure your device is powered OFF, then, plug in the USB-A side of the cable (big head) into your computer and do NOT connect the USB-C (small head) into your phone yet.
- Hold down Volume up AND volume down for five seconds, and while you're continuing to hold, plug the USB-C side into your phone. The drivers should automatically download, and you should see a "Qualcomm QD loader" device in Device Manager. If you see an exclamation mark or you don't see this, you are doing it wrong and you need to repeat the above steps.
- Open up MSMTool.exe as an administrator and click 'start' only. Should take a few minutes, but you will have a good-as-new OnePlus 7 Pro.
Click to expand...
Click to collapse
Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
I did yes, i pressed all buttons and the power button for 5 seconds and plugged my charger in. Then after that went on the MSM tool and it went straight to the fastboot. I really don't know but it loves this fastboot tool haha
Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
https://www.youtube.com/watch?v=jU8a6kDXNNs&feature=youtu.be
MOweenSalah said:
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
&feature=youtu.be
Click to expand...
Click to collapse
It's one of those things where if someone was there with you, it'd likely get figured out. I've seen this kind of situation hundreds of times on XDA, and with all due respect, the problem is most always at the hands of the user. These phones are cookie cutter made, so there's nothing different (besides individual variants) that would make thee tools not function correctly, unless it's operator error. But that's not set in stone. Just don't give up. Try setting up your camera for an overhead view. I couldn't tell if you were plugging in your cord. And it seemed to reboot, instead of power off. Repeat the steps carefully, and see if you can achieve better results.
Don't give up! We're here for you ?
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Command in Fastboot mode is:
Fastboot boot "name of the recovery".img. Phone should boot to twrp. Then flash twrp.zip
or try Fastboot roms:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Choose the one for youre phone (region)
MSM tool it's the last option.
Can't you just switch slots from fastboot or did you mess up both?
trapcoder666 said:
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
Click to expand...
Click to collapse
Firstly I'm terribly sorry for no response (same goes to everyone else looking into this matter for me. THANK YOU!)
However, I have done this multiple times in the past and it instantly goes back to boot menu. it sucks :/
IronSingh said:
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Click to expand...
Click to collapse
Okay. I shall go and look into this situation when I receive my phone back (going to explain that in a later quote)
larsdennert said:
Can't you just switch slots from fastboot or did you mess up both?
Click to expand...
Click to collapse
If i'm honest with you.. i'm not sure in the slightest. My only assumption is no because the only thing I can access is only the fastboot. if i attempt to go into recovery mode it will go back to fastboot. when I flash twrp it will flash but it won't boot into it. It's confusing as hell.
Just to add to this whole situation:
Since I have no idea and just wanted it fixed in the day; i was willingly to give money for this phone to be fixed, but thanks to the person, he just made it a slower process by doing things i've already done.. going to pick the phone back up in an hour of this message.
I haven't used the fastboot boot twrp cmd yet, but from how everything else has been so far i feel like that won't work, but i will update everyone on that situation.
Just to add additional things that I may have not mentioned in the past will be below:
- Whenever i type in "ADB Devices" in cmd, it will not show up with anything. However, when I type in "fastboot devices" it shows it's serial and in "fastboot". It will only show as fastboot and i can't access the phone via file explorer in windows.
When i say "ADB Devices" it says *devices attached* and will show none of my phones details, but when i say fastboot devices it will then show the devices.
^ what i said above means I can't use the guap recover, or anything which means the phone has to be detected in windows, because other than fastboot, it won't work at all.
- So far I can't access twrp as a whole, so if anyone knows how to give me a guide on how to install it from where I am at, that would be amazing (if not, i'll try and reiterate what to do with the one given from a previous comment, so thank you )
- There was one time I was allowed in TWRP but i completely forgot how i entered it (so i can't explain), So i feel like there is hope in that aspect. I feel like i entered something via cmd so maybe there's a way?
In terms of hardware my phone is completely fine, there's not a single problem other than the software being a pain in the ***!!
if anyone can just spew out a bunch of help in different explanations it means the world because so far all I can see is that I wasted about £600 on an amazing phone because of dumb *** haha.
Thank you to everyone who has helped, and is helping
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
larsdennert said:
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
I do appreciate the help. If i'm honest with you the only reason I did this is to increase my data speeds (which from look of things is outdated now), and a longer battery life. I don't know much about rooting/jailbreaking but believe me that I have been in the scene for years, but not even knowing everything haha!
that being said.. i'm in twrp! thank you so much mate, i'll try and go and install the rom now. thank you!
Now install the zip twrp
Thankfully.. IT'S FIXED!
I didn't have to install twrp again or any of that. I simply changed the slot from A to B and pressed all buttons when it was showing the "! Your decide is unlocked" orange/black screen.
I had msm tools up and it detected and instantly installed the OS to the latest one and boom. It works again!
I got to thank everyone for helping me because without you people I wouldn't of been able to fix it. I looked everywhere and no help anywhere as I feel like it's pretty dumb to do what I did haha!
Thank you again people!
Oh you gave up on root?
You are supposed to read the instructions and follow them to the letter. When I read your post I realized you tried to install twrp like you would pre Oreo but it changed you have to boot into twrp then install it via zip file.
Anyways just remember that for next time.
I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.
adrunkenmess1 said:
I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.
Click to expand...
Click to collapse
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.
MrSteelX said:
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.
Click to expand...
Click to collapse
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.
adrunkenmess1 said:
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.
Click to expand...
Click to collapse
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.
MrSteelX said:
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.
Click to expand...
Click to collapse
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
adrunkenmess1 said:
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"
Click to expand...
Click to collapse
amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I was able to get it to flash successfully. I used the files from the tmobile to international conversion since it required a hacked MSM tool. I'm a complete Noob at phone flashing and really spent a LOT of time reading tonight to figure it out. Phone flashed successfully but said the battery was now too low to turn on. At least it says something!
I'm charging it up now and hopefully it works after this!
amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I use a USB 3.0 and USB c port on my computer and no issues
OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?
jamescable said:
I use a USB 3.0 and USB c port on my computer and no issues
Click to expand...
Click to collapse
Really, I couldn't get the phone to come up on the MSM tool in the Qualcomm mode on USB 3 port. But when I connected the cable to the USB port, it appeared there.
adrunkenmess1 said:
OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?
Click to expand...
Click to collapse
MSM phone, unlock bootloader and flash twrp. Use twrp to flash system update and see if it works
Hey guys,
Recently after a software update my OP 8 started to crash and after that it would restart itself up. One day it just decided not to do it again, power button did nothing and it just wouldn't boot at all. I thought that the phone was dead, but after a couple of weeks I decided to connect the phone to my computer and after a "low battery warning" it boot up. When booting up, after a while it did the same thing as before, it crashed and decided to restart itself up. I did a factory reset and the same thing happened when I got to the android set up screen.
The same day, I decided that I needed to change the ROM since there could be a problem with it. While trying to unlock the bootloader I realized that I need a code from T Mobile (which I'm solicited and still waiting on), I decided to turn the phone off (so that it didn't restart or crashed) and wait for the code to get to me.
The next day, I tried to boot up the phone and it didn't. When connected to my pc i saw that it was recognized as a QCBulk (something like that), I learned about Qualcomm EDL, downloaded drivers and the phone is kinda talking to my pc. Now, I have used MSM tool to install new firmware but after installing the phone doesn't boot back up but stays on the same EDL mode.
So I need some advice,
1. I thought of waiting on the battery to run out and maybe the phone would get out of EDL mode that way.
2. Keep trying to flash different OOS roms via MSM tool and hope that the phone boots back up afterwards.
3. Using QFIL (one of Qualcomm tools) install need firmware. Problem is, I need a .efl or .mbn file which should be included in the firmware but can't find anywhere.
Please help me guys,
I just bought the phone and I miss it
THANKS!
I would think MSM tool is your only hope. Are you using the MSM tool for the tmobile version?
Did you fix your problem yet? @Gipsydanger120
I can give you the .efl firehose for the device if you want it, but it's almost useless cuz you can only use it with partition manager thats all.
L0ND0NB0Y said:
I can give you the .efl firehose for the device if you want it, but it's almost useless cuz you can only use it with partition manager thats all.
Click to expand...
Click to collapse
I would appreciate if you could give me the .efl file. I can use QFIL to flash it. Maybe that works cause I haven't been able to make it work, I'm still in EDL mode
Gipsydanger120 said:
I would appreciate if you could give me the .efl file. I can use QFIL to flash it. Maybe that works cause I haven't been able to make it work, I'm still in EDL mode
Click to expand...
Click to collapse
Alright I'll give it to you as soon as I get home
There you go @Gipsydanger120 !
Report back how it goes @Gipsydanger120
L0ND0NB0Y said:
Report back how it goes @Gipsydanger120
Click to expand...
Click to collapse
Thank you very much, I'll let you know if it works
trinidude4 said:
I would think MSM tool is your only hope. Are you using the MSM tool for the tmobile version?
Click to expand...
Click to collapse
Yes, I'm but it's no help. After installing, the phone disconnects and then goes back into EDL mode. I can tell since my pc makes a noise every time something connects/disconnects. I thought auto-reboot in MSM would help, but it doesn't.
L0ND0NB0Y said:
Report back how it goes @Gipsydanger120
Click to expand...
Click to collapse
So I tried to use QFIL with the efl file along side the "firmware" that i downloaded from OnePlus site, but it looks like I need some other type of file. I was following a tutorial and they mentioned that the firmware usually came with this efl file and maybe an XML file too.
So my conclusion is that I need other type of files too be able to use QFIL.
Any advice? Or am I missing something?
Gipsydanger120 said:
Yes, I'm but it's no help. After installing, the phone disconnects and then goes back into EDL mode. I can tell since my pc makes a noise every time something connects/disconnects. I thought auto-reboot in MSM would help, but it doesn't.
Click to expand...
Click to collapse
You know you could force restart the phone out of EDL mode by disconnecting USB holding all buttons at once for about 10 or 12 secs the phone should boot, but if there is a problem with a partition the phone will reboot once again to EDL. If it does reboot to EDL again, your last option would be a SMT download which will 100% make it boot but you will lose your IMEI and widevine certificates. It's a problem to solve another problem.
Gipsydanger120 said:
So I tried to use QFIL with the efl file along side the "firmware" that i downloaded from OnePlus site, but it looks like I need some other type of file. I was following a tutorial and they mentioned that the firmware usually came with this efl file and maybe an XML file too.
So my conclusion is that I need other type of files too be able to use QFIL.
Any advice? Or am I missing something?
Click to expand...
Click to collapse
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
L0ND0NB0Y said:
You know you could force restart the phone out of EDL mode by disconnecting USB holding all buttons at once for about 10 or 12 secs the phone should boot, but if there is a problem with a partition the phone will reboot once again to EDL. If it does reboot to EDL again, your last option would be a SMT download which will 100% make it boot but you will lose your IMEI and widevine certificates. It's a problem to solve another problem.
Click to expand...
Click to collapse
I've tried to get it out of EDL but i can't. Any key combination doesn't work, that's the main problem.
What's wrong about losing my IMEI? I can probably live without widevine certificates, but what about IMEI?
L0ND0NB0Y said:
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
Click to expand...
Click to collapse
And after you create the xmls and arrange them in folders with firmware files you are going to realize that QFIL can't flash the files for some reason and all your work have gone.
L0ND0NB0Y said:
That's what I was referring above to "it's almost useless", you won't be able to flash it with qfil unless you have the rawprogram.xml and patch.xml for EACH LUN, so that's 5 pairs of xml files.
Click to expand...
Click to collapse
Dang, and do you have any idea where can I get all that? It really sucks that I can't find anything for this phone.
Gipsydanger120 said:
I've tried to get it out of EDL but i can't. Any key combination doesn't work, that's the main problem.
What's wrong about losing my IMEI? I can probably live without widevine certificates, but what about IMEI?
Click to expand...
Click to collapse
No signal, no data!!!
and most important you will lose the ability of flashing the unlock_token cuz it's gonna say "Verify failed" obviously because of the null imei.
Gipsydanger120 said:
Dang, and do you have any idea where can I get all that? It really sucks that I can't find anything for this phone.
Click to expand...
Click to collapse
Dude, I spent nights creating them I have them but QFIL won't flash our phones idk maybe because of secure boot.
L0ND0NB0Y said:
No signal, no data!!!
and most important you will lose the ability of flashing the unlock_token cuz it's gonna say "Verify failed" obviously because of the null imei.
Click to expand...
Click to collapse
Hmm is it possible to get another IMEI? What if I already have the unlock_token? I'm guessing it won't even work since it doesn't have the IMEI anymore
L0ND0NB0Y said:
Dude, I spent nights creating them I have them but QFIL won't flash our phones idk maybe because of secure boot.
Click to expand...
Click to collapse
Man that sucks! I don't even know how my phone got so messed up in the first place.