Related
Hi, I think my phone is hard brick. I tried to follow this method:
To everyone who donated, I love y'all. This took a really long time to get lol but it's straight from support and I did not make any modifications to it; I hope it helps a lot of people. The revision is listed in the archive, I believe it's guacamole_21_O.07_190512_repack and the L2 drivers are included as well. MSM Tool/Guac for all
guacamole_21_O.07_190512_repack
Here are some instructions, kinda:
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
But my pc don't recognized my Oneplus. I don't know if I have the good driver. What can I do ?
Thanks
MrMegaBoss said:
Hi, I think my phone is hard brick. I tried to follow this method:
But my pc don't recognized my Oneplus. I don't know if I have the good driver. What can I do ?
Thanks
Click to expand...
Click to collapse
Can you mode Fastboot or no ?
MrMegaBoss said:
Hi, I think my phone is hard brick. I tried to follow this method:
But my pc don't recognized my Oneplus. I don't know if I have the good driver. What can I do ?
Thanks
Click to expand...
Click to collapse
Unbrick tool also tested? https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
MrMegaBoss said:
Hi, I think my phone is hard brick. I tried to follow this method:
But my pc don't recognized my Oneplus. I don't know if I have the good driver. What can I do ?
Thanks
Click to expand...
Click to collapse
Download msm tool latest from here
https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
-Install qualcomm 9008 driver
-Restart your pc
-Extraxt msm tool and open msm.exe
-Switch off your phone
-Now press both up & down volume button and -connect the usb cable.
-Now if you installed 9008 qualcomm driver correctly then your pc detect automatically your phone in edl mode....and you can easily revive your phone...
Enjoy
Or if u dont understand this thread then... Go and search on YouTube...
After trying to install twrp recovery on my oneplus 9 I started getting the "Qualcomm Crashdump" error. After trying to fix this error through fastboot, I flashed a supposed compilation for the oneplus 9. After that the phone was dead and did not give any response.
I have tried to solve it with the msm tool on 3 laptops with different versions of windows (8, 10 and 11), installing all kinds of qualcomm drivers (first deleting the previous ones to avoid errors) and using different versions of the msm tool downloaded from different sites, different cables, different ports (on laptops with windows 10 and 8 I tried usb 2.0 and 3.0 ports. Laptot with windows 11 does not have usb 2.0), different button combinations (vol + and power, vol- and power, vol- vol + and power, power solo, vol + solo, vol - solo, vol + and vol-). I even tried different positions of the notification slider to rule out. But the msm tool always returns the error "Sahara Communications Failed, try again after power off phone (FH: 258)" after reaching the time counter at 18 seconds in the step "Start Donwload Firehose Binary" even though the phone it is apparently off or completely dead.
When connecting the device to the pc it appears as "Qualcomm HS-USB QDLoader 9008 (COM3)" without any exclamation point or anything strange. I tried to install the drivers by disabling the windows driver signing on the 3 laptops.
Tried holding down all button combinations after the sahara error comes up but it doesn't work either.
I do not know what to do now. I'm desperate.
Help
By the way, I want to clarify that I am Spanish, since I suppose that my English will be very bad.
EDITED: (The whole process was done on a laptop with windows 11 and usb 3.0 ports)
I solved it by doing the following:
What I did was use the msm tool for the indian op9 pro with the option "sha256 check" unchecked and the option "Use lite firehose" checked. Doing these steps the msm tool did not give any failure. Following this I loaded the device and even started it with the op9 pro india rom to test it (it is not recommended to leave this rom because it has certain errors in the image).
Finally I turned off the device and I did the same process with the msm tool for the global op9 normal, but with the default options.
Use this thread. Thread '# Solved # Global MSM op9 Flashing' https://forum.xda-developers.com/t/solved-global-msm-op9-flashing.4373511/
mattie_49 said:
Use this thread. Thread '# Solved # Global MSM op9 Flashing' https://forum.xda-developers.com/t/solved-global-msm-op9-flashing.4373511/
Click to expand...
Click to collapse
Ok, after trying what one of the answers in that thread says (disabling the "Sha256 check" box and activating the "Use Lite Firehose" box) I have managed to switch to "Param preload" and the error it returns is the next:
The device does not match the image
For what it's worth my device is the LE2110 model with gloval rom.
Thank you for your time and for responding so quickly.
Angel Cubero said:
Ok, after trying what one of the answers in that thread says (disabling the "Sha256 check" box and activating the "Use Lite Firehose" box) I have managed to switch to "Param preload" and the error it returns is the next:
The device does not match the image
For what it's worth my device is the LE2110 model with gloval rom.
Thank you for your time and for responding so quickly.
Click to expand...
Click to collapse
You have to do that with the Indian op9 pro msm tool. Then after you get device up and running flash stock firmware. Either by local upgrade off oxygen updater or through fastboot.
mattie_49 said:
You have to do those on the Indian op9 pro msm tool. Then after you get device up and running flash stock firmware. Either by local upgrade off oxygen updater or through fastboot.
Click to expand...
Click to collapse
Testing with the version of the msm tool for the oneplus 9 pro india returns the error:
Unsupported Target O2
So I will try the version for the oneplus 9 pro global.
mattie_49 said:
You have to do that with the Indian op9 pro msm tool. Then after you get device up and running flash stock firmware. Either by local upgrade off oxygen updater or through fastboot.
Click to expand...
Click to collapse
I have not been able to do anything with the Indian op9 pro msm tool version or with the global version. In the Indian version the aforementioned error appears and in the global one the error "Devices not match image" appears.
I can't think of what else to do.
Angel Cubero said:
I have not been able to do anything with the Indian op9 pro msm tool version or with the global version. In the Indian version the aforementioned error appears and in the global one the error "Devices not match image" appears.
I can't think of what else to do.
Click to expand...
Click to collapse
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/India_LE15DA/R%20(11)/OnePlus_9_Pro_India_OxygenOS_11.2.4.4.zip
Use this one and try to untic sha-256 check and tic use lite-firehose.
mattie_49 said:
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/India_LE15DA/R%20(11)/OnePlus_9_Pro_India_OxygenOS_11.2.4.4.zip
Use this one and try to untic sha-256 check and tic use lite-firehose.
Click to expand...
Click to collapse
Again "Unsupported Target O2".
Angel Cubero said:
Again "Unsupported Target O2".
Click to expand...
Click to collapse
OnePlus customer support and get a remote session. They will msm for you
mattie_49 said:
OnePlus customer support and get a remote session. They will msm for you
Click to expand...
Click to collapse
Obviously that will cost money, right?
Angel Cubero said:
After trying to install twrp recovery on my oneplus 9 I started getting the "Qualcomm Crashdump" error. After trying to fix this error through fastboot, I flashed a supposed compilation for the oneplus 9. After that the phone was dead and did not give any response.
I have tried to solve it with the msm tool on 3 laptops with different versions of windows (8, 10 and 11), installing all kinds of qualcomm drivers (first deleting the previous ones to avoid errors) and using different versions of the msm tool downloaded from different sites, different cables, different ports (on laptops with windows 10 and 8 I tried usb 2.0 and 3.0 ports. Laptot with windows 11 does not have usb 2.0), different button combinations (vol + and power, vol- and power, vol- vol + and power, power solo, vol + solo, vol - solo, vol + and vol-). I even tried different positions of the notification slider to rule out. But the msm tool always returns the error "Sahara Communications Failed, try again after power off phone (FH: 258)" after reaching the time counter at 18 seconds in the step "Start Donwload Firehose Binary" even though the phone it is apparently off or completely dead.
When connecting the device to the pc it appears as "Qualcomm HS-USB QDLoader 9008 (COM3)" without any exclamation point or anything strange. I tried to install the drivers by disabling the windows driver signing on the 3 laptops.
Tried holding down all button combinations after the sahara error comes up but it doesn't work either.
I do not know what to do now. I'm desperate.
Help
By the way, I want to clarify that I am Spanish, since I suppose that my English will be very bad.
Click to expand...
Click to collapse
Angel Cubero said:
After trying to install twrp recovery on my oneplus 9 I started getting the "Qualcomm Crashdump" error. After trying to fix this error through fastboot, I flashed a supposed compilation for the oneplus 9. After that the phone was dead and did not give any response.
I have tried to solve it with the msm tool on 3 laptops with different versions of windows (8, 10 and 11), installing all kinds of qualcomm drivers (first deleting the previous ones to avoid errors) and using different versions of the msm tool downloaded from different sites, different cables, different ports (on laptops with windows 10 and 8 I tried usb 2.0 and 3.0 ports. Laptot with windows 11 does not have usb 2.0), different button combinations (vol + and power, vol- and power, vol- vol + and power, power solo, vol + solo, vol - solo, vol + and vol-). I even tried different positions of the notification slider to rule out. But the msm tool always returns the error "Sahara Communications Failed, try again after power off phone (FH: 258)" after reaching the time counter at 18 seconds in the step "Start Donwload Firehose Binary" even though the phone it is apparently off or completely dead.
When connecting the device to the pc it appears as "Qualcomm HS-USB QDLoader 9008 (COM3)" without any exclamation point or anything strange. I tried to install the drivers by disabling the windows driver signing on the 3 laptops.
Tried holding down all button combinations after the sahara error comes up but it doesn't work either.
I do not know what to do now. I'm desperate.
Help
By the way, I want to clarify that I am Spanish, since I suppose that my English will be very bad.
Click to expand...
Click to collapse
hi bro , i have the same issue like you , did you found a solution , can you help me plz
thanks
best regard
You can try this and see if it works: (last post)
Display becomes unresponsive after OOS 12 update
I upgraded my OnePlus 9 LE2115 from OOS 11 to OOS 12, and every time the phone reboots after completing the update, the touch screen is completely unresponsive, so it stays stuck at the lock screen forever. I upgraded from OOS 11.2.10.10 to OOS...
forum.xda-developers.com
Angel Cubero said:
After trying to install twrp recovery on my oneplus 9 I started getting the "Qualcomm Crashdump" error. After trying to fix this error through fastboot, I flashed a supposed compilation for the oneplus 9. After that the phone was dead and did not give any response.
I have tried to solve it with the msm tool on 3 laptops with different versions of windows (8, 10 and 11), installing all kinds of qualcomm drivers (first deleting the previous ones to avoid errors) and using different versions of the msm tool downloaded from different sites, different cables, different ports (on laptops with windows 10 and 8 I tried usb 2.0 and 3.0 ports. Laptot with windows 11 does not have usb 2.0), different button combinations (vol + and power, vol- and power, vol- vol + and power, power solo, vol + solo, vol - solo, vol + and vol-). I even tried different positions of the notification slider to rule out. But the msm tool always returns the error "Sahara Communications Failed, try again after power off phone (FH: 258)" after reaching the time counter at 18 seconds in the step "Start Donwload Firehose Binary" even though the phone it is apparently off or completely dead.
When connecting the device to the pc it appears as "Qualcomm HS-USB QDLoader 9008 (COM3)" without any exclamation point or anything strange. I tried to install the drivers by disabling the windows driver signing on the 3 laptops.
Tried holding down all button combinations after the sahara error comes up but it doesn't work either.
I do not know what to do now. I'm desperate.
Help
By the way, I want to clarify that I am Spanish, since I suppose that my English will be very bad.
EDITED: (The whole process was done on a laptop with windows 11 and usb 3.0 ports)
I solved it by doing the following:
What I did was use the msm tool for the indian op9 pro with the option "sha256 check" unchecked and the option "Use lite firehose" checked. Doing these steps the msm tool did not give any failure. Following this I loaded the device and even started it with the op9 pro india rom to test it (it is not recommended to leave this rom because it has certain errors in the image).
Finally I turned off the device and I did the same process with the msm tool for the global op9 pro, but with the default options.
Click to expand...
Click to collapse
You have, single-handedly, saved me from having to send my phone into OnePlus for repair. I was getting the same error where the global MSM tool would not work. I downloaded the Indian version, unchecked sha256, and checked use Lite firehose. It restored my phone on the first try.
Once my phone booted, I went back into EDL mode by powering off my phone fully, plugging it back into the computer, and holding the power + vol up + vol down buttons. I was then able to use the Global MSM tool to restore the Global ROM.
THANK YOU SOO MUCH!!!!
LE2125
Hi, this thread seems to be kinda old but I am trying this on my LE2110 and it always fails at Downloading super.img..
I actually tried a different MSM (OnePlus 9 EU) one month ago and it worked but now it does not
Hope that it works soon i guess
CitaroSR said:
Hi, this thread seems to be kinda old but I am trying this on my LE2110 and it always fails at Downloading super.img..
I actually tried a different MSM (OnePlus 9 EU) one month ago and it worked but now it does not
Hope that it works soon i guess
Click to expand...
Click to collapse
Is the pc plugged into the internet? It can aquire the needed files to fix device if it's connected to data.
mattie_49 said:
Is the pc plugged into the internet? It can aquire the needed files to fix device if it's connected to data.
Click to expand...
Click to collapse
yes it is connected to the internet
This MSM Tool worked (it worked last time too but it did not work since yesterday for me, until now)
thank you for your reply anyway. My phone is restored!
So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me
Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.
gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?
gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
download the correct drivers and replace them in the device manager
gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!
worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time
Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse
Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com
So I recently changed phones, as one of my main hobbies is tinkering with Smartphones and their respective OS's , I decided to Unlock my Xiaomi Redmi 9A (My previous phone) and flashed Ubuntu Touch to it as it was stated as a supported device, using their prebuilt simple installer app seemed to work but midway through the install the installer crashed and the phone powered off, When I turned it I realised it was stuck in a Bootloop, I tried Power + Vol Up for Recovery, that didn't work and neither did Power + Vold Down for Fastboot i tried ADB to push a command to enter EDL (Qualcomm Emergency Download Mode) but that didn't work either. Does any body have any suggestions for how I could get this device running again?
Hector_GH11 said:
Hector_GH11 said:
So I recently changed phones, as one of my main hobbies is tinkering with Smartphones and their respective OS's , I decided to Unlock my Xiaomi Redmi 9A (My previous phone) and flashed Ubuntu Touch to it as it was stated as a supported device, using their prebuilt simple installer app seemed to work but midway through the install the installer crashed and the phone powered off, When I turned it I realised it was stuck in a Bootloop, I tried Power + Vol Up for Recovery, that didn't work and neither did Power + Vold Down for Fastboot i tried ADB to push a command to enter EDL (Qualcomm Emergency Download Mode) but that didn't work either. Does any body have any suggestions for how I could get this device running again?
Click to expand...
Click to collapse
Yea sure, try flashing with Sp Flash Tool
(Btw this device isn't a Qualcomm procesor so no EDL).
You can solve it with Sp Flash Tool
Needs:
- Pc/Laptop
- Usb Cable
- Miui Rom ( Choose your version : https://xiaomifirmwareupdater.com/miui/dandelion/ )
- Mtk Bypass Tool + LibUsb : https://www.bypassfrpfiles.com/2021/02/mediatek-bypass-tool-mct/
( You have some steps to do here - see the website)
-----------------------------------------------------------------
Flashing :
1. Download all the things I gived to you + drivers.
2. Extract and open Sp Flash Tool and MTK Bypass Tool ( Be sure to install the libusb driver)
3.Open MTK Bypass Tool and click on Bypass button.
4. Hold all the buttons from the phone ( or try power + vol up / down, if all doesn't work)
5. When holding the buttons, connect the phone to the pc, wait a few seconds until it finishes to bypass ( Wait ~2 seconds more after bypassing - holding the buttons) ( Hold buttons - connect phone --> PC with usb cable -- wait like 2 seconds after bypassing to work properly.)
6. Open Sp Flash Tool.
7. Select your download agent ( MTK_AllinOne) - from program folder
8. Select your rom in scatter file section ( to be more exactly, choose the mt6765...... File from the rom)
9. Be sure to check Sp Flash Tool Settings - check if u have selected your device port
10. Where it shows - *"Download Only*" ( you can use that, but for me worked Firmware upgrade) - NOT Format
11. Press download button from up
12. If you need help, here is my discord :
raresgabriel #4803
Click to expand...
Click to collapse
Click on " Click to expand" to see the instructions
Rares6567 said:
Click on " Click to expand" to see the instructions
Click to expand...
Click to collapse
Thanks, Will Try!
Hector_GH11 said:
Thanks, Will Try!
Click to expand...
Click to collapse
Ok, Good Luck!!!!
Rares6567 said:
Ok, Good Luck!!!!
Click to expand...
Click to collapse
It's stuck on a Red Bar saying Downloading DA 100%, and it doesn't do anything else. The phone shows up on Mediatek COM Port 5.
It now says USB Device not Recognised. Yada yada yada, USB device corrupted.
Hector_GH11 said:
It now says USB Device not Recognised. Yada yada yada, USB device corrupted.
Click to expand...
Click to collapse
Ok so discord
Rares6567 said:
Ok so discord
Click to expand...
Click to collapse
I still have this problem my pc does not tell me (usb not recognized) What I wanted to do was downgreade from 12.5.6 to 12.0.5. but my redmi is dead
N0tvich said:
I still have this problem my pc does not tell me (usb not recognized) What I wanted to do was downgreade from 12.5.6 to 12.0.5. but my redmi is dead
Click to expand...
Click to collapse
You need to take the phone case and unplug the battery, and try to flash again.
Rares6567 said:
You need to take the phone case and unplug the battery, and try to flash again.
Click to expand...
Click to collapse
The battery thing worked for me (now I can't go from there, Mr. disconnects and Mr. connects) I was able to get there, I don't know how to continue
N0tvich said:
The battery thing worked for me (now I can't go from there, Mr. disconnects and Mr. connects) I was able to get there, I don't know how to continue
Click to expand...
Click to collapse
Unplug and plug the battery and connect phone.
Try reinstalling drivers
I corrupted my phone's root/system/etc files and when I restarted it, it wouldn't turn on and got stuck on the realme logo. i hold my phone vol+ and - and power key and when the realme logo comes up, i release the power key, i think download mode opens, but it usb device is faulty for 1-2 seconds and disappears immediately, meanwhile in device manager it shows unknown device for 1-2 seconds and disappears. After 10-15 seconds there is a usb connection sound but nothing happens. I can send adb commands but I have to confirm the confirmation window but I cant.
Please help me, how can I fix it?
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Renate said:
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Click to expand...
Click to collapse
Yes, I get the unauthorized message as below. If I can somehow authorize it, I will be able to enter fastboot mode and flash the stock rom.
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Okay, I'm trying
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
mvikrant97 said:
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
Click to expand...
Click to collapse
I updated with Driver Booster, no luck.
I only tried the front USB ports, do I need the back ones? There are 2 2.0 and 1 3.0 port on the front
The computer is new so I don't think it's defective, the phone is charging and I was using it before it went brick.
I also modified the boot file to install a new GSI and used the following guide.
Spoiler
First, you need to unlock fastbootd:
1. Download the stock ROM version 91: Download and extract the .pac file Link
2. Install the SPD research tool and drivers: GDrive
3. Open it
4. Click on the single gear icon
5. Select the .pac file of the stock rom
6. Wait until it loads
7. Click on the two gear icon
8. Find BOOT in the list
9. Right-click on the path next to it
10. Download here and select boot_r1.img
11. Click OK and then click the arrow icon
12. Turn off your phone
13. Press and hold Power + VolumeDown until you see the text "Downloading"
14. Release the buttons after seeing
15. Wait until you see the text "Passed"
16. Click on the Stop icon, disconnect your phone and turn it on
[/ISPOILER]
@leanord Can you help me?
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Renate said:
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Click to expand...
Click to collapse
I don't fully understand your question, but I have the stock recovery, I didn't install TWRP, and I installed dotOS 5.2 as GSI. I think I corrupted the fastboot, download mode boot files in the root files. I will take it to the service center, but if you have a solution, you can write, I don't want to give money.
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Renate said:
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Click to expand...
Click to collapse
It may have been disabled or because I corrupted system files.
Wanted? I came, to flash the phone, you do not need to press anything except the volume keys, the power button is only a catalyst, you need to hold it down until the screen goes out, and then just Keep the volume - and flash as usual, the main thing is to keep it immediately plugged into the PC with a ready-made flasher
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Luuukie said:
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Click to expand...
Click to collapse
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
leanord said:
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
Click to expand...
Click to collapse
SP Flash Tool doesn't see my device so I can't flash it. If you mean Fastboot, I can't get into it.
By the way, that font that's showing up in my UsbLog is UGLY.
I readjusted things, you can download a new copy that is prettier.
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Renate said:
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Click to expand...
Click to collapse
I'm sorry, I don't know that much. But if you tell me the steps how to do it, I can do it.
@leanord when installing GSI, I flashed boot_r1.img from your Realme C21Y GSI installation guide, did you disable fastboot or something?