Hello,
i post my very first request on XDA because i have a serious problem.
My Xiaomi mi A3 doesn't boot.
I bought it one year ago and he didn't receive any update since the August 2020 patch. So today i decided to flash the last stable stock rom.
First i unlocked the bootloader and then i flashed "laurel_sprout_global_images_V12.0.&3.0RFQMIXM_20210810" version,
but when it reboot, it was stuck on the android one logo.
After that i decided to cancel everything to not take any more risk and i flash a previous version which is "Xiaomi_Mi_A3_V10.3.4.0.PFQMIXM_20190815.0000.00_Global_9.0_XFT".
I'm on linux so i executed "flash_lock.sh", i thought that it means "flash the rom, and then lock bootloader" but i don't know what it means precisely. So i used that, and when it finished the flash, the phone turn off and since this moment it doesn't want to boot, and even if a do the fastboot access combinaison, nothing boot.
This is my daily phone and I really need help ....
Thank you
I don't think you can do much seeing as you locked the bootloader.
When performing such tasks it is recommended to keep the bootloader unlocked in case anything goes wrong you can flash other ROMs in fastboot.
But because you locked the bootloader fastboot is pretty much useless now.
The only thing you could probably try is booting to EDL mode and flashing stock ROM with mi flash on a Windows computer.
The device is essentially hard bricked without access to fastboot but you should still be able to boot to EDL mode.
Maybe this will work, it's certainly worth a try
garylawwd said:
I don't think you can do much seeing as you locked the bootloader.
When performing such tasks it is recommended to keep the bootloader unlocked in case anything goes wrong you can flash other ROMs in fastboot.
But because you locked the bootloader fastboot is pretty much useless now.
The only thing you could probably try is booting to EDL mode and flashing stock ROM with mi flash on a Windows computer.
The device is essentially hard bricked without access to fastboot but you should still be able to boot to EDL mode.
Maybe this will work, it's certainly worth a try
Click to expand...
Click to collapse
Thank you very much for your answer. I will try the EDL mod and give updates.
garylawwd said:
I don't think you can do much seeing as you locked the bootloader.
When performing such tasks it is recommended to keep the bootloader unlocked in case anything goes wrong you can flash other ROMs in fastboot.
But because you locked the bootloader fastboot is pretty much useless now.
The only thing you could probably try is booting to EDL mode and flashing stock ROM with mi flash on a Windows computer.
The device is essentially hard bricked without access to fastboot but you should still be able to boot to EDL mode.
Maybe this will work, it's certainly worth a try
Click to expand...
Click to collapse
It works, with EDL. thank you very much for advising me on this method.
And now it even receives updates from XIaomi.
I used this guide:
https://c.mi.com/thread-3527044-1-0.html
Related
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Did u try doing factory reset from boot menu
Sent from my MB855 using xda app-developers app
Yes i did try that along with every other option given system still not booting up... but another strange thing ive noticed is that the android recovery is now letting me choose what zip i want to install from my sd card although i cannot because everything keeps failing the signature check. Has anyone been in this same situation?
I think i flashed the ap20bl.img with sv1 but i havnt flashed the microboot because i didnt know what command to issue in fastboot mode. for the bootloader i typed something along the lines of "fastboot flash rdl3.bin rdl3_unlocked.smg" then i think it restarted to only the moto logo was there and i typed fastboot devices it showed my phone so i took the cg file from derpunlock and typed a command like fastboot flash boot cg42_000somthing.smg it said ok finished... ???
sunny530 said:
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Click to expand...
Click to collapse
are you saying you're on 2.3.5? if you are, your bootloader is permanently locked. it won't do any good to try and unlock it, unless you don't mind bricking. otherwise i have never seen this error before.
if you are on 2.3.5 i'd recommend flashing the electrify 2.3.5 sbf method to hopefully unbrick and return to stock.
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
sunny530 said:
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
Click to expand...
Click to collapse
with 2.3.5 you aren't unlocking anything. can almost guarantee it! it's going to take a miracle! i'd say just restore it with the SBF if possible and continue on with life haha. i rooted like a year ago so i don't remember anything about it at this point haha. the only thing that was important was unlocking the bootloader! we need a breakthrough on that for these locked users. that miracle hasn't happened yet. or even gotten close.
Try flashing signed boot.img. This seems to me like failed to boot 2 in other words.
You can flash almost anything into the phone, the signature is checked after reboot, so "flashing ok" in fastboot is normal feedback, sometimes even if it's not ok (radio).
Also with recovery, you can choose whatever zip you want, but when you hit install, signature is checked.
Well you see i receive no failure to boot 1-4 i just get stuck at the moto dual core screen with nothing written at the top. Is it possible that i flashed the bootloader sucsessfully and did not flash the microboot? i didnt know the command to issue to flash microboot. The unrecoverable bootloader error seems interesting to me how would i find out what kernal i should/can flash and what would be the command would it be in fastboot? can i install a system.img via recovery or install bootstrap through fastboot or stock recovery?
I've recently unlocked my bootloader and I wanted to re lock it. Well, I couldn't find any thread about this and I thought it would be good to open one. My question is obviously how to re lock the bootloader in Xiaomi Redmi Note 3 Snapdragon.
Xristomania said:
I've recently unlocked my bootloader and I wanted to re lock it. Well, I couldn't find any thread about this and I thought it would be good to open one. My question is obviously how to re lock the bootloader in Xiaomi Redmi Note 3 Snapdragon.
Click to expand...
Click to collapse
simply flash any official fastboot ROM using miflash.
sanjib734 said:
simply flash any official fastboot ROM using miflash.
Click to expand...
Click to collapse
With edl right?
sanjib734 said:
simply flash any official fastboot ROM using miflash.
Click to expand...
Click to collapse
Did it with the EDL and now i got hard brick. Now I am stuck at mi logo not even bootlooping and i can access fastboot mode but have no permision to do anything in there and cant flash from recovery. Any solution about this?
Xristomania said:
Did it with the EDL and now i got hard brick. Now I am stuck at mi logo not even bootlooping and i can access fastboot mode but have no permision to do anything in there and cant flash from recovery. Any solution about this?
Click to expand...
Click to collapse
Did you use unofficial bootloader unlock? If you did, you're really really f***ed right now. The only way to fix this is to physically open the device, unscrew the motherboard, plug in the usb and use a metal object to connect the two "testpoints", which will force the phone into edl mode.
justinxfan said:
Did you use unofficial bootloader unlock? If you did, you're really really f***ed right now. The only way to fix this is to physically open the device, unscrew the motherboard, plug in the usb and use a metal object to connect the two "testpoints", which will force the phone into edl mode.
Click to expand...
Click to collapse
I know about the testpoint but thank god i did wait for the unlock aproval.
Xristomania said:
I know about the testpoint but thank god i did wait for the unlock aproval.
Click to expand...
Click to collapse
In that case of official unlock, guess you can take to service center and get it repaired?
For unofficial unlock, there is simple way to lock bootloader by putting back original "emmc_appsboot.mbn" from fastboot rom.
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
Xristomania said:
I know about the testpoint but thank god i did wait for the unlock aproval.
Click to expand...
Click to collapse
You used official unlocked and the phone still bricked?
mGforCe said:
In that case of official unlock, guess you can take to service center and get it repaired?
For unofficial unlock, there is simple way to lock bootloader by putting back original "emmc_appsboot.mbn" from fastboot rom.
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
Click to expand...
Click to collapse
Greece doesn't have a service center for xiaomi phones. Yeap, this sucks.
justinxfan said:
You used official unlocked and the phone still bricked?
Click to expand...
Click to collapse
Yep, still bricked. Hard Bricked. I have used tespoint again but it was actually hard to trigger it because it caused phone to restart normally instead of going to edl.
When I tried to EDL Flash my phone normally when i had access to android, I got and max memory something problem in Mi Flash and when i tried again it sent a hello package to my phone and then it said catastrophic failure. So, don't know what that actually means and I hope not what it actually says. However i still have access to fastboot mode and recovery mode but i found out that I actually have locked bootloader after flashing this "emmc_appsboot.mbn" and had the phone alive in chinese dev rom and then i wanted to roll back to global stable via edl and got brick. Sadly I do not have access to this test mode where you test your phone's sensors, display and more.
Xristomania said:
When I tried to EDL Flash my phone normally when i had access to android, I got and max memory something problem in Mi Flash and when i tried again it sent a hello package to my phone and then it said catastrophic failure. So, don't know what that actually means and I hope not what it actually says. However i still have access to fastboot mode and recovery mode but i found out that I actually have locked bootloader after flashing this "emmc_appsboot.mbn" and had the phone alive in chinese dev rom and then i wanted to roll back to global stable via edl and got brick. Sadly I do not have access to this test mode where you test your phone's sensors, display and more.
Click to expand...
Click to collapse
Hey, you can go into EDL mode?
If yes, why don't you flash the Fastboot ROM - Global one if you don't want CHinese one
Refer this post for basic steps.
http://forum.xda-developers.com/showpost.php?p=66962198&postcount=7
mGforCe said:
Hey, you can go into EDL mode?
If yes, why don't you flash the Fastboot ROM - Global one if you don't want CHinese one
Refer this post for basic steps.
http://forum.xda-developers.com/showpost.php?p=66962198&postcount=7
Click to expand...
Click to collapse
I might can with the testpoint method. Although I can not boot into android.
Xristomania said:
I might can with the testpoint method. Although I can not boot into android.
Click to expand...
Click to collapse
Suggest trying @Rajdip's thread here
http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
EDL
mGforCe said:
Suggest trying @Rajdip's thread here
http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
Click to expand...
Click to collapse
Just got into edl mode with testpoint and flashed successfully global firm. I'll charge it fully and the find out if it actually works.
Xristomania said:
Just got into edl mode with testpoint and flashed successfully global firm. I'll charge it fully and the find out if it actually works.
Click to expand...
Click to collapse
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
mGforCe said:
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
Click to expand...
Click to collapse
Actually it is not that difficult but it is extremely tricky since if you press only the left one test point it will just reboot. You need to touch them at the same time. Although you'll need to be accommodated with electronics since they are sensitive.
mGforCe said:
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
Click to expand...
Click to collapse
Weirdly enough, it shows battery sign when charging but button do not seem to respond for a weird reason. I'll check cables.
Oh god yes
Xristomania said:
Weirdly enough, it shows battery sign when charging but button do not seem to respond for a weird reason. I'll check cables.
Click to expand...
Click to collapse
I had a little heart attack because I thought That i had cut the Button Cable during the flash process but THANK GOD it was right underneath the motherboard and IT NOW WORKS. YES I AM IN MIUI GLOBAL. THANK GOD. Just for you to know, every failed bootloader unlock on any smartphone is equal to several heart attacks.
Can anyone please guide me how unlock bootloader unofficially, I am on latest miui global beta??
There are so many threads on how to unlock bootloader. And almost always someone complaining breaking their phone with said method, mostly the said person's fault. There's really no need now to unlock bootloader to flash custom ROMs, etc. The only disadvantage being you cannot flash in fastboot which isn't really a disadvantage as you can just use TWRP. Everything works fine even with locked bootloader.
Here: https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
The one I followed is the experimental updated method. You only need to download a 20 MB file. It literally just took me 10 min. after opening the box to get out of MIUI.
bloodytolits said:
There are so many threads on how to unlock bootloader. And almost always someone complaining breaking their phone with said method, mostly the said person's fault. There's really no need now to unlock bootloader to flash custom ROMs, etc. The only disadvantage being you cannot flash in fastboot which isn't really a disadvantage as you can just use TWRP. Everything works fine even with locked bootloader.
Here: https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
The one I followed is the experimental updated method. You only need to download a 20 MB file. It literally just took me 10 min. after opening the box to get out of MIUI.
Click to expand...
Click to collapse
I don't know why but if i boot into edl mode it is not recognised in mi flash tool. Please help!!
Ashish Banka said:
I don't know why but if i boot into edl mode it is not recognised in mi flash tool. Please help!!
Click to expand...
Click to collapse
Download Mi flash suite. You probably haven't installed drivers yet.
bloodytolits said:
Download Mi flash suite. You probably haven't installed drivers yet.
Click to expand...
Click to collapse
I have installed mi pc suite but i cant see qualcomm drivers in device manager
Ashish Banka said:
I have installed mi pc suite but i cant see qualcomm drivers in device manager
Click to expand...
Click to collapse
Sorry don't about that. Never had problems with that.
I used the Mi PC Suite on this thread: https://forum.xda-developers.com/redmi-note-3/how-to/redmi-note3-prokenzo-guiderom-global-t3341102
If drivers still isn't installed, try Mi Unlock. I think Mi Unlock also installs drivers.
bloodytolits said:
There are so many threads on how to unlock bootloader. And almost always someone complaining breaking their phone with said method, mostly the said person's fault. There's really no need now to unlock bootloader to flash custom ROMs, etc. The only disadvantage being you cannot flash in fastboot which isn't really a disadvantage as you can just use TWRP. Everything works fine even with locked bootloader.
Here: https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
The one I followed is the experimental updated method. You only need to download a 20 MB file. It literally just took me 10 min. after opening the box to get out of MIUI.
Click to expand...
Click to collapse
Thnx.. it worked after using a different cable..
Hi everyone, first of all, thanks for reading and trying to help out.
I have a 1+7t Pro Indian unit. I unlocked the Bootloader on my device and installed Magisk but as I saw that there were not much benefits of rooting at the moment since twrp is not also available yet so no flashing of custom roms.
So I tried to relock the Bootloader. For that I Flashed the stock rom from scratch so that no modifications stay in the system and then tried "fastboot oem lock". This however got me into a bricked stage where I got following error:
"Your device is currept. It can not be trusted and will not boot."
This comes with a red exclamation mark and nothing happens means it gets bricked. I also tried "fastboot flashing lock". That did not work either. I did unbrick it without any issue but I want to relock the Bootloader just in case I need to sell the device.
Has anyone faced the same problem or could help me out here?
Any help much appreciated and thanks in advance!!
Chandler_Bing_1995 said:
Hi everyone, first of all, thanks for reading and trying to help out.
I have a 1+7t Pro Indian unit. I unlocked the Bootloader on my device and installed Magisk but as I saw that there were not much benefits of rooting at the moment since twrp is not also available yet so no flashing of custom roms.
So I tried to relock the Bootloader. For that I Flashed the stock rom from scratch so that no modifications stay in the system and then tried "fastboot oem lock". This however got me into a bricked stage where I got following error:
"Your device is currept. It can not be trusted and will not boot."
This comes with a red exclamation mark and nothing happens means it gets bricked. I also tried "fastboot flashing lock". That did not work either. I did unbrick it without any issue but I want to relock the Bootloader just in case I need to sell the device.
Has anyone faced the same problem or could help me out here?
Any help much appreciated and thanks in advance!!
Click to expand...
Click to collapse
Same here when I was trying to lock bootloader of my 7T (non pro) yesterday. I figured out a solution. Simply download unbrick tool, connect device in Qualcomm EDL mode and flash proper firmware (choose between india and O2 (which mean global) firmware. After restoring firmware with MSM tool your device bootloader will be locked again.
EugenStanis said:
Same here when I was trying to lock bootloader of my 7T (non pro) yesterday. I figured out a solution. Simply download unbrick tool, connect device in Qualcomm EDL mode and flash proper firmware (choose between india and O2 (which mean global) firmware. After restoring firmware with MSM tool your device bootloader will be locked again.
Click to expand...
Click to collapse
Thanks a lot, will try that.
Chandler_Bing_1995 said:
Thanks a lot, will try that.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261684661
I have tried for multiple hours to get fastboot and ADB to work with my S6 Edge but it is not working. I suspect I might need to try older Samsung drivers (I only tried the latest ones as far as I remember). I wanted these tools in order to check if my bootloader was unlocked so that I wouldn't brick my device if I tried to install a custom ROM and TWRP. Anyway I followed a video and installed TWRP on my phone and installed Lineage OS Android 10 without checking the bootloader since the guy in the video did not mention doing so and still installed the custom ROM and TWRP. It is working fine. I know it is most likely that since this was possible, the bootloader should probably be unlocked but I just wanted to confirm with more experienced smartphone modders if this is indeed the case. Is it then safe to root my phone without checking bootloader?
Sub-question: If a person were to theoretically attmept to install custom ROM or TWRP or root the phone while the bootloader is locked, would that result in the root failing but the device still being usable or would the attempt result in the device being bricked? IE if the bootloader is locked is it dangerous to attempt to flash software to the phone or will it result in a harmless "failed" message, etc.?
Thank you.