Question Help Qualcomm CrashDump Mode NE2213 - OnePlus 10 Pro

Hello forum team,
I have a OnePlus 10 Pro with NE2213 version.
I have follow this thread successfully https://forum.xda-developers.com/t/guide-install-twrp-root-install-magisk-bypass-safetynet.4533511/
and this thread "How to Remove Orange State Warning on OnePlus Android 13" with no success
Now i'm on the Qualcomm Crashdump mode, with no access to bootloader or twrp. How to acess to flash an other rom or reset that?
Thanks you for your help

Never trust droidwin.com. In the current situation there is no way to fix this. I think RMA is the only option.

Did a quick google and it looks like you used the OP9 method on OP10... oof. The second link on google was the XDA page in the OP9 forums, and yeah that first link is super suspect since they don't even list model number. Sucks.
Most likely stuck with RMA or MSM as only options, you can attempt to boot into the other slot but I'm not sure if that file is persistent between the two.

DD228 said:
Hello forum team,
I have a OnePlus 10 Pro with NE2213 version.
I have follow this thread successfully https://forum.xda-developers.com/t/guide-install-twrp-root-install-magisk-bypass-safetynet.4533511/
and this thread "How to Remove Orange State Warning on OnePlus Android 13" with no success
Now i'm on the Qualcomm Crashdump mode, with no access to bootloader or twrp. How to acess to flash an other rom or reset that?
Thanks you for your help
Click to expand...
Click to collapse
Qualcomm Crashdump is that you are wrong slot ... You still should have fastboot. Just hold the power button and down volume it will reboot to fastboot ... then use this command " fastboot getvar current-slot " after that use this command to change slots " fastboot set_active other "

Or ... when you get back to fastboot flash twrp to both slots ... just dont panic...like some have and tried to load boot. img and bricked there phones
Stuck in bootloop after trying to flash Oxygen OS 13 coming from ColourOS 13
I have a Chinese Oneplus 10 Pro which I received with ColorOS 12.1 Android 12 NE2210_11_A_07. It then updated OTA with ColourOS 13 .x but the Google Assistant ("Hey Google!") functionality was not working. So then I tried to flash a global rom to...
forum.xda-developers.com

Thanks you for your response Canuck and link to post, i try that tomorrow in France to obtain twrp again.
When you say "just dont panic...like some have and tried to load boot. img and bricked there phones" if i have access to twrp again what do i do? usually I will load original boot image? Or or I have to check between slot?

DD228 said:
Thanks you for your response Canuck and link to post, i try that tomorrow in France to obtain twrp again.
When you say "just dont panic...like some have and tried to load boot. img and bricked there phones" if i have access to twrp again what do i do? usually I will load original boot image? Or or I have to check between slot?
Click to expand...
Click to collapse
Try to switch slots first...and reboot...I been there many times...LOL

Ok it's clear thanks
But now, i can't obtain an other thing than Qualcomm crashdump mode, when i make power button and volume bottom since phone off...
And when i keep my phone off it's reboot on the same screen

DD228 said:
Ok it's clear thanks
But now, i can't obtain an other thing than Qualcomm crashdump mode, when i make power button and volume bottom since phone off...
And when i keep my phone off it's reboot on the same screen
Click to expand...
Click to collapse
when it powers off...just hold the power button and the volume down see if it boot in to fastboot

Nothing when i make that, vibration + black screen 10 seconds and Qualcomm Crashdump Mode After

DD228 said:
Nothing when i make that, vibration + black screen 10 seconds and Qualcomm Crashdump Mode After
Click to expand...
Click to collapse
I just put my phone in Qualcomm dump mode...while you are in Qualcomm dump mode....hold the power button and volume down button...it will put you to fastboot...?

I think it go into Qualcomm dump mode because there is nothing on that slot..."not sure" but you need to get to fastboot...can't do anything without fastboot

DD228 said:
Hello forum team,
I have a OnePlus 10 Pro with NE2213 version.
I have follow this thread successfully https://forum.xda-developers.com/t/guide-install-twrp-root-install-magisk-bypass-safetynet.4533511/
and this thread "How to Remove Orange State Warning on OnePlus Android 13" with no success
Now i'm on the Qualcomm Crashdump mode, with no access to bootloader or twrp. How to acess to flash an other rom or reset that?
Thanks you for your help
Click to expand...
Click to collapse
What method did you try to use exactly to remove the orange warning?

