Database Develop

Brick "Service Required Code Corrupt"

Hi dose somebody now how to remove this brick i tried everything ?
and this dose not worked http://forum.xda-developers.com/razr...5?goto=newpost

I think when you have the service code error there is nothing you can do.
But you still get into bootloader, correct?
Have you tried manually flash the recovery / gpl / motoboot etc. once at a time?
If you cant get into bootloader anymore, try this, but only then

dagoban said:
I think when you have the service code error there is nothing you can do.
But you still get into bootloader, correct?
Have you tried manually flash the recovery / gpl / motoboot etc. once at a time?
If you cant get into bootloader anymore, try this, but only then
Click to expand...
Click to collapse
I can not get to bootloaderI tried every thing its stuck on Service Required code corrupt message.
What you mean about manually flash the recovery - you mean over the bootloader fastboot flash recovery recovery.img ?
No i can not, can only connect as MEDFIELD

miky03 said:
I can not get to bootloaderI tried every thing its stuck on Service Required code corrupt message.
What you mean about manually flash the recovery - you mean over the bootloader fastboot flash recovery recovery.img ?
No i can not, can only connect as MEDFIELD
Click to expand...
Click to collapse
Sorry, forgot to include the link: http://forum.xda-developers.com/razr-i/help/help-unbrick-completely-unmodified-razr-t2980659
If you cant get into the bootloader, it means you are not into fastboot mode, which means you will not be able to flash anything (bootloader, recovery, system partition)
If this is the case, then do this http://forum.xda-developers.com/razr-i/help/help-unbrick-completely-unmodified-razr-t2980659
If you successfully flash it but still your phone is not working, then you can throw away your phone, it is bricked beyond good and evil. Happened to me, too, not even Motorola could repair it then. If you are still in warranty, send it to Moto and you get a new device.

dagoban said:
Sorry, forgot to include the link: http://forum.xda-developers.com/razr-i/help/help-unbrick-completely-unmodified-razr-t2980659
If you cant get into the bootloader, it means you are not into fastboot mode, which means you will not be able to flash anything (bootloader, recovery, system partition)
If this is the case, then do this http://forum.xda-developers.com/razr-i/help/help-unbrick-completely-unmodified-razr-t2980659
If you successfully flash it but still your phone is not working, then you can throw away your phone, it is bricked beyond good and evil. Happened to me, too, not even Motorola could repair it then. If you are still in warranty, send it to Moto and you get a new device.
Click to expand...
Click to collapse
I tried everything my razr i still Hardbricked
now i want to tray this method:
set PACKAGE_DIR=unbrick
set FWDNX=--fwdnx %PACKAGE_DIR%\dnx
set FWIMAGE=--fwimage %PACKAGE_DIR%\ifwi
set OSDNX=--osdnx %PACKAGE_DIR%\dnx
set OSIMAGE=--osimage %PACKAGE_DIR%\motoboot
unbrick\xfstk-dldr-solo.exe %FWDNX% %FWIMAGE% %OSDNX% %OSIMAGE% --verbose
Question where i can get this files from (dnx, ifiw, motoboot) ?
I had CM11 before then downgrade to ICS 4.0.4. then used wrong script for rooting then got "Service Required code corrupt message".

miky03 said:
]
Click to expand...
Click to collapse
Please also don't post the same question in several threads, we try to keep it as clean as possible here

Urgent advice needed on Razr i XT890

hi, my phone Razr i XT890 is showing the Red Moto Logo, I tried to factory reset by going into fastboot also but nothing happened, I can find many thread here about the same problem but nothing conclusive could be found in those threads, hence I sent my phone for repairs, the technician hooked it up to a computer and said that most likely it is a software issue and the phone would be ok, after waiting for an hour I was told that the emmc has died and it cannot be replaced and the only solution would be to change the motherboard, since the mother board is not avaible in the market I looked it up on aliexpress and it costs around 70$ where as a new/refurbished phones are listed for 75$, need you guys advice on whether it can be repaired or not and if yes then how. I am a regular user and not an expert like you guys so if you suggest any thing plz do it in detail. FYI its a factory unlocked phone which had jelly bean OS and I never rooted it or did any hanky panky to it. Thanks

What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.

Hazou said:
What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.
Click to expand...
Click to collapse
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.

cooljatt18 said:
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.
Click to expand...
Click to collapse
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?

Hazou said:
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?
Click to expand...
Click to collapse
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !

cooljatt18 said:
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !
Click to expand...
Click to collapse
This is most likely solvable. Try that flash methods a few post above and see what happens s

