Hi everyone, some weeks ago I converted my A2 in 6X because I wanted to test MIUI. Yesterday, dealing with an update my phone get into a bootloop. Well, I used MiFlash to fix it but I selected "flash and lock" (yes, I know, I'm stupid).
The main thing is that I'm in a Chinese ROM with lock bootloader and when I try to unlock it I get error 86023.
I dont know what to do. I've thought about test point to flash Xiaomi.eu but I'm not sure bcause the bootloader is locked.
Someone with a posibble solution? Thanks
Welcome to the Club
Same thing happened to me.
You can now choose between China Developer or Stable.
I tried many progs and tutorials to unlock the bootloader but no way.
If you need GooglePlayStore, CalenderSync and ContactsSync:
https://androidfilehost.com/?fid=818070582850489460
I'm now on stable V10.3.6.0.PDCCNXM and all is working quite well.
rafamb281 said:
Hi everyone, some weeks ago I converted my A2 in 6X because I wanted to test MIUI. Yesterday, dealing with an update my phone get into a bootloop. Well, I used MiFlash to fix it but I selected "flash and lock" (yes, I know, I'm stupid).
The main thing is that I'm in a Chinese ROM with lock bootloader and when I try to unlock it I get error 86023.
I dont know what to do. I've thought about test point to flash Xiaomi.eu but I'm not sure bcause the bootloader is locked.
Someone with a posibble solution? Thanks
Click to expand...
Click to collapse
It didn't happened to me for myself, but I just asked this question to get better knowledge about bootloader stuffs:
As I understood the current problem is this:
You need to unlock your bootloader again, there is just (as much as I know) 2 ways to approach, which both of them will not help you:
1. Unlocking as a A2 : but your device is not a A2 anymore, so the device will not be unlocked by this method.
2. Unlocking as a 6x : but this one won't be successful either since the dedicated unlocking program asks for a real 6X device with a registered IMEI number by factory, which in your case is NOT.
So, you will be left just with the options that need no Unlocked Bootloader, as mentioned above, like Chinese Stable versions. ( That in my opinion it does NOT sound awful. )
(BTW, every day comes with new procedures, maybe you can find a new method to unlocked the bootloader again, there was times that many expertise told, after stucking in ARB4 trap, you just need to find a suitable Trash for your device!, but now we all know that there is plenty new ways to deal with it).
sz.hatef said:
It didn't happened to me for myself, but I just asked this question to get better knowledge about bootloader stuffs:
As I understood the current problem is this:
You need to unlock your bootloader again, there is just (as much as I know) 2 ways to approach, which both of them will not help you:
1. Unlocking as a A2 : but your device is not a A2 anymore, so the device will not be unlocked by this method.
2. Unlocking as a 6x : but this one won't be successful either since the dedicated unlocking program asks for a real 6X device with a registered IMEI number by factory, which in your case is NOT.
So, you will be left just with the options that need no Unlocked Bootloader, as mentioned above, like Chinese Stable versions. ( That in my opinion it does NOT sound awful. )
(BTW, every day comes with new procedures, maybe you can find a new method to unlocked the bootloader again, there was times that many expertise told, after stucking in ARB4 trap, you just need to find a suitable Trash for your device!, but now we all know that there is plenty new ways to deal with it).
Click to expand...
Click to collapse
not the imei, it asks for 6x serial number which device is a2. you have to find someone who has authorized mi account to unlock this device. it is only way for now
q0kHaN said:
not the imei, it asks for 6x serial number which device is a2. you have to find someone who has authorized mi account to unlock this device. it is only way for now
Click to expand...
Click to collapse
And how I can find someone with one?
rafamb281 said:
And how I can find someone with one?
Click to expand...
Click to collapse
Authorized Customer Services, or a friend who works there
It is very possible that they can restore your phone (and as well your bootloader) as what it was in factory.
sz.hatef said:
Authorized Customer Services, or a friend who works there
It is very possible that they can restore your phone (and as well your bootloader) as what it was in factory.
Click to expand...
Click to collapse
R u talking about contact with Xiaomi? Or another service?
I tried it here http://unlock-unbrick.com/, but they also couldnt help me.
rafamb281 said:
R u talking about contact with Xiaomi? Or another service?
Click to expand...
Click to collapse
Yes, exactly.
Hello my friends, i managed to unlock the bootloader of my converted A2/6X.
I tried several times to switch from stable china to developer china but from 9.8.15 to 9.9.3 no one worked.
After installing one of the developer roms, the phone only shows the boot screen for 2 seconds and turns off, with charger it boots endlessly or shows the green battery symbol after some minutes.
One thing that works, is using a rubber band to fix "Vol+" and connect phone via usb or charger, mostly after 5-10 minutes it will enter the "Miui-Recovery", then you can start "Mi-Assistent" in the "Miui-Recovery" and flash back the stable china, so luckily no need of EDL.
After flashing the last 9.9.3 rom and the phone was all screwed up, again. I tried the original "miflash_unlock-en-2.2.624.14" and it worked.
I have done this "thousand" times before with all available unlock tools I found but never succeeded before.
Download: miflash_unlock-en-2.2.624.14
https://xiaomifirmware.com/downloads/download-mi-unlock-2-2-624-14-windows/
https://androidfilehost.com/?fid=889764386195916630
Now I tried to boot into recovery “fastboot boot twrp_wayne.img” but it didn't work, because the phone reboots or turns off after 2 seconds.
So I flashed the china stable via fastboot (worked), let it boot up, no setup, reboot to enter fastboot and flashed successful the orangefox-twrp.
Hope somebody can also unlock his bootloader or maybe it was just luck.
puxxi2004 said:
Hello my friends, i managed to unlock the bootloader of my converted A2/6X.
I tried several times to switch from stable china to developer china but from 9.8.15 to 9.9.3 no one worked.
After installing one of the developer roms, the phone only shows the boot screen for 2 seconds and turns off, with charger it boots endlessly or shows the green battery symbol after some minutes.
One thing that works, is using a rubber band to fix "Vol+" and connect phone via usb or charger, mostly after 5-10 minutes it will enter the "Miui-Recovery", then you can start "Mi-Assistent" in the "Miui-Recovery" and flash back the stable china, so luckily no need of EDL.
After flashing the last 9.9.3 rom and the phone was all screwed up, again. I tried the original "miflash_unlock-en-2.2.624.14" and it worked.
I have done this "thousand" times before with all available unlock tools I found but never succeeded before.
Download: miflash_unlock-en-2.2.624.14
https://xiaomifirmware.com/downloads/download-mi-unlock-2-2-624-14-windows/
https://androidfilehost.com/?fid=889764386195916630
Now I tried to boot into recovery “fastboot boot twrp_wayne.img” but it didn't work, because the phone reboots or turns off after 2 seconds.
So I flashed the china stable via fastboot (worked), let it boot up, no setup, reboot to enter fastboot and flashed successful the orangefox-twrp.
Hope somebody can also unlock his bootloader or maybe it was just luck.
Click to expand...
Click to collapse
Amazing Dude. [emoji108][emoji108][emoji108][emoji108][emoji108] Congratulations.
So as the title says I have managed to put my lovely XQ-AT52 into a lovely boot loop of hell.
It all started because I read on XDA that you could install the AT51 software on the AT52 to get VOLTE and other features working. So I downloaded the the AT51 software, connected a good quality USB C to USB A cable and put the phone into flash mode. Installed the software with Newflasher. No errors and the phone rebooted. The initial Sony logo flashed up but after aprox 2 seconds the screen goes blank and then the Sony logo shows up again. It will do this 3 times and the it will go straight into fast boot mode. Notification led goes red and then stays solid blue. I can put the phone back into flash mode by holding the power key until the light goes out the then pressing the volume down key.
I tried re-flashing the correct factory AT52 software (in fact I tried all available AT52 software) but the phone still does the exact same boot loop.
At no point does Newflasher report any issues or faults.
I have tried a different USB cable just in case but no luck. Phone is also above 80% battery.
Does anyone have any suggestions?
Many thanks in advance, Ben
Also I should clarify that I wanted the AT51 software because over here Telstra VOLTE will work on AT51 but not AT52 and I wanted to see if it was just a software difference that caused it to work.
Well I managed to fix it. The Xperia companion application managed to recover it.
FYI the boot loop was caused from the enable OEM unlock option not being selected in developer settings. I have never encountered this issue before but the last phone I owned was a xz2 and I guess things have changed since then.
To all those interested the XQ-AT51 software didn't allow the volte to work on Telstra network but it did allow the RCS messaging to function.
The OEM unlock option is defaulted to off. Should only be enabled if you're going to unlock the bootloader. Did you use newflasher or flashtool to flash? Did you opt for a full wipe or keep user data? If you opted to keep user data, you'll obviously bootloop if you flash from one variant to another.
iArvee said:
The OEM unlock option is defaulted to off. Should only be enabled if you're going to unlock the bootloader. Did you use newflasher or flashtool to flash? Did you opt for a full wipe or keep user data? If you opted to keep user data, you'll obviously bootloop if you flash from one variant to another.
Click to expand...
Click to collapse
Flashed with Newflasher mate. It was a full wipe, I wouldn't dream of trying to keep user data from one to another. That would be a big headache. I have tried to flash 3 times now without the OEM unlock switch on and each time it just boot loops. I think it does something more then just allows bootloader unlocking.
Cheers, Ben.
Hey thanks for this information I'm going to add this to my post as on my model oddly enough I didn't have to have OEM unlock enabled under development settings. I will make sure this is added to my post.
So I messed up with trying to get my phone to global rom without unlocking the bootloader.
A little backstory: I have an 1062 which had an android 8.1, I didn't have my bootloader unlocked.
So I've tried to make my phone Global by using this method https://forum.xda-developers.com/no...-to-convert-nokia-7-china-variant-to-t3769541 . I think it was done successfully and my phone instatly asked me to update to the newer android, so I did it. It was a 1.4 gb update and after it was done I was welcomed by a default android settings screen which asked me to log in to my google account. So I tried and found out that my touch doesn't work at all. I can see the animation that says Welcome and I my phone reacts to Volume up\down and power buttons, but no reaction to my fingers whatsoever. I've tried wiping in the recovery mode, it didn't help.
I can't even find out my imei or get my Rom version.
Is there anything that can help? I'm obviously willing to get my bootloader unlocked if I can get my Imei and rom vers.
I was using the Sony conpanion app to update my phone when we had a power cut mid update.
Now the phone refuses to boot, only message I get is "your device is corrupt and cannot be trusted and cannot boot"
It then restarts after 5 seconds and is now stuck in this constant loop.
The Sony companion app is now useless as even though it can detect the phone it can't repair it. It throws up and error about it not liking the model oh my phone for some reason.
Thinking my phone might be 100% dead I installed Sony's flashing tool Emma, and thanfully it can detect the phone and thinks it is a XQ-AT51 since I flashed UK/EU androind 11 on it before.
I am really not sure how I can even try and fix this phone, I can't flash it because OEM unlocking was not enabled along with USB-Debugging, (why when its a normal update) and I can't get the recovery menu to show up at all anymore.
If anyone has any idea on how I may salvage this id like to know since most if not all guides I find are out of date or require me to be able to enable OEM unlocking or boot into the phone in the first place. If all else fails I am just tempted to buy a used phone with a broken screen from Ebay and just swap out the mainboard...I looses 12GB ram to 8GB but its better than having a brick.
Currently playing 12.13GSI, so seeing your post is too slow, follow the steps below to restore the original factory!
1. https://forum.xda-developers.com/t/tool-xperifirm-xperia-firmware-downloader-v5-6-5.2834142/
Follow the guide~
2. https://forum.xda-developers.com/t/tool-newflasher-xperia-command-line-flasher.3619426/page-83
Follow the guide~
Hope all is well with your phone!
Hello,
I remember that when i last time unlocked bootloader on my Nokia 8 phone, on every phone restart there was an obnoxious splashscreen telling that "this device is unlocked, unsafe..." etc. etc. which made every reboot longer and well, it didn't look nice.
Is the same screen also showing up when I install any custom ROM such as Pixel Experience?
KonradIC13 said:
Hello,
I remember that when i last time unlocked bootloader on my Nokia 8 phone, on every phone restart there was an obnoxious splashscreen telling that "this device is unlocked, unsafe..." etc. etc. which made every reboot longer and well, it didn't look nice.
Is the same screen also showing up when I install any custom ROM such as Pixel Experience?
Click to expand...
Click to collapse
yes, this message on the screen always appears with any ROM while the bootloader is unlocked, it is not something that is from the installed ROM but from the bootloader and it seems to be prior to loading the system like the BIOS on a computer. As for the Pixel Experience, this ROM it is very stable and you hardly ever have to restart the phone, so you will see this message very rarely