Database Info

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

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader
Hi there, I've come in to the possession of the most stubbornly bricked phone that I've ever seen . Bought a OPO off Craigslist, someone cracked the screen and sold it for cheap instead of fixing it. It had been remote wiped but still has some strange difficult software. Posted this problem to the Oneplus Forum but have had no response, thought XDA would be more qualified!
From what I can tell it's a Oneplus One that was sold through a re-seller that replaced all the software on the phone with a high-security version of Android. It's called EncroChat and from their website (encrochat.network or encrochatsure.com) it looks like it removes the recovery from the phone and replaces it with an EncroChat OS (some kind of Cyanogen) that you can boot to in addition to the Android OS.
Well I assume during the remote wipe something went wrong with the software and the phone no longer really functions. It boots up fine but can't connect to Wifi, cellular, not detected when connected to my PC, and has no real apps to speak of. I think most of the device's drivers are missing. Trying to boot to recovery instead boots to their EncroChat OS which is locked behind a password that neither I nor the person I bought it from knows.
I can get to fastboot and my PC will detect the phone then but running the bootloader unlock command doesn't work, the phone just reboots into the locked EncroChat OS. My idea now is to try and hardbrick the phone and then re-do everything on the phone over again, but I can't figure out how to do that. Does anyone else have any ideas?

Contacting EncroChat
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
evronetwork said:
Had one GOOD soft brick in the past, I've used coloros rom(from the Chinese OnePlus One) and fix my phone ...it deleted all media of course but manage to unbrick the phone. Don't ask me how to, it's been a while, google it
It would fix even the most stubborn soft bricks you'll see. Before that I tried everything that was available at the time, no boot as well only fastboot(not even recovery)
Click to expand...
Click to collapse

broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
For your phone to be recognized in your PC as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008, you need to install proper drivers. follow this guide
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
let me know, if I can help you furthermore.

broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )

Thanks!
evronetwork said:
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Click to expand...
Click to collapse
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!

broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
I read just the other day that someone needs the 64gb image instead of the 16gb image. You did so well so far, I'm sure you'll figure this one out. Congrats! "Encrochat Beware!"
The mention of the 64gb vs 16gb image is here:
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
He links to the images here:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

help
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????

redi.c said:
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
Click to expand...
Click to collapse
Hi there, sorry in advance this might not be very helpful in your situation. I ended up using the ColorOS repair tool for Oneplus One that I mentioned earlier in the post. It turned out I just didn't have the correct drivers so once I sorted those out the tool was able to bypass all the software and replace everything on the phone so that I could then install my own OS.
I guess the trick would be to find a version of this tool for OneplusX. I'm not sure if there is one available, I haven't looked. Maybe make a separate post about that? The ColorOS tool I'm talking about is from here: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136 and it just looks directly for the Qualcomm chip and writes to that. I'm not sure where that tool came from, if it made its way out of Oneplus directly or if someone created it afterwards...

Bricked OP7P ON DP3

I recently installed Android Q DP3 and it ended up bricking my phone. Now it won't turn on. When holding the power plus volumes button all that shows up is Upgrade Download Failed!!! Please check your download flow is right. Can anyone help me in finding a fix please?

Strike99Fear said:
I recently installed Android Q DP3 and it ended up bricking my phone. Now it won't turn on. When holding the power plus volumes button all that shows up is Upgrade Download Failed!!! Please check your download flow is right. Can anyone help me in finding a fix please?
Click to expand...
Click to collapse
Try this, hope you get your device back to working state, cheers
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

vtec303 said:
Try this, hope you get your device back to working state, cheers
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Tried that but got stuck in param preload device not match image

Strike99Fear said:
Tried that but got stuck in param preload device not match image
Click to expand...
Click to collapse
have you got the t-mobile device or international or European? cheers

Strike99Fear said:
I recently installed Android Q DP3 and it ended up bricking my phone. Now it won't turn on. When holding the power plus volumes button all that shows up is Upgrade Download Failed!!! Please check your download flow is right. Can anyone help me in finding a fix please?
Click to expand...
Click to collapse
Also, is the phone bootloader unlocked beforehand? Just wondering.

