Database Users

Phone stuck in boot loop (bootloader locked)

So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!

Galrash said:
So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!
Click to expand...
Click to collapse
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?

Heisenberg said:
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?
Click to expand...
Click to collapse
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store

Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
I'm not entirely sure how it works but I believe you'll need to contact Best Buy. Even so it should be covered by warranty.

Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
In my experience, Best Buy will not honor manufacturer warranties on smartphones; So unless you bought their Geek Squad coverage, they will tell you to contact Huawei for a warranty RMA.
Contact Info for Warranty RMA:
Huawei Device USA
1-888-548-2934 (1-888-5HUAWEI)

Got ahold of Huawei and it was surprisingly easy and fast. They emailed me a shipping label I just have to drop my phone in the mail and send it to them and it will be covered under warranty. Luckily I have my old Nexus 6 to use until they get it back to me

Moto G4 - Stuck in Bootloader

EDIT: I know a way of getting out of the bootloader but it requires me to unlock it (even though I left it unlocked after initially doing it). Unfortunately, though, I think I'm left with a £150 paperweight since I need an OS on the device to enable OEM unlocking and the device literally has no OS or recovery after the hard brick. Motorola have been very "supportive" about my situation even after sending them a 10 paragraph email explaining everything which obviously, they didn't read because I wrote on the first line that the device has been rooted so they knew beforehand. I wrote 10 paragraphs, they replied with six lines, so... Yeah.
I installed LineageOS 14 on my Moto G4 months ago with TWRP and I've never had any issues until today. Literally, just updated to a new nightly build for LineageOS and my phone screen went black and didn't turn back on. I plugged it into my computer and it showed up as QHSUSB_BULK. Obviously, at this point, my device was hard bricked but I found a way online of using Qualcomm's recovery thing they have to get my phone working again, which I did. But now, I've sorta ended up soft bricking the device now.
The device boots up into the bootloader (or what I think is the bootloader). What comes up is just white text at the bottom which basically just tells me information about my phone (product/variant, serial number, CPU, eMMC, DRAM etc.) The menu for the bootloader is just one string of text that only reads 'Start' and when I press the volume buttons, it will show up with more options but they're all highlighted in red and they all lead to the same error message, as follows:
Bootloader logs
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer
to repair your device.
Connect your device to your computer to get
the Software Repair Assistant.​
I've looked around Google for the Software Repair Assistant and it appears to only be for Verizon Wireless and since I'm in the United Kingdom, Verizon Wireless doesn't even exist over here, nor do I even have them as my phone carrier. I'm with O2.
Also, I've tried a few things with Minimal ADB and Fastboot but every time I enter a command, it fails and say's 'FAILED (remote failure). My phone is detected in Fastboot, but not in ADB.
Hopefully, I can get this fixed.
Thanks,
Gabriel.

Guys, i am having the same issue too. I am getting the same issue. Since verizon is not available in india, unable to repair the phone since soft bricked. Kindly help.

did you try to enter fastboot>recovery and get the robot? if you can get that try holding the the power key and tap the up volume. that should give you a drop list with a factory reset option. click it and see what happens?

same problem here.

my phone is rescued.
llaalways said:
same problem here.
Click to expand...
Click to collapse

[HELP] Can't unbrick my mi a1

Hi everyone. Yesterday, I flashed Mi5X rom on my mi a1 and now it's stuck on boot page saying "The system has been destroyed. Press power button to shutdown. I can still enter into fastboot mode but my bootloader got locked itself ( it was unlocked before). I tried unlocking boot loader using "fastboot oem unlock" command but i got error
"FAILED (remote: Token verification failed, reboot the device)". I also tried to flash stock rom using mi flash tool but again but flashing completes in 0 seconds. When using another rom file i got error: "error Mismatching image and device". i tried another rom but it also got flashed in 0 seconds. So if anyone knows something then please share with me. It will be a great help to me. Also tell me if i did something wrong in the way. Thanks.

Why would you flash Mi5X ROM on Mi A1? Guess you cant get into the recovery or can you? What do you get if you type fastboot devices?

