(First of all sorry for my English, I'm from Mexico)
Hello Friends, this is my first post, however, I have always used this forum as a guide along the phones I have had.
A few days ago I made a Hard Brick to my Mi Note 10 Pro, this while trying to load the Xiaomi EU Rom. I have seen many tutorials where they indicate how to revive it, without success since most are focused on the phone turning on in Fastboot mode, mine does not turn on in any way
I managed to make the phone recognize the PC in EDL mode but when flashing in Mi Tools it asks for a My account, when entering it the software tells me that my account is not authorized to carry out that transaction.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Someone here managed to solve this or know of some method in which you do not need that authorized account and finally retrieve the phone?
I would greatly appreciate your help
dbaesteban said:
(First of all sorry for my English, I'm from Mexico)
Hello Friends, this is my first post, however, I have always used this forum as a guide along the phones I have had.
A few days ago I made a Hard Brick to my Mi Note 10 Pro, this while trying to load the Xiaomi EU Rom. I have seen many tutorials where they indicate how to revive it, without success since most are focused on the phone turning on in Fastboot mode, mine does not turn on in any way
I managed to make the phone recognize the PC in EDL mode but when flashing in Mi Tools it asks for a My account, when entering it the software tells me that my account is not authorized to carry out that transaction.
Someone here managed to solve this or know of some method in which you do not need that authorized account and finally retrieve the phone?
I would greatly appreciate your help
Click to expand...
Click to collapse
do fastboot mode work?
albo.ma said:
do fastboot mode work?
Click to expand...
Click to collapse
Fastboot is an Android protocol that allows you to modify the filesystem through a USB connection to the smartphone, however, in my case it does not enter that mode, only EDL
i'm sorry but never happened to me... did u tried mi flash to flash something? does mi flash recognize your mi note 10 in edl mode?
albo.ma said:
i'm sorry but never happened to me... did u tried mi flash to flash something? does mi flash recognize your mi note 10 in edl mode?
Click to expand...
Click to collapse
Yes, I already tried Mi Flash, but it seems that you need an authorized account, here is the image of the software:
You could try QFIL (Qualcomm Flash Image Loader). I personally haven't needed to use it but it's designed to work with all Qualcomm Android devices.
Some info links
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
https://androidmtk.com/download-qpst-flash-tool
https://www.google.co.nz/url?sa=t&s...jAEegQIDBAO&usg=AOvVaw2g_XEnwfWA5Aj-IyquRhN2p
did a quick research and found these:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
patched version of mi flash to bypass authorization, but for redmi note 5 - check the thread if it works for other models too
https://in.c.mi.com/thread-1571278-1-1.html
people are requesting authorization there, do not know if they ever succeed but maybe it is worth to try
grandma_p said:
did a quick research and found these:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
patched version of mi flash to bypass authorization, but for redmi note 5 - check the thread if it works for other models too
https://in.c.mi.com/thread-1571278-1-1.html
people are requesting authorization there, do not know if they ever succeed but maybe it is worth to try
Click to expand...
Click to collapse
It seems to work, I have been trying for several hours to find the right .mbl for the MI CC9 Pro without success, I will continue searching and inform you.
Thank you for the support!
It looks like Mi Tools need to bind your computer to your device in order to give you authorization, i think you need to ask for authorization in the Official Xiaomi Support Forums.
tadad1 said:
You could try QFIL (Qualcomm Flash Image Loader). I personally haven't needed to use it but it's designed to work with all Qualcomm Android devices.
Some info links
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
https://androidmtk.com/download-qpst-flash-tool
https://www.google.co.nz/url?sa=t&s...jAEegQIDBAO&usg=AOvVaw2g_XEnwfWA5Aj-IyquRhN2p
Click to expand...
Click to collapse
Thanks, I'm still looking for the correct files for Mi Note 10 Pro, it seems they are limited
CescVicious said:
It looks like Mi Tools need to bind your computer to your device in order to give you authorization, i think you need to ask for authorization in the Official Xiaomi Support Forums.
Click to expand...
Click to collapse
Thank you !, I already tried and posted to see if they hopefully give me authorization :good:
dbaesteban said:
Thanks, I'm still looking for the correct files for Mi Note 10 Pro, it seems they are limited
Click to expand...
Click to collapse
You need to download a fastboot ROM, I checked and they were all there although in the video there is only one XML file but in the MIUI fastboot ROM there are 5 but I was able to load them into QFIL so I think it would not be a problem.
Have a look here you will find all the tucana ROMs
https://t.me/s/MIUIUpdatesTracker?q=#tucana
The last fastboot ROM was 11.0.9.0. you will need to extract the .tgz file which will give you a .tar file which you need to then extract again to get the files needed.
tadad1 said:
You need to download a fastboot ROM, I checked and they were all there although in the video there is only one XML file but in the MIUI fastboot ROM there are 5 but I was able to load them into QFIL so I think it would not be a problem.
Have a look here you will find all the tucana ROMs
https://t.me/s/MIUIUpdatesTracker?q=#tucana
The last fastboot ROM was 11.0.9.0. you will need to extract the .tgz file which will give you a .tar file which you need to then extract again to get the files needed.
Click to expand...
Click to collapse
Yes, in fact I tried all the xml files and their possible combinations without success.
The file "programmer patch", in this case comes in extension .elf and in the videos that I have seen is extension .mbn, Additional the first xml that is loaded is also called rawprogram.xml in the firmware for my Note 10 there are none file named like that.
I will keep searching and if I find something, I will post it for users who have this problem in the future
this is the error that gives me in all cases
.elf and .mbl are both supported by QFIL so should be fine. I have 6 .XML, rawprogram0.xml to rawprogram5.xml. When I press the load XML button I can click and drag and select them all at once. It then prompts me to load the patch.xml once again patch0.xml to patch5.xml and drag and select all. They should now all appear in the Rawprogram and Patch window. Unfortunately I can't get into EDL mode to try flashing but it looks like you are already in EDL. All the best.
Well, after many days of searching without solution, I decided to take it to the technical service, who flashed it in EDL mode with the UFT box.
The cell phone is walking and without any anomaly.
Thank you all for your valuable help.
dbaesteban said:
Well, after many days of searching without solution, I decided to take it to the technical service, who flashed it in EDL mode with the UFT box.
The cell phone is walking and without any anomaly.
Thank you all for your valuable help.
Click to expand...
Click to collapse
is there any way other than UFT box to unbrick the phone mine have working EDL, fastboot , offical recovery but relock bootloader ..:crying:
I am having the exact issue in attempt to update the rom through fastboot. My tucana is no more responding to charging, pwr + Vol combination, detection to laptop etc. I have tried making my own EDL cable and its working with K20 but not with Tucana. Can you please brief how you managed to get phone into EDL mode?
Related
First, let me apologize for the rough guide I'm going to deliver I'll clean this up in due time.
1.) Let's get some files downloaded. So here is a guide by @deadman96385 that details Qfil and the actual process of flashing.
2.) Let's incorporate that into my guide
* You'll choose the programmer from my TWRP folder
* You'll choose the rawprogram0.xml from my TWRP folder
3.) Time to flash....just press Download there's nothing else to do.
4.) Boot into recovery...do I need to explain how?
* Warning* Do not flash Magisk requires a separate boot.img I haven't made it just yet.
So with all this, what is the next step in the process for custom rom installs? Waiting on mine in the mail so I can begin looking into everything as well, sadly I picked the att variant so it looks like things will be more difficult for me.
good work @Unjustified Dev And @deadman96385
ff7cloudsnobody said:
So with all this, what is the next step in the process for custom rom installs? Waiting on mine in the mail so I can begin looking into everything as well, sadly I picked the att variant so it looks like things will be more difficult for me.
Click to expand...
Click to collapse
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
Unjustified Dev said:
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
Click to expand...
Click to collapse
From what I've been reading up on, it had looked like the AT&T variant was more difficult to get through than the others. I could be wrong though. But thanks for this breakthrough!
ff7cloudsnobody said:
From what I've been reading up on, it had looked like the AT&T variant was more difficult to get through than the others. I could be wrong though. But thanks for this breakthrough!
Click to expand...
Click to collapse
I don't know about the other variants. Each firmware is signed so I can't test their Roms, but I used their updated 8.1 proprietary files to build Lineage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my G8142 using Tapatalk
Unjustified Dev said:
I don't know about the other variants. Each firmware is signed so I can't test their Roms, but I used their updated 8.1 proprietary files to build Lineage.
Click to expand...
Click to collapse
Does going the old "data wipe then flash boot img without encryption" not work anymore? If so then my bad, been a while since I've worked with a phone that is locked down with signed firmware. Was looking into doing that right now.
Edit: And I don't mean via flashboot because first boot should cause it to resign
AT&T
Unjustified Dev said:
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
Click to expand...
Click to collapse
Hello!
Thank you for the first ray of light Please, can you answer some questions?
1) As far as I know, AT&T version of Z999 has locked bootloader. Have you tried this TWRP with AT&T Z999 (not T-mob, China or Russian)?
2) As far as I know, AT&T version of Z999 has non-standard EDL mode and until now there was only one tool capable of flashing it, "Uni-Android Tool" for $49. The usual QFIL doesn't see 9008 COM-port on this phone. So, how does your TWRP gets flashed? Or is the included "firehose" an already patched one for AT&T Z999?
3) If all of these works, can root be (some day) obtained with locked bootloader?
I live in a country with GSM 900\1800, UMTS 2100 & LTE B3 & B20, so right now my Z999 is useless as a mobile device & works only as a small tablet. The root is totally necessary for me to unlock additional bands & I have faith in You
Thanks once again,
WBR - Draco.
Drakosha said:
Hello!
Thank you for the first ray of light Please, can you answer some questions?
1) As far as I know, AT&T version of Z999 has locked bootloader. Have you tried this TWRP with AT&T Z999 (not T-mob, China or Russian)?
2) As far as I know, AT&T version of Z999 has non-standard EDL mode and until now there was only one tool capable of flashing it, "Uni-Android Tool" for $49. The usual QFIL doesn't see 9008 COM-port on this phone. So, how does your TWRP gets flashed? Or is the included "firehose" an already patched one for AT&T Z999?
3) If all of these works, can root be (some day) obtained with locked bootloader?
I live in a country with GSM 900\1800, UMTS 2100 & LTE B3 & B20, so right now my Z999 is useless as a mobile device & works only as a small tablet. The root is totally necessary for me to unlock additional bands & I have faith in You
Thanks once again,
WBR - Draco.
Click to expand...
Click to collapse
1.) I have the att variant
2.) The all have edl mode I sniffed the firehose from uniandroid and had a friend reconstruct it to get it working. And the usual qfil does see the phone. You're more than likely in dfu mode and not edl. Uniandroid can send the phone from dfu to edl. You can adb reboot to edl to get in 9008. The issue was the programmer was incorrect.
3.) Root can probably be obtained I just had no interest. I'll look into it later if I have time. Also I'm not sure if you can unlock more bands never looked into that before.
Sent from my G8142 using Tapatalk
Great!
Unjustified Dev said:
1.) I have the att variant
2.) The all have edl mode I sniffed the firehose from uniandroid and had a friend reconstruct it to get it working. And the usual qfil does see the phone. You're more than likely in dfu mode and not edl. Uniandroid can send the phone from dfu to edl. You can adb reboot to edl to get in 9008. The issue was the programmer was incorrect.
3.) Root can probably be obtained I just had no interest. I'll look into it later if I have time. Also I'm not sure if you can unlock more bands never looked into that before.
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Thanks for the answers! Wonderful news, the ability to flash AT&T phone with QFill changes everything. As for the bands, I've seen a lot of articles on how to unlock Qualcomm phones with NV editor, and had success with several Nexus-es & LG's. Let's hope that after (if...) root is obtained, one of the methods works. It will literally breath the new life into this phone & will make it useful everywhere in the world.
WBR, Draco.
Just an FYI, only running this didn't work for me, I changed the img to recovery.img and used the firehose with the stock files, I edited the boot though to remove secure boot.
Root
Unjustified Dev said:
* Warning* Do not flash Magisk requires a separate boot.img I haven't made it just yet.
Click to expand...
Click to collapse
Hello!
Any news on root or, perhaps, some ROM like Lineage?
WBR, Draco.
Any News?
So I tried flashing my bricked Axon M with the provided firehose file, and using provided B37 firmware, but I keep getting an error associated with "userdata.img is 0 bytes!" and if I delete the file, I then get an error stating "userdata.img could not be found!" any ideas?
ehsan96696 said:
So I tried flashing my bricked Axon M with the provided firehose file, and using provided B37 firmware, but I keep getting an error associated with "userdata.img is 0 bytes!" and if I delete the file, I then get an error stating "userdata.img could not be found!" any ideas?
Click to expand...
Click to collapse
Edit rawprogram0.xml where it says userdata.img edit it to be "" basically telling qfil don't flash it. Alternatively use miflash
Sent from my G8142 using Tapatalk
Unjustified Dev said:
Edit rawprogram0.xml where it says userdata.img edit it to be "" basically telling qfil don't flash it. Alternatively use miflash
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Thanks, I did get past that error, but now it is stuck at https://imgur.com/YzyzPNP
ehsan96696 said:
Thanks, I did get past that error, but now it is stuck at
Click to expand...
Click to collapse
Use miflash
Sent from my G8142 using Tapatalk
Unjustified Dev said:
Use miflash
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
How? Whenever I pick the folder with the firmware it just sais "couldn't find flash script"
rawprogram0.xml
ehsan96696 said:
How? Whenever I pick the folder with the firmware it just sais "couldn't find flash script"
Click to expand...
Click to collapse
Here, just use the attached rawprogram0.xml (AT&T B37) with QFil
Drakosha said:
Here, just use the attached rawprogram0.xml (AT&T B37) with QFil
Click to expand...
Click to collapse
Tried as specified and it gets stuck here: https://imgur.com/xMynQ3h
ehsan96696 said:
Tried as specified and it gets stuck here: https://imgur.com/xMynQ3h
Click to expand...
Click to collapse
Do you have spaces in your username? Put firehose programmer file inside the firmware folder, and put the whole folder in C:\Z999 (without any spaces or long filenames). Run Qfil as admin. And never flash phones from DESKTOP...
As title.
Thanks.
gords78 said:
As title.
Thanks.
Click to expand...
Click to collapse
Hope this link helps
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Good luck!
orb3000 said:
Hope this link helps
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Good luck!
Click to expand...
Click to collapse
Thanks, my device is a Redmi 6 with locked bootloader and I'm pretty sure there are no workarounds.
gords78 said:
Thanks, my device is a Redmi 6 with locked bootloader and I'm pretty sure there are no workarounds.
Click to expand...
Click to collapse
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Prodai said:
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Click to expand...
Click to collapse
Thanks. This is my exact situation too. Bought as global version on eBay but after locking the bootloader found out its Chinese. Was going to give the firehose method a go tonight but read id still need an authorised account. Will give it a go.
Solved to a certain degree. My handset doesn't support EDL as its a Mediatek chipset.
Prodai said:
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Click to expand...
Click to collapse
I've bricked my poco f3. samen issue. tried Qfil an QPST. no luck. did you use a stock rom?
Try w
Prodai said:
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Click to expand...
Click to collapse
Prodai said:
I've bricked my friend's redmi note 7 about a month ago and encountered the same issue as I flashed miui global rom into a chinese version via miflash tool with option 'flash all and lock'. She said she bought the device not from an official mi store but instead from a distributor which I think had flashed some modified chinese rom to appear as global one. So the device was in locked bootloader state, and after turning it on it always boots up into mi recovery. After done so many hours researching on the internet about how to bypass this lock bootloader and flash the right version of firmware in edl mode without authorized account, I've successfully unbrick the phone after flashing the firmware with a patched firehose file for redmi note 7. Try it mate. Hope it helps u. Cheers.
Click to expand...
Click to collapse
Try what, will please explain what you just suggested to try?
i have a redmi 5 rosy hard brick but i can enter edl without problem by using test point , flash stock rom and it worrking again
Guan Yu said:
i have a redmi 5 rosy hard brick but i can enter edl without problem by using test point , flash stock rom and it worrking again
Click to expand...
Click to collapse
Will you please share how you flashed?
Because with the MiFlash, you need Mi authorised account (about which I don't know how get one), so which tool you used?
True ayush Kushwaha said:
Will you please share how you flashed?
Because with the MiFlash, you need Mi authorised account (about which I don't know how get one), so which tool you used?
Click to expand...
Click to collapse
well you just need to check if your devices entered edl or not . you can check in device manager and make sure it named " Qualcoom Qloader 9008 " , then download stock firmware and click flashall.bat , dont use miflash
True ayush Kushwaha said:
Try w
Try what, will please explain what you just suggested to try?
Click to expand...
Click to collapse
Try flashing the right version firmware with a patched firehose file in EDL mode. You won't need authorized account anymore using these file. I was using the latest miflash tool at that time. So just give it a try first mate, hope it works for you too.
aaflan88 said:
I've bricked my poco f3. samen issue. tried Qfil an QPST. no luck. did you use a stock rom?
Click to expand...
Click to collapse
Yes i did. Qfil and QPST didn't work for me either as it still asked for an authorized account. So after researching more I found the solution; just flash the stock rom with a patched firehose file in edl mode. The latest miflash tool will do, and it won't ask for an authorized account anymore.
Guan Yu said:
i have a redmi 5 rosy hard brick but i can enter edl without problem by using test point , flash stock rom and it worrking again
Click to expand...
Click to collapse
How do you use the "test point" to access this mode. The truthful answer will allow me to fix my Note8, S6 edge, and my 1+.
Please explain
Delgoth said:
How do you use the "test point" to access this mode. The truthful answer will allow me to fix my Note8, S6 edge, and my 1+.
Please explain
Click to expand...
Click to collapse
search youtube usb edl cable or "your device name " + test point , make sure your device is recognized as Qloader 9008 not Diagnostics 900E then flash stock rom using miflash or cmd
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guan Yu said:
search youtube usb edl cable or "your device name " + test point , make sure your device is recognized as Qloader 9008 not Diagnostics 900E then flash stock rom using miflash or cmdView attachment 5556141
Click to expand...
Click to collapse
I kinda know that part already. I've dealt with 9008 and 9006 mode before on multiple devices.
But when you use a test point what equipment are you using outside just a USB cable?
Delgoth said:
I kinda know that part already. I've dealt with 9008 and 9006 mode before on multiple devices.
But when you use a test point what equipment are you using outside just a USB cable?
Click to expand...
Click to collapse
i use this lol (no joking i dont have a tweezers and i dont want to buy a new usb cable )
Prodai said:
Try flashing the right version firmware with a patched firehose file in EDL mode. You won't need authorized account anymore using these file. I was using the latest miflash tool at that time. So just give it a try first mate, hope it works for you too.
Click to expand...
Click to collapse
Thank you very much, but please tell me where I can get the patched files?
Have a xiaomi mi 11 lite 5g ne I just need an authorized mi account for flashing the edl firehose and I’m set I have no idea about how to become authorized or what to do to even find the information to gain authorization so I’m stuck. Does anyone have the information to help me become authorized or is someone authorized who can help
edl authorized for qualcomm.my device is redmi 7 onclite
thanks
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded
wouldnt there be a way through twrp or brom mode?
tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
Nope you can try brom mode but i dont trust if works
If you buy a samsung device depending of the device (like this A12 and the MTK imei bug) is not a good idea to upgrade
tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help
I tryed to downgrade via TWRP flashing baseband and BL
Now my A12 is DEAD and i dont had a box to repair it (after flash i see the security error screen and flashed again the Binary 3 BL once odin tell me passed the phone doesn't booted again)
I just wanted to get the imei working because the firmware on the binary 3 (11 and 12) android system uses all my ram memory trying to get the signal working
F*** *** Samsung and mediatek next time i bought an exynos or qualcomm variant
tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
The last rom that i used on my A12 was pixel experience and worked perfectly on binary 3 android 11 based firmare (A125MUBUS3BVF1) just installed TWRP with nulled vbmeta flashed the image as system (not as super) and wiped the data (not advanced wipe) rebooted and the gsi was booted (only bugs mentionated on the thread and the touch bug)
Allehandro said:
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help
Click to expand...
Click to collapse
i can access brom mode if that helps
tekkitheidiot said:
i can access brom mode if that helps
Click to expand...
Click to collapse
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.
Allehandro said:
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.
Click to expand...
Click to collapse
i downgraded to the earliest binary 3, then used test points. worked perfectly
tekkitheidiot said:
i downgraded to the earliest binary 3, then used test points. worked perfectly
Click to expand...
Click to collapse
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
its relatively easy tbh. just be careful around the volume buttons, but everything else is okay. there arent too many cables to rip
Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
Its easy to open but be careful with the power/fingerprint sensor flex i think the testpoint is near of the charger flex in the mainboard (i see youtube tutorials to access to Brom mode and preloader)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.
LAST_krypton said:
Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.
Click to expand...
Click to collapse
where would i find this scattar firmware?
tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working
MauriJ2001 said:
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working
Click to expand...
Click to collapse
ill look through it. thanks
tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
You generate it your self
To unlock bootloader on these the easiest way is to convert it to an a125w xac by flashing the a125w bl files. Unlock bootloader with seccfg. Then flash ap, cp, and csc from a125w with odin and when it boots up it should show as a125w. Also in download mode it shows the same. My imei says unknown but i believe thats caused by unlocking bootloader so if you relock it after converting it should go back to normal. Playing with mtk modem tool to rewrite imei. Tried using xposed imei changer but didnt seem effective.
Hey!
I just bought a Xiaomi Redmi Note 11 Pro+ 5G. As it is a chinese phone, the seller flashed the global ROM himself and sent it to me. It was generally working, except for NFC and the blurry camera. I figured the NFC wasn't working because the device was unlocked before, and so this long journey began. I tried to lock the bootloader again, and the phone shot down immediately, then it started boot looping. All I can get to is the recovery (which displays the "this miui version can't be installed on this device" message) and fastboot pages. I've tried unlocking it again, flashing a clean stock ROM, bypassing the lock, and it all came to nothing.
It seems that MediaTek devices are hard to fiddle with. This phone has a Dimensity 900 (MT6877). I've tried tools like:
Xiaomi Official Unlock Tool (no success) as it won't let me unlock the phone.
Xiaomi Official Flashing Tool (no success) as it won't flash a lock phone.
MTK Flash Tool (no success) as it won't accept my ROM's scatter file. It says the file is invalid.
SP Flash Tool (no success) as it won't accept my ROM's scatter file. It says the version is not supported/the file is invalid.
MTK Client (no success) as I can't make it work at all. Setuptools module is missing for some ****ing reason.
MTK Bypass Utility Master (no success) as the "usb" module is missing. I don't know what to do.
Honestly, this is all my fault. Both for bricking the phone and for doing something wrong while trying the methods above. Please enlighten me. Is there any way to recover this phone? It's OEM Locked. I need a tool that bypasses the mediatek stuff or something (with a detailed guide with ALL needed requirements to install, if possible).
"MTK Bypass Utility Master (no success) as the "usb" module is missing"
try installing some drivers, such as:
-mtk driver
-vcom
-xiaomi usb driver
-libusb-win
and maybe u could study these step from redmi 6A:
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com
Hey there. So...
I'm trying out your guide, but I'm already stuck. Sorry for that. When I try to add the scatter file (from the stock ROM), I keep getting the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The same happens with other flash tools. MTK Flash Tool tells me the file is invalid, while SP tells me it's not supported. Any tips?
You should never lock the bootloader on a chinese xiaomi phone with global rom
Howerr said:
Hey there. So...
I'm trying out your guide, but I'm already stuck. Sorry for that. When I try to add the scatter file (from the stock ROM), I keep getting the following error:
View attachment 5772747
The same happens with other flash tools. MTK Flash Tool tells me the file is invalid, while SP tells me it's not supported. Any tips?
Click to expand...
Click to collapse
thats right, check in case your device still locked.
if it does locked, try to unlock it first.
also, you could try using another scatter files (from different spflash or else).
Hi Howerr,
Afaik, our device is definetly a qualcomm device + not an mtk device. try it out, this will help you, or you typed the wrong device model. VEUX has a qualcomm chip.
Hi I have a Redmi Note 11 Pro+ updated to MIUI 13.0.5.0. global. Can I use the Recovery Stock to go back to MIUI 12.0.5.0? thank you
Good evening. Guys could this work to unlock the MEDIA TEK processor?
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
Tajil said:
"MTK Bypass Utility Master (no success) as the "usb" module is missing"
try installing some drivers, such as:
-mtk driver
-vcom
-xiaomi usb driver
-libusb-win
and maybe u could study these step from redmi 6A:
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com
Click to expand...
Click to collapse
Hello. I have the same PISSARRO Global ROM device. Mediatek. Can I flash with Miflash? Risk of blocking the device? Thank you
Michael P. said:
You should never lock the bootloader on a chinese xiaomi phone with global rom
Click to expand...
Click to collapse
Can you do it the other way around though? Global phone flashing China ROM ? Thank you!
darkguy2008 said:
Can you do it the other way around though? Global phone flashing China ROM ? Thank you!
Click to expand...
Click to collapse
You can flash any rom on global phone, but don't lock the bootloader. Also nfc might not work in China rom.
Michael P. said:
You can flash any rom on global phone, but don't lock the bootloader. Also nfc might not work in China rom.
Click to expand...
Click to collapse
I see, thanks for your answer, so basically there's no way to have the MIUI Dialer on the 12T with Global ROM MIUI 13 right? Only way is to use the China ROM except not blocking the bootloader. What happens if I lock it? Will it get bricked?
darkguy2008 said:
I see, thanks for your answer, so basically there's no way to have the MIUI Dialer on the 12T with Global ROM MIUI 13 right? Only way is to use the China ROM except not blocking the bootloader. What happens if I lock it? Will it get bricked?
Click to expand...
Click to collapse
If you lock bootloader your phone will get bricked. But you can use miui Indonesian version if you want miui dialer. I use miui Indonesian for my redmi note 11 pro 5g without any issue.
apollo_81 said:
Hello. I have the same PISSARRO Global ROM device. Mediatek. Can I flash with Miflash? Risk of blocking the device? Thank you
Click to expand...
Click to collapse
sorry, I am not yet using miflash
Michael P. said:
If you lock bootloader your phone will get bricked. But you can use miui Indonesian version if you want miui dialer. I use miui Indonesian for my redmi note 11 pro 5g without any issue.
Click to expand...
Click to collapse
Hi Michael, I would like to buy a redmi note 11 pro 5g in Europe and then install indonesian firmware. Can I lock the bootloader after firmware upgrade? Can I then use Google Pay and NFC for payments?
Phone: Redmi Note 11 Pro (IMEI search shows model number 21091116C sticker that came with phone shows model number 21091116SG not sure if this matters)
I have accidently patched and written the wrong boot.img to my phone after poorly attempting to setup Magisk to get google pay working on this phone
Am now stuck with the phone either booting to recovery window or I Can enter fastboot
Device bootloader is locked and i do not have a Xiaomi account linked to phone, trying to flash what i believe is ROM using MiFlash tools but fails since bootloader is locked, attempted to unlock using mediatek unlocker tools and cant manage to get this to work either
Feels like there's nothing i have not tried at this point have 20 chrome tabs open, downloaded so many different ROMs and followed heaps of different methods without any success
Edit: Account had not been linked to phone yet
Apologies if this is not posted in the correct format/section believe its right from the rules
Any help would be really apprechiated
I would think MiFlash should still work on a locked BL from EDL. What specific error do you get on MIFlash?
@orangekid thanks for the reply
Tested with multiple Global and CN roms "error:FAILED (remote: not allowed in locked state)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you in fastboot or EDL?
just reflash the original unpatched boot.img in fastboot.
I have currently the problem that im stuck in poco boot logo, when I flash patched-boot.img. reflashing unpatched boot.img makes it boot again.
orangekid said:
Are you in fastboot or EDL?
Click to expand...
Click to collapse
Fastboot with the orange "FASTBOOT" display
seedlord said:
just reflash the original unpatched boot.img in fastboot.
I have currently the problem that im stuck in poco boot logo, when I flash patched-boot.img. reflashing unpatched boot.img makes it boot again.
Click to expand...
Click to collapse
I tried flashing heaps of different stock ROM boot.img's but must not be able to find the original not sure, believe its a CN phone that had a Global ROM installed when i brought it but could be wrong
Connor.- said:
Fastboot with the orange "FASTBOOT" display
Click to expand...
Click to collapse
Ok you might need to get the phone in EDL mode. If you cannot do it thru fastboot (I think newer phones might not be able to) you might have to remove the back cover and use tweezers to do it thru test point (google or youtube test point EDL for your phone).
Then once in true EDL you can try flashing again with the tool. If you still cannot due to no authorization or locked BL or whatever, you might need to extract the stock image and use a patched firehose file to trick MIFlash tool.
I can try to look but it looks like these guys have a collection as well over here:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
I know this is a lot but my thing is in the future if you are going to modify your phone like kernel patching or anything of the sort you need to unlock your BL first. Just trying to point you in any direction that can resurrect your device.
Believe me I have been in weird situations, such as last year when I somehow flashed a bad file on my OnePlus 9 and the ONLY solution was to literally flash an Indian OnePlus 9 Pro (different device, different region) ROM on my phone from EDL, so my point is there's almost always something you can do unless you want to say screw it and send it in for repair.
I would remove the back of the phone and leave it off, because whatever you're going to do might require test point EDL until you actually get something to flash and boot. At this point I guess it can't really get any worse.
orangekid said:
Ok you might need to get the phone in EDL mode. If you cannot do it thru fastboot (I think newer phones might not be able to) you might have to remove the back cover and use tweezers to do it thru test point (google or youtube test point EDL for your phone).
Then once in true EDL you can try flashing again with the tool. If you still cannot due to no authorization or locked BL or whatever, you might need to extract the stock image and use a patched firehose file to trick MIFlash tool.
I can try to look but it looks like these guys have a collection as well over here:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
I know this is a lot but my thing is in the future if you are going to modify your phone like kernel patching or anything of the sort you need to unlock your BL first. Just trying to point you in any direction that can resurrect your device.
Believe me I have been in weird situations, such as last year when I somehow flashed a bad file on my OnePlus 9 and the ONLY solution was to literally flash an Indian OnePlus 9 Pro (different device, different region) ROM on my phone from EDL, so my point is there's almost always something you can do unless you want to say screw it and send it in for repair.
I would remove the back of the phone and leave it off, because whatever you're going to do might require test point EDL until you actually get something to flash and boot. At this point I guess it can't really get any worse.
Click to expand...
Click to collapse
Thanks for this, i believe its a Mediatek processor not qualcomm unfortunately but EDL pins dont look too hard to access was suprised to see how easy it is to remove the glass back. I'm in talk with the store i purchased it from at the moment so will see how this goes before falling back to pulling the phone apart (only recieved it last Friday )
Realistaclly i am happy with MIUI it works fine for me only intention was to bypass safetynet with magisk so i can use it for contact payments everything else I had already setup just how i like it
Also I would try this maybe?
My experience unbricking a Xiaomi Redmi Note 11 Pro 5G (China) - Hovatek Blog
The Xiaomi Redmi Note 11 Pro (China) is an Android 11 device powered by the MediaTek Dimensity 920 chipset. In
www.hovatek.com
Also you can try this:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
Tou should never try to flash anything on a phone with lovked bootloader. Even if you had patched the correct boot.img you would have ended with a brick because your bootloader is locked.
Michael P. said:
Tou should never try to flash anything on a phone with lovked bootloader. Even if you had patched the correct boot.img you would have ended with a brick because your bootloader is locked.
Click to expand...
Click to collapse
well it wasnt locked when i first tried