Hi everyone,
I have bricked nexus 6. It has a locked bootloader plus no bootloader, no recovery, no system no nothing.. If i boot up the phone it goes into bootloader kind of thing and pc can recognize it as a fastboot device but since it has locked and corrupt bootloader there is no command i could get it to run anything.
I know most of you think its simple bricked and cant work it again but refuse to believe that just because the simple fact that i couldnt get any answers from anyone relavent to this. I have been using android for years, basically from the beginning, i know i am not a developer but i think i know few things and i been in similar situations before but this is the first time i got stuck. I know it can be done since its a qualcomm device. There should be a way to put the device in edl mode flash with qfil or something. I know all the post about these kind issues i read them all. Whenever somebody asks about how to put it in edl mode the answer is always go check that post about how to recover from edl mode. Please understand i need to put it in edl mode first to get it out of there.
So if anyone knows a way to put this device in edl mode please help so i can try to recover from there..
I already tried modified fastboot so it can run "fastboot reboot-edl command" it doesnt work for me.
I also tried a custom cable for triggering edl mode on xiaomi devices. But it doesnt work either.
The only other way i know is the short test points on the board or on the chips legs itself.
Like i said there may be no way because the lack of information out there if it is please say so so i can rest
Thank you for your time patience.
The best I can do is point you to [FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1
If memory serves, there was a point when the adb reboot edl was patched in an upgrade. That was rather late in the device's supported lifetime. Maybe when Pie came out?
I recently brick my k20 pro I was in twrp I formated my data I think some how I wiped the entire system.anyways I'm now hard brick with a black screen no recovery no fastboot option. When I connect the phone to then PC it shows up as (Qualcomm hs-usb qloader 9008). I didn't do the test point method, that's how it automatically reads. I tried the using mi flash tool but get errors ( will attach screen shots) any guidance will be greatly appreciated. I don't mind paying for some help.
Is your device unlocked?
Have you downloaded and installed the drivers that cam with the mi flash tool?
Can you access fasboot mode by holding power down ?
Try and make sure there are no spaces in the file name you created.
Ex:* miui11globalromfastboot firmware (= bad)
* Miui11globalromfastboot.firmware (= good)
https://forum.xda-developers.com/k20-pro/how-to/xiaomi-mi9t-k20-hard-brick-recover-t4037591
Could try this ^.
Alternatively XiaomiTool might do the trick.
https://www.xiaomitool.com/
So my phone's stuck in fastboot mode, oem unlocking and usb debugging is off, recovery mode doesn't work, and a custom rom was installed when bootloader was turned off, so is there any way to at least get the phone back to stock, or is it just useless now?
Since your phone is Qualcomm based, then you should have EDL mode in your device.
Have you tried it? There are multiple ways to boot into EDL mode, like adb reboot edl or the EDL cable method.
I don't know if it is unlocked by default on your device or you need unlock key first though.
If it requires unlocking then you have to send your device to an authorized service center, not just any service center.
If it doesn't then you can easily find guides on the internet about how to unbrick your phone with EDL mode.
Goodluck.
XDHx86 said:
Since your phone is Qualcomm based, then you should have EDL mode in your device.
Have you tried it? There are multiple ways to boot into EDL mode, like adb reboot edl or the EDL cable method.
I don't know if it is unlocked by default on your device or you need unlock key first though.
If it requires unlocking then you have to send your device to an authorized service center, not just any service center.
If it doesn't then you can easily find guides on the internet about how to unbrick your phone with EDL mode.
Goodluck.
Click to expand...
Click to collapse
Yeah I've tried entering it with the command, didn't work, but I suppose I could send it to a service center for it to get unlocked. I've heard other people have their phones enter EDL mode and other people saying it's basically useless though which was why I was slightly scared about entering it but I'll give it a shot, thanks.
Jaideus said:
Yeah I've tried entering it with the command, didn't work
Click to expand...
Click to collapse
EDL mode doesn't have a UI, if you enter the command and get black screen instead chances are that you're already in EDL mode.
Similarly if you turn off the device and leave it like that for a couple of minutes, some Qualcomm devices can detect that it's bricked and enter EDL mode automatically.
Alternatively you can just make your own EDL cable to force your device to boot to EDL mode, follow this thread here.
Or just get an EDL cable, they're cheap really.
Jaideus said:
I've heard other people have their phones enter EDL mode and other people saying it's basically useless
Click to expand...
Click to collapse
EDL mode is very low level and very powerful, you can literally do anything to your device with EDL mode the sky is the limit. However it requires special Qualcomm EDL tools which depend on your Qualcomm type (sahara or firehose) and correct driver.
Beware that EDL mode commands are very powerful and can mess anything beyond repair. So be careful with whatever command you use while in this mode if you're not sure what it does then don't use it. And send it to an authorized service center instead.
You can extract data with EDL mode and I recommend doing that before flashing anything.
Be careful of unofficial EDL tools, most are just trojans for the desperate.
The official tools are already on the internet. I don't recall the exact name but i think it was something along "QSPT" or something. Sorry for not being of much help.
I'd have searched for the correct tools for you, but it's getting really late here.
XDHx86 said:
EDL mode doesn't have a UI, if you enter the command and get black screen instead chances are that you're already in EDL mode.
Similarly if you turn off the device and leave it like that for a couple of minutes, some Qualcomm devices can detect that it's bricked and enter EDL mode automatically.
Alternatively you can just make your own EDL cable to force your device to boot to EDL mode, follow this thread here.
Or just get an EDL cable, they're cheap really.
EDL mode is very low level and very powerful, you can literally do anything to your device with EDL mode the sky is the limit. However it requires special Qualcomm EDL tools which depend on your Qualcomm type (sahara or firehose) and correct driver.
Beware that EDL mode commands are very powerful and can mess anything beyond repair. So be careful with whatever command you use while in this mode if you're not sure what it does then don't use it. And send it to an authorized service center instead.
You can extract data with EDL mode and I recommend doing that before flashing anything.
Click to expand...
Click to collapse
Yeah for the first part when I did the command it just said "unknown command" so nothing happened, but yeah I was thinking about getting an EDL cable, would any cable work or would only a specific type work? Also how would you know what the qualcomm type is?
Jaideus said:
would any cable work or would only a specific type work? Also how would you know what the qualcomm type is?
Click to expand...
Click to collapse
I worded this poorly my bad, what I meant is sahara and firehose are actually firmware boot type and it doesn't matter what tool you use as long as it is meant for Qualcomm devices.
Any EDL cable should work, and as for the tool it's QPST or QFIL.
As for the driver: Qualcomm driver link.
They say QFIL is much easier to deal with as it is standalone, anyway both work similarly.
As for the deep flashing process, you can follow this guide here.
The guide has updated driver, QPST and QFIL links.
For the firmware images I only found this one and it doesn't have Qualcomm firmware in it, in case you need Qualcomm firmware you need to follow the guide I gave you to extract the firmware from another RP2. Here is a video guide on how to extract qualcomm firmware with QFIL.
EVERYTHING I JUST SAID IS TESTED, HOWEVER I DON'T HOLD ANY RESPONSIBILITY SHOULD YOU PREM-BRICK YOUR PHONE.
Hope i helped. And goodluck.
I forgot to tell you how to use EDL mode to extract data, here is an article.
It might be hard to understand at first but you'll get used to it. It's completely safe so you can mess around as much as you want, Don't click random buttons though. Note that: The openpst tool isn't a flashing tool and only meant to communicate with Qualcomm devices in EDL mode.
Here is a different method, although it's meant for Xiaomi devices it's still generally for Qualcomm devices.
Just follow step 7 only. Obviously you won't be using MiFlash nor flash a MIUI ROM.
After flashing the ROM flash a custom recovery to backup your data.
Then delete all data including dalvik cache.
I can't confirm if those methods are tested so follow them on your own risk. However I suggest trying the second method since the extracted data from the first method would be encrypted therefore useless. Unless you know how to decrypt it.
I followed the instructions on this thread Flashing TWRP and Rooting Realme 8, and it bricked my phone. I must have done something wrong but I dont know what. After the step where I had to hold Volume Down and Power and release 5 times, I got the message the recovery/bootloader has been damaged.
I managed with to get the recovery working again with stock recovery, but it wont boot. It wont detect my SD card nor does it detect any WiFi for online Update.
I tried SP Flash, but now it gives me the error that verified boot is enabled, even though im using MTKSecureBoot.
Can someone help?
Try to flash back stock boot and vbmeta images using MTK client or SP flash.
and where that an be got ?
fullflash 7.5gb zip for A.22 have no such files ...
So ... Found ... in near topic
[GUIDE][UNBRICK] Realme 8 Unbrick/Upgrade/Downgrade [RMX3085]
Hello everyone! So after the new MediaTek DAA and SLA protection bypasses you can find GitHub repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX3085 (Realme 8) ONLY. DON'T DO...
forum.xda-developers.com
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me
Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon
Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing
hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha
KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files
I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.
KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?
yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot
Damn!! I hope you find some way to fix your device. Good luck.
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?
yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)