TrueMS said:
Why would you flash Mi5X ROM on Mi A1? Guess you cant get into the recovery or can you? What do you get if you type fastboot devices?
Click to expand...
Click to collapse
First of all I thought that both devices are similar so I flashed Mi5X rom on my mi a1. I can't get into recovery mode. And fastboot devices command recognizes my mi a1 . I have no problem in getting my mi a1 into fastboot mode and connecting it to my PC.

Expermint said:
First of all I thought that both devices are similar so I flashed Mi5X rom on my mi a1. I can't get into recovery mode. And fastboot devices command recognizes my mi a1 . I have no problem in getting my mi a1 into fastboot mode and connecting it to my PC.
Click to expand...
Click to collapse
Thats interesting... what about getting in EDL mode? There you can flash stock ROM. In EDL mode you dont have to unlock bootloader to flash.

Try to use EDL mode, there is a guide here
https://forum.xda-developers.com/showpost.php?p=76347021&postcount=2
Dont ever to flash Mi5x rom again, the hardware is similar but not the same, we MiA1 use A/B partitions.

The reason the fastboot OEM unlock command no longer works may be that you flashed an MIUI ROM onto your phone and that command isn't how you unlock the bootloader on MIUI. My understanding is that you need to request unlock permission on the Xiaomi website and after you get verification that it's been approved you use their unlock tool to unlock the bootloader. If you manage to get the bootloader unlocked then you can hopefully use the MI Flash tool to restore your phone to stock.

like someone said already use EDL mode.. https://www.youtube.com/watch?v=70hYUCjAsCM
and if you have updated miui EDL could be blocked here is miui forum post about it http://en.miui.com/thread-1680467-16-1.html
best of luck.
edit : I revived father's redmi1a once using testpoint.. nasty but works out ok, if you have a PC , cable and drivers needed..
earlier MI allowed use of EDL cables but with new miui they removed this functionality from bootloading

Since you can get into fastboot, try the following command to go into EDL:
fastboot oem edl

MiA1 is a **** low tier phone. Big mistake if you buy it!

udaan said:
MiA1 is a **** low tier phone. Big mistake if you buy it!
Click to expand...
Click to collapse
It's a good cheap phone for people who can't afford a flagship. It's also priced at what it's worth. New OnePlus & Pixel phones cost much more than they are actually worth based on build quality and resale value after 1 year. You can easily buy a refurbished or used Pixel XL ($1000 list) for $200. I paid $800 (including sales tax, shipping and insurance) for a new OnePlus 5 and got $270 when I sold it 8 months later and threw in over $100 in accessories. Buying an expensive flagship phone that loses most of its value within a year is the big mistake.

jhs39 said:
It's a good cheap phone for people who can't afford a flagship. It's also priced at what it's worth. New OnePlus & Pixel phones cost much more than they are actually worth based on build quality and resale value after 1 year. You can easily buy a refurbished or used Pixel XL ($1000 list) for $200. I paid $800 (including sales tax, shipping and insurance) for a new OnePlus 5 and got $270 when I sold it 8 months later and threw in over $100 in accessories. Buying an expensive flagship phone that loses most of its value within a year is the big mistake.
Click to expand...
Click to collapse
So go head and help OP. I'm sure your wonderful phone can survive. lol

udaan said:
So go head and help OP. I'm sure your wonderful phone can survive. lol
Click to expand...
Click to collapse
The number one rule for any phone is don't flash stuff if you don't know what you're doing. If you flash an incompatible ROM on any phone you're going to brick it. That kind of user error can't be blamed on the MI A1.

