Xiaomi mi a2 - bootloop after erase system - Xiaomi Mi A2 Lite Questions & Answers

After using the '' adb erase system '' command my phone got a booloop without being able to turn on fastboot... :crying:

Hasanoes said:
After using the '' adb erase system '' command my phone got a booloop without being able to turn on fastboot... :crying:
Click to expand...
Click to collapse
So technically you're expecting to boot in a system that you just erased...
Why the hell are you even trying to do anything that you don't know what they do... What did you expect the erase system command do? Give you free pancakes?
Check the forums on how you can reflash the system via ADB or via Mi Flash Tool. And next time, stay away from modding or stray commands if you have no sense of the meaning of the commands and the result you're going to get.

Related

Soft Bricked Nexus....other threads not helping...

My CDMA Nexus froze....battery pull, boot looped. Recovery restore backup....."error while restoring /data"
Been trying to get back to stock ever since and I can't get the fricken ADB command prompt stuff to work.
I have installed drivers like 10 times, and it shows "Android phone" in device manager when the phone is plugged in with fastboot on.
Everytime I try and do the fastboot commands it just says "error: device not found"
Does it let you mount usb so you can stick a new rom file on it?
Sent from my Galaxy Nexus using Tapatalk 2
edit/disregard
does "fastboot devices" reveal your phone?
eqjunkie829 said:
Does it let you mount usb so you can stick a new rom file on it?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It doesn't show up as a drive, just in the device manager as Android ADB Interface.
I just restarted my computer to see if the drivers needed that....this time I ran the 'adb reboot bootloader' and I got daemon not running. Now starting on port 5037. Daemon started successfully. Then it still said error: device not found
animal24 said:
Hold both volume rockers down and start your phone ... then in your command prompt
fastboot flash bootloader bootloader-toro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.fc05.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.fa04.img
fastboot reboot-bootloader
fastboot -w update image-mysid-imm76k.zip
fastboot reboot-bootloader
then just to be sure boot into recovery and wipe.
Click to expand...
Click to collapse
This
Does it show as fastboot devices?
Click to expand...
Click to collapse
Yeah.....it returns the phone serial number....
So I dunno what the deal is.
biscuitownz said:
This
Click to expand...
Click to collapse
yeah...I know....that has been my goal for the past 4 hours.
The command prompt wont push to a device it doesn't find...
Cadillac Kid said:
yeah...I know....that has been my goal for the past 4 hours.
The command prompt wont push to a device it doesn't find...
Click to expand...
Click to collapse
if the serial number comes up then it should be able to push the factory images back into it.
try fastboot erase userdata
IINexusII said:
if the serial number comes up then it should be able to push the factory images back into it.
try fastboot erase userdata
Click to expand...
Click to collapse
that did it.........weird. THANKS!!!!

How do I write a batch to execute these commands?

