Related
So I was running a custom ROM for a while and decided to switch back to the stock ROM. After doing that, I flashed the stock recovery so that I could install the OTA update from version 4.28.502.2 to version 6.20.502.5. During installation, the phone got stuck in a bootloop, so I wiped the cache and tried to start it again. After that didn't work, I factory reset it (in the bootloader, and then in recovery after it didn't work), and it still doesn't work. ADB and fastboot doesn't detect my device even though I had USB debugging on before I tried to update it (I'm guessing that the factory reset disabled that?). I can access the bootloader and recovery, and my phone has an unlocked bootloader with S-On. I have the AT&T HTC One M8 if that helps. Can someone help me please?
Hi,
Can you go to boot loader and then connect your phone into your computer after that you flash the recovery like TWRP, wipe all the data and reflash your rom, you can find it on XDA. After that you have to find the correct recovery for your device (see the website of Mike1987), find the correct recovery for your device and then flash the stock recovery and it have to work. Waiting for your news.
Have a nice day
BelDev said:
Hi,
Can you go to boot loader and then connect your phone into your computer after that you flash the recovery like TWRP, wipe all the data and reflash your rom, you can find it on XDA. After that you have to find the correct recovery for your device (see the website of Mike1987), find the correct recovery for your device and then flash the stock recovery and it have to work. Waiting for your news.
Have a nice day
Click to expand...
Click to collapse
I'm saying that my computer doesn't recognize my phone, and that's why I can't flash a custom recovery like TWRP
Have you got the right drivers installed, have you tired another hub ? Is your battery fully charged ?
BelDev said:
Have you got the right drivers installed, have you tired another hub ? Is your battery fully charged ?
Click to expand...
Click to collapse
Yes, I have the right drivers installed. Yes, I have tried a different USB port. Yes, my battery is fully charged.
Try to uninstall the drivers and download the HTC drivers, fastboot and adb from Internet and try again. Do you have another PC? Because one time i have got the same problem than you and when i take another PC it's worked.
BelDev said:
Try to uninstall the drivers and download the HTC drivers, fastboot and adb from Internet and try again. Do you have another PC? Because one time i have got the same problem than you and when i take another PC it's worked.
Click to expand...
Click to collapse
The drivers fail to install everytime, and I've tried on three different PCs
Your problem is not the phone cause it detected by the PC but the drivers failed to detect you HTC. Can you say if you boot your phone in the boot loader, the phone show you if is in boot loader connected by usb or not?
BelDev said:
Your problem is not the phone cause it detected by the PC but the drivers failed to detect you HTC. Can you say if you boot your phone in the boot loader, the phone show you if is in boot loader connected by usb or not?
Click to expand...
Click to collapse
In fastboot on the phone, it shows that it is connected with USB, but ADB says that there is no device connected
Jhaleefi said:
In fastboot on the phone, it shows that it is connected with USB, but ADB says that there is no device connected
Click to expand...
Click to collapse
adb won't work on bootloader/fastboot mode. Only fastboot does.
When on fastboot, type command fastboot devices, do you get your device serial no. ?
On bootloader/fastboot, what is x the OS-x.xx.502.x now ?
See : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
ckpv5 said:
adb won't work on bootloader/fastboot mode. Only fastboot does.
When on fastboot, type command fastboot devices, do you get your device serial no. ?
On bootloader/fastboot, what is x the OS-x.xx.502.x now ?
See : http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
Click to expand...
Click to collapse
I followed the instructions in that link, and everything works perfectly now. It's updated to 6.20.502.5. Thanks
Jhaleefi said:
I followed the instructions in that link, and everything works perfectly now. It's updated to 6.20.502.5. Thanks
Click to expand...
Click to collapse
Seems like your main issue was not properly using fastboot mode for fastboot, and realizing that adb doesn't work in bootloader mode? That, and having the proper firmware and RUU files.
I have a two phones.
Mi Max 3/32 : Global 8.1.6.0. I recieved OTA to 8.2.1.0. Start downloading, on 40%+- phone freeze and reboot. Stuck on MI logo and dont boot. Dont show powered by android. Just mi logo.
Then i flash 8.2.1.0 trough MiFlash, bootloader locked, and... Same situation. Stuck on bootlogo. I Flash china rom, i flash global, flash older version. Come on Xiaomi! What wrong with you?!
Okay. Story #2
Mi max pro 3/64. Global 8.0.3.0. I downloading OTA, press instal, phone reboot and go install update. Ok. After this process, phone boot and... Cycle reboot. Again and again. On launcher, on setup wizards, on mi logo. Everywhere. Hmmm, okay, i open miflash repeat all as in story #1. Not effect. Zero. Cycle reboot. How?!
I dont know.
Both phones not bricks. But and dont work.
Debugging on usb is a necessary? I dont activated bcaz my phones dont booted. Funny, yeah.
Can it connect via adb?
Sent from my MI MAX using Tapatalk
RAMBO29 said:
Can it connect via adb?
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
yes
If it can connect via adb, flash via EDL mode and see.
If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom
IndDoc said:
If it can connect via adb, flash via EDL mode and see.
Click to expand...
Click to collapse
hmm, for this it is necessary unlock boot?
SubwayChamp said:
If you are on miu you must check developer settings cause miui time to time unchecks option oem unlocking (in my case two times) for this reason ever i look at this and allow usb debugging always must be allowed and look at dev options is absolutely necessary to correct flash of roms, may be you are rooted when you tried to update and system cannot update by this way (device itself or autoupdate). to solve try first installing same version through fastboot, probably yet you don`t loose your data. but you must select option "flash_all_except_storage" from your unpacket zip rom
Click to expand...
Click to collapse
okay,
I did so. flash firmware and immediately bootloop. no root.
Dark_Eyes said:
hmm, for this it is necessary unlock boot?
Click to expand...
Click to collapse
Not required if you're going to flash the stable version.
IndDoc said:
Not required if you're going to flash the stable version.
Click to expand...
Click to collapse
sorry my mistake, i try but fastboot devices comand work (see device), adb ... not.
flash via fastboot
FAILED (remote: device is locked. Cannot erase).
need to unlock, yep?
That's not EDL, that's fastboot. See here for a guide how to use EDL mode.
IndDoc said:
That's not EDL, that's fastboot. See here for a guide how to use EDL mode.
Click to expand...
Click to collapse
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE
Dark_Eyes said:
i know about that. but my phones flashing via miflash (edl mode, Qualcomm HS-USB QDLoader 9008) and no boot (mi logo or mi logo plus powered by android stuck 5-10-15-55 mins)
why? i dont know.
upd. It's a MIRACLE. one phone (3/32) is ALIVE
Click to expand...
Click to collapse
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.
IndDoc said:
Good! Make sure you are flashing the right verison. If your phone is stuck on 'powered by android' screen, it's a good sign. It means your phone will eventually boot up.
Click to expand...
Click to collapse
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Sounds like you have a hardware problem. Take it to a service center.
IndDoc said:
Sounds like you have a hardware problem. Take it to a service center.
Click to expand...
Click to collapse
agree, it seems. thank you.
Dark_Eyes said:
this is not quite right.
2nd phone flashing, booting, setup wizard (white screen, w\out miui 8 logo, freeze, reboot. cycle.)
1st phone working 5-7 min, freeze and reboot, stuck mi logo w\out powered by android. damn.
Click to expand...
Click to collapse
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you
SubwayChamp said:
Well, let me tell the way that I flash exactly, for me works perfectly, EDL never work for me. Flash for fastboot couldn't work properly if you place files in any side of your PC. I place adb folder in main disk, in my case c:, unpack all the files of you rom beside the 4 files of adb in same folder (adb has created a path in system environment) then in mode fastboot with usb plugged device (how you loosed your data) right click on "flash_all" for rom can repair your partitions. (I don't remember now if appears with right click option to execute like an administrator better) don't use meanwhile your pc. may that help you
Click to expand...
Click to collapse
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?
Dark_Eyes said:
correct me:
you reboot to fastboot (vol- + power), rabbit logo, connect usb w\out pressing any buttons
create folder adb (4files adb + all files of firmware w\out folder image)
and run flash all
unlock boot required?
Click to expand...
Click to collapse
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom
SubwayChamp said:
Yes, mode fastboot in device with any trick like EDL, just connect to pc, no unlock bootloader required but must be an stock rom, fastboot image rom
Click to expand...
Click to collapse
after i click flash all, window appears 1 sec and all. no effect. what wrong?
Dark_Eyes said:
after i click flash all, window appears 1 sec and all. no effect. what wrong?
Click to expand...
Click to collapse
Recogniced device?, type first fastboot devices to be sure
So, a few months ago I rooted my device with twrp and then installed magisk manager... A few days later the manager stopped working and I got tired of not being able do do nothing so I tried to unroot. I used mi flash to flash the daisy rom and it didn't work so I tried to load to the twrp app and flash through there. Didn't work either. From then on every time I boot the device it shows the message "the system has been destroyed" and Bc of that I searched for solutions. I kinda found one. I boot to fastboot mode and with the platform tools I write on the command line ". /fastboot devices" and then it shows my device. After I write ". /fastboot boot continue" and it starts booting the device and it has worked for like 2 months but 2 days ago I had to reboot my device Bc it started to freeze but when I load to fastboot mode and plug it to the pc it show a prompt saying "the device is not recognized" and the device reboots to the message "system has been destroyed". Pls help, I've searched everywhere and didn't find any solution
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Os_Herdz said:
Are you have your bootloader unlocked? I guess no, the most "easy" solution for your problem is test point , never fail, you need to download Qualcomm drivers (search in Google) open your device connect your device, your phone need to be recognized like 9008 in manager drivers of your PC then flash stock room in mi flash (flash all option) my recommendation is flash 10.0.13.0 or 10.0.18 version of stock rom, good luck.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
0flip3 said:
Yes, my bootloader is unlocked, and is not recognized on the miflash tool.
I cant't even boot the phone to edl mode
Click to expand...
Click to collapse
you are trying to get to edl mode by typing command "fastboot oem edl" when phone is in fastboot?
Hello. I decided today to clean install the Pixel Experience 10 rom. I previously had a Pixel Experience 9.0 Pie. I did the following:
1. Booted into TWRP and selected Format Data
2. Everything is deleted, so it's time to flash a new rom. The guide says to go Advanced/ADB sideload and enter a command.
3. Command is not working. My phone is connected to the computer but it's not recognized. I can't even manually transfer it to the phone so i can install it via TWRP.
So i enter fastboot. Phone is recognized. When i type fastboot devices i get this:
Code:
C:\adb>fastboot devices
42abad9b fastboot
If i try to flash again a TWRP, my phone disconnects and it asks to reboot the phone by pressing a volume button. And i am stuck here. Nothing i can do. Any suggestions? I haven't done anything unusual. I am truly desperate. Any help will be appreciated.
naruto14 said:
Hello. I decided today to clean install the Pixel Experience 10 rom. I previously had a Pixel Experience 9.0 Pie. I did the following:
1. Booted into TWRP and selected Format Data
2. Everything is deleted, so it's time to flash a new rom. The guide says to go Advanced/ADB sideload and enter a command.
3. Command is not working. My phone is connected to the computer but it's not recognized. I can't even manually transfer it to the phone so i can install it via TWRP.
So i enter fastboot. Phone is recognized. When i type fastboot devices i get this:
If i try to flash again a TWRP, my phone disconnects and it asks to reboot the phone by pressing a volume button. And i am stuck here. Nothing i can do. Any suggestions? I haven't done anything unusual. I am truly desperate. Any help will be appreciated.
Click to expand...
Click to collapse
Hi !
Did you bypass ARB with dummy.img before you flashed TWRP?
Do you use win 10, if you are change usb or use usb hub. If that doesn't help use win 7.
follow the link for details
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Good luck and stay safe.
drnightshadow said:
Hi !
Did you bypass ARB with dummy.img before you flashed TWRP?
Click to expand...
Click to collapse
I already had TWRP from long ago. And i didn't even try to flash a new ROM. I just formatted Data. I have the TWRP version 3.3.1-0. But as i said, PC does not recognize phone in TWRP and i can't adb sideload any ROM because of it.
naruto14 said:
I already had TWRP from long ago. And i didn't even try to flash a new ROM. I just formatted Data. I have the TWRP version 3.3.1-0. But as i said, PC does not recognize phone in TWRP and i can't adb sideload any ROM because of it.
Click to expand...
Click to collapse
Go back to previous version of TWRP(latest is buggy) or use OrangeFox recovery.
But still if you lose custom recovery you need again start over and bypass ARB.
And check if your bootloader is still unlock.
drnightshadow said:
Go back to previous version of TWRP(latest is buggy) or use OrangeFox recovery.
But still if you lose custom recovery you need again start over and bypass ARB.
And check if your bootloader is still unlock.
Click to expand...
Click to collapse
I can't go to a previous version of TWRP. I can't flash any recovery via fastboot because of the problem i said at the first post. I somehow managed to boot into some previous versions of TWRP via a tool called TOOL_ALL_IN_ONE, but nothing changed. I had the same exact problems.
How will i check in my current status if bootloader is still unlocked?
naruto14 said:
I can't go to a previous version of TWRP. I can't flash any recovery via fastboot because of the problem i said at the first post. I somehow managed to boot into some previous versions of TWRP via a tool called TOOL_ALL_IN_ONE, but nothing changed. I had the same exact problems.
How will i check in my current status if bootloader is still unlocked?
Click to expand...
Click to collapse
Use this and post the result...
Code:
fastboot oem device-info
So you managed to get TWRP via TOOL_ALL_IN_ONE, ... when you are in TWRP flash TWRP again via TWRP or better flash OrangeFox Recovery(use SD CARD or adb push - for more info google it for adb commands), than reboot it directly into recovery again by TWRP option reboot to recovery... and now you can flash your ROM.
So make it simple
1st time you'll boot in TWRP by TOOL_ALL_IN_ONE,
than you'll flash recovery via TWRP and make it permanent,
Than you'll directly reboot to recovery via TWRP,
now you can wipe and flash your ROM.
Happy ending :highfive:
The problem was that i couldn't use ADB sideload because the phone wasn't recognized by the computer. And i fixed it in a very weird way, by connecting the phone to the PC monitor's USB hub and that way the phone was discovered by the computer. So i fastbootted the latest TWRP and then easily transferred the ROM i wanted to flash via TWRP. It's crazy that i spent all day just to connect the phone to a USB hub so it could work...
naruto14 said:
The problem was that i couldn't use ADB sideload because the phone wasn't recognized by the computer. And i fixed it in a very weird way, by connecting the phone to the PC monitor's USB hub and that way the phone was discovered by the computer. So i fastbootted the latest TWRP and then easily transferred the ROM i wanted to flash via TWRP. It's crazy that i spent all day just to connect the phone to a USB hub so it could work...
Click to expand...
Click to collapse
I'm glad that you fixed your phone :highfive:
I told you usb hub is the solution :laugh: yeah win10 sh*t mess with usb and all other stuff :crying: its a total [email protected]'ll never gonna use it.
nicee your phone is alive now ....
Good luck and stay safe.
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