Database Develop

Bricked Mi3 - Showing QHUSUB Bulk in PC

I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.

Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Don't worry have you backup you data?
if you have, just install the driver for qhusb
then your phone should be able to recognises by MIflash then flash any fastboot rom, You phone should be good to go.

I had a similar issue but i tried to hold the power button for like 30 seconds and the phone booted. If it didn't work, you should follow this thread: en.miui.com/forum.php?mod=viewthread&tid=73348&highlight=Mi3%2Bunbrick&mobile=no

partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone

murattiy said:
partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone
Click to expand...
Click to collapse
Did you personally tried that? Because flash all bat do uses fastboot to flash, which can't be accessed.
I wonder whether the other one u poster doesn't use fastboot, cant check the file content atm

I have tried many times
last times tried 3 hours ago, for alpha 5.12.24
my video under explain
http://m.youtube.com/watch?v=fSl9xrR_J4g

@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol

you need to do İnstall spacial flash_all.batt change to in flash_all.batt "cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global"
dont use miFlash .. enough u clik speical flash_all.batt

If your device not boot into fastboot/recovery mode press power button for around 30-40 seconds .

and still not boot into fastboot/recovery mode
battery cable exist than try.. i tried many times))

Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!

From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?

Prince Chandela said:
From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!

coolkillermax said:
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
Click to expand...
Click to collapse
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?

回复: Bricked Mi3 - Showing QHUSUB Bulk in PC
Prince Chandela said:
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?
Click to expand...
Click to collapse
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4

coolkillermax said:
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4
Click to expand...
Click to collapse
flash miui fastboot rom then

Prince Chandela said:
flash miui fastboot rom then
Click to expand...
Click to collapse
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking

coolkillermax said:
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking
Click to expand...
Click to collapse
can you boot in recovery now?

Prince Chandela said:
can you boot in recovery now?
Click to expand...
Click to collapse
No...
http://forum.xda-developers.com/xiaomi-mi-3/help/mi3w-lost-partition-userdata-img-t3293583

Me_Ashish_ said:
@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol
Click to expand...
Click to collapse
Really need your help..
Can you explain it further?
please..

Updating to pie keeps failing *FIXED*

Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
FIXED
 @RomLover1999: gave the tip to reboot without a sim card, and that seemed to have fixed the problem!

seend said:
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
Click to expand...
Click to collapse
did you tried a factory reset before updating

galardo_2 said:
did you tried a factory reset before updating
Click to expand...
Click to collapse
Nope, but just tried it and it didnt work.

Try booting without sim card

Same and via fastboot method same. Any solution? We need help its a one mi a2 more????

Unfortunately the error is not informative. I had this error when installing November update. The only way I found to see what went wrong is to check logcat during upgrade, but I think it requires root. In the end I flashed the OTA using fastboot. Still didn't get this update. Try opening shell from adb and reading logcat. I don't think anyone can help you unless we know what is 5he reason for failure

RomLover1999 said:
Try booting without sim card
Click to expand...
Click to collapse
Oh my, that worked! :highfive:
Why would something like that even work?

