the current image (boot/recovery) have been destroyed - Realme 3 Pro Questions & Answers

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

Related

Root, How do adb fastboot commands work? need help

Hello, I am student at my university studying Computer Science. I work in tech support at my school. This is the first time I have modified the android os. The community on xda has been really helpful and knowledgeable. I have created an account to see if anyone else has done the same thing I have. Anyway read below for my post.
I am trying to change the recovery on my phone to twrp. Let me start out by saying I rooted my phone before on build number 130 (KIW-L24,Android 5.1,EMUI 3.1,C567B130,United States, Channel-Others). I used the instructions here and it worked http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190.
I then decided to update through the huawei updater to build number 151 (KIW-L24, Android 5.1, EMUI 3.1, C567B151, United States, Channel-Others). It eventually got to a black EMUI menu with installing 0%. So I powered it off even though it warned against it. So my phone was bricked so I followed instructions at http://forum.xda-developers.com/honor-5x/help/bricked-honor-5x-t3328308 and my phone worked again.
Okay so now I want to root my phone so I follow the instructions for rooting. Problem is that I can not replace the EMUI recovery with twrp recovery. I am guessing that it may be because 151 is a security update.
I use these commands on adb with the twrp_kiwi.img in my adb folder(named .android by default)
adb reboot bootloader
fastboot flash recovery twrp_kiwi.img
fastboot reboot
adb reboot recovery
So I wanted to see if I could put the old firmware back so I followed the instructions for bricked device. But the fastboot commands don't seem to do anything with the .img files.
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
Yea so I am lost as to why fastboot commands arent working as it says finished and any advice would be appreciated.
Also is it possible to format the phone similar to a pc and use adb to flash the firmware back on.
I want to eventually backup my phone and put cyanogenmod on it.
... I am guessing that it may be because 151 is a security update
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to flash what you want.
Have you tried reinstalling the Android device drivers on your PC?
JT-on said:
If your bootloader is unlocked, you should be able to flash what you want.
Have you tried reinstalling the Android device drivers on your PC?
Click to expand...
Click to collapse
{
"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"
}
Arobase40 said:
Is this really for a private use unless you are trying to ask us to do your university exercises for you ? LOL
And as you felt need to mention "I am student at my university studying Computer Science. I work in tech support at my school.", you should know first University mission is to teach you to search and exercise by yourself, to do things step by step and to guess by yourself what was wrong. ^^
Just one tip and advice : read up your own post carefully and you should find out what you've done wrong...
Click to expand...
Click to collapse
That was just background information unrelated to my post. I am currently trying to see if I can put the old firmware back to see if it fixes the problem.
honor5x_student said:
That was just background information unrelated to my post. I am currently trying to see if I can put the old firmware back to see if it fixes the problem.
Click to expand...
Click to collapse
TWRP works just fine on B151
plug in usb / Shut down the phone
boot to the bootloader (power + vol down)
open command prompt on PC
fastboot flash recovery twrp_kiwi.img
hold volume up + volume down + power till you see TWRP (about 14 seconds)
In TWRP choose reboot / recovery
Say yes to Root
recovery will reload / flash your rom
If you want to return to Stock use this >> https://www.androidfilehost.com/?fid=24459283995315154
instructions are in the zip

will you solve this?