Canuck Knarf said:
I think it go into Qualcomm dump mode because there is nothing on that slot..."not sure" but you need to get to fastboot...can't do anything without fastboot
Click to expand...
Click to collapse
Yes it's possible!
TheNewHEROBRINE said:
What method did you try to use exactly to remove the orange warning?
Click to expand...
Click to collapse
I have try this method
How to Remove Orange State Warning on OnePlus Android 13
In this guide, we will show you various methods to remove the Orange State Warning on your OnePlus device running Android 13/OxygenOS 13.
www.droidwin.com
But with extract of payload.bin of OnePlus 10 Pro NE2213, Android 13 image on slot A

DD228 said:
Yes it's possible!
I have try this method
How to Remove Orange State Warning on OnePlus Android 13
In this guide, we will show you various methods to remove the Orange State Warning on your OnePlus device running Android 13/OxygenOS 13.
www.droidwin.com
But with extract of payload.bin of OnePlus 10 Pro NE2213, Android 13 image on slot A
Click to expand...
Click to collapse
You did this cause you don't like the Orange state...!!!! Buds thats for oneplus 9 pro ...no where did I see it for 10 pro...
What method did you try...LOL . Method 1 , 2 , 3 , or 4

Look at my pic in my Avatar...says it all

Related

Recovery/fastboot/download modes howto

