Bricked Oneplus 2 not getting detected on pc - OnePlus 2 Q&A, Help & Troubleshooting

Can anyone tell me a way so that the pc detects my bricked OPT? I have tried all combinations but its not getting detected at all

phorcus said:
Can anyone tell me a way so that the pc detects my bricked OPT? I have tried all combinations but its not getting detected at all
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Rebel7022 said:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
finally it got detected but when i run MSM8994DownloadTool.exe as administrator and click on start nothing happens

https://1.bp.blogspot.com/-ZZ-sHUBv...ExaIdiLCYRNQCLcB/s1600/Screenshot+%284%29.png
this is where i am stuck please help guys i am in a fix :'(

Are you sure you disabled driver signature enforcing in Windows? You can't install the qualcomm 9008 serial interface driver without doing this, as this driver is not signed by Microsoft.

pitrus- said:
Are you sure you disabled driver signature enforcing in Windows? You can't install the qualcomm 9008 serial interface driver without doing this, as this driver is not signed by Microsoft.
Click to expand...
Click to collapse
yes i did still it doesn't work, any help would be appreciated

If you power up your phone using volume up in fastboot/bootloader mode and then run fastboot devices, does it list your phone? Just making sure the cable connection works.
If yes, then power down your phone by holding power button until screen goes black (making sure you disconnected usb cable first). Then hold volume up while connecting usb cable (don't touch power button), you should hear Windows detecting a new device, check device manager to see that the qualcomm 9008 usb serial port has been successfully installed and with no warning exclamation mark on it. If all is good, you should now be able the launch the download tool and push the download button to start downloading the file partitions to the phone.

pitrus- said:
If you power up your phone using volume up in fastboot/bootloader mode and then run fastboot devices, does it list your phone? Just making sure the cable connection works.
If yes, then power down your phone by holding power button until screen goes black (making sure you disconnected usb cable first). Then hold volume up while connecting usb cable (don't touch power button), you should hear Windows detecting a new device, check device manager to see that the qualcomm 9008 usb serial port has been successfully installed and with no warning exclamation mark on it. If all is good, you should now be able the launch the download tool and push the download button to start downloading the file partitions to the phone.
Click to expand...
Click to collapse
Thanks a lot for writing out to me, but the thing is that my phone is already dead and i had given up all the hope that i had but luckily it got detected and i cannot boot into fastboot mode or bootloader mode the screen is already black, do you think i still have hope? the phone has been detected as qualcomm 9008 in ports in device manager

phorcus said:
Thanks a lot for writing out to me, but the thing is that my phone is already dead and i had given up all the hope that i had but luckily it got detected and i cannot boot into fastboot mode or bootloader mode the screen is already black, do you think i still have hope? the phone has been detected as qualcomm 9008 in ports in device manager
Click to expand...
Click to collapse
Could it be that the actual screen is dead on your phone? But still, since the PC detects the debug port, it should start restoring the phones partitions when you start downloader tool and press the download button up to the left.

Related

How to use EDL Qualcomm Download cable

Hello,
I have a moto g4 plus with locked bootloader and no OS.
I also have a EDL cable with button, but when i try it my device manager only adds (uknown device) and some error, but i cannot install the qualcomm on that device.
The device automatically goes to fastboot when plugging in usb mode.
You need EDL drivers and also press the button for about 8 seconds just after plugging in the device.
---------- Post added at 12:36 AM ---------- Previous post was at 12:30 AM ----------
There's another way to get into EDL mode that was posted, although it's for a xiaomi device. It uses a modified fastboot.exe to get he device boot into EDL mode...
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Can you help me get the correct drivers?
Im affraid i have tried that method but it said booting to download mode.. and then (remote) command not found
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/
Clicking on the download link will give a .7z file, having QDLoader in the filename... The page is in Turkish though, please translate it.
I have installed the 64 bit one and pressed 8 seconds but still the yellow triangle and uknown usb(unknown device device descriptor request failed)
On the old LG G2, you have to short a capacitor with tweezers to put it in this mode--maybe the same for Athene
HueyT said:
On the old LG G2, you have to short a capacitor with tweezers to put it in this mode--maybe the same for Athene
Click to expand...
Click to collapse
how to do that, i have my phone dissambled now.
codGmer said:
I have installed the 64 bit one and pressed 8 seconds but still the yellow triangle and uknown usb(unknown device device descriptor request failed)
Click to expand...
Click to collapse
my phone is completely dead, no display no fastboot nothing shows on pc. but when I tried to boot it to edl it gives the same error as you faced even though I have all the drivers. if you have found a way to fix this, share with me and Qualcomm flasher rom of moto g4 plus.
emsumit said:
my phone is completely dead, no display no fastboot nothing shows on pc. but when I tried to boot it to edl it gives the same error as you faced even though I have all the drivers. if you have found a way to fix this, share with me and Qualcomm flasher rom of moto g4 plus.
Click to expand...
Click to collapse
Connect it to PC, then go device managers and show me the ports. Then screenshot and give me
Ayan Uchiha Choudhury said:
Connect it to PC, then go device managers and show me the ports. Then screenshot and give me
Click to expand...
Click to collapse
i'm unable to upload the image but it was showing unknown device (device descriptor request failed)
i used edl cable
emsumit said:
i'm unable to upload the image but it was showing unknown device (device descriptor request failed)
i used edl cable
Click to expand...
Click to collapse
Use a normal cable. If it detects anything as Qualcomm, then you're safe
Ayan Uchiha Choudhury said:
Use a normal cable. If it detects anything as Qualcomm, then you're safe
Click to expand...
Click to collapse
With normal cable its shows nothing. It was showing q loader 9008 before giving it to service center, but they did something, it doesn't now.
And now i know it could've fixed with Qualcomm flasher back then.. but now it doesn't connect anymore without edl cable.
edl cable
emsumit said:
With normal cable its shows nothing. It was showing q loader 9008 before giving it to service center, but they did something, it doesn't now.
And now i know it could've fixed with Qualcomm flasher back then.. but now it doesn't connect anymore without edl cable.
Click to expand...
Click to collapse
adb reboot edl

Bricked phone but can still get into EDL mode

Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit
daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible
i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!
A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted
The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.
i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152

Phone not recognized in Fastboot / Download

Three days ago, my phone went off by itself and I had a hard time starting again, it was just loading the bootanimation, I tried to reinstall the ROM, but it did not go into TWRP, although the message Recovery appears on the screen, I insisted and after several attempts, I got into the recovery, formatted everything and I installed the AICP ROM again, and I had to restart,my phone freezes in the LeEco bootloader, then again I insisted until the ROM finally started, but soon realized that it was taking too long to start (30 minutes waiting and nothing).
So I rebooted again, and from then on, I can not go into any mode anymore, trying to access the TWRP, the phone only stays on the Recovery screen until reboot after 2 minutes, when letting the phone try to start the ROM, it only stays on the LeEco screen and restart after 2 minutes, when entering Fastboot, it enters the screen in Fastboot mode, but is not recognized by the computer, not even as unknown device, the same for Download mode.
Is there anything I can try?
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
tsongming said:
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
Click to expand...
Click to collapse
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode.sl Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Well that sucks, if you feel like sending to the phone to China for repair, you can find several shops that are offering to repair any damaged Leeco for $10 and an average cost of $30 for resoldering. On the TaoBao website, use Chrome for translation. Some of their ads mention overseas repair
If it's memory it would be an easy fix for them.
If you don't want to fix it, I highly recommend the Mi8 if it's within your budget, its a perfect phone and you can find them for close to $300. My brother has a Redmi note 6 Pro which is also really nice. He paid $190.
Good Luck.
Sent from my Xiaomi MI 8 using XDA Labs
kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Check out this possible do it yourself fix : https://forum.xda-developers.com/showpost.php?p=79302729&postcount=71

Brick Saved!! OnePlus 8 Pro Oxygen OS 12 to Android 11 downgrade brick saved. Methods I used and pitfalls.

Background:​
OnePlus 8 Pro IN2020
Original OS version is OxygenOS 12 Android 12
How my phone turned into brick:​
Try flashboot unsupported TWRP and other third party recoveries.
After a few tries, eventually causing my phone turning into a brick
What my error looks like:​
Not able to boot into system
Showing "the current image(boot/recovery) have been destroyed"
Can access fastboot and detect by system
​Method:​
Follow the steps in How to UNBRICK OnePlus 8 or 8 Pro! by Max Lee (Thank you my man, Max, for this video)
​Pitfalls in 2022 (IMPORTANT before UNBRICK!):​A USB 2.0 and Third-party USB cable are highly recommended​I was unable to boot into Quadcomm EDL mode while using the stock cable and USB 3.0 connector. Pressing the correct Volumn Up & Volumn Down and Power Button will boot the phone to fastboot in no time.
I successfully got into the EDL mode and finished flashing the phone using my iPad Pro Type-C charging cable which is an USB 2.0 one.
Use a newer version of the Qualcomm driver if you find the device not correctly detected​Use Qualcomm HS-USB QDLoader 9008 driver.
A new Quadcomm driver will help you flash your device correctly the first time!!!
Windows 11 won't let you install unsigned driver by default, but there's a way round​
Press Shift key while click Reboot in start menu to enter Advanced Options
Click Trouble shoot in Advanced Options
Click Advanced options, click Startup Settings then click Restart
After restart press 7 when required
If your computer won't restart, just unplug your phone temporarily
after this your device will detect by your computer correctly.
Pressing buttons requires special timing and preconditions and a few more tries​
To fully power off your phone, press Volume up and Power button for 10 seconds. Release immediately after the screen turns black.
Your phone is in the state of powered off even your screen displaying error message or charging animation, just make sure it's not in fastboot, recovery or booting animations.
Connect your phone to your computer before press Volume up and down and Power Button all at the same time to enter EDL mode.
Prepare yourself with Device Manager and MSM tool open and configured correctly before your phone enter EDL mode. There's a about 10 second window for you to start flashing.
Fail amid your MSM flash process:​Don't panic if you see error message saying you didn't finish flashing​
You can flash it anytime just make sure checking all the things above and enter EDL mode
Check these things:​
Check your Windows can install the unsigned driver correctly
Check Device Manger in Control Panel if your device is correctly detected as a COM device as Qualcomm HS-USB QDLoader 9008 or something like this
Use administrator privilege to open the MSM software
Check your cable connection is stable or not.
Finally, thanks Dr.E (Max Lee) for your help. Without your video instructions, I won't revive my phone. It spares my pain to ask my dad for money for a new phone I don't actually need.
Hope everyone could find some helpful information in this post and flash your phone like a champ.
A even better way to enter EDL mode is power off and unplug your device, and after hold volume up and down at the same time, plug in the USB 2.0 cable to the computer. It works every time!!
i cant join rdl mode always restarting fastboot mode

Question Nothing Phone 1 hard bricked (Edl Mode)

Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
pogradecari said:
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
Click to expand...
Click to collapse
Try holding power+volup+voldown with the phone unplugged from a computer.
If it doesn't work, let me know.
how to boot to edl mode ??
Try this :
Install ADB and Minimal Fastboot drivers through which Windows will recognize your Device.
Enable USB Debugging on your Android Device. You can do this simply by following the given direction:
Settings > About Phone > tap 7 times on the Build Number. This will enable Developer options on it.
Now, again go back to the main Settings > Developer options > USB Debugging and Enable it.
Connect your smartphone with your PC via a USB cable.
Open Command Window by the press and hold Shift Key + right-click of your Mouse.
Choose Open Command Window here.
Type the following command and press the Enter button to check whether the device is connected or not.
" adb devices "
You will see a device serial code on the screen. That means it is successfully connected. Then follow the next step.
Type the command from below and hit enter to Boot into Download Mode (EDL Mode):
" adb reboot edl " or "fastboot oem edl" or "fastboot reboot-edl" or "fastboot reboot edl"
muppetz said:
Try this :
Install ADB and Minimal Fastboot drivers through which Windows will recognize your Device.
Enable USB Debugging on your Android Device. You can do this simply by following the given direction:
Settings > About Phone > tap 7 times on the Build Number. This will enable Developer options on it.
Now, again go back to the main Settings > Developer options > USB Debugging and Enable it.
Connect your smartphone with your PC via a USB cable.
Open Command Window by the press and hold Shift Key + right-click of your Mouse.
Choose Open Command Window here.
Type the following command and press the Enter button to check whether the device is connected or not.
" adb devices "
You will see a device serial code on the screen. That means it is successfully connected. Then follow the next step.
Type the command from below and hit enter to Boot into Download Mode (EDL Mode):
" adb reboot edl "
Click to expand...
Click to collapse
my phone is bricked while flashing stock rom via fastboot
so unable to boot to recovery or bootloader
To begin with, power off your device. If you can’t do so, then you will have to wait until the battery completely drains out.
Now connect one end of the USB cable to your PC, but don’t attach the other end to the device.
Press and hold the Volume Up and Volume Down buttons together for a few seconds.
Now connect the other end of the device to the USB cable.
Your device will now be recognized as Qualcomm HS-USB QDLoader 9008. You may now flash the device-specific firmware to unbrick it.
Even you have a black screen , PC does recognize your phone . Use only a USB 2.0 port . Verify if Qualcomm USB Driver have been installed on Windows .
muppetz said:
To begin with, power off your device. If you can’t do so, then you will have to wait until the battery completely drains out.
Now connect one end of the USB cable to your PC, but don’t attach the other end to the device.
Press and hold the Volume Up and Volume Down buttons together for a few seconds.
Now connect the other end of the device to the USB cable.
Your device will now be recognized as Qualcomm HS-USB QDLoader 9008. You may now flash the device-specific firmware to unbrick it.
Even you have a black screen , PC does recognize your phone . Use only a USB 2.0 port . Verify if drivers have been installed on Windows .
Click to expand...
Click to collapse
tried these steps but phone goes in 900E mode
OK , look then at this :
muppetz said:
OK , look then at this :
Click to expand...
Click to collapse
it does not work as he just changed the drivers from diagnostic mode to qdloader mode
pogradecari said:
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
Click to expand...
Click to collapse
Maybe it's too late already but you can unbrick the phone with this tool
Unbrick / Flash Stock Rom (1.1.7 global) QDLoader 9008 fix | EDL Mode fix
Hi everyone, If your phone (1) does not react on any of yours actions. You may have the same problem. This is an instruction how to fix it without Disassembly. ‼️ Do this at your own risk, I am not responsible for any damage that may occur to...
forum.xda-developers.com
none of these will work
pogradecari said:
none of these will work
Click to expand...
Click to collapse
Why? Have you tried?

Categories

Resources