After trying to lock my bootloader is got a message : "your phone is corrupted and cannot be trusted" error.
Now i can't do anything, i cant go in recovery nothing just stuck in this screen!
Is there a fix for this, the pc recognises the phone as in fastboot mode!
many thanks
Do a RAW flash. Should get you back fairly easily. EDL as a last rsort. You won't be able to do much more as long as you're stuck in CSC mode which is related to your now locked bootloader.
Andrologic said:
Do a RAW flash. Should get you back fairly easily. EDL as a last rsort. You won't be able to do much more as long as you're stuck in CSC mode which is related to your now locked bootloader.
Click to expand...
Click to collapse
I have done couple of things, now i can enter the recovery menu again!
but now my phone is telling me this :
Phone status : locked
Auth status locked
something like in the attached picture
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.
Hello everyone
My brother's Mi A2 is bricked for no reason. I tried to solve this problem and searched a lot but didn't manage to solve it. I hope you can help.
* before telling my story here is some stuff to know:
- The phone was running official firmware and bootloader is locked, I've never played with it's software before.
- Oem unlocking option isn't turned on.
- The phone doesn't go to recovery mode, only fastboot or regular boot.
- I used EDL mode in every flashing attempt.
- I don't remember that there is a mi account assigned to the device.
* Here is what happened:
- The phone suddenly shut down during a call and never passed the AndroidOne logo after that.
- Tried EDL mode and miflash to flash the latest firmware. Flashing completed successfully but the phone still stuck on the androidone logo.
- Did it again and again but the result was constant.
- Tried flashing older firmware "Oreo 8.1" but during flashing system.img the process stopped with an error. (I don't remeber what the error was).
- I tried to turn on the phone but after showing AndroidOne logo This message appeared:
"Your device is corrupt. It can't be trusted and will not boot.
Visit this link on another device: g.co/ABH"
and the device shuts down in a minute.
Hint: Sometimes when I try to turn one the phone the above message appears after androidone logo and sometimes the device just keep showing the logo.
- Trying to flash any firmware version by using Miflash Beta gives an error message "Can not found programmer file" immediately. when I try again it gives: "can't read from port COM4", Changing the port gives the same error with different port number.
-When I use any other version of "Portable miflash", The flashing process starts normally but fails when trying to flash "dsp.img", giving an error of "writing time out".
- I tried reinstalling all drivers needed with no change at all.
I hope that you guys can help me solving this problem.
Thank you so much!
Try EDL mode opening your phone...
Badotti said:
Try EDL mode opening your phone...
Click to expand...
Click to collapse
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Ahmed A. Mohsen said:
I did.
Bootloader is locked, so EDL mode was the only way. But now I get error writing timed out while flashing any firmware version.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Badotti said:
https://www.youtube.com/watch?v=wav1xNdJzII
Youtube you find several tutorials, work and open the phone ...
Click to expand...
Click to collapse
I opened the phone and used edl mode already but the problem is still present.
up
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
HTCDevil said:
Have you tried to use qfil? See in the 3d dedicated to conversion A2 <> 6x
Click to expand...
Click to collapse
This needs bootloader to be unlocked and my device's bootloader is locked.
Any solutions?
Go to service center this is last option you save RIP mi a2 ?
As I can see from picture you have posted, your bootloader is unlocked.
SkullSatan88 said:
Go to service center this is last option you save RIP mi a2
Click to expand...
Click to collapse
They refused to receive my device because I bought it from another country.
bomil said:
As I can see from picture you have posted, your bootloader is unlocked.
Click to expand...
Click to collapse
when I checked bootloader status in the beginning it was locked.
Are you sure that it's now unlocked?
Text me on telegram. @dejavutr
(french) hello
I could not start in edl mode with the xda instructions but I found a videos
phone on android, connected to the computer by usb. you keep pressing the power button and the volume down button.
when the screen goes black immediately you strafe the volume + button for 2 sec.
the secret is the windows song if the phone is on. when you hear windows song strafe the volume +. i know I did it with my phone off and my phone on quite a few times
normally your computer will recognize the phone in the correct mode. if there is a problem do not forget to install these drivers and restart the computer as it will stay in edl mode and will be well supported.
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
that's funny visibbly before you unlock or reflash the original bootloader the phone don't have fastboot mode with me. but fastboot don't work well in windows. it work erfectly on linux ubuntu with me at exemple.
thanks for your attention
yeah, it is very easy
So this is how you go into fastboot ?
I have the V405 EBW & I am unable to go to fastboot to get the device ID.
Doush_504 said:
So this is how you go into fastboot ?
I have the V405 EBW & I am unable to go to fastboot to get the device ID.
Click to expand...
Click to collapse
no no we should not confuse.
there is download mode in originale lg phone for flash stock roms
there is "edl mode" for unlock bootloader
there is fastboot mode when you unlock the bootloader with this screen.
a tips. root first your phone. 2 backup your firmware. 3 flash twrp. i had problem because i don't do this. there is stock firmware already rooted. its easily.
bsteph27 said:
no no we should not confuse.
there is download mode in originale lg phone for flash stock roms
there is "edl mode" for unlock bootloader
there is fastboot mode when you unlock the bootloader with this screen.
a tips. root first your phone. 2 backup your firmware. 3 flash twrp. i had problem because i don't do this. there is stock firmware already rooted. its easily.
Click to expand...
Click to collapse
Unfortunately, I am unable to root because I am unable to unlock the bootloader (because I can't go to fastboot to get Device ID & send it to LG)
Doush_504 said:
Unfortunately, I am unable to root because I am unable to unlock the bootloader (because I can't go to fastboot to get Device ID & send it to LG)
Click to expand...
Click to collapse
But you can get to fastboot, just not the way you read on the internet.
The device doesn't have fastboot available, until, you put it in edl mode and use qfil to flash the 'engineering' abl. That's what gives you fastboot.
You could, at that point, use fastboot to get the info for unlock.bin. But why? because at that point you can just type 'fastboot oem unlock', and it's unlocked.
AsItLies said:
But you can get to fastboot, just not the way you read on the internet.
The device doesn't have fastboot available, until, you put it in edl mode and use qfil to flash the 'engineering' abl. That's what gives you fastboot.
You could, at that point, use fastboot to get the info for unlock.bin. But why? because at that point you can just type 'fastboot oem unlock', and it's unlocked.
Click to expand...
Click to collapse
beware to put your phone in android oreo before the unlock...... i forget this detail. and i try to unbrick my phone with testpoint. maybe i do a howto if i succes to fix my phone.
AsItLies said:
But you can get to fastboot, just not the way you read on the internet.
The device doesn't have fastboot available, until, you put it in edl mode and use qfil to flash the 'engineering' abl. That's what gives you fastboot.
You could, at that point, use fastboot to get the info for unlock.bin. But why? because at that point you can just type 'fastboot oem unlock', and it's unlocked.
Click to expand...
Click to collapse
Oh OK
I'll have to read more about that.
Thank you
bsteph27 said:
beware to put your phone in android oreo before the unlock...... i forget this detail. and i try to unbrick my phone with testpoint. maybe i do a howto if i succes to fix my phone.
Click to expand...
Click to collapse
Unlock only works with Oreo ??
I have Pie
How do I downgrade without root ?
Is it possible ?
If I can flash a firmware without root
I'd be more than happy to flash a custom rom which has LG's apps instead of Google annoying ones.
Doush_504 said:
Unlock only works with Oreo ??
I have Pie
How do I downgrade without root ?
Is it possible ?
Click to expand...
Click to collapse
you are like me your phone is "bricked". your phone don't have download mode, fastboot mode. maybe you have
edl mode 9008. but often you have to open your phone for put it in edl mode.​wait my howto i hope fix mine today or tomorow and i wil do an howto to unbrick lg v40. is not very hard to solve it but it must a howto.
Hi everyone,
I locked my asus rog 3 bootloader with the command "Fastboot oem asus-lock"
after restarting the phone it gave me "your phone is corrupted and cannot be trusted" error.
then I rried to inter recovery mode to do a format but the phone enters CSC Fastboot mode and stuck in it!
Please help me solve this issue.
Darkness191 said:
Hi everyone,
I locked my asus rog 3 bootloader with the command "Fastboot oem asus-lock"
after restarting the phone it gave me "your phone is corrupted and cannot be trusted" error.
then I rried to inter recovery mode to do a format but the phone enters CSC Fastboot mode and stuck in it!
Please help me solve this issue.
Click to expand...
Click to collapse
Use EDL mode to flash a clean firmware - you can find all you need on the forums here. You can also try and flash a clean boot img only first using QFIL and see if that resolves it depending on which ROM you're on.
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
protatocrisp said:
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
Click to expand...
Click to collapse
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
AsItLies said:
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
Click to expand...
Click to collapse
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
protatocrisp said:
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
Click to expand...
Click to collapse
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
AsItLies said:
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
Click to expand...
Click to collapse
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
protatocrisp said:
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
Click to expand...
Click to collapse
well if there's a lesson here it's that it's exceptionally important to pay attention to exactly what you're doing. Double check everything; that you're flashing the correct files, that you back up the correct files and name them appropriately, read directions over and over to be sure u understand.
it sounds like if you keep going back to fastboot when trying to start system, then you're probably re-flashing the engineering abl and not the original abl, which yer suppose to save off first.
yeah, maybe start over again by flashing a stock rom.