Question Data recovery over fastboot on a broken screen - Xiaomi Mi 11

Hello everybody.
I currently have a Mi 11 with a broken screen (touchscreen works but no image is visible).
I want to recover all the user data inside it, because there's important stuff I need to backup.
I have tried booting into EDL and follow this guide, though while trying to load the EDL mode it says FAILED (remote: 'Error Invalid Parameter').
The bootloader is locked, and since I want to take some data from it I cannot unlock it as it will wipe everything inside.
I also have tried having the screen from a USB-C to USB-C/USB/HDMI adapter, it shows nothing. It's not an adapter issue as it works with a OnePlus 8 Pro.
I currently am in lack of solutions and I really need to back everything up.
Thanks in advance for any person that can enlighten me.

Did you prudently enable USB debugging mode?

Related

Messed up via oem lock command - can't access recovery - any help appreciated!

Hi all,
A few days ago I installed a custom ROM, which broke my android pay. I tried to re-lock the bootloader to fix this via the fastboot oem lock command, and i'm now stuck in a bootloop.
I can get the phone to boot into fastboot mode, and it shows up as such when checking via command prompt. I also have a backup of the phone I made a few days ago. I've tried to unlock the phone using the fastboot oem unlock command, but get the following error:
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.008s
I bought the phone second hand with an unlocked bootloader, if that makes a difference? I've set up a new Mi account and applied for an unlock code.
Does anyone have any tips on how to proceed? Thanks in advance!
Stupid thing to think relocking your bootloader would fix android pay while still on that custom rom, whe have hacks for that you know >> magisk14/15.2
Do you still have twrp? also try to flash stock images from xiaomi themselves, here.
that should at least get you booting again.
Hi,
Thanks for replying, i'll download the global stable version. Is it a case of sideloading this once complete? I still have TWRP installed if it makes a difference, I just can't reach it :/
Yes I do feel pretty stupid, and thanks for the link to magisk - hadn't heard of it until now but i'll definitely be using when/if I get my Mi back up and running. Is there anyway to unlock the bootloader other than the Mi Unlock app?
Thanks!
EDIT: Okay, so i tried flashing via the MiFlash tool and got the following error:
FAILED: Remote device is locked. Cannot erase.
Any idea of where to go from here?
So, I fixed it! In the off chance anyone is as unlucky/stupid/trigger happy as me, and finds themselves in teh same situation, here's the solution:
If you can't get it into EDL mode because you can't switch it off (mine kept rebooting), follow this video:
https://www.youtube.com/watch?v=ED96PJ-qYMM
It's in a foreign language but is clear enough - take the back off, unscrew the cover and short the pins he shows you after disconnecting the battery, then plug into your computer.
Your phone will pop up as a Qualcommdevice under the ports section of Device Manager. You should then be able to flash via MiFlash as per usual.
Phew, hairy there but sorted in the end. I'll now wait for the unlock code from Xiaomi, and do a bit more reading in future!
A much easier way to solve this problem
You don't have to follow any long tutorial. Nor do you have to open your phone up. Just power it into fastboot mode, download the mi unlock tool that you used the first time to unlock your bootloader and unlock your device once again. Then you can use miflash to flash the fastboot rom on your device and it won't throw up any errors. Once that's done, just reflash the custom recovery. Install the custom rom, use magisk for root and you're good to go. Safety net won't be tripped and android pay will still work. No need to rip your phone apart to fix it.

xaiomi mI5 loop,stuck.