Strike99Fear said:
Tried that but got stuck in param preload device not match image
Click to expand...
Click to collapse
Make sure you have the OnePlus USB drivers installed on your PC. They're contained in the folder titled "L2" in the archive in the post you linked.

Strike99Fear said:
I recently installed Android Q DP3 and it ended up bricking my phone. Now it won't turn on. When holding the power plus volumes button all that shows up is Upgrade Download Failed!!! Please check your download flow is right. Can anyone help me in finding a fix please?
Click to expand...
Click to collapse
Did you ever come up with a fix for this? I'm having the same problem.

el80ne said:
Did you ever come up with a fix for this? I'm having the same problem.
Click to expand...
Click to collapse
Had the same issue when I unplugged the phone accidentally during the qualcomm download process in MSN tool. When you plug it in maybe thinking that the phone is off (EDL mode is barely noticable when it's booted in this state and seems like off) when msntool is still enabled or on start the download starts no matter what.
When you get stuck on param preload it's 99% a bad or old driver. I learned this the hard way.
What you have to do is open device manager and delete all Qualcomm 9008 devices (also delete the drivers when the prompt is asking you). You may need to click on "view" and "show hidden devices" and click through all usb connections.
When done, install this Qualcomm USB Driver. I found it when I had the same issue, and since I've installed it, it works perfectly.
Qualcomm USB Driver v1.0.exe
Nextcloud
anphex.one
I hosted it on my own server since I get HTTP 503 error on AFH and I am not even sure I can upload there without registering. It's not worth the hassle since I am not even really a prosumer .
Hope that helps you fellow troubled people.

anphex said:
Had the same issue when I unplugged the phone accidentally during the qualcomm download process in MSN tool. When you plug it in maybe thinking that the phone is off (EDL mode is barely noticable when it's booted in this state and seems like off) when msntool is still enabled or on start the download starts no matter what.
When you get stuck on param preload it's 99% a bad or old driver. I learned this the hard way.
What you have to do is open device manager and delete all Qualcomm 9008 devices (also delete the drivers when the prompt is asking you). You may need to click on "view" and "show hidden devices" and click through all usb connections.
When done, install this Qualcomm USB Driver. I found it when I had the same issue, and since I've installed it, it works perfectly.
Qualcomm USB Driver v1.0.exe
Nextcloud
anphex.one
I hosted it on my own server since I get HTTP 503 error on AFH and I am not even sure I can upload there without registering. It's not worth the hassle since I am not even really a prosumer .
Hope that helps you fellow troubled people.
Click to expand...
Click to collapse
Thank you for this, never really was able to use MSM due to the param preload issue... Tried many times. Will give this a go.
Thank you for sharing.

I moved the share of the file to a more long lasting location on my server and this brokee the link in the Quote from @soka. Make sure to use this one. Maybe some veteran could mirror it on AFH or the likes?
Qualcomm USB Driver v1.0.exe
Nextcloud
anphex.one

T-Mobile OnePlus -- Hard (HARD) Brick

Sorry for lack of details, but I'm not sure it will help anyway. Feeling pretty bad right now.
T-Mobile Oneplus 7 Pro. 256GB version.
I wanted to go to stock OxygenOS after buying the branded version two weeks ago.
I successfully got T-Mobile to unlock my SIM, and got OnePlus to send me unlock code for my bootloader after a week.
Successfully unlocked via fastboot. Tried several times to flash TWRP and no success using fastboot.
Tried MSM-Downloader from guacamole_21_O.07_190512_repack and successfully held volume both buttons to connect to the PC. MSM-Downloader said it was successfully connected.
I cannot find the exact error message I got from MSM-Downloader, but it said it didn't match plus another error message. At that point, my heart sank.
USB Device Not Recognized keeps popping up on windows again and again, while the connect sound plays. Doesn't matter if I hold down the volume buttons or not.
Can't get into qualcomm EDL mode. My guess is I hosed my boot and now it restarts endlessly when connected to anything at all.
Is this the end of my journey? I did tons of research on the best phone and the best deals available to save money, but looks like I played myself here with lack of caution.

I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.

bmg1001 said:
I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.
Click to expand...
Click to collapse
I cannot get into EDL. Regardless of what buttons I press (I am holding both volume buttons down in excess of 5 seconds) when connecting USB to the phone, Windows makes the "connect" sound endlessly and the driver isn't recognized.
If I can get into EDL, I will definitely try the above.

Do you have the proper drivers installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.

bmg1001 said:
Do you have the proper URL installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.
Click to expand...
Click to collapse
Ok. I may be making progress thanks to your help but do have some hurdles I can see.
I do see the device when I hook it up to another computer. It shows up as Unknown USB Device (Device Descriptor Request Failed).
When I go to device manager to manually update the driver, and browse to the location I extracted the CAB file into, I see lots of devices to choose from, but the Qualcomm driver cab file list does not show "Qualcomm HS-USB QDLoader 9008" as an option. I see many Qualcomm USB Composite Devices in the list but none I have chosen seem to work (install fails).

Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?

bmg1001 said:
Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?
Click to expand...
Click to collapse
Yes, that is correct. Same cable i used to get into fastboot, etc... The original PC I caused the problems with recognized the device differently (showed up as a Qualcomm device) when I got into EDL with it before.
Edit: First event when plugging it into this second PC under device properties:
Device USB\VID_0000&PID_0002\5&3c8d678&0&2 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_0000&PID_0000\5&1AE39384&0&2
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0xF000FFFFFFFFF000
Present: false
Status: 0xC0000719

I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.

bmg1001 said:
I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.
Click to expand...
Click to collapse
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?

unluckyoneplus7pro said:
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?
Click to expand...
Click to collapse
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
I'll try there next. Can't seem to get any of my windows machines to recognize the thing.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.

unluckyoneplus7pro said:
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.
Click to expand...
Click to collapse
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.

razorshiv said:
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.
Click to expand...
Click to collapse
That's pretty cool. Makes the whole process much less stressful.
Got it up and running with international version. Now to see if I can get LOS installed. My sincere thanks to all and apologies for crapping up the board with my panic. I thought I had really screwed up, but it appears it was just stuck in EDL mode and needed a hard (HARD) reset.

Hey man, thanks for the donation. Glad you were able to get your phone up and running!

Holy Sh*t man. I know 5 bucks ain't much but I wanted to thank you so much. I thought I was fukd

Moto G7 Power XT1955-4 Hard Brick

Hello!
I think i trashed my phone, after flashing PixelExperience it didnt wake up after rebooting.
It appears to be completely dead,doesnt respond to any of my boot or fastboot attempts and windows doesnt recognize it either.
Ive read about unbrick-usb-jigs but cant find a tutorial how to make one for usb-c, would that even work for me?
LG
joe

Peppo420 said:
Hello!
I think i trashed my phone, after flashing PixelExperience it didnt wake up after rebooting.
It appears to be completely dead,doesnt respond to any of my boot or fastboot attempts and windows doesnt recognize it either.
Ive read about unbrick-usb-jigs but cant find a tutorial how to make one for usb-c, would that even work for me?
LG
joe
Click to expand...
Click to collapse
What phone u have? https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw. Go here I have the files u need

roadkill42 said:
What phone u have?
Click to expand...
Click to collapse
Moto G7 Power as it says in the title lol
I was just able to make some progress
Im following this guide https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 and got my phone to show up properly in the device manager by installing a qualcom driver on my pc.

Peppo420 said:
Moto G7 Power as it says in the title lol
I was just able to make some progress
Im following this guide https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 and got my phone to show up properly in the device manager by installing a qualcom driver on my pc.
Click to expand...
Click to collapse
Ok I have a program and one file that will get u up and running to big to post here let me know at that address I gave you