Database Info

[Q] Bricked Nexus 5 doesn't boot + no access to fastboot

Hi guys,
I have had my Nexus 5 rooted with franco kernel on it now for about 5 months. Yesterday I tried to autoflash to the new r57 of franco kernel and accidentally aborted it. My phone will now not boot or go into fastboot or recovery. The only way to get my computer to recognize it is by holding the volume up button and plugging in the usb cable. My computer recongnises it as "Qualcomm HS-USB QDLoader 9008 (COM8)". Did I kill my Nexus 5? Please help!.
P.S. please dont tell me how stupid I am, I know. :crying:

kevindj360 said:
Hi guys,
I have had my Nexus 5 rooted with franco kernel on it now for about 5 months. Yesterday I tried to autoflash to the new r57 of franco kernel and accidentally aborted it. My phone will now not boot or go into fastboot or recovery. The only way to get my computer to recognize it is by holding the volume up button and plugging in the usb cable. My computer recongnises it as "Qualcomm HS-USB QDLoader 9008 (COM8)". Did I kill my Nexus 5? Please help!.
P.S. please dont tell me how stupid I am, I know. :crying:
Click to expand...
Click to collapse
Have you tried for example these steps? http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/
Here are some good files it seems http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Most often its possible to recover an android as long as you can access the Download mode.

linuxares said:
Have you tried for example these steps? http://trendblog.net/fix-soft-bricked-android-device-first-aid-guide/
Here are some good files it seems http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Most often its possible to recover an android as long as you can access the Download mode.
Click to expand...
Click to collapse
I'm not able to access Download mode.

What about backuo bootloader? Vol up, down and power?
Sent from my Nexus 5 using Tapatalk

rootSU said:
What about backuo bootloader? Vol up, down and power?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No, the only thing that does anything is just holding volume up while plugging it in to the computer. Screen stays black, but computer recognizes it as "Qualcomm HS-USB QDLoader 9008 (COM8)"

So to clarify, you cannot get into either the primary or secondary bootloader? You've tried both and literally nothing happens?
Sent from my Nexus 5 using Tapatalk

rootSU said:
So to clarify, you cannot get into either the primary or secondary bootloader? You've tried both and literally nothing happens?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
exactly

Well if you can't get lg flashtool to work, you're pretty screwed.
Sent from my Nexus 5 using Tapatalk

kevindj360 said:
exactly
Click to expand...
Click to collapse
Try the LG Flashtool. That's your only hope. If it doesn't fix your issue, RMA/repairing is the only option.

vin4yak said:
Try the LG Flashtool. That's your only hope. If it doesn't fix your issue, RMA/repairing is the only option.
Click to expand...
Click to collapse
Will google still accept my RMA. My phone is over 5 months old.

kevindj360 said:
Will google still accept my RMA. My phone is over 5 months old.
Click to expand...
Click to collapse
Try lg flashtool first. Click link in my signature and look in section 3 for the guide. It uses vol up + USB which may work for you
RMA is 1 or 2 years depending which country it is in however it is warranty for manufacturing defects not user destruction. If you RMA it and they identify (rightfully) that you caused this issue, they will charge you for a new phone.
You would be better sending it to LG who may offer to repair for cost. You won't have fried the memory, just corrupt the partition so I wouldn't expect it to be expensive.
But try flashtool first.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Try lg flashtool first. Click link in my signature and look in section 3 for the guide. It uses vol up + USB which may work for you
RMA is 1 or 2 years depending which country it is in however it is warranty for manufacturing defects not user destruction. If you RMA it and they identify (rightfully) that you caused this issue, they will charge you for a new phone.
You would be better sending it to LG who may offer to repair for cost. You won't have fried the memory, just corrupt the partition so I wouldn't expect it to be expensive.
But try flashtool first.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I get to this screen here.
EDIT: Attached the photo

kevindj360 said:
I get to this screen here.
EDIT: Attached the photo
Click to expand...
Click to collapse
If you have qualcomm 9008 you cant do much just rma your device.

