Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""
I'm handling a bricked Zenfone 3 ZE552KL WW model, but I am unable to flash the stock rom back into the device.
For context, this device has never been unlocked, rooted, and always worked under its original factory Android. As told by the owner, he received an OTA update notification last week and confirmed all prompts to initiate the update. As instructed, he plugged the device to its original charger, left the update running and went by with his day doing other stuff. When he returned, the device was completely OFF with 0% battery. We figured the charging cable disconnected due to a bad connector endpoint, and the phone ran out of juice while the update was running!
The result is a bricked Zenfone unable to boot beyond the ASUS logo. It keeps crashing and gets into a boot loop.
I have tried most of the basic tech support I can give him.
I have downloaded a fresh copy of the official ZE522KL firmware from the ASUS website.
I can boot the phone into recovery, which is still the original ASUS recovery. But as I try to flash the firmware, I get this lovely error message:
{
"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"
}
ERROR: This package is for "WW_Phone" device. This is a "".
I know for a fact this is a WW_Phone device because when I try to flash the JP firmware, the error message is different.
ERROR: This package is for "JP_Phone" device. This is a "WW_Phone".
Already tried "Wipe data/factory reset" and "Wipe cache partition" from the recovery menu, but that didn't help.
Already tried pushing the firmware via "adb sideload" and placing it in a SD card. Those didn't help either.
I am also willing to flash a community ROM, like LineageOS or Mokee, but I first need to unlock the bootloader. I'm running adb and fastboot from Linux, and I can't find a descent tool to unlock using Linux is proving to be a real pain. Every tool seems to be made for Windows only.
So, I'm resorting to anyone here, hoping anyone could give me a light before we send this phone directly to ASUS tech support, not available in our region (we'll need to ship it to another city).
Anything I can try before that? I'm running out of ideas.
Best regards and thanks in advance for any help.
Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg
Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.
wang1chung said:
Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.
Click to expand...
Click to collapse
Since his phone is locked, he can't flash anything except RAW firmware.
---------- Post added at 11:52 AM ---------- Previous post was at 11:41 AM ----------
juliohm said:
Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg
Click to expand...
Click to collapse
Hey juliohm,
Just follow these steps & your device will operate normally
1) Download and install ASUS Flash Tool :
2) Download Latest Oreo RAW
ZE520KL:
ZE552KL:
3) Enter Fastboot Mode (Power + Volume Up)
4) Open ASUS Flash Tool
5) Select device & select firmware (select YES on wipe data tab too)
6) Connect phone to PC
7) Hit Start and wait 10-15 minutes (ignore the error 5 [FRP])
MOD EDIT: PAY-PER-CLICK LINKS REMOVED
Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?
juliohm said:
Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?
Click to expand...
Click to collapse
Check PM
Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.
GrenadeofTacos said:
Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.
Click to expand...
Click to collapse
No need. Flash RAW firmware is enough.
Just a quick follow up.
The owner decided to take it a local assist shop. I don't know what method they used, but they managed to reflash the stock firmware back into the device, and it's working fine again.
Thank you all for the tips. If this was my own device, I would be tinkering a lot more. But the owner decided to play safe and pay for repair in some authorized assistence shop.
Best regards all!
Related
My a500 cannot perform factory reset or flash rom, and reflash recovery doesn't update the recovery, even i tried to flash bootloader using apxflasher it stuck at stage 2...
here is the situation.
im using teamwin recovery, recently i couldnt flash any rom, nor wipe all partition.
every times i flash rom or wipe partition, reboot, my tablet will back a previous state, is like every times i reboot my tab, it will restore to a "backup"
i called it restore is because all the changes i made after reboot will gone.
i tried to flash other recovery using the fasboot, it doesnt replace the teamwin recovery.
i tried use apxflasher to flash bootloader again, i get stucked in stage 2 uploading image
{
"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"
}
finally i tried flash the euus, but i got N/A for the new image version and stuck at there.
Anyone can help me with this?
chinseng85 said:
My a500 cannot perform factory reset or flash rom, and reflash recovery doesn't update the recovery, even i tried to flash bootloader using apxflasher it stuck at stage 2...
here is the situation.
im using teamwin recovery, recently i couldnt flash any rom, nor wipe all partition.
every times i flash rom or wipe partition, reboot, my tablet will back a previous state, is like every times i reboot my tab, it will restore to a "backup"
i called it restore is because all the changes i made after reboot will gone.
i tried to flash other recovery using the fasboot, it doesnt replace the teamwin recovery.
i tried use apxflasher to flash bootloader again, i get stucked in stage 2 uploading image
finally i tried flash the euus, but i got N/A for the new image version and stuck at there.
Anyone can help me with this?
Click to expand...
Click to collapse
When you tried the EUUS did you follow the flowchart in the second post of this thread? http://forum.xda-developers.com/showthread.php?t=1816560
I just ran a EUUS fine following the flowchart - But had a result similar to yours when I didn't unzip the EXE and fill in the CPUID.txt file.
I'm in the same situation, no way to get the v8 UNL BL, stops at stage 2 (BT's apxflashtool) and "3/4 recovery" with AfterOTA TOOL.
I shall try the EUUS flashing (will delete your internal memory), but now I'm very busy so I renounced..
The EUSS file flashing should help
Wedee said:
When you tried the EUUS did you follow the flowchart in the second post of this thread? http://forum.xda-developers.com/showthread.php?t=1816560
I just ran a EUUS fine following the flowchart - But had a result similar to yours when I didn't unzip the EXE and fill in the CPUID.txt file.
Click to expand...
Click to collapse
yes i did unzip it to a folder, and put in my cpuid. i got my cpuid from dmesg dump
MadMav88 said:
I'm in the same situation, no way to get the v8 UNL BL, stops at stage 2 (BT's apxflashtool) and "3/4 recovery" with AfterOTA TOOL.
I shall try the EUUS flashing (will delete your internal memory), but now I'm very busy so I renounced..
The EUSS file flashing should help
Click to expand...
Click to collapse
im not sure why i cant get the new image version. tried on winxp and win7
chinseng85 said:
yes i did unzip it to a folder, and put in my cpuid. i got my cpuid from dmesg dump
im not sure why i cant get the new image version. tried on winxp and win7
Click to expand...
Click to collapse
Couple of ideas to try...
Make sure that when that screen comes up there is not a second window it spawned hiding behind it... For me when it got to that screen I saw another window pop, and it was hidden behind the main, the popup window walks you thru the next steps of setting APX mode, plug in cable, hit ok......
Another thing to try is Right click the PBJ20upgrade.exe and choose "Run as Administrator"
Finally download a new copy... when you unzip it you should end up with Several files and then two folders /Image and /usbpcdriver. The /Image folder has all the img files it needs to install. In the root there is a file called version.cfg that when I view inside it seems to have the info that the program uses to tell what version it is going to install... Hazzard a guess that if that file is missing it might not know what its going to install.
I have good experience with other phones but this is my first time working with ZE550KL.
So I took my uncle's phone and he asked me to update his phone to the latest firmware to get the VoLTE feature.
He is was on ZE550KL_WW_21.40.1220.1708 which is Marshmallow of the ZEN UI.
I have downloaded the latest firmware from the ASUS website but I couldn't update it because the recovery which came with the marshmallow update is broken.
These are the errors I got
{
"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"
}
Here is what I did, and hope this works for everyone.
Hoping that you already went and searched about the problem over the internet.
These are the things you need to download :
ADB and fastboot
https://drive.google.com/file/d/0B0aDjdU4gTwZZW1HUHhqWnEteXM/view
Recovery image file
https://drive.google.com/open?id=0B0aDjdU4gTwZa1MyUmVPN3BhQjQ
Latest firmware:
https://www.asus.com/in/support/Download/39/1/0/22/ZROQURlyupei1ZQz/32/
1. Download the adb and fastboot drivers. Download the latest firmware and copy it onto your internal storage.
2. Boot into the bootloader.
3. Download the recovery image and paste it into the adb folder.
4. Now type the following command.
Code:
fastboot flash recovery recovery.img
5. This step is very important.
Now, all you have to do is hold the power button and the volume down button to boot into the installed recovery.
Remember that if you restart your phone after step 4, your old recovery(which does not work) will still be there.
6. Now select update from sdcard and select the zip file of the latest firmware you downloaded.
7. It will take at least 10 minutes to install, don't panic if you think the screen froze.
I hope this solves the issues many users are facing.
Feel free to ask questions, I will be very happy to answer.
The recovery we installed is the recovery of Android Lollipop version of the Zen UI ROM.
Thanks. It worked. The only difference is that after flashing the old recovery, my SD card was showing blank. So i selected the adb sideload option and flashed the new build.. Thanks for your guide.
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
hellbraker said:
Thanks but few doubts remain. The recovery you used is from Lollipop`s 1.17.40.1503 right?
Can we not do this by installing a temporary recovery image (twrp)?
I have also read elsewhere ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) that you would need the boot image too. But your instructions are way too easier and easy to follow. Why don't you use boot image?
If we are using the boot image then which version of it should we use?
Click to expand...
Click to collapse
Before I tried any of this... First thing I did was boot TWRP and install the lastest firmware.
But I couldn't do so because TWRP doesn't let you flash .img files.
And for the best result it is always better for you to use the official recovery to flash an official firmware.
Because ASUS f***ed up, I needed to install the previous version of the recovery to flash the firmware.
And I'm very happy that my guide worked for you.
Don't forget to give thanks. :laugh:
I haven't tried it yet. So you didn't tamper with boot.img at all. Right?
Also as previously asked what's the build number from which you extracted the recovery.img? Is it from .1503?
My current build is .1708 same as what you worked on. And will data get erased during this process?
How can I boot into the bootloader? is it by unlocking it? or is there any other non-invasive way?
Update: I installed as per your instructions. Device shows "Optimizing app 5 of 51".
Thank you.
Thank you
Thank you sir, this helped me a lot.
recovery link is asking need access plzz help
My Asus Zenfone doesn't boot anymore and doesn't even allow me to factory reset it from the bootloader. How to force reset it??
I'm not rly good with electronics etc, my phone came with root access permissions via Security MIUI app so I installed SuperSu to manage it easier (MIUI app reqiured to manually check each app to allow access), no custom ROM or anything installed, the way it happened was
1. updated supersu from google play
2. entered supersu app,it asked me to update su binary
3. I clicked yes through recovery
4. it rebooted and got bootlooped.
It's stuck at the "mi.com" screen when turning on, can't go into recovery, fastboot mode only shows an image of Miui mascot without any fastboot options. I've followed some tutorials online and got the thing below from minimal adb.
{
"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"
}
sufoc said:
I'm not rly good with electronics etc, my phone came with root access permissions via Security MIUI app so I installed SuperSu to manage it easier (MIUI app reqiured to manually check each app to allow access), no custom ROM or anything installed, the way it happened was
1. updated supersu from google play
2. entered supersu app,it asked me to update su binary
3. I clicked yes through recovery
4. it rebooted and got bootlooped.
It's stuck at the "mi.com" screen when turning on, can't go into recovery, fastboot mode only shows an image of Miui mascot without any fastboot options. I've followed some tutorials online and got the thing below from minimal adb.
Click to expand...
Click to collapse
Fastboot will show that android icon only.
No fastboot options will be available there.
Now you need to perform some steps to recover your device..
Note - Your data will be wiped. Also, remove memory card (if any).
Now let's start the process -:
Download MIUI Fastboot ROM file.
Here's the link..
1GB RAM model - http://update.miui.com/updates/v1/fullromdownload.php?d=wt88047_global&b=F&r=global&n=
2GB RAM model - http://update.miui.com/updates/v1/fullromdownload.php?d=wt88047_pro_global&b=F&r=global&n=
Also extract this file and put in C Drive.
Now turn your PC on..
And install latest Mi flash tool. http://api.bbs.miui.com/url/MiFlash
Turn your device off. By pulling battery. (Assuming that your device is in bootloop).
Go to fastboot mode (power + volume down)
Now turn your PC on.
Open Mi flash tool.
Connect your device.
Click on refresh button in flash tool.
Now, it will show some random numbers. (This is your device).
Now, select your ROM fastboot file which you downloaded and extracted.
After that, choose 'flash all' and click Flash..
It will take some time.
After that your device will be rebooted.
Voila! Your device is back to life!
edit: solved
edit: solved
sethidheeraj06 said:
Fastboot will show that android icon only.
No fastboot options will be available there.
Now you need to perform some steps to recover your device..
Note - Your data will be wiped. Also, remove memory card (if any).
Now let's start the process -:
Download MIUI Fastboot ROM file.
Here's the link..
1GB RAM model - http://update.miui.com/updates/v1/fullromdownload.php?d=wt88047_global&b=F&r=global&n=
2GB RAM model - http://update.miui.com/updates/v1/fullromdownload.php?d=wt88047_pro_global&b=F&r=global&n=
Also extract this file and put in C Drive.
Now turn your PC on..
And install latest Mi flash tool. http://api.bbs.miui.com/url/MiFlash
Turn your device off. By pulling battery. (Assuming that your device is in bootloop).
Go to fastboot mode (power + volume down)
Now turn your PC on.
Open Mi flash tool.
Connect your device.
Click on refresh button in flash tool.
Now, it will show some random numbers. (This is your device).
Now, select your ROM fastboot file which you downloaded and extracted.
After that, choose 'flash all' and click Flash..
It will take some time.
After that your device will be rebooted.
Voila! Your device is back to life!
Click to expand...
Click to collapse
The fastboot rom is incorrect for my model (missmatching image and device error)
sufoc said:
The fastboot rom is incorrect for my model (missmatching image and device error)
Click to expand...
Click to collapse
Which device do you have..?
Kindly tell the model no. Such as 2014818.
sethidheeraj06 said:
Which device do you have..?
Kindly tell the model no. Such as 2014818.
Click to expand...
Click to collapse
It's the same as in the title, 2014811 TD-LTE
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"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"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP
is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?
Hi,
I've installed an ota update and the device didn't boot... it is stuck in a bootloop....
When i try to flash via fastboot, it appears an error saying that the device is locked ant cennot erase...
via fastboot oem unlock i get the error message: Remote: oem unlock is not allowed
via MiUnlocker the unlock gets to de 50% and gives an error and on its logs it says: Remote: oem unlock is not allowed
I tryed to flash TWRP with command fastboot flash recovery but the error is the same: remote: partition flashing is not allowed
Can anyone help me please??
I'm stuck on the bootloop i can't go to setting - developer - allow oem unlock option!!
Have you tried doing a Factory Reset from stock recovery?
This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?
Parnas72 said:
This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?
Click to expand...
Click to collapse
How can i do that?
Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!
Tepig said:
Have you tried doing a Factory Reset from stock recovery?
Click to expand...
Click to collapse
No recovery.. i get this:
{
"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"
}
Typhus_ said:
Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!
Click to expand...
Click to collapse
Obrigado!
I'll try it now!!
xistolas said:
No recovery.. i get this:
Click to expand...
Click to collapse
Actually you have a recovery. You need to long press the power button and, afterwards (not at the same time), press the volume + button. You'll see that all options will appear.
xistolas said:
How can i do that?
Click to expand...
Click to collapse
fastboot getvar current-slot
to show the current slot,
fastboot --set_active=a or fastboot --set_active=b
to change it.
xistolas said:
Obrigado!
I'll try it now!!
Click to expand...
Click to collapse
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
---------- Post added at 09:27 PM ---------- Previous post was at 09:23 PM ----------
akashavel said:
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
Click to expand...
Click to collapse
follow from step 6 to end in below link
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624