Hi,
I bricked my Xiaomi Mi 6.
My phone was bought in china, I unlocked bootloader and flashed global version.
Lately I flashed TWRP and Magisk.
Than I wanted to come back to stock and lock bootloader, so I flashed global ROM, everything was fine, stock recovery came back, so I used command "fastboot oem unlock" (I couldn't use Mi Flash, because it just stops working, when I'm trying to do anything). Than phone kept starting only to fastboot. I could also start phone to recovery, but not to system.
So, using MI Flash Unlock I unlocked bootloader again. And now I still can only enter to fastboot or recovery, not to system. And, my PC doesn't see the phone. I don't see the phone after typing adb devices to Command Prompt, also Mi Assistant doesn't see phone. I wiped everything through recovery, but it didn't help.
Please, help me with unbricking the phone. It doesn't need to be with locked bootloader or so, I just want phone to work...
I don't think it is bricked in fastboot the command should be fastboot devices not adb devices try that command
Hopefully someone here has more knowledge to help you sort it out.
You should format your userdata from fastboot that's why you can't boot into the system.
I suggest you to read this https://xiaomifirmware.com/downloads/download-install-drivers-xiaomi-mi6/ page before anything and then get XiaoMiFlash from that page, install it. It will also install fastboot and adb drivers for you.
Then I suggest you to use this https://forum.xda-developers.com/showthread.php?t=2317790 adb & fastboot tool since it's easy to use.
After getting miflash ready with the drivers and also the tool from the second link,
Reboot to fastboot and type
fastboot devices
After seeing your device type
format userdata
Then find a twrp image if you'd like to install any custom rom and install it from fastboot (you can find how to do it in their respective threads) or download miui from miui site then follow the instructions there go back to stock. But in case of the latter you may not to select lock bootloader option in miflashtool in case you may want to experiment with custom roms in the future.
Related
So I tried to flash another rom by flashing TWRP and unlocking the bootloader, which worked and I then had installed Freedom Os. Then I locked the Bootloader to get the Message away, but know when you charge it or turn it on it is in an boot loop which repeats the Oneplus Logo what you normally see, but very short and after that it bobrates turns the screen off and it atart again. Or I can go into fastboot mode, but when I try to go into the recovery, it goes into the Boot Loop again. Is there a way to get the Original OS back? Ive already dopwnloaded it but I cant get in on there. Can you tell me how to fix it on my own?
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 3 > METHOD 1
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
anup807 said:
If you can access fastboot mode, connect the phone to a PC, then go to ADB and erase recovery using the command " fastboot erase recovery" and install TWRP 3.0.4-1 using the command " <fastboot flash recovery <recovery.zip/img> again.
Once you do that, boot into TWRP, go to wipe and wipe everything. Once you do that, transfer the stock OOS into the internal memory using copy-paste , then go to install , select the transferred file to install the OS or else go to advance setting in TWRP and select adb sideload and use the command "adb sideload <filename.zip>".
This should install the OS on the phone.
If you want to go complete stock, then you also need to install the stock recovery. Search the forum to get the relevent files or else you can download it from the OnePlus website and later on update to latest OS via OTA.
NEVER EVER LOCK THE BOOTLOADER , IF YOU'RE USING ANY ROM OTHER THAN STOCK OS AND STOCK RECOVERY
Click to expand...
Click to collapse
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
revedar said:
Can you tell me how to go to adb? When doing it while being in fastboot I get the error "remote: Partition erase is not allowed"
Click to expand...
Click to collapse
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
anup807 said:
Download Universal ADB software, download the latest version and install it.
TWRP 3.0.4-1
Official Oxygen OS 4.0.3
Official Recovery
Connect your phone to the PC and then navigate to installed folder, right click holding SHIFT key and select "Open command window here"
Inside command window type
adb devices
If all the drivers are installed properly, you should see you're device ID here.
then type
adb reboot bootloader
your phone will enter fastboot mode.
then type
fastboot devices
again you should see you're device ID here.
then follow the instruction , i've given earlier.
Click to expand...
Click to collapse
So i've downloaded the software, installed the driver and typed in cmd adb devices "adb devices List of devices attached" is returned, so it seems like there is going something wrong. Is it because the Driver is installed wrong or because "target reported max download size of 440401920 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.551s"
This is returned when trying to flash. Do I have to be in fastboot mode or something else to be able to follow your instructions? In Fast Boot is written that the Device State is locked and Secure Boot is enabled. I messaged Oneplus and hope they have a solution which can just unlock the Bootloader when being in fastboot mode, so everything is fine again. I hope you can help me, but I still wanna say thank your for now
Errr... fastboot can unlock the bootloader. fastboot oem unlock
emuandco said:
Errr... fastboot can unlock the bootloader. fastboot oem unlock
Click to expand...
Click to collapse
Thank you, but it dont works because i forgot to re-enable the oem modification and usb debugging in freedom os, maybe there is an option to do this without having this enabled but I didnt found it. So I wait for a helpful answer from somebody here or from Oneplus, I consider sending my smartphone to oneplus to let them repair it if I cant do it. Just saying that modding an S3, Asus transformer pad and nvidia shield is way easier.
never ever relock your bootloader while you in custom OS
oopstairs said:
never ever relock your bootloader while you in custom OS
Click to expand...
Click to collapse
Thank you for not helping me
revedar said:
Thank you for not helping me
Click to expand...
Click to collapse
Yeah I'm sorry I can't help you in your case. I'm just stating the fact. Sorry if I offended you.
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
emuandco said:
Shouldn't it still be possible to reflash the properly signed official updates? TBH I never had such a problem and thus never had to cope with it. Same with recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img Try flashing this one with fastboot. It's the official one. By flashing this one you might fix your stuff over adb sideloading the official full update zips.
Click to expand...
Click to collapse
I already tried to do this, but the console returns something like permission denied.
anup807 said:
Try the unbrick guide provided in the 2nd post to your query. It should definitely help. Better contact OnePlus tech2 support and they'll flash your phone for you. They're really helpful.
Click to expand...
Click to collapse
The MSM Software disconnects the smartphone while the process works
U cannot flash in adb while the bootloader is locked, u can not unlock the bootloader unless u can access ur OS, I am not sure y people was trying to get u to flash via fastboot the answer was provided to u in the 2nd post
^^^ This!
It's pretty much obvious fastboot flash will not work with a locked bootloader.
It's pretty obvious unlocking the bootloader will not work, while one can not access the OS.
Unbrick tool is the only option to bring it back to life, or sending it for RMA. If unbrick tool fails, try using different drivers and make sure it is connected with the stock cable (I've only tried with a Nilkin cable besides the stock one, which always failed at different stages during the process).
Not even sure drivers must be installed manually, I've never done that myself on Windows 10, as they were automatically installed (3 different's PC's, both on x86 and x64).
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
rk2612 said:
Which version of stock firmware did you last have? If it was 4.0.1 or earlier, then you can use
Code:
fastboot oem 4F500301
to issue a flash command even without unlocking the bootloader. If you are on that, then use that command and flash stock recovery and then flash stock zip.
Click to expand...
Click to collapse
I had the most recent update installed. Is there a similar command at the moment?
revedar said:
I had the most recent update installed. Is there a similar command at the moment?
Click to expand...
Click to collapse
Don't think so.
Hello guys!
I just unlocked my Redmi Note 5, and I want to flash it to pixel experience 8.1.0 Oreo.
I've been reading around a lot about the antirollback thingy on the RN5, and all those risks to brick the phone etc.
How can I make sure to flash the phone without risking to brick it?
Before you tell me to read around (which I have), I just want to confirm if these are the right steps for me.
I have firstly enabled USB debugging.
I downloaded minimal ADB and fastboot tool and ran the code "Fastboot Devices" it found my device due I get some numbers etc...
In Fastboot I also wrote "Fastboot Getvar Anti" and got the code 4. So I'm guessing my antirollback thingy is 4...
Sooo here is the steps I want to do next, correct me if I'm wrong.
1. I have downloaded TWRP version 3.2.3.2 from this website: https://eu.dl.twrp.me/whyred/
And I downloaded LazyFlasher from this website: https://androidfilehost.com/?fid=890129502657590339.
I got that LazyFlasher link from here: https://www.google.com/amp/s/forum....aomi-redmi-note-5-whyred-unlock-t3778049/amp/
2. Now since my antirollback is 4 (and correct me if I'm wrong here), my next step now is to boot the phone I "Fastboot" by holding volume down button + Power button. And then write in the console from the computer "Fastboot boot TWRP.img".
Here is what I'm wondering. Is it "Fastboot boot TWRP.img" or "Fastboot flash TWRP.img"??
3. Let say that it's "Fastboot boot TWRP.img". The next step from here is to install the TWRP image inside TWRP recovery. And after when I have installed TWRP and should flash to LazyFlasher. After that reboot and boot up to TWRP recovery again.
4. Now since I have TWRP installed, I'm guessing everything is correct??
From here can I just wipe everything and flash to a custom ROM I have downloaded??
I have already downloaded Pixel experience 8.1.0. Or should I do something else?
5. If everything is correct, can I flash my kernel to derp kernel 4.2 even though I have Oreo 8.1.0??
https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996
Thank you!
In question 3 I believe it is "fastboot flash recovery twrp.img"
After I did this and flashed lazy flasher mine did not boot into two recovery but was replaced by stock recovery.
So the 2nd time I entered fastboot on the phone. Flashed twrp again but this time used fastboot command to enter twrp recovery.
I think it was " fastboot boot recovery twrp.img"
I then was in twrp on the handset and could flash my room
My previous phone was a Redmond note 3. I am new to deep so have not looked into what it is or what newer versions do do ill leave that for you.
prefor said:
Hello guys!
I just unlocked my Redmi Note 5, and I want to flash it to pixel experience 8.1.0 Oreo.
I've been reading around a lot about the antirollback thingy on the RN5, and all those risks to brick the phone etc.
How can I make sure to flash the phone without risking to brick it?
Before you tell me to read around (which I have), I just want to confirm if these are the right steps for me.
I have firstly enabled USB debugging.
I downloaded minimal ADB and fastboot tool and ran the code "Fastboot Devices" it found my device due I get some numbers etc...
In Fastboot I also wrote "Fastboot Getvar Anti" and got the code 4. So I'm guessing my antirollback thingy is 4...
Sooo here is the steps I want to do next, correct me if I'm wrong.
1. I have downloaded TWRP version 3.2.3.2 from this website: https://eu.dl.twrp.me/whyred/
And I downloaded LazyFlasher from this website: https://androidfilehost.com/?fid=890129502657590339.
I got that LazyFlasher link from here: https://www.google.com/amp/s/forum....aomi-redmi-note-5-whyred-unlock-t3778049/amp/
2. Now since my antirollback is 4 (and correct me if I'm wrong here), my next step now is to boot the phone I "Fastboot" by holding volume down button + Power button. And then write in the console from the computer "Fastboot boot TWRP.img".
Here is what I'm wondering. Is it "Fastboot boot TWRP.img" or "Fastboot flash TWRP.img"??
3. Let say that it's "Fastboot boot TWRP.img". The next step from here is to install the TWRP image inside TWRP recovery. And after when I have installed TWRP and should flash to LazyFlasher. After that reboot and boot up to TWRP recovery again.
4. Now since I have TWRP installed, I'm guessing everything is correct??
From here can I just wipe everything and flash to a custom ROM I have downloaded??
I have already downloaded Pixel experience 8.1.0. Or should I do something else?
5. If everything is correct, can I flash my kernel to derp kernel 4.2 even though I have Oreo 8.1.0??
https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996
Thank you!
Click to expand...
Click to collapse
I am trying to flash the LineageOS on my Redmi Note 5 Pro (whyred). Initially, I used Windows 10 for the Xiaomi Unlock Tool. However, the Xiaomi Unlock Tool did not detect my device. So, I used this tool https://www.xiaomitool.com/V2/ to unlock my bootloader and it unlocked instantly. Now, I am using Ubuntu 21.04 (I am more comfortable using the command line here) (with android-tools-adb and android-tools-fastboot packages installed) to try to flash TWRP first.
When I connect my device, adb devices can recognise it. Then I use adb reboot bootloader to enter into fastboot. Now, fastboot devices can recognise it too. The screen of the phone shows the fastboot icon.
But, the problem comes here. I use fastboot flash recovery twrp.img and I get this error
FAILED (Write to device failed (No such device))
Click to expand...
Click to collapse
Now, when I use fastboot devices again. I don't see my device. Another change I see is press any key to shutdown written on the top left corner of the screen of my phone.
USB debugging, USB debugging security, OEM debugging are all enabled. Bootloader is unlocked (as I see in the settings). The phone is updated to latest MIUI version supported officially. And I used the same laptop and method to flash TWRP in a Redmi 3S (land) some time back.
(Posted the same question on android.stackexchange.com also) (https://android.stackexchange.com/questions/238996/redmi-note-5-pro-unable-to-flash-twrp)
Something else I experienced is that after randomly trying to get this right again and again, the command fastboot flash recovery twrp.img did not terminate or fail and got stuck.
So, this was a duplicate. I used the 5th method here and it worked for me. https://forum.xda-developers.com/t/everything-about-anti-roll-back-whyred.3816219/
My Poco F3 is Global, but I've heard people say that re-locking global results into a brick. Is this true? I want to go back to stock MIUI and re-lock my phone.
Read this thread. https://forum.xda-developers.com/t/how-to-flash-a-stock-rom-alioth.4355797/
Yeah you can download a Fastboot ROM from xiaomifirmwareupdater.com & flash it through Mi Flash. By default Mi Flash will lock your bootloader.
But be careful to choose the right ROM for the right region & that the USB connection is stable.
Flashing ROMs is dangerous. Speaking from experience ...
Actually l unlocked Mi6x bootloader but didnt installed/flashed anything. It has China ROM. How to re-lock it?
sunny155 said:
Actually l unlocked Mi6x bootloader but didnt installed/flashed anything. It has China ROM. How to re-lock it?
Click to expand...
Click to collapse
"fastboot oem lock" in fastboot mode locks the bootloader.
This will also wipe your phone, so proceed accordingly.
Thank you! Worked perfectly
user0u said:
"fastboot oem lock" in fastboot mode locks the bootloader.
This will also wipe your phone, so proceed accordingly.
Click to expand...
Click to collapse
HI,
I would like to relock the bootloader on my Xiaomi Mi9T Pro and it's not a problem to lose the data because I changed my phone and transferred everything.
I already turned off find device and signed out Xiaomi account.
I just boot the phone in fastboot mode and digital on command prompt "fastboot oem lock"?
Does the phone restart by itself formatting everything?
I have the original ROM, TWRP and I don't have root.
Let me know if I've forgotten anything.
A thousand thanks.
bricca said:
HI,
I would like to relock the bootloader on my Xiaomi Mi9T Pro and it's not a problem to lose...
Click to expand...
Click to collapse
Yes, you can do that. The phone does everything itself after you enter the command.
Also remove your password. I don't know if it has any effect on anything but I remove it just in case.
You'll need to go out a number of actions in order to restore stock MIUI and lock the bootloader on your Xiaomi device. Please be aware that depending on the precise model of your Xiaomi gadget, these instructions may differ somewhat. If you follow them wrong, you risk bricking your device or encountering other problems. Be sure to move cautiously and pay close attention to the directions. Here is an overview:
Backup your data: Before continuing, make sure that all of your vital data has been backed up, since the operation might delete your device.
Download the MIUI stock ROM here: To locate the stock MIUI ROM for your particular smartphone model, go to the MIUI website or the Xiaomi forums. Your computer should download the ROM.
On your Xiaomi handset, go to Settings > About phone and repeatedly touch on the MIUI version to activate Developer options. This will allow USB debugging. Then, enable USB debugging by going to Settings > Additional settings > Developer options.
Unlock bootloader (if locked): If the bootloader on your device is locked, you must do so first. Visit the Xiaomi unlocking page and follow the steps there to accomplish this. Please be aware that removing the bootloader will erase all of the data on your device.
Install ADB and Fastboot: Install the Android Debug Bridge (ADB) and the Fastboot software on your PC. The platform tools are available for download from the official Android developer website.
To enter Fastboot mode on your Xiaomi smartphone, turn it off, then hold down the Power and Volume Down buttons at the same time until the Fastboot logo appears on the screen.
Connect your device to the computer: To connect your Xiaomi gadget to the computer, use a USB cord.
Flash the MIUI stock ROM: Go to the directory where the ADB and Fastboot utilities were installed on your computer by opening a command prompt or terminal window and selecting it. To see if your device is recognised, use the command: Continue to the next step if your device is listed. If not, check to see if the right drivers are installed.
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5