kevindj360 said:
I get to this screen here.
EDIT: Attached the photo
Click to expand...
Click to collapse
Tried the qpst tool?
https://drive.google.com/file/d/0B3E5yjXCeMBbUmVRdl9VSHhHVkE/preview
Newer version link
http://code.google.com/p/mydownloadsection/downloads/detail?name=QPST.2.7.374.rar&can=2&q=

doctor_droid said:
Tried the qpst tool?
https://drive.google.com/file/d/0B3E5yjXCeMBbUmVRdl9VSHhHVkE/preview
Newer version link
http://code.google.com/p/mydownloadsection/downloads/detail?name=QPST.2.7.374.rar&can=2&q=
Click to expand...
Click to collapse
He cant do anything with qpst tool without a nexus 5 specific flash programmer and a special nexus 5 bootloader.

It seems when you get "Qualcomm HS-USB QDLoader 9008" you have really bricked your phone (hardbrick). Someone with knowledge must program sometool to unbrick it. (example. for a HTC device http://forum.xda-developers.com/showthread.php?t=1627882)
I think it's best to send it to Google.

Flashed wrong bootstack/modem, Pls HELP unbrick m8

Hi there,
I accidentally flashed (inside twrp) my HTC m8 with a bootstack/modem of a different phone (39a,LG G2). I'm pretty embarrassed about it, didn't mean to do it...I thought I was following instructions to install a new rom for the m8,except I was in the wrong forum..
details: in TWRP I flashed the wrong file, then went on to install a new rom and an error appeared: this is not vs980, this device is m8wl...so I thought, what? strange....
I turned off the phone (without realizing yet what happened. Sorry, stressful couple of weeks) and when I tried to turn it back on, it wouldn't. No matter how long I held the power button, or power and vol down. It will not go in download mode, neither detect it is plugged in to charger or a computer. Basically totally off without any response.
My question: is there any way possible to resuscitate this phone? please help me! any advice is appreciated.
before I had the m8 with s-off,rooted,with a 5.1 rom installed.
Thank you in advance!!!

HTC m8
danielr324 said:
Hi there,
I accidentally flashed (inside twrp) my HTC m8 with a bootstack/modem of a different phone (39a,LG G2). I'm pretty embarrassed about it, didn't mean to do it...I thought I was following instructions to install a new rom for the m8,except I was in the wrong forum..
details: in TWRP I flashed the wrong file, then went on to install a new rom and an error appeared: this is not vs980, this device is m8wl...so I thought, what? strange....
I turned off the phone (without realizing yet what happened. Sorry, stressful couple of weeks) and when I tried to turn it back on, it wouldn't. No matter how long I held the power button, or power and vol down. It will not go in download mode, neither detect it is plugged in to charger or a computer. Basically totally off without any response.
My question: is there any way possible to resuscitate this phone? please help me! any advice is appreciated.
before I had the m8 with s-off,rooted,with a 5.1 rom installed.
Thank you in advance!!!
Click to expand...
Click to collapse
You need all in one kit 2.0
M8 firmwareTWRP or probably RUU file
my choice will be firmware TWRP
you can flash it with help of All in one tool kit 2.0

ok_then_so said:
You need all in one kit 2.0
M8 firmwareTWRP or probably RUU file
my choice will be firmware TWRP
you can flash it with help of All in one tool kit 2.0
Click to expand...
Click to collapse
No, a toolkit won't help. He needs a new phone.
Sent from my HTC6535LVW using Tapatalk

beaups said:
No, a toolkit won't help. He needs a new phone.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
thanks for the help so far guys!
Here's another funny thing. After a few attempts of plugging it in to a computer, it was recognized and it showed up in the device manager. The phones still did not turn on though. Additionally it seems that the phone is seen as an LG model (even though it's not), but I am not sure yet. I will get the HTC drivers installed,and if it doesn't work, I will try the LG drivers.
by the way, isn't there a way to flash the correct modem/bootstack with ones of those kits? i also remember from downloading the wrong LG G2 modem/bootstack that it didn't come with fastboot in it.
I will try a few things and report it back.
thanks again,