Hi folks.
It seems there's not much info about the phone.
That is why let's share any useful information regarding it.
What I have found so far:
ColorOS recovery - start the phone with "Vol Down" + "Power" buttons
Qualcomm Download mode (QDL mode, 9008) - from ColorOS recovery tap a few times recovery version line.
For now I did not succeed in booting into fastboot mode. It immediately reboots into system
EDIT. 3 taps on Version string bring QDL mode (see the attachment). After first tap string turns green.
yakovpol said:
Hi folks.
It seems there's not much info about the phone.
That is why let's share any useful information regarding it.
What I have found so far:
ColorOS recovery - start the phone with "Vol Down" + "Power" buttons
Qualcomm Download mode (QDL mode, 9008) - from ColorOS recovery tap a few times recovery version line.
For now I did not succeed in booting into fastboot mode. It immediately reboots into system
Click to expand...
Click to collapse
Did you see oem unlock toggle in developer settings? Try to adb via the model of the phone instead?
Also could you provide a camera2 test info in FULL mode here as an attachment please?
yakovpol said:
Hi folks.
For now I did not succeed in booting into fastboot mode. It immediately reboots into system
Click to expand...
Click to collapse
Hi. Bootloader not unlock now. Because you can't boot to fastboot.
New version came out today - RMX1991_11_A.11
Yea, a new version came out, dark mode is included now, security level is October 5th. The list of the changes is quite long (see it attached if interested). The shot of the update process is attached too. What "realme Lab" means is in the attachment too.
xterminater07 said:
Did you see oem unlock toggle in developer settings? Try to adb via the model of the phone instead?
Click to expand...
Click to collapse
The OEM option is present, see the attachment.
The second part of the statement about adb is not clear.
If you mean adb reboot bootloader, it does not help either. The phone boots into fastboot mode and immediately (in about half a second) reboots to system.
adb starts working only if File Transfer is enabled after USB cable is connected.
xterminater07 said:
Also could you provide a camera2 test info in FULL mode here as an attachment please?
Click to expand...
Click to collapse
See the file attached. You are welcome.
The phone stays in fastboot mode for 0.6 sec
The text I see is
已进入Fastboot
长按电源键6〜10秒或重装电池退出
What means
You entered Fastboot
Press and hold power button for 6 - 10 seconds or reload battery to exit
Is there any way to stop there?
yakovpol said:
The text I see is
已进入Fastboot
长按电源键6〜10秒或重装电池退出
What means
You entered Fastboot
Press and hold power button for 6 - 10 seconds or reload battery to exit
Is there any way to stop there?
Click to expand...
Click to collapse
so what happens after that 0.6second in fastboot? It reboots back to normal?
---------- Post added at 04:23 PM ---------- Previous post was at 04:19 PM ----------
yakovpol said:
See the file attached. You are welcome.
Click to expand...
Click to collapse
when you run the camera2 test app by the author tetsomething something in playstore, hit analyze, then go to the "Full" tab on top, then share it as file on here if you can. Or copy and paste it to notepad and upload it.
Here you are
Today's answer from Realme Support for bootloader unlock and kernel sources
Hello,
Greetings from realme Europe. Thank you for reaching out to us.
We would like to inform you that as of now bootloader unlock for realme X2 and kernel source code is not available. Further, kindly stay tuned to our official website: https://www.realme.com/eu/ for the latest news and updates. Have a nice day.
Warm Regards,
Team realme Europe
yakovpol said:
Hello,
Greetings from realme Europe. Thank you for reaching out to us.
We would like to inform you that as of now bootloader unlock for realme X2 and kernel source code is not available. Further, kindly stay tuned to our official website: https://www.realme.com/eu/ for the latest news and updates. Have a nice day.
Warm Regards,
Team realme Europe
Click to expand...
Click to collapse
It's good. But where is tools for it?
Some sort of test in recovery
ColorOS recovery, tap recovery version line 10 times, a prompt pops up about nearly 30-minute test. What kind of test I do not know. It took about 17 minutes. See the shots attached.
Also it is not clear to me when tapping on recovery version line initiate QDL mode, when this test?
Installation attempt for Euro version of software
There are two documented ways to install a downloaded ROM file: from inside ColorOS (tap *.ozip from built-in file browser; boot recovery and initiate installation from there). Both fail, but the second one gives interesting result (see the shot attached; native and alien=euro files are both visible).
Realy frustating. I guess it will neuer come because of OPPO. 5 Pro can do, eventuell x2 pro can do.
The bootloader looks different to x2 pro and 5 Pro.
With the Test lap apk you will get in touch with OPPO.
What exactly the app is Ding i dont know.
I look inside the smali code but iam not a coder.
I guess we download a new Bootloader Image and install it.
Could someone from you post some files for me?
/sbin/recovery
Second one
adb pull /vendor/lib64/libapplypatch_jni.so
Have you got CN or global devices?
yakovpol said:
There are two documented ways to install a downloaded ROM file: from inside ColorOS (tap *.ozip from built-in file browser; boot recovery and initiate installation from there). Both fail, but the second one gives interesting result (see the shot attached; native and alien=euro files are both visible).
Click to expand...
Click to collapse
So, you directly tried to switch from Chinese to Global rom by using recovery! Have you succeeded yet?
I want to change my rom to global to...
Plzzz help
FYI
It seems (at least once it worked to me, though it seems quite strange) the language mix in stock recovery may be solved by format userdata in recovery.
Iam trying to unlock the EU Device 1993.
I dont think this will work.
Only China devices 1991 will work.
djsven said:
Iam trying to unlock the EU Device 1993.
I dont think this will work.
Only China devices 1991 will work.
Click to expand...
Click to collapse
They have limit like 1000 unlocks per month or something like this... May it be the reason?
djsven said:
Iam trying to unlock the EU Device 1993.
I dont think this will work.
Only China devices 1991 will work.
Click to expand...
Click to collapse
Have you unlocked the Realme X2 1993 (European version) successfully? If yes then with which in deep testing app?
yakovpol said:
The phone stays in fastboot mode for 0.6 sec
The text I see is
已进入Fastboot
长按电源键6〜10秒或重装电池退出
What means
You entered Fastboot
Press and hold power button for 6 - 10 seconds or reload battery to exit
Is there any way to stop there?
Click to expand...
Click to collapse
How to solve problems

Mi9 Global - Accidentally locked bootloader and stock in recovery/fastboot