Hazou said:
This is most likely solvable. Try that flash methods a few post above and see what happens s
Click to expand...
Click to collapse
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it

cooljatt18 said:
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it
Click to expand...
Click to collapse
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk

AGISCI said:
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !

cooljatt18 said:
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !
Click to expand...
Click to collapse
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk

AGISCI said:
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
thanks a ton!!!

hi, guys sorry for posting so late, was super busy, any how haven't got a mechanic to flash the phone, guess I will have to do it myself, request you to answer my queries
.1) a mechanic to whom I went convinced me to believe that the problem was due to a faulty battery and he could fix it in 5 mins flat, He opened the phone did some tinkering with it, I am not sure what but the phone was in same condition ie Red logo on booting. Was very disappointed came back home and I tried to restore it through fast boot and I noticed that the Battery Current was coming as 4.1 V earlier it was 3.7 !!! I am sure that the mechanic messed it up. Now my question is will it harm the phone, battery or any other part?? Should I just leave it the way it is ie 4.1V and not try to rectify it to bring it to 3.7V.
.2) I am not able to get a mechanic who can flash the phone as suggested in previous posts, pl tell how I can do it myself, I am a newbie at this and have zero knowledge of the process, pl tell what all software are needed! And hardware if any. All I have got currently is the firmware posted in previous posts.
Thanks

SOFT BRICK using tool Xiaomi Mi A2

Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy

What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...

AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this

Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work

AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?

erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.

AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:

erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.

AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me

erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers

AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?

erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.

Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861

ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:

AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp

erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.

ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?

Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.

prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?

erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.

So I tried to unlock via EDL...

...and I thought it had worked but as it turns out, it did not. I found out it did not when I tried to root to which the phone proceeded to tell me it was lock.
Now, when I go into Recovery Mode, the phone does not come up in ADB even when trying to unlock after using the ASUS unlocker tool... Is the ADB bridge fried forever? How do I reinstate it to be able to root? I don't mind wiping, I just want to recover the possibility to root. Any way to do that? God I feel dumb right now...
Edit: I've gotten ADB to recognize the phone in Recovery Mode by installing the exact Manufacturer and Model ADB drivers but the second I get into Fastboot mode, it's like the side USB-C suddenly becomes non-existent, same goes for the bottom one. Feels like a kill.switch from ASUS to me :/
Edit 2: Is there a way to flash while in Recovery? Or in normal OS operations? (sounds like a bad idea but I'm out of ideas as of now)

So neither of the two USB ports in the phone seem to work for you in bootloader mode?

dennis96411 said:
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
Click to expand...
Click to collapse
Exactly, the bootloader is also unlocked after using ASUS's tool .apk, I am on 1910.44 WW, I tried different ADB's while in Windows, tried to copy DeviceID, it all works when in normal boot OR in recovery mode but the second I am in fastboot mode, both USB's stop working. As if ASUS locked the access when I mistakenly tried to gain root while the bootloader was locked. Maybe if I could lock it back but that would require me being in fastboot afaik.
Can I lock it back while in recovery? If so, what would be the prompt?

I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.

dennis96411 said:
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
Click to expand...
Click to collapse
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.

WhyKlwd said:
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
Click to expand...
Click to collapse
Is there an option to apply a full OTA from the stock recovery?

dennis96411 said:
Is there an option to apply a full OTA from the stock recovery?
Click to expand...
Click to collapse
Before anything, thanks for helping, it's greatly appreciated!
So, no sadly, when I get in Recovery Mode my options are:
Reboot system now
Reboot to bootloader
Wipe data/factory reset
Power off
As anyone would, I tried kicking into bootloader from recovery hoping that it would trigger something different to give me fastboot but to no avail, I wiped a couple of times as well, that didn't pan out.
Edit: I feel like my best chance at this point is when ASUS releases a new WW firmware update, that it HOPEFULLY brings Fastboot Mode to it's original value... But according to a thread somewhere on XDA, it does not install a full partitioned recovery so I'm not having my hopes up...
The other thing would be to butcher a USB-C cable and see if I get a response when connected on the orange USB-C but that's also a risk to take. So that doesn't work, that USB-C gets no response whatsoever.

What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.

HomerSp said:
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
Click to expand...
Click to collapse
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!

WhyKlwd said:
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
Click to expand...
Click to collapse
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.

HomerSp said:
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
Click to expand...
Click to collapse
Yeah it works, or at least it did long enough for me to be able to root. I haven't tried it since but I would assume that it fixed it, tomorrow I'll most likely do a RAW flash to fix all potential risks as well as try the latest CN firmware. EDL never worked, that's what got me in that situation in the first place... well that and me not paying full attention.

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