Ok, I'll explain the problem(s)
My mate 10 pro (BLA-L09) can boot in recovery (TWRP 3.2.1-0) and fastboot:
When I flash other recovery with the .img by recovery (like for example the stock recovery) give me error;
When I flash other recovery with the .img by fastboot (like for example the stock recovery) give me error;
When I flash ROM by .zip/UPDATE.APP give me error;
In fastboot mode I read "Phone Locked FRP unlock"
the phone has no ROM in it, wehn I boot it automatically put me to recovery;
So, My bootloader is locked and I can't unlock it beacause I can't boot the phone.
I just want to reinstall the stock ROM, have you any ideas?
thanks to all
flash recovery from fastboot
Shandroid_94 said:
Ok, I'll explain the problem(s)
My mate 10 pro (BLA-L09) can boot in recovery (TWRP 3.2.1-0) and fastboot:
When I flash other recovery with the .img by recovery (like for example the stock recovery) give me error;
When I flash other recovery with the .img by fastboot (like for example the stock recovery) give me error;
When I flash ROM by .zip/UPDATE.APP give me error;
In fastboot mode I read "Phone Locked FRP unlock"
the phone has no ROM in it, wehn I boot it automatically put me to recovery;
So, My bootloader is locked and I can't unlock it beacause I can't boot the phone.
I just want to reinstall the stock ROM, have you any ideas?
thanks to all
Click to expand...
Click to collapse
If the FRP is unlocked, just unlock your bootloader again with your unlock code from huawei.
Or pay 4 euros and use dc unlocker.
I can't unlock bootloader 'cause dc unlocker can give me the code only when the smartphone is booted, and it hasn't a ROM mounted in..
Could you specify the error?
EngrVan said:
Could you specify the error?
Click to expand...
Click to collapse
which one?
Shandroid_94 said:
When I flash other recovery with the .img by recovery (like for example the stock recovery) give me error;
When I flash other recovery with the .img by fastboot (like for example the stock recovery) give me error;
Click to expand...
Click to collapse
These.
EngrVan said:
These.
Click to expand...
Click to collapse
1st pic, tried to flash recovery.img by fastboot;
2nd pic, tried to flash system.img by fastboot;
3rd pic, tried to flash stock ROM by TWRP 3.2.1-0 (Yeah, it CAN'T works, but whatever I flash it's the same results)
4th pic, dc-unclocker that can't pick up code for unlocking bootloader
{
"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"
}
Should have used dc-unlocker to read the bootloader code first, then unlock manually.
Now you have two options; wait for the unlock code page to get back up or use FunkyHuawei to restore your phone.
Since you don't have your bootloader unlocked you can't flash images as the partitions are protected. This causes the "Command not allowed" errors.
How did you erase/delete/remove the ROM in the first place? Anything you did before the incident?
Try to boot to erecovery... (vol + on boot w/o usb cable plugged in) Load the rescue system image over wifi. Hope it works!
I said just unlock bootloader because obviously you must alredy have the code if you have TWRP installed, that means that at some point you had it unlocked and you should have a code.
Anyway, huawei unlock page is up, so you should be able to get the code again in case you lost it. Dcunlocker gives your the data needed like imei, product id (not sure about this one) and SN in the box.
I think dc unlocker can unbrick your device (you need like 15 credits) it uses a back door to flash and unbrick. then you can get the unlock code to unlock.
Another thng you can try is flashing the BLA-Recovery no check from hwota8 directrly from TWRP (flash image) transfer it to your device through mtp or adb push.

Qualcomm CrashDump Mode