danielr324 said:
thanks for the help so far guys!
Here's another funny thing. After a few attempts of plugging it in to a computer, it was recognized and it showed up in the device manager. The phones still did not turn on though. Additionally it seems that the phone is seen as an LG model (even though it's not), but I am not sure yet. I will get the HTC drivers installed,and if it doesn't work, I will try the LG drivers.
by the way, isn't there a way to flash the correct modem/bootstack with ones of those kits? i also remember from downloading the wrong LG G2 modem/bootstack that it didn't come with fastboot in it.
I will try a few things and report it back.
thanks again,
Click to expand...
Click to collapse
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk

dottat said:
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I got it to be recognized on a computer again, and windows installs a driver. The name of the device is forge hs-usb qdloader 9008.
I tried the all in one 2.0 kit, adb sideload, etc but anything I try I get a "device not found".
I think I am giving up unless someone finds a way to unbrick this kind of severe problem in the future. I also researched a bit on google, and there's a way to unbrick the LG G2 when it's seen as forge hs-usb qdloader 9008, which is known as a board unbrick. I found nothing for the HTC m8 though.
We tried all we could Thanks all for the help, it's very much appreciated! You guys are the best and this forum is awesome. I also ordered a new phone...and I will root it too

dottat said:
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Might be completely wrong on this.
Wouldn't he be able to JTAG the appropriate boot image back onto the device?
Also, I know we had a hard brick recovery for the S3 back in the day. Worked consistently on full hard brick's.
http://forum.xda-developers.com/showthread.php?t=2581166
Isn't it possible to dump a debrick image from a working device and follow the guide with that? I know the two devices are completely different, but the premise is the same.
My technical know-how isn't anywhere near your level, just thought I'd throw these ideas out there is case it hasn't been thought of yet. I'd be happy to put together a guide on how to do this if it can work on the M8.

BadUsername said:
Might be completely wrong on this.
Wouldn't he be able to JTAG the appropriate boot image back onto the device?
Also, I know we had a hard brick recovery for the S3 back in the day. Worked consistently on full hard brick's.
http://forum.xda-developers.com/showthread.php?t=2581166
Isn't it possible to dump a debrick image from a working device and follow the guide with that? I know the two devices are completely different, but the premise is the same.
My technical know-how isn't anywhere near your level, just thought I'd throw these ideas out there is case it hasn't been thought of yet. I'd be happy to put together a guide on how to do this if it can work on the M8.
Click to expand...
Click to collapse
Not likely with the nand used on this device.
Sent from my HTC6535LVW using Tapatalk

[Possible Brick?] I Dun Goofed

Funny story.
I was attempting to use ODIN v3.09 to change the partition table on my SG 2 Skyrocket (SGH-i727)
Now realizing I shouldn't have, ODIN failed to complete the flash with the same recovery. (CWM v6.0.5.1)
As of right now, pressing the power button DOES NOTHING. It no longer vibrates when it turns on. It can't even turn on I believe. ODIN, Windows or Heimdall cannot detect the device. I believe that I may have just ended up breaking this. Would anyone be able to tell me how (if there is one) I may get this stupid thing to work again?
I have a Nandroid Backup before I did this.
EDIT: Now that I think of it, it's possible that it no longer has its booter xD. Would I be able to restore that Backup?

ItsJorden said:
Funny story.
I was attempting to use ODIN v3.09 to change the partition table on my SG 2 Skyrocket (SGH-i727)
Now realizing I shouldn't have, ODIN failed to complete the flash with the same recovery. (CWM v6.0.5.1)
As of right now, pressing the power button DOES NOTHING. It no longer vibrates when it turns on. It can't even turn on I believe. ODIN, Windows or Heimdall cannot detect the device. I believe that I may have just ended up breaking this. Would anyone be able to tell me how (if there is one) I may get this stupid thing to work again?
I have a Nandroid Backup before I did this.
EDIT: Now that I think of it, it's possible that it no longer has its booter xD. Would I be able to restore that Backup?
Click to expand...
Click to collapse
Nothing? Or no fix?

