Develop Bugs

The system has been destroyed

I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?

ghtcp said:
I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Did the PC shut down or the phone?
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
If unlocked you can fastboot the firmware as you normally would

Dobsgw said:
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
Click to expand...
Click to collapse
You can flash images with Mi Flash on locked bootloader no problem.

marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
They can try but if recovery isn't accessible then fastboot is the only option and without unlocked bootloader you cannot use it.
Test point is then the only way.
Obviously its best to try flashing without opening the phone first.

marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
Wtf! You can't use mi flash tool unless your bootloader is unlocked

The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END

ghtcp said:
The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END
Click to expand...
Click to collapse
The bootloader gods have smiled upon you this time

Hello! I have locked bootloader with "fastboot oem lock". I was in panic, but randomly I press "Volume -" + "power-on" and my Mi A1 have loading in Fastboot mode, where I was able to unlock bootloader again.
Hope, this can help you.

HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone

same issue in redmi note 4
indersethi said:
HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone
Click to expand...
Click to collapse
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....

Basilp275 said:
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....
Click to expand...
Click to collapse
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.

ccelik97 said:
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.
Click to expand...
Click to collapse
Yes,it's worked

Basilp275 said:
Yes,it's worked
Click to expand...
Click to collapse
Cool then ?

I had the same problem today. my phone was distroed when I tried to install Gcam.
my phone was not unlocked so that the flash of the new stock of the ROM was not possible. The solution is to connect the phone to a PC in fastboot mode and from the platform tools in cmd to type fastboot oem unlock. After that, I did not have to have a flash phone. Everything worked as if I only had to backup the data.
now I have a new phone.
People, with Mi A1, cling to two things - slot A or slot B and lock or unlock. The easiest way to do this is a cardinal error.
Greetings.

Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?

jesus4android said:
Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?
Click to expand...
Click to collapse
With locked bootloader I got no chance to flash anything. Neither fastboot nor MiFlash - any solutions? Also would be helpful to enabke USB Debugging via fastboot. Anyone knows?

If you brick your device on the way as it happened to me... check: https://forum.xda-developers.com/showpost.php?p=77755947&postcount=11
These guys helped me unbricking my mi8 using EDL (Test Point) and Mi-flash!

I want to sell my Google Play app developer license.
Please email me or call me if you are interested.
phone - +917007797787
Email- [email protected]