Hi, can anyone help me
I have my asus rog phone locked in fastboot with starting error qualcomm craachDump Mode.
I am looking for an img image to be flashed via fastboot.
Or any guide to bringing my phone back to life thanks.
Maybe you need to flash the raw files in fastboot mode.
WW_ZS600KL_15.1630.1907.98_M3.15.35.29-ASUS_1.1.12_Phone-user.raw.zip
Download raw.zip and unzip
ROG reboot into fastboot mode
Click on "flashall_AFT.cmd"
Thanks tried but not working it runs all ok, but it restarts again in Qualcomm crash ....... any other solution? Ver __Zs600kl __15.1616.1808.23 i can not find It
Ashba01 said:
Thanks tried but not working it runs all ok, but it restarts again in Qualcomm crash ....... any other solution? Ver __Zs600kl __15.1616.1808.23 i can not find It
Click to expand...
Click to collapse
What usb port on your phone did you use? I believe it will only work on the side port.
yes I used the side one, does everything but then restarts and enters ancota in Qualcomm Crash .......
Ashba01 said:
yes I used the side one, does everything but then restarts and enters ancota in Qualcomm Crash .......
Click to expand...
Click to collapse
Will it go into regular fastboot mode if while the phone is off, hold down volume up and power buttons?
you in fastboot by pressing plus button and ignition, and enter faatboot
Ashba01 said:
you in fastboot by pressing plus button and ignition, and enter faatboot
Click to expand...
Click to collapse
And when you do that do you get the error or just get the error when normal power on.
I get the error only when it starts normally
Ashba01 said:
I get the error only when it starts normally
Click to expand...
Click to collapse
When you tried the above raw install, were you in the normal fastboot or in the fastboot with the error? If you were in fastboot with the error maybe try the normal fastboot mode.
fastboot I never have the error, written error occurs only if I start asus rog phone normally.
With fastboot and lateral usb I did the procedure until the end, then unfortunately when Asus rog starts normal error returns
Ashba01 said:
fastboot I never have the error, written error occurs only if I start asus rog phone normally.
With fastboot and lateral usb I did the procedure until the end, then unfortunately when Asus rog starts normal error returns
Click to expand...
Click to collapse
I know of an ASUS flasher tool. I don't know if it is clean, so be careful. If you have an old computer, I would use it and keep it off your network.
https://www.asusflashtool.com/
That is the only idea I have left to try. Maybe others will have more ideas.
Thanks for the help, you are very kind, explain to me how to use the tools this evening when I come home I try.
Seeing my asus phone brick is sad.
Ashba01 said:
Thanks for the help, you are very kind, explain to me how to use the tools this evening when I come home I try.
Seeing my asus phone brick is sad.
Click to expand...
Click to collapse
You're welcome. To use the tool you'll have to download the firmware that matches your phone from here:
https://www.asus.com/us/Phone/ROG-Phone/HelpDesk_BIOS/
If the flash tool doesn't work, maybe ASUS support can help:
https://www.asus.com/zentalk/forum.php?mod=forumdisplay&fid=433
Perfect tonight or tomorrow morning I try, we hope to be able to solve !!!! thank you all friend.
Tesla74 said:
You're welcome. To use the tool you'll have to download the firmware that matches your phone from here:
https://www.asus.com/us/Phone/ROG-Phone/HelpDesk_BIOS/
If the flash tool doesn't work, maybe ASUS support can help:
https://www.asus.com/zentalk/forum.php?mod=forumdisplay&fid=433
Click to expand...
Click to collapse
Errore: Device Is not connected Yet ........
hi friends my asus rog phone i flash it with qfile with stock rom now my imei has be 0 nothing and me serial has be chance how i can fix it back i need unlock boot loader i cant use the tool when ik flash raw file and its done and i go to phone info and go to imei i have no imei and me serial has not the orginal one and if i wil use unlock tool to unlock boot loader it no works tels me something error me network has some thing how i can fix this i need some qcn file to fix that me imei is this i got 2 imei codes the first imei 351555101262549 now the 2 imei 351555101262556 and me serial is this JCAZGV040926299 i cant fix this by flashing need help now rog 2 phone can be unlocked the boot loader with fastboot this must also voor the rog phone zs600kl work voor it users please so whe dont need more the unlock tool of asus boot loader apk need unlock rog phone zs600kl with fastboot no more unlock ttool need help
nenebear said:
Maybe you need to flash the raw files in fastboot mode.
WW_ZS600KL_15.1630.1907.98_M3.15.35.29-ASUS_1.1.12_Phone-user.raw.zip
Download raw.zip and unzip
ROG reboot into fastboot mode
Click on "flashall_AFT.cmd"
Click to expand...
Click to collapse
This File Link Error
404. That’s an error.
The requested URL was not found on this server. That’s all we 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"
}
Good day. Did you succeed?
Tih1 said:
Good day. Did you succeed?
Click to expand...
Click to collapse
Not Now Succeed Still

Oppo A51w encryption unsuccessful, help

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?

help with whatever i have done

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?

Categories

Resources