jhs39 said:
The number one rule for any phone is don't flash stuff if you don't know what you're doing. If you flash an incompatible ROM on any phone you're going to brick it. That kind of user error can't be blamed on the MI A1.
Click to expand...
Click to collapse
This I completely agree with. I have a similar problem with Mi A1 but I flashed the Official fastboot ROM and now it's bricked. Here is the full detail:
Hey, I have a question for you since google can't help me with it, trust me, I tried.
I have a Mi A1 device and after I flashed the latest Oreo update (official) on it, it went into a coma (bricked but not dead), i.e. the phone kept vibrating every 1 second when it's connected to PC or when I push the power button. Can't get to fastboot or recovery, screen doesn't turn on and no charging screen when connected to power.
So I had to open up the back cover and did the "two point short" trick to force boot it to EDL mode, where I was able to flash the factory (earlier) fastboot image (Nougat) through Miflasher program.
After that I was able to boot to fastboot, and its default recovery. But the problem remains, I cannot boot to the system itself. When I press the power button it shows the splash screen and says "The system has been destroyed". I can go to fastboot with volume down + power button combo. I tried to flash the same fastboot rom through fastboot as well, I got the same result.
I also flashed the official and unofficial TWRPs on it, it boots into them as well. I also tried to flash other custom ROMs in it through those TWRPs, following every step clearly, where they say that after flashing the ROM TWRP needs to be flashed again. I did all that. But the problem remains, after the flash and reboot it always shows me that "The system has been destroyed" message and the phone has to be shut down (because it asks you to power it off on that message.)
And ofc the phone is unlocked. Although it is easy for it to be locked and unlocked through fastboot anyway.
So I am basically stuck now. Do you know a way forward? Is there a cure for it? Or my last option is to take it to service center when I know for sure that they are going to ask me to change the motherboard. This device was bought in Hong Kong so the warranty card is useless here.
Thanks for reading.
And I also made a thread about it, needs to be updated with this.

Mi A1 stuck at MI logo page

Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.

What error show miflash when you try to flash in edl mode?

balannaer said:
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
Click to expand...
Click to collapse
take your sd card off your phone i had similar issues and fixed them that way

ccalixtro said:
What error show miflash when you try to flash in edl mode?
Click to expand...
Click to collapse
it depends on which version of the flash tool is used. the beta version of the flash tool claims that it is successful, but the phone will not load to the Android OS after that is completed and it still will not load into the recovery mode to attempt to factory reset or anything else.
other versions have given errors:
miflash 2017.7.20.0 gives the response after attempting for about 10 seconds of "ACK count don't match!"
miflash 2018.11.15.0 gives the error response of "cannot receive hello packet"
and as stated before the miflash beta goes through the complete flash process with the result stating a "success" response, but the phone will not load to OS, just remains stuck on the MI logo screen when the phone is booting up
i have some screen grabs of all this but i am not yet worthy through XDA to be permitted to share them
thanks for the reply

kuartito said:
take your sd card off your phone i had similar issues and fixed them that way
Click to expand...
Click to collapse
i dismantled the phone manually bro, when you use EDL mode this way the SIM/SD tray is removed you then remove the entire backplate and then disconnect the battery cable from the circuit board and you use the test point method to short two pins that force the system to start in EDL mode when you connect the usb-C cable, so unfortunately that is not the issue :crying:
it never seems to be the simple solutions
Thanks for the reply!

Still dead in the water on this one.
Going to look into getting a replacement, that is a disappointing end to the Xiaomi experience

Facing similar issue. Am able to flash however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.

Help!!!!!! Boot image destroyed pls read this::::

Hii!! I have a realme 2 pro rmx1801. I was on real.e ui v1.0. I somehow managed to unlock the bootloader by fastboot. Then i tried to flash twrp recovery. My phone was stucking on the white realme logo and was again automatically booting normally into system. I tried to flash recovery 10-11 times but the same thing happening. Then i searched for it and found a guy who was saying that after flashing recovery, I will have to flash a file named " boot+patched+magisk". Then i did the same but found that my phone now niether was able to boot into recovery nor into system. It was just showing white realme logo, then turned off again, again tried to start and again turned off... the process repeated again and again until i booted it into fastboot. I got afraid and thought that after relocking bootloader it would return to normal but when i locked it again it just showed---- " the current boot image (boot/recovery) has been destroyed and can not boot." I took it to a local repair shop as there is no official realme service centere in my city. He said it would take 3 days to repair it, he told that he will have to download files. I left it there and then the third day called him. He said that he tried to flash but he was not able to repair it. He also told that the phone booted up one time upto the home screen but again reached to the same boot image destroyed message automaticall. I told him that i want my phone repaired and he asked for 2 more days. I allowed. It is about 21 days and he is saying the same thing again and again. Is my phone dead? He is saying that the chances of my phone get reapaired are very low. He said i have also tried ufi but no success. Is he lying? I have not seen my phone from about 21 days, as it is covid-19 spread. We are only talking on phone. Pls tell that can my phone be reapired?
Edit: I bring my phone back from him today. He said that he was not able to repair it. When i gave the device to him it was turning on upto realme and then showing boot image destroyed. But now it is not even turning on. What should i do now. Is this a mistake of mine or he is responsible?

