Related
On Saturday appeared an OTA update to do on my mi A2 but after installed and restarting it died. It does not enter recovery mode and the screen is always on with android one bootscreen logo.
PS: I never flash the phone and i never change anyting in the system of the phone.
The only response that i have in the phone is enter in it Fastboot menu. I read some threads and untill now i cant fix my phone.
I will try to explain what i do:
I've tried using this tool https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585.
I try option 3 (Unbrick/Revert to Stock/Force update and the program tell me to unlock the bootloader.
When i tried to unlock bootloader by option 1 and then 1, 2 and 3 ( Unlock flashing critical, unlock OEM , unlock flashing ) the programs says: Failed Unlock is not allowed.
Then i try the response 9 to this thread https://forum.xda-developers.com/mi-a2/help/impossible-flashing-xiaomi-mi-a2-t3837565 to try unlocked the bootloader
But i have the same response ( Flashing Unlock is not allowed )
I read and i try but i cant unbrick my phone, someone can help?? Thanks
We are in the same boat buddy, the same thing happened to the phone of my wife.
It *sounds* like the update failed, and normally that would mean it would switch the slot back to the one that was working and boot that.
But you've tried a bunch of options from some tool, I've no idea what it did, as the tool doesn't tell you what commands it's doing.
I'd suggest to go to fastboot and see if you can tell which slot is active, then switch it to the other slot, then do fastboot reboot and cross your fingers
I have the same problem (for other reasons, but exactly the same problem). You can also try "fastboot oem edl", but it did not work for me, so I suppose you have little chance for it to work.
I have been searching and it looks like there are some "deep flash cables" that can make the phone enter edl mode to flash it using mi flash tool. Maybe these could work for us. There is apparently other way to enter edl mode, but it requires opening the phone (that I do not want to do) to short two test points.
I cant enter revorymode only fastboot mode. But when in fastbootmode my connected pc cant even find the phone. Im going to return the phone.
I have the same problem, I have this edl cable but so far no luck.
Do not realy k Ow how to use.
Are you sure it was the OTA update that bricked your phone? That Treble system isn't just there for the kicks, its there to prevent serious issues like these.
I'm stucked on fastboot, I don't want to open my phone. Could anyone help us? I already tried a lot of things, my computer doesn't recognize my mobile when is on fastboot mode. I already tried to install a lot of drivers or try to use differents adbs.
...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.
Hey guys,
I need some assistance as I am not able to unbrick my RM3 with unbrick tool. Multiple times I have already got it worked, flashed many times, but this time I am not getting my phone started. Normally, I use the NON-EU unbrick tool, all goes well but this time, it says THIS DEVICE CAN'T BE TRUSTED, WON'T BOOT UP. After multiple tries, I tried that EU unbrick too as well, but the same result.
I think I have locked the bootloader while on CN Rom 5.14, most probably this is the only reason, I was doing some tweakings and got it bricked. Anyone here who can tell me if there is such thing named CN Unbrick tool or any other way around to get it worked. I can enter FASTBOOT and EDL Mode but recovery mode showing black screen and adb is not recognising as didn't enable USB debugging. please help...
[email protected] said:
Hey guys,
I need some assistance as I am not able to unbrick my RM3 with unbrick tool. Multiple times I have already got it worked, flashed many times, but this time I am not getting my phone started. Normally, I use the NON-EU unbrick tool, all goes well but this time, it says THIS DEVICE CAN'T BE TRUSTED, WON'T BOOT UP. After multiple tries, I tried that EU unbrick too as well, but the same result.
I think I have locked the bootloader while on CN Rom 5.14, most probably this is the only reason, I was doing some tweakings and got it bricked. Anyone here who can tell me if there is such thing named CN Unbrick tool or any other way around to get it worked. I can enter FASTBOOT and EDL Mode but recovery mode showing black screen and adb is not recognising as didn't enable USB debugging. please help...
Click to expand...
Click to collapse
I think any unbrick tool should work both EU and non EU
you must pc driver uninstall reboot pc driver install again reboot your pc and also check your port number eld mode
red magic 3 driver reinstall in may case port number change automaticly i m notice this point it will help you to start your device red magic 3
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.)
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Andris85 said:
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Click to expand...
Click to collapse
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
gurtnyi said:
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Click to expand...
Click to collapse
Just the boot.ini. but I think this would make fastboot mode work. But it's not working
tutibreaker said:
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
Click to expand...
Click to collapse
What should I use to reflash? Mi flash? This is the NS
Yes... I probably mixed up the boot file in the downloads folder and not the correct received flash
Click to expand...
Click to collapse
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
gurtnyi said:
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
Click to expand...
Click to collapse
yepp, enable oem unlock. But fastbootmode is required for all operations. But fastboot mode doesn't work.
What do you mean it doesn't work?
Can't enter into fastboot mode?
gurtnyi said:
What do you mean it doesn't work?
Can't enter into fastboot mode?
Click to expand...
Click to collapse
Can't enter fastboot mode. The device only shows "Redmi" lettering. If fatboot worked, I could have done it already. power+volume down, the device just restarts and shows "redmi".
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
gurtnyi said:
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
Click to expand...
Click to collapse
it just restarts, as long as I press and hold volume down+power, if I don't press it, it just shows the redmi text
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
gurtnyi said:
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
Click to expand...
Click to collapse
TXH
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Pegelaar_NL said:
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Click to expand...
Click to collapse
Yep, this guy here 's got the point. If you can't flash with sp flash tool because auth fail, there's a method to bypass it.
You can find the tutorial here: https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
I also got some help from this guy's post, many thanks to him too.
https://forum.xda-developers.com/t/...ad_da_fail-0x7d4-2004-for-mtk-phones.3692259/
Let us know how it's going with it! ;D
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buytoday there is a lot of devices for gaming like rog phone and red magic
Click to expand...
Click to collapse
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Click to expand...
Click to collapse
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
tutibreaker said:
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Click to expand...
Click to collapse
If you can root it easily, then the expensive one is good for me! Normal root was not available for typical gamer phones for years. If I buy something for which root may not be available, then I'm wasting my money...
gurtnyi said:
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
Click to expand...
Click to collapse
I will look today