I'd like to make a batch file to execute a series of commands like below.
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
I flash a lot so I wanted to make things easier, could anyone help me out please?
I once knew a thing or two, something about echo and such, but that was a long time ago.
Thanks!
D3VICE said:
I'd like to make a batch file to execute a series of commands like below.
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
I flash a lot so I wanted to make things easier, could anyone help me out please?
I once knew a thing or two, something about echo and such, but that was a long time ago.
Thanks!
Click to expand...
Click to collapse
START fastboot flash boot boot.img etc...
save it as .bat in your fastboot folder
should work
since there is no wait-for-device on fastboot, you'd probably have to do something like this...
Code:
adb reboot bootloader
sleep 15
fastboot flash boot boot.img
fastboot erase cache
Otherwise the adb command would return the moment the command is sent to the phone and it'd try and execute the fastboot flash command before the phone is actually in fastboot.
Squirrels said:
since there is no wait-for-device on fastboot, you'd probably have to do something like this...
Code:
adb reboot bootloader
sleep 15
fastboot flash boot boot.img
fastboot erase cache
Otherwise the adb command would return the moment the command is sent to the phone and it'd try and execute the fastboot flash command before the phone is actually in fastboot.
Click to expand...
Click to collapse
Makes sense, thanks I will try, hope it works.
Thanks to both of you !
I would use a pause command in the batch script on Windows so that the user can make sure that the phone is actually in fastboot USB mode prior to running fastboot. Sleep is not provided in the default command set on Windows so won't work.
Having said that ignore the above para if your script is running on an Unix environment.
Code:
adb reboot bootloader
timeout /t 10
fastboot flash boot boot.img
fastboot erase cache
try this one, timeout is built in since windows 7 i think
hmm my Windows 7 had sleep, must have been installed by a third-party app then if it is not included by default. Noted.
Squirrels said:
hmm my Windows 7 had sleep, must have been installed by a third-party app then if it is not included by default. Noted.
Click to expand...
Click to collapse
The windows resource kit must have been installed on your PC? Anyway, it can be downloaded from here.
Any idea how to do something like this?
After running the batch it shows a message saying something like.
Please plug in your phone and enable USB-mode and press any button when finished
Click to expand...
Click to collapse
After plugging in the phone you press the button and it executes the bootloader command, then it says.
Please press any button to flash boot.img
Click to expand...
Click to collapse
You press a button, it finishes flashing and then gives a message saying.
Please press any button to erase the cache
Click to expand...
Click to collapse
After pressing a button it erases the caches and displays something like
''Flashing successful, please reboot into recovery to flash your ROM.''
Click to expand...
Click to collapse
I remember needing echo commands for this to work, but all of my attempts have failed .

Need Help For switching rom from china to global

hi devs
i flashed accidentially Chinese recovery rom on my whyred now i m unable to switch from Chinese to global version as i tried every method fastboot,recovery,qfil,mi flash and edl mode i mean every possible way but all in vain as every method ended with error and my fastboot command is locked.
so what can i do please suggest me
it's Chinese miui 11
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
aliasgertaj said:
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
Click to expand...
Click to collapse
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
SubwayChamp said:
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
Click to expand...
Click to collapse
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
aliasgertaj said:
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
Click to expand...
Click to collapse
Fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on Developer section, i.e. USB debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
subwaychamp said:
fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on developer section, i.e. Usb debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
Click to expand...
Click to collapse
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
aliasgertaj said:
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
Click to expand...
Click to collapse
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
SubwayChamp said:
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
Click to expand...
Click to collapse
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
drnightshadow said:
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
Click to expand...
Click to collapse
thanks for response bro
i did it under developer option and trusted my computer connection also and install adb fastboot devices many time changed cable and port but nothing happen. i tried fastboot files of china stable rom but it also doesn't worked
aliasgertaj said:
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
Click to expand...
Click to collapse
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
SubwayChamp said:
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
Click to expand...
Click to collapse
i m frustrated now tried all the thing tried official flash tool official build but even official build by miflash official latest tool unable to flash image
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
aliasgertaj said:
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
Click to expand...
Click to collapse
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
drnightshadow said:
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
Click to expand...
Click to collapse
ok bro i will try today with another pc and update you
aliasgertaj said:
ok bro i will try today with another pc and update you
Click to expand...
Click to collapse
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
aliasgertaj said:
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
Click to expand...
Click to collapse
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
drnightshadow said:
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
Click to expand...
Click to collapse
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
aliasgertaj said:
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
Click to expand...
Click to collapse
TWRP can't bypass encryption, when you have no access to read data (0mb) then you have to format it, to avoid that is always recommended use OrangeFox, just for future reference, if you understand that you can flash OrangeFox through TWRP for better experience.
Also you can use this tool to help you to automate some stuff https://github.com/Szaki/XiaomiADBFastbootTools

Soft bricked, need help.