seend said:
Oh my, that worked! :highfive:
Why would something like that even work?
Click to expand...
Click to collapse
The november update has a bug in it that it only boots in english with a simcard inserted , other languages make the screen bug out ( at least that's what I had ) and only boot without a simcard

Worked greatly
Hey folks, just reinforcing the answer: removing the sim card before restart did the trick, the update went smooth.
Thanks @RomLover1999 and @seend

January update failed
Help! My phone is Mi A2 lite. I can't install January update. My phone is rooted and unlocked.
Thank you!

The same problem....
The same problem....anyone help?

nedjog said:
The same problem....anyone help?
Click to expand...
Click to collapse
did you unlock ? ever run TWRP/Magisk or similiar?

luminoso said:
did you unlock ? ever run TWRP/Magisk or similiar?
Click to expand...
Click to collapse
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?

nedjog said:
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
Click to expand...
Click to collapse
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend

luminoso said:
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
Click to expand...
Click to collapse
Ok, my phone is not rooted.

I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues

luminoso said:
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
Click to expand...
Click to collapse
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks

Mr.Krulez said:
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Click to expand...
Click to collapse
I´m assuming you have xiaomi a2? it must match codename "jasmine"

luminoso said:
I´m assuming you have xiaomi a2? it must match codename "jasmine"
Click to expand...
Click to collapse
fastboot does say that my product is jasmine

Hello!
I just got this phone today and tried to update (8.0 November security update) and keep getting the same error!
I've tried with and without sim card, tried with and without my google acc, and tried with full battery!
Do not really want to unlock/install rom again... Any ideas?

Phone in Hard Brick mode

I was trying to install Arrow OS custom ROM to Motorola one power using TWRP. It got flashed, when I flashed the Gpps Rom with it, it didn't flashed and I rebooted the phone right there. The phone is now in a hard brick mode and is not responding to anything, is there anything I can do to fix it? Could you please guide me with the complete procedure?

You must use a blankflash to boot bootloader.BlankFlash available for
Moto One Power (Chef) https://mirrors.lolinet.com/firmware/moto/chef[/
.1 install Motorola drivers,2 install quallcom drivers for Motorola procesor(gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows) .3 use flashbat in blankflash directory,4 press volume down and power on phone.5 connect phone with pc and proces will be starting.if your phone starting in bootloader mode ,you can flash stock room

Thank you for your help and response. I followed the steps as you mentioned. On step 3 when I run the Flashbat file, It gives the below error, and the phone never started
[112.478] ReadFile() failed, GetLastError()=0
[125.434] ReadFile() failed, GetLastError()=0

when blankflash starting you can release the wolume and power.try differrent usb port in pc.I have the same problem with custom roms,You see port com in device manager on pc?

It worked, but how did you know all this? Just spot on :good:

I tried this method but not working on my phone, xt1942-1. This is the Chinese version p30 note I got from AliExpress. I see the device in device manager as port 9008
Any help would be appreciated!

Hi,you are try change a port USB in PC?this method works,my phone is the same like your,Moto p30 note from aliexpress

Thanks, I tried all usb ports on my pc but same problem. Should we press power and volume down buttons after connecting to pc? Please help I just got this phone today and bricked right away ...
Also there are two blankfash versions on the link you provided which one to use?

Hello again.you can reinstall drivers,change partition with blankflash folder.last time when I'm bricked my phone ( trying flash customrom )I waste half day to recover my moto.im change drivers,folders,USB port,try the same on laptop and nothing.But when I'm wakeup morning and try one more time it's works!I don't no why,maybe I'm stupid,but I think is a problem with drivers or something.You must try more and more,and do not give up!I'm use blankflash from Android 9

dadm said:
Hello again.you can reinstall drivers,change partition with blankflash folder.last time when I'm bricked my phone ( trying flash customrom )I waste half day to recover my moto.im change drivers,folders,USB port,try the same on laptop and nothing.But when I'm wakeup morning and try one more time it's works!I don't no why,maybe I'm stupid,but I think is a problem with drivers or something.You must try more and more,and do not give up!I'm use blankflash from Android 9
Click to expand...
Click to collapse
I tried again today and Voila its working! Blankflash literally tests your patience. Thanks @dadm for your suggestions and now I have a working moto one power as my daily driver!

htcmusic said:
I tried again today and Voila its working! Blankflash literally tests your patience. Thanks @dadm for your suggestions and now I have a working moto one power as my daily driver!
Click to expand...
Click to collapse
Hi @dadm I could not get my SIM card detected in RR rom and tried to flash stock again. Now I am in a bootloop whatever I do. Which stock did you use to revert back? And is your SIM card detected?

I have a few questions if anyone could answer. I am looking to get hands on this phone but making sure everything goes as I expect.
1.Does any member have knowledge which of this Device variants (XT1942-1, XT1942-2, XT-942-3) qualify for "Unlocking Boot-loader" and which variant does not support unlocking. I am lookig for 4/64gb Chef.
2. Is there Any Custom Pie Rom with Solid stability + Efficient & Effective Kernel?
3. Does stock Motorola Camera app works 100% in a custom flashed Rom as it does in Stock Rom or we have to use Google Pixel Camera apps as an alternative?
4. Is there anyway to get back to stock image from Custom rom.
5. How to recover the device from a Hard Brick.
6. Not but least. How well this device performs while playing PUBG.

Phone flashing locked and stuck at fastboot mode
I have done a stupid thing after flashing stock ROM I have flashed twrp and my stock ROM was stuck at loop after that I have locked the device and it showing it device is corrupted and will not boot
Could any body help me plss.??
I tried this blankflash.bat but it showing <waiting for device> my phn is already connected to pc

Ravi2730 said:
I have done a stupid thing after flashing stock ROM I have flashed twrp and my stock ROM was stuck at loop after that I have locked the device and it showing it device is corrupted and will not boot
Could any body help me plss.??
I tried this blankflash.bat but it showing <waiting for device> my phn is already connected to pc
Click to expand...
Click to collapse
Phone must be in EDM to flash blankflash
Sent from my ali using XDA Labs

Thanks for reply
sd_shadow said:
Phone must be in EDM to flash blankflash
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Actually how to enter EDM mode could you pls explain in steps my phone just start into fastboot,no recovery, no boot. Pls help me bro.

Problem solved
Ravi2730 said:
Actually how to enter EDM mode could you pls explain in steps my phone just start into fastboot,no recovery, no boot. Pls help me bro.
Click to expand...
Click to collapse
Anyone stuck in fastboot when it shows your phone is corrupt and will not boot just flash the command
fastboot boot boot.img file in stock room phn will automatically start everything working it work as a flash...?

Question The current image (boot/recovery) have been destroyed

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.)