if theres no signs of life then its bricked, jtag is the only option

ItsJorden said:
Nothing? Or no fix?
Click to expand...
Click to collapse
Im researching to bring phone back to life with chipset software that BoardDiag3.99c
I dont remember what i was thinking ............ THINK.............THINK...........THINK.........
ALL i can say is i have 2 phones I WAS NOT FOLLOWING DIRECTIONS.
so It is showing on PC as
Forge HS-USB QDLoader 9008 (COM11)
looking to extract info from a IMAGE.
with BoardDiag3.99c
any help or files that are need
list or links to help
may help others to make BRICKS non-brickable
LG has been done if you search BoardDiag3.99c or Forge HS-USB QDLoader 9008
Any help or working with chipset software would be helpful.
PM me to keep BLOG clear of miss info.
THANK YOU

vincom said:
if theres no signs of life then its bricked, jtag is the only option
Click to expand...
Click to collapse
Whats this jtag I hear about on other forums as well?

LG G3 D850 Bricked

Hi all,
I seem to have bricked my LG G3 when I was trying to install TWRP using Kingroot and Autorec MM. When I try and boot normally, I get flashing red and blue lights. When I try to boot into recovery, I get a flashing blue light with about a second in between flashes. When I boot into download mode, I get no flashing lights and Qualcomm HS-USB QDLoader 9008 shows up under the Ports (COM & LPT) section in device manager. When trying to flash back to stock, I get the error "Model Information Check FAIL!". I've read that this tool can be finicky, so I tried different USB ports, cables, compatibility modes, and even installed Win7 on a different partition (I'm on 10).
Anyone have any ideas on where to go from here? The assistance is much appreciated.

leisy said:
Hi all,
I seem to have bricked my LG G3 when I was trying to install TWRP using Kingroot and Autorec MM. When I try and boot normally, I get flashing red and blue lights. When I try to boot into recovery, I get a flashing blue light with about a second in between flashes. When I boot into download mode, I get no flashing lights and Qualcomm HS-USB QDLoader 9008 shows up under the Ports (COM & LPT) section in device manager. When trying to flash back to stock, I get the error "Model Information Check FAIL!". I've read that this tool can be finicky, so I tried different USB ports, cables, compatibility modes, and even installed Win7 on a different partition (I'm on 10).
Anyone have any ideas on where to go from here? The assistance is much appreciated.
Click to expand...
Click to collapse
The 9008 thing in device manager means your hard bricked or semi bricked. You'll have to put it on boarddiag mode by shorting 2 separate pins there's a guide in the general section.
Sent from my iPhone using Tapatalk

hyelton said:
The 9008 thing in device manager means your hard bricked or semi bricked. You'll have to put it on boarddiag mode by shorting 2 separate pins there's a guide in the general section.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I will look that up. Thank you.

leisy said:
I will look that up. Thank you.
Click to expand...
Click to collapse
Your welcome, Here is a link - https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359

hyelton said:
Your welcome, Here is a link - https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
Worked like a charm. Much appreciated.

hyelton said:
Your welcome, Here is a link - https://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Click to expand...
Click to collapse
This is a bit off topic, but would you happen to know where I could download the latest stable release of CM13 for the G3 d850? CM appears to have shut down their mirrors since they killed off development in December.
If you have any other recommendations for G3 ROMs, I'd be open to those as well.

leisy said:
This is a bit off topic, but would you happen to know where I could download the latest stable release of CM13 for the G3 d850? CM appears to have shut down their mirrors since they killed off development in December.
If you have any other recommendations for G3 ROMs, I'd be open to those as well.
Click to expand...
Click to collapse
You'd be better off creating a new thread on this. But to me I'll always recommend stock based Roms over CM due to random issues. But that's me personally.
Sent from my iPhone using Tapatalk

help !. Bricked OP8 t-mobile unlocked

Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks

kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks

kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !

solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF

JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.

Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.

JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......

kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha

JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/

kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you

kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.

kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol

JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.

kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!

JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol

I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com