Hi guys, in short, I wanted to install the latest xiaomi.eu MIUI 12.5 beta on a Mi 10T Pro, european version.
What I did was: unlocked bootloader, flash latest TWRP 3.5 beta version, I think I booted the device normally after this...
Then went back to TWRP and flashed the Zip file right away, don't know what I wiped after the install.
All in all the device won't boot now, I'm stuck to either twrp or fastboot.
Problem is I cant flash a fastboot stock rom, says it's successful but the flashing process is like 2 seconds, i can't copy a recovery rom to the internal storage, i think Data partition got corrupted.
Can't wipe Data partition, there is a FBE decription error, and says unsupporter file system auto.
Does anyone have any idea what can I try.
Already tried to change Data file system to ext2 then back to ext4 but no luck.
PC recognizes the phone as a media device, I can see the Internal storage icon, but can't see any files nor can I copy anything to it.
Tried flashing the stock rom with mi flash tool and with command prompt too.
Any advice is welcome.
WSSRoach said:
Hi guys, in short, I wanted to install the latest xiaomi.eu MIUI 12.5 beta on a Mi 10T Pro, european version.
What I did was: unlocked bootloader, flash latest TWRP 3.5 beta version, I think I booted the device normally after this...
Then went back to TWRP and flashed the Zip file right away, don't know what I wiped after the install.
All in all the device won't boot now, I'm stuck to either twrp or fastboot.
Problem is I cant flash a fastboot stock rom, says it's successful but the flashing process is like 2 seconds, i can't copy a recovery rom to the internal storage, i think Data partition got corrupted.
Can't wipe Data partition, there is a FBE decription error, and says unsupporter file system auto.
Does anyone have any idea what can I try.
Already tried to change Data file system to ext2 then back to ext4 but no luck.
PC recognizes the phone as a media device, I can see the Internal storage icon, but can't see any files nor can I copy anything to it.
Tried flashing the stock rom with mi flash tool and with command prompt too.
Any advice is welcome.
Click to expand...
Click to collapse
LOG IN IN MI FLASH
jjgvv said:
LOG IN IN MI FLASH
Click to expand...
Click to collapse
What do you mean?
how do you flash stock rom 2 secs?
jjgvv said:
how do you flash stock rom 2 secs?
Click to expand...
Click to collapse
I think it doesn't fully flash, says it's successful but nothing really happens.
use what flash tool?
jjgvv said:
use what flash tool?
Click to expand...
Click to collapse
Tried latest from xiaomis website but that gives error, so i tried to download one from another website, says its latest version too
have you log in in that flash tool?
jjgvv said:
have you log in in that flash tool?
Click to expand...
Click to collapse
There is no way to log in, aren't you talking about the mi unlock tool?
mi flash?
jjgvv said:
mi flash?
Click to expand...
Click to collapse
Yes, there is no option to log in to mi flash tool
fastboot erase data then
jjgvv said:
fastboot erase data then
Click to expand...
Click to collapse
How do i do that?
WSSRoach said:
How do i do that?
Click to expand...
Click to collapse
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
jjgvv said:
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
Click to expand...
Click to collapse
Will try as soon as i get near a PC
jjgvv said:
go into fastboot and Type fastboot erase data in the fastboot cmd prompt
Click to expand...
Click to collapse
Sadly it fails
WSSRoach said:
Sadly it fails
Click to expand...
Click to collapse
how does it fail
jjgvv said:
how does it fail
Click to expand...
Click to collapse
I typed fastboot erase data, i get: FAILED (remote: Check device console)
Code:
fastboot -w
or
Code:
fastboot erase userdata
is the correct command. Now, if this fails, find lr-twrp, flash that, reboot, wipe data, and try again... And you have to do fastboot commands from fastboot, not from twrp...
calinorg said:
Code:
fastboot -w
or
Code:
fastboot erase userdata
is the correct command. Now, if this fails, find lr-twrp, flash that, reboot, wipe data, and try again... And you have to do fastboot commands from fastboot, not from twrp...
Click to expand...
Click to collapse
this looks like it worked, still now says unable to mount storage when trying to format data from twrp, but thats a step ahead...now it says in yellow )
I have an idea to flash lineage os recovery with fastboot, might that work?

Recovering data on a DEAD Redmi Note 8 PRO

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

Categories

Resources