Have you locked Bootloader?
If yes then probably you must flash using flash tool.
(Which may work or not)
If you haven't locked Bootloader then easily flash stock recovery,then flash stock rom
For guide go to YouTube then search your title
The current boot recovery destroyed and cannot boot.

androport said:
Have you locked Bootloader?
If yes then probably you must flash using flash tool.
(Which may work or not)
If you haven't locked Bootloader then easily flash stock recovery,then flash stock rom
For guide go to YouTube then search your title
The current boot recovery destroyed and cannot boot.
Click to expand...
Click to collapse
My bootloader is locked. But i thing ufi should work as it directly flashes emmc of device.

Kartikkala said:
My bootloader is locked. But i thing ufi should work as it directly flashes emmc of device.
Click to expand...
Click to collapse
Will msm work? the guy which is repairing my phone is telling that the device turned on for some time but it went to the same condition automatically again. I am thinking is this even possible? Well i tried connecting it to msm and it showed up there on msm as com4 and in devices as qualcomm hs qdloader.

How did you unlock bootloader ?? Can you help me with that please ?? a
Kartikkala said:
Hii!! I have a realme 2 pro rmx1801. I was on real.e ui v1.0. I somehow managed to unlock the bootloader by fastboot. Then i tried to flash twrp recovery. My phone was stucking on the white realme logo and was again automatically booting normally into system. I tried to flash recovery 10-11 times but the same thing happening. Then i searched for it and found a guy who was saying that after flashing recovery, I will have to flash a file named " boot+patched+magisk". Then i did the same but found that my phone now niether was able to boot into recovery nor into system. It was just showing white realme logo, then turned off again, again tried to start and again turned off... the process repeated again and again until i booted it into fastboot. I got afraid and thought that after relocking bootloader it would return to normal but when i locked it again it just showed---- " the current boot image (boot/recovery) has been destroyed and can not boot." I took it to a local repair shop as there is no official realme service centere in my city. He said it would take 3 days to repair it, he told that he will have to download files. I left it there and then the third day called him. He said that he tried to flash but he was not able to repair it. He also told that the phone booted up one time upto the home screen but again reached to the same boot image destroyed message automaticall. I told him that i want my phone repaired and he asked for 2 more days. I allowed. It is about 21 days and he is saying the same thing again and again. Is my phone dead? He is saying that the chances of my phone get reapaired are very low. He said i have also tried ufi but no success. Is he lying? I have not seen my phone from about 21 days, as it is covid-19 spread. We are only talking on phone. Pls tell that can my phone be reapired?
Edit: I bring my phone back from him today. He said that he was not able to repair it. When i gave the device to him it was turning on upto realme and then showing boot image destroyed. But now it is not even turning on. What should i do now. Is this a mistake of mine or he is responsible?
Click to expand...
Click to collapse
I am running realme ui v1 f.11.. In depth test app is not working.help me please..

Samanto70 said:
I am running realme ui v1 f.11.. In depth test app is not working.help me please..
Click to expand...
Click to collapse
Go in below thread and check #2 post
https://forum.xda-developers.com/realme-2-pro/help/bootloader-unlock-problem-t4167125
I already posted how to unlock bootloader on realme ui

Samanto70 said:
I am running realme ui v1 f.11.. In depth test app is not working.help me please..
Click to expand...
Click to collapse
Doesn't work on realme ui

Samanto70 said:
I am running realme ui v1 f.11.. In depth test app is not working.help me please..
Click to expand...
Click to collapse
You are lucky. Dont try to unlock ur boot loader forcefully. Or you will perish too. You can unlock it but any custom recovery is not yet launched for realme ui. If u want to still unlock it, download bugjaegar app form playstore on another device, turn on usb debug on ur realme 2 pro and the another device too , connect ur device and open bugjaegar app on ur other device, it will ask for allowing bugjaegar to debug via usb. Allow it, a prompt will pop up on ur realme 2 pro. Allow it. If u are not asked, click on reboot bootloader on bugjaegar app, definitely the prompt will pop up on your realme 2 pro. Click allow and u are good to go. Make sure that u turn on oem unlock too.