Related
Hey everyone!
So, I've got a HD1903, 8GB RAM 128GB ROM. I updated to OxygenOS 11.0.02, but it was still buggy as hell, so I decided to downgrade. I also had rooted the phone, and decided to get rid of that too. I went to the stock fastboot roms page, downloaded the 10.0.13 ROM and used 'flash-all.bat' file to clear everything. But halfway, it reboots, goes into recovery, then goes to Qualcomm Crashdump mode. That's it. No code or anything, just Qualcomm Crashdump mode, in Blue and Red letters. I tried to hold vol-up, vol-down and power to get into fastboot, but it just loads the fastboot splash screen, then goes back to the same qualcomm crashdump mode screen. Even if i try to hard reset it, by holding vol-up and power, it still goes to the same screen.
Anyone know what to do? I have no idea how to use the 'MSM tool' that everyone talks about, so any guiding advice would be great!
Thanks!
DM me here - https://www.facebook.com/prantor.khan.16 I'll help
HueyT said:
Click to expand...
Click to collapse
I didn't install TWRP, this was all on stock recovery. I also cannot get into fastboot mode.
Msmtool does not need twrp or fastboot--just the software, rom image, drivers, and button combo pushes and holding
OK, so I got it working again, thanks to the advice of reddit users, discord users and the latest msm tool and some googling. I held the vol-up and vol-down buttons for 30 seconds, then connected it to the laptop, with msm running, to a usb 2.0 port, and pressed start. hey presto, it worked. Thanks guys!!
scoped_ar07 said:
Hello
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: only works on Windows PC
1. Unzip the contents of the RAR into a folder.
2. Run the MSM application
3. Click Start.
4. Connect the cell phone in EDL mode (volume up + down button)
5. Wait for the process to finish (it takes a long time, please be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically boot into fastboot mode and display a menu, but if it doesn't and instead boots to the T-mobile screen, you need to force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you need to unlock the bootloader with the command from a Windows CMD window, but you need to download this ADB tool first.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a Windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this time your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, on the command line, run the flash-all.bat file
12. When the phone restarts and the yellow and white letters appear informing that the phone is not safe because the bootloader is unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-PC will detect the phone again in fastboot mode and continue to flash
-Leave the phone and PC still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (ignore it)
13. Finally, the computer will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just turn it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before locking the bootloader again (if you plan to do so) first update via OTA, to the most recent version of Oxygen, otherwise the system will crash again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Stronger1101 said:
Hi
Using the MSM tool is very simple, you just have to download it from this link.
hotdogt_11_O.01_190920 op7t tmo usa patched unlock bootloader.7z
drive.google.com
NOTE: It only works on Windows pc
1. Unzip the contents of the RAR into a
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it is delayed)
6. A message appears informing that the equipment is damaged, do not be careful.
7- Now you must unlock the bootloader with a command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8. Now run this command while the cell phone is connected in Fastboot mode.
fastboo ...
Hi
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: Only works on Windows PC
1. Unzip the contents of the RAR into a folder
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it's time consuming, be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically start in fastboot mode and show a menu, but if it doesn't and instead starts on the T-mobile screen, you must force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you must unlock the bootloader with command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this moment your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, in the command line, run the file flash-all.bat
12. When the phone restarts and the yellow and white letters appear informing that the phone is unsafe due to having the bootloader unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-The PC will detect the phone again in fastboot mode, and continue flashing
-Leave the phone and the pc still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (don't pay attention)
13. Finally the equipment will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just force it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before blocking the bootloader again (if you plan to do it) first update via OTA, to the most recent version of Oxygen, otherwise it will crash the system again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Oh wow that was a long and well defined post. Thank you for taking the time to type it out.
As it happens, I fixed my issue already (IDK if there's a solved flair for XDA or something?). I downloaded the latest (10.0.15) MSM Tool from the XDA page, held the vol-up and vol-down for 30 seconds this time (as per advice from discord users) got the phone into edl mode, connected to a usb 2.0 port and let msm tool do it's thing. Everything is working perfectly now.
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Āryan-9909 said:
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Click to expand...
Click to collapse
Yes, theyll just change out the motherboard
HueyT said:
Yes, theyll just change out the motherboard
Click to expand...
Click to collapse
If they're going to just change the motherboard, I wonder what the EDL mode is meant for. Anyways, I won't go for motherboard change one can buy a new and better phone at that kinda price.
Anyways, I Fixed it through EDL method, you have to hold vol up and down simultaneously and immediately connect to windows (while still holding both buttons) via original USB cable. Check with Device manager if your device shows up, it's easy enough but you might have to keep trying to you get it right. Thereafter, disable driver verification in windows and if Sahara communications failed message appears in msm tool, turn off phone and repeat the procedure again.
The repair peeps only fix hardware and not software. It's more cost effective for them to swap out hardware faster than messing with msmtool like us
Āryan-9909 said:
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Click to expand...
Click to collapse
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
scoped_ar07 said:
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
Click to expand...
Click to collapse
You don't have to hold buttons for that long, you can immediately connect it to PC. There is usually a sound to indicate that a new device has been connected to windows, you can also keep device manager open for confirmation. This video really helped.
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
hightech316 said:
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
Click to expand...
Click to collapse
Qualcomm 9008 drivers too?
HueyT said:
Qualcomm 9008 drivers too?
Click to expand...
Click to collapse
Yes.
I went ahead and ran another factory reset via recovery, no luck.
New cable, another PC?
HueyT said:
New cable, another PC?
Click to expand...
Click to collapse
Tried both, my desktop would always connect, adb, fastboot, etc.
I had just just freshly installed oneplus drivers including qualcomm on my laptop. Device was not recognized before driver installation or after.
Figure id try on my Mac, and linux laptop. no dice.
ADB is enabled.
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" . Not phone will not even be seen
Hey all,
So i've unlocked by bootloader, flashed a custom recovery to then proceed with LineageOS flashing. However it went completely wrong as on reboot i'm stuck with the bootloader unlocked warning and then a blackscreen.
I still have access to fastboot mode however it's impossible to flash a customer recovery ("No Such Partition") and also impossible to directly "fastboot boot recovery.img" as the phone simply reboots on the warning and then blackscreen.
The only solution seems to get the device to qualcomm EDL mode and reflash all with the MSM tool (which I have as well as all the drivers) however I cannot get my Oneplus 9 pro to EDL mode...
I've tried all the fastboot commands (fastboot oem EDL, fastboot reboot EDL, none of them work) as well as the combination volume UP + volume DOWN + plugging the cable (it just boots the fastboot mode.
Honestly would greatly appreciate any help as it is the first time in a decade I hard bricked a phone like this as it seems all the partitions are broken.
Make sure you have it unplugged when you do the button combos, as it will just start to boot while it's plugged in. Also, if you can reach fastboot, you can almost definitely reach EDL. Try unplugging and holding power+vol up for a bit which forces it to completely power off. Then try getting into EDL through the normal button combo/plugging. This is what I had to do since once it got into the booting/no-booting cycle I couldn't get to EDL.
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Good advice above.
Last time I couldn't reach EDL with my previous phone, it turned out to be an issue with the drivers I had installed. I uninstalled all Android-related drivers including some generic thing that showed up in device manager when plugging in the phone, then reinstalled the latest Qualcomm drivers.
Also possibly try a different USB cable if you have one. My OP9P didn't show up when the cable it came with was plugged into my USB-C port for some reason, but it worked fine with a generic Type-A to C cable I had sitting around.
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Tornadeur said:
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Click to expand...
Click to collapse
I can fix it bro pm me telegram .. @Hunar71
Hunar999 said:
I can fix it bro pm me telegram .. @Hunar71
Click to expand...
Click to collapse
Can you help me too, I have exactly the same problem…
If you use Windows, you need to see "QDLOADER 9008" in Device Manager > Portable Devices.
When you got this it will work, 100% .
It worked for me a few days ago. My laptop runs on Windows 11 x64. And only have usb 3.0. NO usb 2.0.
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Alberhasky said:
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Click to expand...
Click to collapse
Yeah make sure it's exactly the same name of that driver - worked for me on oneplus 9
If you have access to fastboot still. Try switching slots. Then going into EDL
For anyone looking for help, please DM me.
djsubterrain said:
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Click to expand...
Click to collapse
Thanks a lot man. Saved my Day. First 9Pro successfully restored ;-) Thank you and merry Christmas to all.
Guys I do not need to use the MSM Tool Anywhere until I reach the step where my device is being successfully detected as "QDLOADER 9008" in my windows device manager correct?
Or does the MSM Application need to be running when I reboot to EDL mode?
I am following this guide.
Please help
I always have phone powered off, and while holding both volume keys I plug it into USB cord(that is already plugged to pc) and then click on enum(button in msm screen) until it says connected then hurry and click start. Once it starts I can let go of volume keys.. Also more than likely u will need to click the box to "use lite firehose" or "Sahara communicaion" will keep failing.
make sure you have oneplus 9 pro drivers and " qaulcomm incorporated - Ports" Driver) and ("qaulcomm communications inc-Net" Driver) so your phone in edl which will be already most likely be running before you plug it in. just hold down both volume buttons and plug in to the usb port to your pc and release once plugged in and start the msm tool and hit enum it should say connect provided that you have all the necessary drivers above so the pc usb port will be able to communicate/recognize you device. its never usually A 1 and done type of thing. everytime i brick my phone its always the 100th try before i get a com port connected and the software communicating successfully, so just be patient and take your time. you will get it back up and running,
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
can't get into edl mode
how can I get oneplus 9 pro into edl mode while it's refusing to turn off? keep in mind that I can't use adb. but was able get fastboot devices command to work and I did not use any third party roms, didn't unlock the bootloader, and do not have...
forum.xda-developers.com
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
Well you have a corrupted boot.img or you would not be trying to edl. Also you probably are holding down multiple buttons to power off to your phone and your either not remembering or forgot that these combination of buttons are booting you into other modes fastboot, recovery or system.
I flashed the 11.0.1 global boot image to my BE82CB to attempt root via these instructions: https://forum.xda-developers.com/t/...eplus-nord-with-magisk-and-temp-root.4340113/
Unfortunately, it bricked my device. It boots to a T-Mobile loading screen but feezes there.
I'd like to use the MSM for 10.5.8.BE82CB to unbrick this, but I can't enter EDL mode. These are the ways I've tried:
a) hold down vol up / down for 10 seconds - attach USB
a result) device boots to fastboot
b) fastboot reboot emergency
b result) device boots to fastboot
note: even just plugging in a charging USB boots the device to fastboot
Any ideas on how to get my phone into EDL mode, or did I kill it and permanently brick my phone?
let me help you here. if youre in fastboot you still have flashing access. do you remember your old version number?
I have exactly the same problem, after installing twrp I accidently formatted some partitions including system, and they aren't mounted, because of this I can't use edl and i can't decrypt data to get access to system partition. I can use only fastboot.
does fastboot reboot edl work? if not you might have to buy a deep flash cable off amazon to get it into edl, only about $10-15
You have to enter recovery mode and make windows look for the Qualcomm driver first. May take a few reboots of the phone in recover to trigger windows but you'll see optional link inwindows update when it does find something. Click and download the comm driver. mine was "Qualcomm HS-USB QDLoader 9008 (COM3)" your COM may not be COM3.
Reboot PC and turn off phone.
Open the msm downloader and click start
hold UP and DOWN only - plug in phone -> phone will seem like nothing happens but you should see a COM pop up in the software
then continue with the download, it take some mins.
hope it helps some. I have N100 sprint/t-mobile
i can say that the software saved me for sure. it took me back to android 10 but im ok with it.
Possibly unrelated, I was testing different GSI images accidentally wiped system. wouldn't turn off just rebooted. I was able to get into EDL mode I just had to hold down volume up & down just after selecting power off in fastboot menu. maybe this will help, but no guarantee.
bouyakasha said:
I flashed the 11.0.1 global boot image to my BE82CB to attempt root via these instructions: https://forum.xda-developers.com/t/...eplus-nord-with-magisk-and-temp-root.4340113/
Unfortunately, it bricked my device. It boots to a T-Mobile loading screen but feezes there.
I'd like to use the MSM for 10.5.8.BE82CB to unbrick this, but I can't enter EDL mode. These are the ways I've tried:
a) hold down vol up / down for 10 seconds - attach USB
a result) device boots to fastboot
b) fastboot reboot emergency
b result) device boots to fastboot
note: even just plugging in a charging USB boots the device to fastboot
Any ideas on how to get my phone into EDL mode, or did I kill it and permanently brick my phone?
Click to expand...
Click to collapse
I had to use a cable, but it worked well. Make sure the drivers are installed before. It took a few tries and I had to rotate the cable, but it worked eventually. Install the drivers, reboot, make sure phone is off, plug in cable and press the button. Qualcomm should show up under ports in device manager and you should be all set.
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Call whoever you bought the phone from and do warranty claim.
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
rao_hamza said:
Hi there,
I am looking for some guidance on my bricked Pixel 6 Pro.
I transfered the data from my old pixel, but then decided to do a full flash to refresh. Downloaded the stock image from google, used the fastboot-all script to flash the phone, but as soon as it was done, I never reboot. my phone is looking completely dead since.
Attempt # 1
- black screen, with no sound to any actions of response to any key combination (power or volume keys).
- tried holding the power button for 60 secs, no response
- tried holding power and volume down, no response
- tried holding power and volume up, no response
- when I plug the phone on charge, no response. neither the charging display.
Atempt # 2
- Only time the phone shows some sign of life, is when I connect the phone to my PC, it makes a sound of detecting a device, but then instantly it get a disconnect sound, (in 2-3 sec).
- I tried holding the power button, while plugged in. it makes a sound of usb detection, (but no visual response on the phone) after holder for 30 secs, it makes another sound of usb detach.
- While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone.
Not sure, if I have bricked the bootloader, and if yes, what can be done? Any guidance in this regards will be highly appreciated.
Thanks
Click to expand...
Click to collapse
Bootloader unlocked?
cultofluna said:
Bootloader unlocked?
Click to expand...
Click to collapse
If I remeber correctly flashing factory images forces you to unlock the device. So yes, the bootloader of rao_hamza's device should be unlocked.
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Pixel 6 uses Google's own new Tensor chip - so no Qualcomm tools
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
roirraW edor ehT said:
What @ridobe said. Make sure you're using the latest official Google Platform Tools (there's a link in my thread at the top of my signature below if you need it, or just Google for it). If I had a nickel every time someone didn't update the tools when they went to use them...
Click to expand...
Click to collapse
This and a bad/wrong cable seem to be the most common culprits
ridobe said:
Like @Baumhouse I went through something similar. Two things for me: it took way longer to hold power and volume down than any other phone I've owned. I was seriously concerned I wasn't going to get there. Two, the factory images all made it to fastbootd and then failed all because I hadn't updated to the latest SDK.
Just throwing this out in hopes you don't have to send it back.
Click to expand...
Click to collapse
Any idea how long you had to hold that button combinaiton? I tried longer, maybe 60 sec, but still no response from the phone.
tids2k said:
From memory you can revive it through QPST and orher Qualcomm utilities, however hard part is to get the files. the phone is too new and many shops dont have the unlock tools yet.
" While I am experimentating with PC connection, I also tried fastboot reboot command, it only shows waiting for a device and nothing happens, either on the console or phone. " - this is still good news, as phone is being detected by windows, try to install Qualcomm drivers and see if you can get it to boot into EDL. GOOD LUCK.
Click to expand...
Click to collapse
What is EDL? and had the Google usb drivers installed, to get the fastboot working.
Baumhouse said:
I struggled with a soft bricked / bootlooping phone after removing Magisk. Although my phone at least booted to bootloader and a connection via fastboot was working, the factory images wouldn't flash properly. Google support couldn't help me and I thought I had to send it to repair.
In the end I could solve the issue by switching to the Android SDK 31. I know your case is different, because your phone is bricked worse than mine was, but you could give it a try.
Click to expand...
Click to collapse
Yes, I don't know who to get into a bootloader in this situation, if that were working I would have some hope.
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
pysklona said:
If you can get to the bootloader you can use google's flashing website, flash.android.com. I just use that to go back to stock, even with an unlocked bootloader.
Click to expand...
Click to collapse
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
rao_hamza said:
Thanks @pysklona. you are right, but the problem is I can't get into the bootloader. This is what I am seeking help for.
Click to expand...
Click to collapse
Sorry, misread the post.
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
ootri said:
@pysklona came here because I'm in the same boat, hard-bricked my device after running the flash-all script. Was using the most recent version of platform tools and the brand new cable that came with the phone.
Was getting the same result, attaching it to a windows pc makes the attached device chime, but disconnects after a few seconds. It came up first as "Setting up Pixel ROM Recovery". I let it sit overnight and now it doesn't auto-disconnect and I get a serial device under com3 on windows. Attaching it to macos gives me a "Pixel ROM Recovery" device. Despite "recovery" in the name, I think it's actually in EDL mode, not recovery mode. No devices come up for adb or fastboot on windows, linux or macos. Screen is completely blank no matter what.
Not being a Qualcomm chip makes this whole process from here a bit of an unknown, but will assume the process for recovery is more or less the same. Looking into QPST/MsmDownloadTool/OpenPST, although as pointed out, I'm not sure any of those tools will work since this isn't a qualcomm chip. MsmDownloadTool is for oneplus, but maybe something can be modded.
Click to expand...
Click to collapse
Thanks for sharing your experience. I just returned the device and got myself a new one.
anyways, i am not sure what is causing this hard brick. thats is something we all should be careful about it.
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Hmm, maybe plug it in to a PC via USB to supply it with power (maybe the battery is down) and just do a very long press of the power button - at least 30 seconds - until the phone starts up. If it does and isn't in fastboot you could try "Power-VolDown" to get into fastboot...
If it just doesn't react to all of this and waiting a bit (in case the battery was at 0% and needs some minimal charge) I think a replacement is the only way to go....
Enddo said:
same thing here. pixel 6 from google store. magisk installed on the december update and i downgraded to the november one using the flash-all.bat script. phone reboots and am told the software is corrupt
reboot back into fastboot mode, run the script again. and get this software is corrupt message again
this time I cant' even boot into fastboot/bootloader mode. and plugging the phone into windows gives me the "pixel rom recovery" message
phone seems dead (black screen, not responding to hardware buttons)
any other solutions than to get it replaced?
Click to expand...
Click to collapse
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
roirraW edor ehT said:
You could try Official Google Android Flash Tool. It's merely another method of doing what you effectively tried, but from what I've read, it's helped some folks. Sadly, others have reported that the Official Google Pixel Update and Software Repair hasn't been updated for the P6P yet.
If that doesn't help, hang in there. There are others in here who will likely have even better advice.
Click to expand...
Click to collapse
appreciate the links. right now, I can't even get into fastboot/bootloader mode. so neither of those tools detect the phone.
@s3axel the battery definitely isn't low. I charged it up before all this specifically so that I know it had plenty of juice (was at 93% or something).
I'm thinking maybe after letting the battery die, charging it back up will let me boot into a special boot mode
but any other ideas, please, I'm all ears
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this
I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now
Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.
TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!