Hi,
Recently purchased a Mi 9 Global version, got the OTA update to MIUI 11, and everything was well. It is a superb phone, but I like to have root on my phones (mostly for Adblocking and System2, better control overall). I tried to install TWRP (custom version for Mi9) because I wanted to install Magisk/Root or try a different rom eventually. Anyway... I made a huge mistake. After trying to reboot, I noticed things had gone wrong, and was stuck in a boot loop. I guess I panicked and tried to flash the phone back to the latest global MIUI rom (Version 11, Android 10, from official site), using the Xiaomi Flash App but I did not uncheck the "clean and lock bootloader" checkbox on the bottom right of the app, which is somehow enabled by default. The flash failed at that time, for unknown reason, but it seems like it succeeded in locking my bootloader, with an empty partition, except for fastboot access and Mi Recovery module. I have to admit I've always been pretty lucky with all my previous flashes on other devices, and I guess I got a little careless. That was pretty stupid of me, in retrospect.
Since then, I am stuck in either Mi Recovery or Fastboot, and it seems that my originally Global Mi 9 with unlock bootloader has now a locked bootloader. Any attempt at either using the Xiaomi Flash utility gives me an error message ("Erase boot error"), and if I boot into Fastboot and try to flash TWRP, I get the "Remote:Erase is not allowed in Lock State" error.
From what I understand, my options are pretty limited now. The phone is still powered on, stuck in Recovery mode and rebooting every 5 or 10 minutes by itself (probably a way to avoid screen burn-in?), but I can't seem to be able to shut it down in anyway, as there are no fastboot commands to send a shutdown signal. And no matter what button combination I press, the phone always ends up rebooting.
I tried the Xiaomi Unlocker utility, but it needs the phone to be out of recovery to check the credentials binding the phone to my account. All data on the phone has been wiped already, so that's not an option. Two options I have seen :
1. Open the battery cover (required a heat gun and risky), to short some pins and try to flash while there is a short to circumvent the security. I'm not that brave yet, and since the phone is still running and has probably about 80% battery, I don't want to use a heat gun on the device.
2. Shady stuff involving paying 30 or 40 Euros to a random guy who can somehow make everything work magically by remotely logging in on my computer via Teamviewer (Not happening in a million years).
I'm wondering if there is an alternative, other than bringing the device to an official Xiaomi store (I'm in Bangkok and they do have one official shop at Fortune Town), but even then, I don't know if they'll just tell me I got myself an expensive paperweight.
Any help/insight regarding this issue would be much, much appreciated!
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
g_seva said:
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
Click to expand...
Click to collapse
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Twomby said:
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Click to expand...
Click to collapse
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
g_seva said:
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
Click to expand...
Click to collapse
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
To enter fastboot mode, long press the volume down key and the power key. Then unlock bootloader with Xiaomi app.
zahdekar said:
To enter fastboot mode, long press the volume down key and the power key. Then flash stock rom.
Click to expand...
Click to collapse
I have managed to enter fastboot mode, as described in my initial post. The problem is that when I try to flash, I get the following error: "Flashing not allowed in lock state".
Twomby said:
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
Click to expand...
Click to collapse
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
g_seva said:
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
Click to expand...
Click to collapse
From what I understand, the "normal mode" needs the tool to be able to access the OS while it's running. I don't have an OS. I will give it a shot tomorrow (3 AM here, exhausted, and don't want to boot into Windows again!), but my hopes are not so high. Anyway, thanks for the help, much appreciated! Will let you know what happens! Cheers!
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
zahdekar said:
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
Click to expand...
Click to collapse
I've stumbled upon this link earlier today. But it's 404 on my end. Can you access it from where you are? Thanks!
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
zahdekar said:
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
Click to expand...
Click to collapse
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Twomby said:
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Click to expand...
Click to collapse
I have the same problem! "The system has been destroyed" (((
And mi unlock tool not work abount 2 days (authorization not passes)
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
zahdekar said:
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
Click to expand...
Click to collapse
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Twomby said:
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Click to expand...
Click to collapse
Hello @Twomby did you managed to get it working it the end?
Same issue here
Hi,
I am encouraging the same issue. Does someone found a solution to this?
tago4ever said:
Hi,
I am encouraging the same issue. Does someone found a solution to this?
Click to expand...
Click to collapse
I came across this Mi8 thread, not sure if it's possible on the Mi9, but he seems to have been able to flash it through EDL mode, you might ask him the question: https://xiaomi.eu/community/threads/mi-8-bricked-from-nowhere.55723/#post-543605
There's also this Mi9 thread: https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966

Question Hard brick

PLEASE HELP!!
I just hard bricked my wife's new Redmi Note 10 Pro!
I bought the Chinese version and got the bootloader unlocked, and then tried to replace it with the global Rom from the official website.
In the process I kept receiving an error: "Mismatching Image and device error ".
I followed a couple of tutorials and this particular seem popular, where I had to delete some lines in the .bat file.
After that the flashing process started but halfway an error appeared again. After several attempts I decided to restart from Fastboot mode, and this was when I realized it had bricked.
Now I can't go to Fastboot mode and I keep getting Vibrations but a dead screen.
PLEASE HELP
swarzB said:
PLEASE HELP!!
I just hard bricked my wife's new Redmi Note 10 Pro!
I bought the Chinese version and got the bootloader unlocked, and then tried to replace it with the global Rom from the official website.
In the process I kept receiving an error: "Mismatching Image and device error ".
I followed a couple of tutorials and this particular seem popular, where I had to delete some lines in the .bat file.
After that the flashing process started but halfway an error appeared again. After several attempts I decided to restart from Fastboot mode, and this was when I realized it had bricked.
Now I can't go to Fastboot mode and I keep getting Vibrations but a dead screen.
PLEASE HELP
Click to expand...
Click to collapse
Download the chinese version
So open google translate and translate" Redmi Note 10 Pro stock firmware China "
copy and paste in google the translated text once you fing one you can download try that one but only flash the partition you need other wise your phone will be in chinese
flairepathos.info said:
Download the chinese version
So open google translate and translate" Redmi Note 10 Pro stock firmware China "
copy and paste in google the translated text once you fing one you can download try that one but only flash the partition you need other wise your phone will be in chinese
Click to expand...
Click to collapse
The problem currently is that I can not boot into Recovery or Fastboot
swarzB said:
The problem currently is that I can not boot into Recovery or Fastboot
Click to expand...
Click to collapse
Check if the oem option in developer locked again
flairepathos.info said:
Check if the oem option in developer locked again
Click to expand...
Click to collapse
I unlocked it before i started
swarzB said:
I unlocked it before i started
Click to expand...
Click to collapse
When you flash things (usually boot.img) it will lock it again
just check and confirm if its still unlocked
plug in your device and do adb reboot bootloader
flairepathos.info said:
When you flash things (usually boot.img) it will lock it again
just check and confirm if its still unlocked
plug in your device and do adb reboot bootloader
Click to expand...
Click to collapse
unfortunately for me my screen wont come on
Usually Its just stuck in engineer/ edl mode
So not to worry but try flashing using sp tools
Put your phone on charger for now
Then
If your phone not getting recognised by pc, unplug and wait for a 6-10 seconds and plugin again or plug in and hold Power+ Volume down or up button till pc recognises it, this will be handy later
here's a guide to flash via SP tools, or you can follow a youtube video to guide you along step by step
How to Flash Xiaomi Redmi Note 10 Pro Android phone - Easy and Working methods [2022]
Flashing Xiaomi Redmi Note 10 Pro Android phone can be difficult task! But not anymore, flash ROMs on your Xiaomi Redmi Note 10 Pro phone easily with this
flashifyit.com

Question dm-verity corruption Redmi Note 10 5G

Hello,
I don't know if this is right forum. If this is wrong forum, please suggest me the right one.
I have a Redmi Note 10 5G bought at China. There are all Chinese apps and No Google apps. I didn't like it so, decided to flash it into Global ROM. I have done this kind of thing many times before, but never in this device and never got this error. I downloaded the latest Global ROM which was MIUI 12.0.7.0. I extracted it and flashed using Xiaomi ADB and Fastboot tools. Everything was alright. When the device rebooted, I got:
dm-verity corruption.
Your device is corrupted.
It cannot be trusted and may not work properly.
Press power button to continue.
Or, your device will power off in 5s.
I pressed the power button and it got stuck on redmi logo forever.
Then i downloaded MIUI 12.0.6.0 Global. Then flashed it, got the same error? I tried all tricks on internet, nothing worked.
I thought Nothing is working, lets just install Chinese ROM and use it anyway. I flashed Chinese ROM and got the same error ! What is going on? What is problem?? I haven't locked bootloader
I am now hopeless. Can anyone tell me how to fix this? Should I take to somewhere to repair, or there is a trick? Any answer will be thanked!
My device:
Redmi Note 10 5G (6GB RAM 128GB ROM)
My PC:
Dell Inspiron 15 3567 (Windows 10 21H1 Latest)
Thank YOU!!!
My guess is you've re-locked phone's bootloader after flashing the ROMs in question.
No I did not Re-Lock the Bootloader
jwoegerbauer said:
My guess is you've re-locked phone's bootloader after flashing the ROMs in question.
Click to expand...
Click to collapse
no,
while for you "un known" why don't you check my post "root gained" you'll get rid of that dm-verity corruption
simika said:
no,
while for you "un known" why don't you check my post "root gained" you'll get rid of that dm-verity corruption
Click to expand...
Click to collapse
Hello, Thank you for replying. I already tried that. I wont get the error, but my phone is stuck on Redmi Logo. I don't want to fix that error. I just want to get out of bootloop. Even after I press power button, I got stuck on Redmi Logo
Un KnOwN said:
Hello, Thank you for replying. I already tried that. I wont get the error, but my phone is stuck on Redmi Logo. I don't want to fix that error. I just want to get out of bootloop. Even after I press power button, I got stuck on Redmi Logo
Click to expand...
Click to collapse
bootloop also is NOT a real one.. if you read ( or see the screenshot i previously posted in another thread , you need to press POWER button.. press it even 2 times and be sure it's going to load your phone properly !
i was in the same situation at begin and it's not a real bootloop
( and if you load vbmeta you won't even get that message/bootloop at all ! )
simika said:
bootloop also is NOT a real one.. if you read ( or see the screenshot i previously posted in another thread , you need to press POWER button.. press it even 2 times and be sure it's going to load your phone properly !
i was in the same situation at begin and it's not a real bootloop
( and if you load vbmeta you won't even get that message/bootloop at all ! )
Click to expand...
Click to collapse
WELL i tried everything you said. i even waited overnight. nothing happened only redmi logo. I took my phone to repair, so lets close this
Hat ihr Telefon schon repariert? Wieviel wurden Sie bezahlen? Mein Telefon ist wie Ihr Telefon defekt.
Has your phone been repaired yet? How much would you pay? My phone is broken like your phone.
Un KnOwN said:
Hello,
I don't know if this is right forum. If this is wrong forum, please suggest me the right one.
I have a Redmi Note 10 5G bought at China. There are all Chinese apps and No Google apps. I didn't like it so, decided to flash it into Global ROM. I have done this kind of thing many times before, but never in this device and never got this error. I downloaded the latest Global ROM which was MIUI 12.0.7.0. I extracted it and flashed using Xiaomi ADB and Fastboot tools. Everything was alright. When the device rebooted, I got:
dm-verity corruption.
Your device is corrupted.
It cannot be trusted and may not work properly.
Press power button to continue.
Or, your device will power off in 5s.
I pressed the power button and it got stuck on redmi logo forever.
Then i downloaded MIUI 12.0.6.0 Global. Then flashed it, got the same error? I tried all tricks on internet, nothing worked.
I thought Nothing is working, lets just install Chinese ROM and use it anyway. I flashed Chinese ROM and got the same error ! What is going on? What is problem?? I haven't locked bootloader
I am now hopeless. Can anyone tell me how to fix this? Should I take to somewhere to repair, or there is a trick? Any answer will be thanked!
My device:
Redmi Note 10 5G (6GB RAM 128GB ROM)
My PC:
Dell Inspiron 15 3567 (Windows 10 21H1 Latest)
Thank YOU!!!
Click to expand...
Click to collapse
1. power on phone insert usb cable mobile show dm-verity corruption option then quick click 3 time volume up and down
your mobile skip restarting
2. after phone on. go setting developer option oem on and mobile go to update option and update your phone .

			
				
Free Solution in this video
Free Software X said:
1. power on phone insert usb cable mobile show dm-verity corruption option then quick click 3 time volume up and down
your mobile skip restarting
2. after phone on. go setting developer option oem on and mobile go to update option and update your phone .
Click to expand...
Click to collapse
nice tip!
boot to fastboot and issue command " fastboot oem cdms "
will fix the dm verity issue
chopwell20 said:
boot to fastboot and issue command " fastboot oem cdms "
will fix the dm verity issue
Click to expand...
Click to collapse
how to do this pls?
heyika26 said:
how to do this pls?
Click to expand...
Click to collapse
You must have Minimal ADB and Fastboot installed in your PC.
After installing it, open it.
Write exactly the command line above.
Connect you phone via USB while is in FastBoot Mode*, with your PC.
* For FastBoot Mode on your phone, Turn OFF your phone.
Press VOL Down & Power Button for some secs together.
** Not sure if this is necessary ,but before doing all these, you have turned ON Developer Options on your phone. (search google how to enable Developer Options)
OEM Unlocking Checked & USB Debugging Checked.
Press Enter and you're done.
For me it worked!

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

Categories

Resources