I have an Oppo A51w (Oppo Mirror 5) that I just reset to factory settings, out of nowhere when I restared the phone after that it shows encryption unsuccessful, and a reset phone button, which I couldn't press.
Going into ColorOS recovery mode, I tried wiping data and cache, but wiping data doesn't work because it says I have no space it needs at least 250mb, but I remember the phone does have plenty of space, more than 7gbs, so I don't get why it shows that.
As for fastboot mode it doesn't really do anything other than show its starting logo and text and it turns off? Is there anything else I'm supposed to do I'm not sure?
Anything I could do to get past the encryption screen? I don't mind having to fully reset the phone or flash it but I might need a guide.
There is also an install from sd option in the recovery mode, if somehow it can be fixed from there then please help me with that.
The android version is 5.1.1 and ColorOS 2.1.0i
The version that shows on the ColorOS recovery is 1.2
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
NextGenMagisk said:
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
Click to expand...
Click to collapse
Does this need USB debugging? I don't have it enabled and can't enable it because I can't get past the encryption screen.
I tried using MSM download tool but for some reason it won't detect my phone and I'm not sure which usb driver to use and how to install it.
The phone also isn't rooted.
Update:
The phone is now stuck on boot loop. I tried to flash it from sd card using stock rom from the official website, without wiping data first because it wasn't possible (needs 250mb of storage space even though there IS enough free space). It said it was successful, but after rebooting it just gets stuck on boot loop.
- for adb I'd need usb debugging? Which can't be enabled
- the phone isn't rooted, so no cwm
- msm download tool I tried, v4 and v5 doesn't work it says "Packed image not exist" but v1.6.7 does? except even it won't detect the phone, and the rom that i downloaded for that from a different source had different phone model options which i do not recognize (oppo15008.bin etc and rawprogram0_MSM_15070.xml) so I'm not sure which one to choose. Maybe I haven't installed the driver but I don't know which to install and how to.
I really have no experience with this and just tried different guides on the internet to get the phone working. For now I don't know what to do. Any help is appreciated.
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
NextGenMagisk said:
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
Click to expand...
Click to collapse
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
{
"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"
}
southeeast said:
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
Click to expand...
Click to collapse
Sorry, I cannot help with selection of firmware.
Is there any reason why you can't get this repaired in the Oppo service center?
Related
Last night I unlocked my bootloader and installed twrp recovery but somehow my mind changed so I thought to revert back changes and i download stock recovery of Realme 3 pro from somewhere(can't remember source) and after flashing it without checking it I ran a need command "fastboot flashing lock " and after that I rebooted my device and now it shows "the current image (boot/recovery) have been destroyed and can not boot " and now I can't even boot into fastboot mode to do something to revert back it .....At last, I'm here for suggestions on how can I make my device run normally.
{
"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"
}
Hi,
I also had the same problem but I managed to get out of it. Install twrp recovery through fastboot and flash the stock rom of realme 3 pro after doing a wipe. It worked for me and I got back my phone.
contact 'softichnic'
it will cost 30 us dollar.
I also suffered from bootloader relock error, but softichnic engineer fixed my phone through remote control.
good luck
i have same issue, please sameone help... i can't enter the bootloader...
No one got any solution to this?
killerxda said:
No one got any solution to this?
Click to expand...
Click to collapse
go to fastboot mode then simply flash recovery with stock recovery
elsapex said:
go to fastboot mode then simply flash recovery with stock recovery
Click to expand...
Click to collapse
If you read the post carefully it says 'cant enter fastboot mode', if we could enter fastboot there wouldnt be an issue. When recovery and fastboot dont work then only QDLoader mode remains (vol up + down) but to use the realme flash tool you need a login which only service center staff have. Only option in this situation is to take it to the service center, which i have done and got it fixed under warranty.
When a cracked version is available for the flash tool then we wouldnt need to go to the service center and flash its .ofp file on our own
killerxda said:
If you read the post carefully it says 'cant enter fastboot mode', if we could enter fastboot there wouldnt be an issue. When recovery and fastboot dont work then only QDLoader mode remains (vol up + down) but to use the realme flash tool you need a login which only service center staff have. Only option in this situation is to take it to the service center, which i have done and got it fixed under warranty.
When a cracked version is available for the flash tool then we wouldnt need to go to the service center and flash its .ofp file on our own
Click to expand...
Click to collapse
i'm sorry did not read that, service center is your only hope. but what i experience i had your for 3rd in row, but still manage to go to fastboot mode.
same issue
Hi my mobile is also in boot loop
fastboot not working i have tried every button but none worked
not connecting to pc/laptop as well
any one have a solution please help
killerxda said:
If you read the post carefully it says 'cant enter fastboot mode', if we could enter fastboot there wouldnt be an issue. When recovery and fastboot dont work then only QDLoader mode remains (vol up + down) but to use the realme flash tool you need a login which only service center staff have. Only option in this situation is to take it to the service center, which i have done and got it fixed under warranty.
When a cracked version is available for the flash tool then we wouldnt need to go to the service center and flash its .ofp file on our own
Click to expand...
Click to collapse
which flash tool ? because of lockdown i cant contact to the service center
najam489 said:
which flash tool ? because of lockdown i cant contact to the service center
Click to expand...
Click to collapse
The flash tool is included with the ofp file, but its just a waste of time. It will ask for login which only realme/oppo staff have or wait until we get a cracked version. File link is here:
https://androidfilehost.com/?fid=1395089523397963466
Hi, I've recently hardbricked my redmi k40 pro when trying to flash some custom roms and custom recoveries. I managed to get it into EDL mode hoping to flash a working recovery from there. However when I try to use the miflash tool it gets stuck on "ping target via firehose", or goes to "write time out, maybe device was disconnected" and I cannot get anything to work. I realized that even if i get past that part that I still require an authorized xiaomi account to flash in EDL mode. So I thought i'd try it using QFiL, however that requires the programmer file for the phone, and from my understanding that's a proprietary file that only xiaomi has and you can only get from leaks and such.
I was wondering if anyone knew where to get the programmer file or if you knew how I could get an EDL authorized xiaomi account so i could use the miflash tool to fix my phone.
Also does anyone know how to fix the "write timeout, maybe device was disconnected"? I have tried different usb ports and different usb cables and I can' get anything to work.
Also is any snapdragon 888 programmer file usable? Or do I have to have one specific to my phone?
Any help would be greatly appreciated as I am very new to EDL mode.
froggydood said:
Hi, I've recently hardbricked my redmi k40 pro when trying to flash some custom roms and custom recoveries. I managed to get it into EDL mode hoping to flash a working recovery from there. However when I try to use the miflash tool it gets stuck on "ping target via firehose", or goes to "write time out, maybe device was disconnected" and I cannot get anything to work. I realized that even if i get past that part that I still require an authorized xiaomi account to flash in EDL mode. So I thought i'd try it using QFiL, however that requires the programmer file for the phone, and from my understanding that's a proprietary file that only xiaomi has and you can only get from leaks and such.
I was wondering if anyone knew where to get the programmer file or if you knew how I could get an EDL authorized xiaomi account so i could use the miflash tool to fix my phone.
Also does anyone know how to fix the "write timeout, maybe device was disconnected"? I have tried different usb ports and different usb cables and I can' get anything to work.
Also is any snapdragon 888 programmer file usable? Or do I have to have one specific to my phone?
Any help would be greatly appreciated as I am very new to EDL mode.
Click to expand...
Click to collapse
UNBRICK XIAOMI PHONES WITH EDL
DOWNLOAD MODIFIED MIFLASHAND Qualcomm HS-USB QDLoader 9008 DRIVER
The following actions :
1) Connect phone to pc in EDL mode
2) Open Miflash and specify the path to the firmware
3) Click on flash
4) A window will appear where you will need to register the keys
5) On the second line you will need to write the password -
Code:
055F4BBD62228C3E55433D11D59BB445
6) On line 3, write "answer" -
Code:
jL6N48NekgtUZ/3ubbjqXi5RPllB+MoM6Rwqvrvz62jIPQLAVtekYtBxTumF0G95xEAJn2GDsT4G
iMByr/jp5HgtMMsF01DckdGctz7TfddXJ5XDT1Ki/IqQYFZf79M7z+3vFPuVsAL8muq4HBsMYFnm
A5jWj1zaFBtZ+N9VX/0QfRBUcZamyVsWv7X7hd8zVX6MY86eyb6H6EbLaQRueI8j71TcyUaVkUS5
FOyTJ4J1g+XQVeTTNd7Ht9qkfsOkbMha1SPVdLSCHwpI0kc2GXVz/noIv7PatXNQ7II1Sddmo2pn
qNYMfKqpEttJxfVg0No9KBuyzWBNf/sE/W3EBw==
actually don’t know if this still works, but it was a major loophole found.
Kenora_I said:
UNBRICK XIAOMI PHONES WITH EDL
DOWNLOAD MODIFIED MIFLASHAND Qualcomm HS-USB QDLoader 9008 DRIVER
The following actions :
1) Connect phone to pc in EDL mode
2) Open Miflash and specify the path to the firmware
3) Click on flash
4) A window will appear where you will need to register the keys
5) On the second line you will need to write the password -
Code:
055F4BBD62228C3E55433D11D59BB445
6) On line 3, write "answer" -
Code:
jL6N48NekgtUZ/3ubbjqXi5RPllB+MoM6Rwqvrvz62jIPQLAVtekYtBxTumF0G95xEAJn2GDsT4G
iMByr/jp5HgtMMsF01DckdGctz7TfddXJ5XDT1Ki/IqQYFZf79M7z+3vFPuVsAL8muq4HBsMYFnm
A5jWj1zaFBtZ+N9VX/0QfRBUcZamyVsWv7X7hd8zVX6MY86eyb6H6EbLaQRueI8j71TcyUaVkUS5
FOyTJ4J1g+XQVeTTNd7Ht9qkfsOkbMha1SPVdLSCHwpI0kc2GXVz/noIv7PatXNQ7II1Sddmo2pn
qNYMfKqpEttJxfVg0No9KBuyzWBNf/sE/W3EBw==
Click to expand...
Click to collapse
I still get the write time out, maybe device was disconnected error.
{
"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"
}
Does that work with redmi k40 ???
+1
I am facing the same issue with the bricked device. Mi Flash won't let me install anything using EDL mode without authorization. Anyone can help?
Kenora_I said:
actually don’t know if this still works, but it was a major loophole found.
Click to expand...
Click to collapse
It doesn't work anymore.
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"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"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?
Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
{
"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"
}
Solved without using EDL test points. see The Solution below.
BIG Thanks goes to @NOSS8 for his help.
ramiro2016 said:
Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
Click to expand...
Click to collapse
this phone did not need edl or test point.
https://forum.xda-developers.com/t/...-after-flashing-gsi-rom.4448229/post-86995731
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
ramiro2016 said:
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
Click to expand...
Click to collapse
https://xiaomitools.com/sp-flash-tool-en/
there is also this tool (new not tested).
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
https://gearupwindows.com/how-to-disable-driver-signature-enforcement-on-windows-11-10/
check for program update
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
ramiro2016 said:
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
Click to expand...
Click to collapse
This is not the latest version(V52).
https://mega.nz/file/H0MW3BST#PfzzmSwbncT5aV7A1ZhWztQonLj4CgJLDHbXoRtCu54
Maybe useful
https://www.bypassfrpfiles.com/2021...h_Secure_Boot_Disable_Tool_V52_Latest_Version
BTW: I don't have and would never have a xiaomi Mediatek and therefore never use these tools for Mediatek, that's why I can help you for the links but not for the use of these tools.
If it still doesn't work post the latest log.
Unfortunately, even the latest version v52 doesn't work, but this tool helped me solve the problem.
https://github.com/bkerler/mtkclient (You need to follow the readme document).
I've used the mtk_gui, and after it got connected, I sent my original firmware boot.img that is currently installed on my mobile after renaming it to boot.bin to the device partitions boot_a and boot_b
Rebooting the device got me the original recovery mode and the fastboot mode.
Then I used the MiFlash tool to flash my phone using flash_all.bat
Every thing is working fine know.
BIIIIIIIIIIIG Thanks goes to @NOSS8 for helping me all the way to the solution .
disclaimer - sorry i really have no idea what i am doing and my goal is to just go back to my normal phone
my phone is poco f1 and now i can only access fastboot and this "powered by android" screen. fastboot into twrp doesnt work because of "boot command is not allowed in lock state" error
hello all so i tried rooting my phone and then realized that its going really badly (i have a more details about it down) so i decided to flash stock rom using techno treatment's tutorial on it but along the way i have faced a couple of problems - when trying to install drivers, program crashes, and others below
first time i flashed i got an error (timeout error in logs) , so i tried to flash again but this time i left it open for some time (at around 500 seconds i pressed flash again, in logs it shows that flashing already started) and when i came back it was at 12000 seconds still flashing so i closed miflash and am flashing once again but with a shorter folder path (desktop\xiaomi\firmware).
after this i deleted 2 lines in flash_all.bat because i kept getting stuck on echo mismatching image and device. after this everytime i try to flash i get this error - error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
and also error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State') in the other log file
and after this i tried to go into fastboot but noticed that the fastboot logo is different, it was a bunny with a hat repairing android robot but now it is android robot repairing itself
{
"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"
}
(this is what it looks now)
what i did before flashing stock - sorry my memory isnt the best this is all in a span of around 5 hours and my phone is pocophone f1. so at first i followed munchys tutorial on how to root, i succesfully enabled bootloader then in twrp i flashed recovery with some errors like failed to mount /system and 3 others like this but i ignored and continued then i installed magisk and after that in the video he goes into his phone no problem but i had "no os" and i think i just clicked around like backing up, restoring and wiping. then i thought i need a rom because its an os right? so i installed lineage and that was the last time when i could put files into my phone through usb. then i flashed the zip and after that rebooted and got "cant load android system, your data may be corrupt" so i pressed format something like that and did it a few times (i think this is when i couldnt put my files) until eventually saw that its no use so i went back to twrp and again clicked around until eventually wiping everything now i have no os and i cant transfer anything through usb.
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
khusika said:
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
Click to expand...
Click to collapse
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
medioqre said:
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
Click to expand...
Click to collapse
That's right, but i recommend go to the service center if you aren't able to do it.
khusika said:
That's right, but i recommend go to the service center if you aren't able to do it.
Click to expand...
Click to collapse
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
medioqre said:
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
Click to expand...
Click to collapse
If you are still in locked bootloader, you can't write firmware through fastboot or recovery
Why don't you try unlocking the bootloader officially?