hi friends, i need so much your help!.
I have xaiomi mi5, the operating system of the cellphone has been updated, and then the device has entered the loop.
He can not get up at all.
I've tried to do so far:
FAST BOOT - but even the computer can not read the device despite all the permissions I have approved for the computer.
MIPCSUIT - does not work well because the computer does not recognize the device.
Your help must be smart and good people!
I am also stuck with the same problem.
At least I can get fastboot.
I think if you OK to loose data then just go to recovery mode with Volume up + power button pressed together. And wipe all. This may solve the problem. But I don't want to loose data I am skipping this option.
If any one knows other way to unbrick without full wipe then please let us know.
Thanks
have you unlocked bootloader?
you can try run by fastboot twrp recovery mode.
Code:
fastboot boot twrp.img
after few seconds phone boot to recovery, you can encrypt the phone and copy data.
twrp is here
My bootloader is locked I think.
I tried that command. Didn't boot to twrp.
Any other way.
Anyway Thanks for suggesting.
Are you on latest MIUI global stable? I think Xiaomi's guys ****ed it up this time around and got bootloop for everybody on latest update.
Take a read here and good luck: http://en.miui.com/thread-2776961-1-1.html
ok listen me... if you have got unlock permission and unlocked your phone or you have unlock code.. you must bind your acc with other xiaomi phone easly enter your acc and bind acc now go fastboot download mi flash unlocker install adb driver and unlock then you can flash stock rom i had that problem and i solved
Hello,
I had similar issue.
To be able to start phone/miui you should remove sim card,
in my case it was connected to connecting to cell network that caused reboot.
Than it will be possible to update phone using WiFi.
For me issue was solved with V9.5.2.0.NAAMIFA update.
BR Jarek.
jarek102 said:
Hello,
I had similar issue.
To be able to start phone/miui you should remove sim card,
in my case it was connected to connecting to cell network that caused reboot.
Than it will be possible to update phone using WiFi.
For me issue was solved with V9.5.2.0.NAAMIFA update.
BR Jarek.
Click to expand...
Click to collapse
Lifesaver here!
This worked perfectly for me! Go figure?
Cheers
You can try
I tried version gemini global images v10.2.2.0. OAAMIXM 2019115 GLOBAL but failed then tried v8.11.22.20181122.000 8.0 GLOBAL but failed then 2 month later i tried with good battery and good on off and main important is version GEMINI GLOBAL IMAGES 6.11.10 _20161110 and version GEMINI GLOBAL IMAGES V7.2.4.0.MAAMIDC 20160129. AND GUESS WHAT SUCCESS. NEVER TRY WITHOUT BATTERY AND WITHOUT EDL POINT. EDL POINT FOR UNLOCKING BOOTLOCK AND DOWNLOAD SOFTWARE FLASH FILES WITH GOOD INTERNET WITHOUT INTERUPPT SO FLASH SUCCESS. MY 2 MOTHERBOARD OF MI5 SAVED WITHOUT HARDWARE. HOW TO KNOW SOFTWARE OR HARDWARE....1ST CHECK CHARGING HAPPENING OR NOT IN SWITCH OFF AND CAN IT GO TO FASTBOOT MODE OR RECOVERY MODE. IF ALL THIS GOOD GO FOR FLASH IN SAME PROCESS. OTHERWISE HARDWARE AS STATED THAT RESISTOR ALSO PLAY A VITAL ROLE IN BOOTING OR STUCK AT MI LOGO. MOISTURE IN PHONE UNDER IC REQUIRE HEAT WITH PASTE AT HARDWARE LEVEL.

Please Help_After OTA Update Xiaomi Mi A2 died