I got a bricked Mi 6 from a friend. He was trying to flash firmware, and somehow messed up. Trying to boot normally or into recovery showed "The system has been destroyed". `fastboot continue` did not work. Bootloader was locked ( = no possibility to do fastboot oem unlock). On top of that, the phone only accepted fastboot commands right after the usb cable was connected ( => I had to run a fastboot command, like `fastboot getvar all`, fastboot would output `< waiting for any device >`, then I connected cable, and it would work). Running fastboot commands later resulted only in fastboot hanging / getting stuck, with no output, can not be terminated with ctrl+c unless cable was disconnected.
I got myself a windows computer (I use linux), tried to do bootloader unlock. Failed on "add your mi account in Settings -> Developer -> blablabla" - no way to do that with a bricked phone. Then I found out about EDL (Emergency download) mode. This is what worked.
The only way to get into the EDL mode in this state was the hardware way (shortcutting the pins / "PCB test points"). Search online for "mi 6 edl mode testpoints". Basically, you have to:
1. remove the rear cover
2. remove the screws on the plastic part above the battery, remove the plastic piece
3. disconnect the battery (shorter connector on the left side)
4. shortcut the pins using a tweezer (the pins are just above the battery connector)
5. while the pins are connected, connect the USB cable
6. check in device manager that you have "HS-USB QDloader 9008" in the COM devices
7. use mi flash tool to flash the fastboot firmware
The pins (from https://www.mobilerdx.com/2019/02/xiaomi-mi-6-test-points-xiaomi-mi-6-edl-mode-pinout.html):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And after you succeed, maybe unlock your bootloader, so that you don't have to do this again

Unlock bootloader without losing data

For those who are waiting to unlock bootloader but don´t want to lose data this quick guide is intended to do so.
Usually in most of threads out there about unlocking anyone find the typical phrase "unlock bootloader erase all your data" like is advertised in the same MiFlash Unlock tool and for other devices which method to unlock it is through the same fastboot mode by command.
Really unlock bootloader doesn´t erase nothing itself, the problem is at time to reboot to system and here is the issue, if we reboot inmediately then data will gone. (some users of older devices reported that not always this happened BTW)
Steps that I did are the next (maybe some step was unnecesary and I´ll indicate which)
1 - Unlock bootloader as normally through the tool when time it´s came.
2- When it finishes exit the tool, don´t tap on "Reboot device" in the tool, just close the tool.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3- Device stays in fastboot, check bootloader status in fastboot mode by typing
Code:
fastboot oem device-info
View attachment 4637936
4- Extract recovery image fromOrangeFox-R8.3-vince zip inside adb folder and type
Code:
fastboot flash recovery fox.img
(I renamed it fox).
5- Reboot to recovery by typing
Code:
fastboot boot fox.img
.
View attachment 4637937
6- Once in recovery don´t swipe to allow modifications, tap on Read Only.
7- Some drivers will be updated between device and pc, then copy OrangeFox-R8.3-vince zip to internal memory (or if you prefer to an ext. sdcard) if you already don´t have it in your device.
Now flash the zip, I guess that this is necessary to OrangeFox can unpack all the tools in Fox folder onto device.
8- I enabled these options in recovery and flashed magisk, you can enable some additional features.
9 - Then Flashed No+Verity_R5Plus.zip uploaded file (I´m not sure if this step is needed so I enabled before this option and OrangeFox has in-builded this feature but just to made sure, you know..)
10- Reboot normally and you´re done.

Thanks for the info!
I intended to do what you explained in the guide.
Unfortunately, I couldn't go further than step n°1 because I haven't activated the "USB Debugging" function in my phone and this tool requires it in order to unlock the phone.
The thing is my phone (a Redmi Note 5) is currently stuck in the recovery mode so I can't access inside and activate the "USB Debugging" function.
My phone is stuck in this mode since I tried to update it with the official MIUI 10 version. I definitely want to recover my datas before doing anything else so I haven't click on the "WIPE DATAS" option (obviously).
1-Do you know another way to activate the "USB debugging" function without a proper access into the phone and in order to follow your guide afterwards ?
2-Do you know another way to recover my datas before unlocking the bootloader and flashing a new version ?
Thanks !

Thanks for the trick! but we can use another recovery for this method?

I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.

sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
Demoxing said:
Thanks for the trick! but we can use another recovery for this method?
Click to expand...
Click to collapse
Yes, all the trick resides on that, avoid to boot up from fastboot but from a complete shut off state then the order to format data would be deactivated. Newer bootloaders would prevent this but it worth the try.

sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
Do you know if that works with pocophone or newer miui phone?

Dunno.. I only own the redmi5plus

Hello there,
Can someone help me with my questions ? It's not possible for me to unlock bootloader with the tool because my USB debugging function was not activated before I got a problem during the installation of the new MIUI version and let my phone in the recovery mode...
Thanks!

popoFR said:
Hello there,
Can someone help me with my questions ? It's not possible for me to unlock bootloader with the tool because my USB debugging function was not activated before I got a problem during the installation of the new MIUI version and let my phone in the recovery mode...
Thanks!
Click to expand...
Click to collapse
You have first of all to recover your device and then to fix it try again to unlock bootloader.
In recovery do a format data it could be solve it. then set up again all

SubwayChamp said:
You have first of all to recover your device and then to fix it try again to unlock bootloader.
In recovery do a format data it could be solve it. then set up again all
Click to expand...
Click to collapse
Thanks for your answer.
To do what you wrote, I have to wipe datas, right ? The thing is I want to recover all the data from my phone...is there a possibility to do everything without wiping datas ?

popoFR said:
Thanks for your answer.
To do what you wrote, I have to wipe datas, right ? The thing is I want to recover all the data from my phone...is there a possibility to do everything without wiping datas ?
Click to expand...
Click to collapse
The problem is that is a cyclical issue. In order to can boot (presumably) due to a dirty/wrong update you need to format data, if you had have enable USB debugging before then you could flash the same firmware that was previously working well but with USB debugging disabled you can´t.

SubwayChamp said:
The problem is that is a cyclical issue. In order to can boot (presumably) due to a dirty/wrong update you need to format data, if you had have enable USB debugging before then you could flash the same firmware that was previously working well but with USB debugging disabled you can´t.
Click to expand...
Click to collapse
That was my fear...my phone didn't start again after an official update that went wrong...
There is no other possibility in enabling USB debugging with adb for example ?
I'm stuck and have to erase all my datas...?:crying:

popoFR said:
That was my fear...my phone didn't start again after an official update that went wrong...
There is no other possibility in enabling USB debugging with adb for example ?
I'm stuck and have to erase all my datas...?:crying:
Click to expand...
Click to collapse
The first I do with a new device is enable USB debugging and check on OEM unlock bootloader cause mainly the first also sometimes can cause a bootloop on a wrong/failed update and to have more options in a worst scenario, take it like a lesson for the next time.
There are ways to enable USB debugging under adb commands but you will need su permissions for this, there are a way to flash a firmware through recovery using adb sideload but again you will need USB debugging and lastly in R5+ you can flash a rom through MiFlash Tool but in download mode so fastboot never worked for me on a Xiaomi with locked bootloader.
Try this last to see if it works, I don´t think but some time ago that I don´t use this tool, try flashing the same firmware that previously was onto your device using this tool on fastboot moed and checking in the centered option to flash and keep data at the right down of the tool.

is this still working?
sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
hey,
is this trick is still working??
did u try this?
if yes then tell me the exact version in which it works...

sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
Anyone else tried this trick from Sanjisin?
I am on Mi 9t pro (MIUI 11.0.3 global), waiting for 168h timeout for unlock

popoFR said:
That was my fear...my phone didn't start again after an official update that went wrong...
There is no other possibility in enabling USB debugging with adb for example ?
I'm stuck and have to erase all my datas...?:crying:
Click to expand...
Click to collapse
maybe you can try using fastboot recovery, do a backup from there (to sd card) , then reflash to stock, unlock again (this time enable usb debugging), and after that use your backup to get back your data.

zlikovac said:
Anyone else tried this trick from Sanjisin?
I am on Mi 9t pro (MIUI 11.0.3 global), waiting for 168h timeout for unlock
Click to expand...
Click to collapse
did you try it out yourself? haven't unlocked mine yet, no need yet, but just in case for the future

Dxue said:
did you try it out yourself? haven't unlocked mine yet, no need yet, but just in case for the future
Click to expand...
Click to collapse
I missed to pull the cable on time, already phone was rebooting :/ ah well backup restore well semi ok. Not sure will i stay rooted. I only needed root so i could automate cell data, vpn. Used MacroDroid for automation. Eg. when off the home wifi, turn on cellular data, when on again, turn off. When on non home/work wifi, turn on vpn, etc. Now i need some like smart unlock (don't lock phone when on home wifi or when bt watch connected) macro and i am done.
Will stick to MIUI for now, but wish Xiaomi would tweak those few things, so we do not have to root phone.

sanijsnj said:
I think clicking on 'Reboot' on the unlock tool sends the script to erase all data.... Here's what I did:
1. unlock bootloader normally
2. unplug phone without clicking on 'Reboot' button at the end
3. Force power off by holding power button for about 10s
and when it rebooted.. it went right into system..phone booted normally with the 'unlocked' logo at boot with all my data untouched.
Click to expand...
Click to collapse
Has anyone tried this pls? I have an Redmi Note 7 and dont want to lose my data pls

Unlock mi note 5 pro without data loss
Dear sir
I want to unlock my mi note 5 pro any way out please help me I haven't installed anything

Question Bricked OP9pro

Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?

craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?

U not able to flash boot the stock boot.img?

i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed

You need to be in fastbootd,
Code:
fastboot reboot fastboot

craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)

@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.

MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com

New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off

danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse

djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign

danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support

djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help

craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?

djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on

craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked

Question Qualcomm CrashDump Mode

Hi everyone,
I didn't do anything special to my phone, no messing with it from system point of veiw.
Yet yesterday it just bricked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am on latest OxygenOS version that is the only thing that I can say right now :/
One thing -> It is detectable by PC when switched on into that mode or into Recovery mode.
Did anyone here had similar issue? Or maybe you know what at least I should try on my own?
I contacted Oneplus Support already, but it is weekend and I just stuck without phone...
Cheers!

Device Model?

LE2123

hold volume up/down and power. It should reboot

Thanks,
I tried that but nothing changed.
I tried to reboot also from recovery mode but the same result.

Message oneplus for a remote session they fixed mine

Thanks
Did ask for it already, just hoped that there is some other DIY solution
But seems that I need to wait for that session

awsan said:
Message oneplus for a remote session they fixed mine
Click to expand...
Click to collapse
Did you save the msm tool? Do you still have the download link? Can you pm them to me?
NVM thought you were OP haha

Did you try keep holding the Power button for approximately 10 seconds, the phone should shutdown. and when completely off, just press Power + Vol Up + Vol Down to boot into fastboot mode. To boot normally just select Start by pressing the power button.

rgadge said:
Did you try keep holding the Power button for approximately 10 seconds, the phone should shutdown. and when completely off, just press Power + Vol Up + Vol Down to boot into fastboot mode. To normally y just select Start by pressing the power button.
Click to expand...
Click to collapse
Thanks,
I tried that, the same result, CrashDump Mode without info of an error as on my picture from first post.

weapecet said:
Thanks,
I tried that, the same result, CrashDump Mode without info of an error as on my picture from first post.
Click to expand...
Click to collapse
In my previous OnePlus devices, whenever this has happened, I was always able to get out by simply pressing Power +Vol Up+Vol Down all three buttons together to reboot into fastboot, try this combinations as well.

rgadge said:
In my previous OnePlus devices, whenever this has happened, I was always able to get out by simply pressing Power +Vol Up+Vol Down all three buttons together to reboot into fastboot, try this combinations as well.
Click to expand...
Click to collapse
Yep,
Did that once on my OP5T and then it worked, but here no option from fastboot works, neither recovery mode, start or restart bootloader. :/

Can you get to fastbootd? From the bootloader screen type
Code:
fastboot reboot fastboot

craznazn said:
Can you get to fastbootd? From the bootloader screen type
Code:
fastboot reboot fastboot
Click to expand...
Click to collapse
I cannot type or do anything more than select between Start, Restart bootloader, Recovery mode, barcode or power off.

weapecet said:
I cannot type or do anything more than select between Start, Restart bootloader, Recovery mode, barcode or power off.
View attachment 5283239
Click to expand...
Click to collapse
Plug it into your computer, make sure latest platform tools and fastboot drivers are installed, run
Code:
fastboot devices
Does your device show up?

Just use the MSM tool, or request a remote repair session with oneplus.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com

Konfuzion said:
Just use the MSM tool, or request a remote repair session with oneplus.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com
Click to expand...
Click to collapse
Doesn't apply to his LE2123, that's why I asked for his model to begin

I have fixed my past devices from this issues by following these steps:
1. Download latest firmware from OnePlus (Official Site or XDA Links)
2. Extract the downloaded file and there will be "payload.bin" file that you need to extract by using a payload dumper (you may try this link or this one)
3. Once you have all the images (img ) files to flash the phone you can use this guide for flashing.
Disclaimer:: If you have not done something similar or not sure what this is and not comfortable with this, please avoid following this guide.
All the best!

Hi,
craznazn said:
Plug it into your computer, make sure latest platform tools and fastboot drivers are installed, run
Code:
fastboot devices
Does your device show up?
Click to expand...
Click to collapse
Nope, didn't showed up.
I've got my remote session to learn that they cannot help, device need to be send to repair.
2/10, since Remote session technician didn't even knew my problem, when I stated to him that I cannot do his instructions because of my error then he realized that they cannot help me like that.

Help "failed to write partition" error Redmi 5A (riva)

I had installed in this phone a custom rom a few months back for my friend. Yesterday he told me that the device froze when he was browsing the phone gallery app, and a few minutes later the phone rebooted and couldn't pass the mi logo (so the system wasn't loading I guessed, because the logo of the ROM wasn't showing). I tried to enter TWRP, but even there the phone would get stuck on the TWRP splash page and rebooted back to the MI logo. So I tried to reinstall TWRP (I have still access to fastboot mode) and, after, a newer version, but the problem was the same. I tried booting a recovery image without installing it (fastboot boot twrp.img) and the problem was similar, but instead of rebooting to the MI logo, the phone would get stuck on the TWRP logo. I tried with OrangeFox recovery too, but same problem. I read in another post that it may be a problem with the /data partition, so I (fastboot erase userdata) and tried again the above recovery installation, but it didn't work. I, then, tried to wipe all partion via fastboot, and tried the command "fastboot erase system -w", but it didn't work either. So I tried the way to restore the phone with MiFlash tool, I found the firmware I needed, I flashed it, and after ~4s it gave me the error "failed to write partiton" (see image).
Spoiler: Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried with another firmware (this time based on Oreo instead of Nougat), same error. I searched a solution for this error, but I found nothing helpful. Now I have the phone working (=it can power on) and can access to fastboot, but don't know what to do. Can someone out there, with maybe a clearer idea of what's going on, help me? Thanks in advance

Update:
I found out that the problem is flashing this file "gpt_both0.bin" (which is the partition table). Every firmware that I tried failed to flash when trying to fastboot this file. So I tried to remove the line (
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash tz error" && exit /B 1
) from the flash_all.bat and everything was flashed without errors, but the phone won't start, so this file is necessary. Flashing it separately gave me the same error (failed to write partition). So, I ask again for help, hoping that someone will come to save me

I have same issue. Did you get any working method?

amitkr.xda said:
I have same issue. Did you get any working method?
Click to expand...
Click to collapse
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work

TheMagicWafer said:
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work
Click to expand...
Click to collapse
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool

amitkr.xda said:
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool
Click to expand...
Click to collapse
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar

TheMagicWafer said:
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar
Click to expand...
Click to collapse
How can I boot in fastboot? It's not going in fastboot or anything

amitkr.xda said:
How can I boot in fastboot? It's not going in fastboot or anything
Click to expand...
Click to collapse
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo

TheMagicWafer said:
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo
Click to expand...
Click to collapse
Nothing works, it's just blank screen, no vibrate, no logo nothing

amitkr.xda said:
Nothing works, it's just blank screen, no vibrate, no logo nothing
Click to expand...
Click to collapse
I'm sorry, but I'm not an expert and I can't help you any further. If one day I find a solution, be sure I'm going to write it here

have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died

Avisadius said:
have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died
Click to expand...
Click to collapse
Already tried, and it gave me the same error. I really hope it's not a motherboard issue, because a replacement is not worth it. Thanks anyway