Endless bootloop (Redmi 9 lancelot)

I tried installing crDroid (unlock bootloader, uploaded FW, recovery SHRP, then install ROM) and after reboot the phone would go back to recovery.
By mistake I "installed" SHRP from ZIP package (I thought I need to install latest recovery file to install ROM with android 12) and phone went into reboot loop, I can't do anything, any key combination doesn't help - I can't even turn it off.
help!

I opened the phone, disconnected the battery, but nothing happened - still bootloop
I'm planning to use SP Flash Tool
Immediately after connecting USB C, the phone boots into bootlop (after disconnecting and reconnecting the battery)

What happens when you flash the custom ROM?
Try to flash the stock firmware and miui
again. Download the latest miui recovery ROM for Lancelot and copy it to the sd card. If you can still boot into recovery you can connect the phone with a PC.
You can also try to reboot into bootloader if the reboot options work from sharp, if not connect the phone to a PC with adb and fastboot installed on it and type:
Code:
adb reboot bootloader
And now if you are in fastboot you can do anything, you can try to reflash the firmware, recovery etc.
I personally don't use SHRP, it was really buggy and not great. I use the twrp from this link: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/.
Thanks for reading and I hope u succeed,
Bye.

U can also try to flash it with MI flash tool.

Sergij-SApcPro said:
What happens when you flash the custom ROM?
Click to expand...
Click to collapse
Operation completed with status [ ]. It looks like there should be a * in the middle and then it would be a sign to me that the ROM is loaded.
Sergij-SApcPro said:
Try to flash the stock firmware and miui
again. Download the latest miui recovery ROM for Lancelot and copy it to the sd card. If you can still boot into recovery you can connect the phone with a PC.
Click to expand...
Click to collapse
At the time of writing, no key combination was working - I can't get into Fastboot or Recovery. I let the battery run out for that moment.
Sergij-SApcPro said:
You can also try to reboot into bootloader if the reboot options work from sharp, if not connect the phone to a PC with adb and fastboot installed on it and type:
Code:
adb reboot bootloader
And now if you are in fastboot you can do anything, you can try to reflash the firmware, recovery etc.
I personally don't use SHRP, it was really buggy and not great. I use the twrp from this link: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/.
Thanks for reading and I hope u succeed,
Bye.
Click to expand...
Click to collapse

Sergij-SApcPro said:
U can also try to flash it with MI flash tool.
Click to expand...
Click to collapse
That's what I'll do first, then move on to the solution below.
I opened the phone and disconnected the battery, but plugging in the USB cable immediately turns the phone on and bootloops again.
I'm using Linux and Windows, and one user hinted at hacking the USB driver so I believe it won't boot the phone, only then will I have communication? Other than that I don't know how to do it anyway.
For now, after the phone's battery runs out, I'll try with this solution
MTK Authorisation Bypass
Thanks to Dinolek ErdilS xyzz **All Steps Are Mandatory, Don't Skip Any Of Them** How to install: 1. Download the attached file: Alternate Download:https://anonfiles.com/l0yeSfD2u7/MTK-Bypass_zipAlternate Download:https://dl.uploadgram.me/6126628127c5fh?raw 2. Extract the file and open the...
telegra.ph

I've exhausted the battery, Mi Flash needs Fastboot, which I don't have.
I used
Deleted Account in Redmi Note 9 / Redmi 9 / 10X 4G Community
• Unbrick method for basically any device covered in this group. - Download SP Flash Tool from here. - Download the corresponding Engineering ROM for your device using #engrom - Download this zip and extract it. You Should find a DA file and an auth file in it. - Do the steps in this video...
t.me
I got to the point of connecting the phone to the computer and it connects (the procedure says to use the Power button, but I had to disconnect the battery because Bootloop was falling in), using the Vol- button - the phone keeps connecting and disconnecting....