On Saturday appeared an OTA update to do on my mi A2 but after installed and restarting it died. It does not enter recovery mode and the screen is always on with android one bootscreen logo.
PS: I never flash the phone and i never change anyting in the system of the phone.
The only response that i have in the phone is enter in it Fastboot menu. I read some threads and untill now i cant fix my phone.
I will try to explain what i do:
I've tried using this tool https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585.
I try option 3 (Unbrick/Revert to Stock/Force update and the program tell me to unlock the bootloader.
When i tried to unlock bootloader by option 1 and then 1, 2 and 3 ( Unlock flashing critical, unlock OEM , unlock flashing ) the programs says: Failed Unlock is not allowed.
Then i try the response 9 to this thread https://forum.xda-developers.com/mi-a2/help/impossible-flashing-xiaomi-mi-a2-t3837565 to try unlocked the bootloader
But i have the same response ( Flashing Unlock is not allowed )
I read and i try but i cant unbrick my phone, someone can help?? Thanks
We are in the same boat buddy, the same thing happened to the phone of my wife.
It *sounds* like the update failed, and normally that would mean it would switch the slot back to the one that was working and boot that.
But you've tried a bunch of options from some tool, I've no idea what it did, as the tool doesn't tell you what commands it's doing.
I'd suggest to go to fastboot and see if you can tell which slot is active, then switch it to the other slot, then do fastboot reboot and cross your fingers
I have the same problem (for other reasons, but exactly the same problem). You can also try "fastboot oem edl", but it did not work for me, so I suppose you have little chance for it to work.
I have been searching and it looks like there are some "deep flash cables" that can make the phone enter edl mode to flash it using mi flash tool. Maybe these could work for us. There is apparently other way to enter edl mode, but it requires opening the phone (that I do not want to do) to short two test points.
I cant enter revorymode only fastboot mode. But when in fastbootmode my connected pc cant even find the phone. Im going to return the phone.
I have the same problem, I have this edl cable but so far no luck.
Do not realy k Ow how to use.
Are you sure it was the OTA update that bricked your phone? That Treble system isn't just there for the kicks, its there to prevent serious issues like these.
I'm stucked on fastboot, I don't want to open my phone. Could anyone help us? I already tried a lot of things, my computer doesn't recognize my mobile when is on fastboot mode. I already tried to install a lot of drivers or try to use differents adbs.

Bricked device, bootloader disaster. Help?

I have a xiaomi mi a2 device which had bootloop all the time. I was not able to get into device at all. So in other words oem unlock and usb debugg was not active at all. I tried so many times to get into the phone just to activate those. Now since some other phones doesnt really need those to flash because they use different kind of flashing i asumed i wouldnt need those.
when i tried to flash using adb sideload which was available it couldnt flash it went to 47% and then it just failed or stopped with some message and 1.00x at the end. I did try couple of times without any luck. I was never awared that thus phone had project treble rom wich in turn have 2 partitions. I acted on impuls. Then i tried fastboot commands with error about failed not able to flash restriction. Then i found that you could flash using emergency download mode which is in my mind something lg has with shorting the pins. There you dont have any issues because emergency download mode in lg dont require any permission or any problem for you to make your degice alive again. You could do that how often you will.
now i assumed it was the same with mi a2 that it would write rom the same but automatically because in lg you need to flash particular files in order to make that method work. I did flash mi a2 in edl and it did flash but the result was catastrophic. I got message about some partition something while flashing was a success. Then i thought how can edl fail even if oem is locked. It shouldnt work like that. Then i tried and tried to unlick bootloader through fastboot but its impossible. From start it was impossible to activate those settings. Then now i figure it out that it must do something with project treble and those 2 partitions. Is there any way to make this phone alive again?? Is there any way to flash partitions and partitions table manually
P. S I flashed it with what i thought was the anwser about my problem. I flashed it with mi x6 recovery rom from xda which made whole situation worse. Now i dont even have adb option nor do i have option to roll back to stock.
Just for comparison, in google pixel phone you dont even need unlocked bootloader or anything for that matter to flash pixel phone as long the rom is stock rom. Adb sideload works flawlessly
Any help is appreciated

Phone freezes 1sec after welcome screen, cant flash to fix

Hey guys,
just received this phone from a friend and am trying to fix it.
I can boot into system, which crashes about 1sec after displaying the first welcome animation after the boot screen and just reboots then.
I can also boot into Recovery and Fastboot but the bootloader is LOCKED. To unlock it I would have to first add the account in developer settings, but I cant reach that screen at all.
What are my options here? Flashing official roms via MIFlash is not doing anything (4sec flash, green success message but no reboot, and no change) and I cant flash anything else due to the locked BL?!
Ordinary folk can't flash fastboot ROMs with a locked bootloader. It can only be done by EDL flashing, which requires an authorised account.
You need to open the back and use the test pin method to put the phone in EDL mode. The location of the pins are near the battery, a YouTube video will show you the exact location and which pins to bridge.
Despite numerous guides suggesting it's possible for anyone to EDL flash the phone using Qualcomm tools, I've never yet heard of anyone getting it to work. The only way to EDL flash is via an authorised account. You will need to ask on the K20 Pro telegram group for details of someone who has an authorised account. Depending on who you find, you'll need to pay between $20 - $40 US. They will then arrange a time with you when they can remote onto your PC and flash the phone for you, with their account.
I gave the same advice on here a couple of weeks ago and they found someone to do it for $22 fairly quickly.
[Bricked] TWRP doesn't mount flash drive, PC doesn't recognise in fastboot, TWRP doesn't work with MTP
I've wiped my phone, no realising TWRP doesn't actually work with MTP or a flash drive. I've been using the flash drive when it was booted, before the wipe. So the port is fine. Flashing a recovery via fastboot just leads to an infinite loop of...
forum.xda-developers.com

Categories

Resources