For a while I tried to connect the phone via SP Flash under Linux - in administrator mode the message "memory protection violation" appears (I don't know how the message is in English).
Adding a udev exception was supposed to help - after lsusb the Mediatek device appeared, I added the exception, restarted - and the same thing happens (the program crashes).

I finally managed (with the help of a group on telegram https://t.me/HelioG85_Unified) by switching off the phone and carefully going through all the points (except the update at the very end) from this link
MTK Authorisation Bypass
Thanks to Dinolek ErdilS xyzz **All Steps Are Mandatory, Don't Skip Any Of Them** How to install: 1. Download the attached file: Alternate Download:https://anonfiles.com/l0yeSfD2u7/MTK-Bypass_zipAlternate Download:https://dl.uploadgram.me/6126628127c5fh?raw 2. Extract the file and open the...
telegra.ph
There is a little problem, because SP Flash must be from the link in this post (because it will not fit DA)
Deleted Account in Redmi Note 9 / Redmi 9 / 10X 4G Community
• Unbrick method for basically any device covered in this group. - Download SP Flash Tool from here. - Download the corresponding Engineering ROM for your device using #engrom - Download this zip and extract it. You Should find a DA file and an auth file in it. - Do the steps in this video...
t.me

Wow so many posts... Did you manage to fix the phone now? What do you mean by SP Flash will not fit the DA? Did you download the eng ROM for Lancelot? BTW I haven't done this kind of thing, but when I tried to flash my Lancelot with SP Flash tool it didn't work, because it was just waiting for device.

Sergij-SApcPro said:
Wow so many posts...
Click to expand...
Click to collapse
Often when reading threads I see "managed to fix, thanks!" but it doesn't say what and how, so that's why so many posts - so someone knows what was going on.
Sergij-SApcPro said:
Did you manage to fix the phone now?
Click to expand...
Click to collapse
Yes
Sergij-SApcPro said:
What do you mean by SP Flash will not fit the DA?
Click to expand...
Click to collapse
Other versions of SP Flash (newer) other than in the package with ENGROM didn't work with DA file with manual from links given above - it had to be the one from the package. SP Flash showed errors and crashed or informed about wrong file.
Sergij-SApcPro said:
Did you download the eng ROM for Lancelot?
Click to expand...
Click to collapse
Yes
Sergij-SApcPro said:
BTW I haven't done this kind of thing, but when I tried to flash my Lancelot with SP Flash tool it didn't work, because it was just waiting for device.
Click to expand...
Click to collapse
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.

Great to hear that you fixed the phone, congratulations!
TomekParuszewski said:
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Click to expand...
Click to collapse
Thanks for the info, but I don't need to flash it with SP Flash tool because that was earlier when I didn't try to install custom recovery. Now I have SHRP with CRDroid A12 and its Awesome.
Thanks for reading,
Bye

TomekParuszewski said:
Often when reading threads I see "managed to fix, thanks!" but it doesn't say what and how, so that's why so many posts - so someone knows what was going on.
Yes
Other versions of SP Flash (newer) other than in the package with ENGROM didn't work with DA file with manual from links given above - it had to be the one from the package. SP Flash showed errors and crashed or informed about wrong file.
Yes
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Click to expand...
Click to collapse
What version of SP Flash tools did you use? I'm running into this (status_ext_ram_exception error) kind of error while trying to flash the firmware provided in the Telegram channel.

SandShadow said:
What version of SP Flash tools did you use? I'm running into this (status_ext_ram_exception error) kind of error while trying to flash the firmware provided in the Telegram channel.
Click to expand...
Click to collapse
yes, im stuck at same error. any ideas? someone said we should let the phone completely discharge, im waiting on that, but just incase any other ideas...

voland34 said:
yes, im stuck at same error. any ideas? someone said we should let the phone completely discharge, im waiting on that, but just incase any other ideas...
Click to expand...
Click to collapse
The battery trick does'nt work for me. I can't remember exact version, sorry - but my way was going BACK with SP Flash tool version (from newest to working with file). When I found right version the rest was only going with procedure.
I did it twice: first time I was scared, second - with finding right version of SPFT, every time - like walk in the park. Looong walk all procedure was like 2-3 hours.
Second one try was after trying to load Andorid 13 (2x). Don't do it kids!
After all, my Revolut app stop working lately on my phone and Redmi is retired for now... (and also becoming unusable because slowing dramatically)

Thanks for your answer. it has worked with battery empty (though that might not have benn necessary); not on 1st atttempt v5.2020 but it did with version 5v.2216 in case it might help someone...it didnt flash miui fastboot rom 12.5 but it did flash engineering rom. and from there i will twrp and miui.
Thanks for your suggestion of trying different spflash versions.