Develop Bugs

[BRICKED] Stuck in android 8.1 bootloop

I just bricked my phone :crying: :crying:
I wanna get back to the official rom, after trying android P (without make it work).
(the rom is from http://en.miui.com/download-354.html)
But I run the wrong script and take the flash_all_lock.img
And my device is stuck on android 8.1 bootloop (It boot, but i get an animated line loop ...)
Any ideas or tricks before i get it back to warranty ?
Thanks

Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.

BubuXP said:
Unlock bootloader and flash again. You can find a guide to unlock bootloader at the beginning of this guide.
Click to expand...
Click to collapse
But since I flashed the official rom with data whipe, I'm unable to go to dev option and enter OEM Unlocking .... And Fastboot respond me that my device is locked

Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem

droopeur said:
Seems like my only option left is to boot into EDL mode ...
But seems fastboot oem edl does not work I don't lnow how to handle the problem
Click to expand...
Click to collapse
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.

BubuXP said:
Have you tried to switch the active slot?
Try if it boots using
fastboot set_active a
or
fastboot set_active b
Click to expand...
Click to collapse
In fact, both work, but my phone still stucked at the bootloader (infinite line animation in both cases).
BubuXP said:
If not working, can you enter recovery (power on with Volume up button pressed)?
If you can enter recovery, hold down the power button for 3-5 seconds and then press and release the Volume up button, to make commands appear. Then your only hope is to install the OTA update zip from there (copy the OTA in a microSD card, there is a thread where you can find the link to the OTA zip).
Click to expand...
Click to collapse
Yes I can enter recovery and I have already tried this, but I always end up with the error:
Code:
E: Unknow volume for path [/sideload/package.zip]
Verifying update package...
Update package verification took 17.3 s (result 0)
Installing update...
E:Error il /sideload/package.zip (Status 1)
Installation aborted
BubuXP said:
In my opinion, "OEM unlocking" in developer options MUST be always keep active, because incidents like this could happen, and because even without modding, an OTA could go wrong resulting in your same situation.
I was in your same situation (OEM unlocking disabled and then I locked bootloader with a custom ROM installed) with a Nexus 5X.
I don't remember well how I fixed it, but I remember entering in Qualcomm download mode (should be the same EDL mode) and loading a file found after many hours of research in strange forums and sites.
Click to expand...
Click to collapse
Yes of course !
But I revert to stock rom with Mi Flash and I click on Flash all and lock, since the telephone should have been "brand new" it should not have any problems but ...
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...

after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool

LUNARIO said:
after unlock bootloader type fastboot flashing unlock_critical and flash with miflash tool
Click to expand...
Click to collapse
But since I can't activate OEM I can't unlock bootloader....

try this http://www.xiaomitool.com/ not sure if it works on our phone but maybe can unlock the bootloader so you can use miflash

Have you sideloaded the zip? I think it's better to copy the OTA zip to microSD than ADB sideload.
droopeur said:
I have to enter EDL mode, but don't know how to do it since modified fastboot executables does not activate it it just reboot the phone...
Deep flash cable may help but not shure if it works, or I may have to disassemble the device to find EDL pins...
Click to expand...
Click to collapse
There should be only two methods for entering EDL:
1- request authorization in en.miui.com forum. Sometimes the admins accept requests to give an account one EDL flash permission (but I don't know if it works with AndroidOne devices).
2- finding the test point in the phone's motherboard.

Hi guys,
i tried to install this twrp but it doesnt work...
so i searched on internet and i found another article, i tried to check the current partition and install in another way
for first:
fastboot getvar current-slot
after i do this
fastboot boot_b recovery.img
and then
fastboot set_active b
so nothing to do....but right now my MI A2 lite not boot.
i try again to check my partition but this time i have no replay.
i have unlocked bootloader but i cant go to recovery and i cant boot!!
someone can help me please?

I HAVE THE SAME PROBLEM
everything you said is completely simillar to mine. Can someone help us? Or did you already fix it? Please help me i need my phone working.

I have same problem fastboot flash but after that, it started to reboot automatically. The phone was automatically turning off and on. I again did a "clean all and lock" via miflash tool but still now, no result!
I can boot into recovery without having any problem. But when I boo to setup country date....etc, it starts its auto rebooting process,
Any help ?

droopeur said:
But since I can't activate OEM I can't unlock bootloader....
Click to expand...
Click to collapse
Same situation here. I am desperate!! Did you solve it?

Isso resolve
steledama said:
Same situation here. I am desperate!! Did you solve it?
Click to expand...
Click to collapse
gadgetsfarm.com/download-mi-a2-lite-fastboot-rom-v9-6-4-download/[/url]

How to unbrick?
Hey guys. I bricked my Mi2 Lite as well. Is there any step by step way to unbrick?

had the same problem, was stuck in the bootloop even after I flashed img with MiFlash! NOTE: MY BOOTLOADER WAS UNLOCKED!!! (LUCKLY I DID NOT TRIED FLASH ALL AND UNLOCK!)
headed to this thread
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
did not work, I get error saying FAILED
but after i used
Code:
fastboot oem edl
I went to MiFlash and used "Clean all" option (again note DON'T use "Clean all and lock"!!!). It took around 5 minutes to flash and my notif. light blinked whole the time. After it say "Success" I was able to normaly boot the phone again

Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.

Hi, where i can find MI A2 Lite Tool Kit? i open my device and i can put in EDL mode., my computer detect my pone in EDL mode, but i can not know do.
I like bypass FRP, can anybody help me
Thanks.
mr_techno said:
Find "Mi A2 Lite toolkit V 1.0.4.2" and use it to flash stock 8.1, it will do all the magic with a few clicks, just don't interrupt it until your phone restarts and you get the "Welcome" screen. After you can do the upgrade to Pie via OTA.
Click to expand...
Click to collapse

Hi all,
I also had same problem and I just resolve it.
My phone was in bootloop mode after stock rom flashing...
You don't need apply "fastboot oem edl" !
Just be sure your device is unlocked.
Download first stock rom (V9.6.4.0.ODLMIFF Firmware for Mi A2 Lite). If you flash last ROM, it don't work.
Flash it with XiaoMiFlash tool (don't forget to enable "Clean All") in bottom of the tool.
After reboot, you can apply OTA updates.
Enjoy !

The Complete Noob Guide to Rooting MetroPCS XT1955-5 Qualcomm Variant

This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy A20 crap.
Follow the following at your own risk! I am not responsible for any mishaps with your devices. I also don't know if this will work on other variants, as I only have these for MetroPCS, and from my understanding this will NOT obviously work for Verizon, AT&T, and Cricket phones.
I want to thank @diversenerd, and @jhjhjhjhjhjh for their hard work tinkering with the phone as I tried to figure it all out from their notes and instructions. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this, as the information wasn't quite clear in some places and I got some bootloops.
Introduction/Preparation
First, go and prepare by READING EVERYTHING IN THIS FORUM. Very important. Don't even jump into this without reading this thread here all the way to the last page: https://forum.xda-developers.com/g7-power/how-to/versions-moto-g7-power-supra-magisk-t3923857 (this is so you know start to finish what worked for some might not work for this variant).
Second, unlock the bootloader. The MetroPCS variant can be unlocked by Motorola; follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). I did it in Firefox this go round and it sent the codes immediately . When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
***NOTES SO YOU DON'T FREAK OUT***
1. Every time you power up the phone after you unlock the bootloader Moto will try and make you feel like crap with a bad key error in the middle of a nice message that your phone is not to be trusted. :laugh: This is normal. Give it a minute, you havent broke it.
2. There is no custom recovery/TWRP for this variant, so read carefully so you don't delete something you might not be able to flash back later.
3. OEM Unlocking toggle switch is interesting. On my first phone it was activated once the bootloader is unlocked and greyed out to where it couldn't be accessed anymore; On the significant other's phone it is still accessible and can be toggled even with the bootloader unlocked.
Files
There is confusion in some of the threads about leaving the Sim Card/SD Card in while flashing. Yes, pull it out and flash without it. Flashing with the sim card/SD card in can cause problems flashing. I did my first phone without it, but forgot to take it out with my second and had to start from scratch. Avoid that step.
1. Get Minimal ADB and Fastboot (it's easier to use than Android SDK and smaller).
2. Download the Motorola Drivers from their site (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (This is a good thing to have to know your hardware responsibly).
4. Stock Firmware. I used XT1955-5_OCEAN_RETUS_9.0_PPO29.114-63-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml which is the US Retail software instead of MetroPCS's firmware because of the issues I was having with it straight out the box. Both of my phones flashed fine with it and you can find it here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ I used the 2nd one with success - the first one doesn't play nice with Magisk.
5. MagiskManager-v7.3.2 apk.
6.The Boot .img separately extracted from the Firmware listed in Step 4.
7. Root Checker.apk
8. Patience (and a good movie keeping you going).
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card and SD card is REMOVED from the phone. Again, this is to prevent problems in the flashing.
3. Make sure your wifi is OFF. Every time you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and immediately pushes updates galore.
4. Make sure you save Magisk and the Boot .img to your phone directly. Using the Download folder is a great place and easily accessible in Magisk. You will not be able to add files once in fastboot).
5. Make sure your developer options are activated.
6. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
7. Make sure to check CPU-Z for your hardware specs and to make sure you're avoiding potential problems.
8. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device). Once you flash, you have to constantly check USB to Transfer because it will not do it.
9. Make sure you have the STOCK CABLE that comes with the phone. This model is funky about using other cables.
10. Make sure you set your display to time out to ten minutes. If the phone screen goes to sleep mode, it may interfere with flashing.
Rooting
Here is the fun part. Please keep in mind you may get a bootloop. I did on both phones on the first try with two different methods. I was on the infamous March 1 2019 security update and still got a bootloop from the patching. The second phone I just flashed ahead of time to the new firmware and still got a bootloop until I flashed again. Expect it.
1. Go into your developer options and DISABLE Automatic Updates. This is important for later on.
2. With the phone on, install Magisk. Make sure you use the version 7.3.2 or update to it since it's the latest version at the time of this guide.
3. Say yes when your phone asks whether or not you want to install things from unknown sources. It will grant access for this application only.
4. Open Magisk Manager and turn on your Wifi. If you don't Magisk will hang at checking updates. If necessary, force close Magisk and open it up again with Wifi on. It should bring you to One Green Check Mark that Magisk Manager is Up To Date, and One Red Mark above it that says Magisk isn't installed.
5. Click install on that tab ONLY (there is no need to click install by the Green Check Mark one). Magisk will then ask you "Do You Want To Install Magisk v19.3(193000) now? and click Install again.
6. Under Select Method, navigate to the folder on the phone where you saved your boot.img file (or whatever you named it). Once you select it you will be taken to a screen where the letters are funky looking but spell FLASHING at the top. Once it patches your file, it will tell you when it's done. Should it hang or you get errors, you WILL HAVE TO REFLASH THE FIRMWARE AND START OVER.
7. When the screen tells you it's all done, plug your phone up to the computer and drag the patched img file (it should by default say magisk_patched.img) and put it in the folder with Minimal ADB and Fastboot.
8. Turn the phone completely OFF.
9. Plug your phone via USB cable into the computer.
10. Press Volume Down and Power to boot into fastboot mode.
11. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your boot image file is in the Minimal ADB directory or it won't work.
12. Type "fastboot flash boot thenameofyourrecoveryfile.img" and hit enter.
If all goes well it should flash to "a" partition, and you should see in the command prompt "image signed with key bad key" before it says done. If it doesn't take do not re-flash as it will flash to "b" partition which will definitely bootloop and ensure you have to reflash the firmware.
13. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
14. Wait for the bad key/device cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
15. Open Magisk Manager. The icons should be in green, letting you know you have root. Follow @diversenerd advice and Click Tap To Start SafetyNet Check. Make sure your Wifi is on for that check. This apparently tests to see if it can deceive Google checks and possibly install OTA (can't say I did all that, not a update junkie).
16. Install Root Checker and confirm root.
17. Disable Updates. I know this is hard for some people, but you dont know if a forced OTA update will take root away, and leave us with no option to get it back or roll back to an earlier version of Pie.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. I have no idea why it doesn't work device to device, but it doesn't. And while I thank @jhjhjhjhjhjh for giving up his original files, it was incompatible with my phone (even though we are on the same variant) and bootlooped me.
2. You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. You will lose everything datawise flashing and playing with the boot.img. My phone reset itself tinkering with flashing, every time. Don't be alarmed if it takes you through a reset.
4. I wasn't able to confirm by going into updates (couldn't find the system settings) and verifying that nothing said anything about Device Integrity Compromised. I just assumed it.
5. Magisik is TEMPERAMENTAL. So if first you don't succeed, reflash the firmware and try again.
6. You cannot just go into the Stock Rom file and extract the boot.img file, put it in the Minimal ADB file folder and flash it if it bootloops. YOU MUST REFLASH ALL THE FIRMWARE OVER.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, here's what you're going to have to do. And don't worry - it won't relock the bootloader.
1. Make a duplicate folder of Minimal ADB & Fastboot that is clean (doesn't have any boot images or any added files in it).
2. Extract the firmware to the folder where Minimal ADB & Fastboot are at on your computer.
3. Turn the phone completely OFF and back ON if you haven't done so yet. Make sure there is no Sim Card of SD card in it.
4. Press Volume Down and Power to boot into fastboot mode.
5. Plug your phone via USB cable into the computer.
6. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure all your firmware files have been extracted in the Minimal ADB directory or it won't work.
7. Cut, Copy, and Paste in Fastboot All Together the following:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
8. When it is done it will stop on fastboot reboot. Hit enter and the phone will reboot.
9. Repeat all steps in the Pre-Rooting and Rooting section to obtain root.
Hope this helps my fellow MetroPCSers. I boot looped both of my phones this evening and brought them back with this method, and eventually achieved root on the 2nd tries, respectively. Old girl is working and I got Root Explorer and Titanium Backup going full stop. At least this root was easier than on my E4, lol.:laugh:
I will try and answer questions if I can or point you in the right direction.

I believe my boot img was flashed to "b" partition and everything is fine...
do you know a way to sim unlock it?

edwardxi said:
I believe my boot img was flashed to "b" partition and everything is fine...
do you know a way to sim unlock it?
Click to expand...
Click to collapse
Make sure it is okay, because when I flashed it the first time and it flashed to "a" and it bootlooped the Moto intro, I only flashed the boot image again and it flashed to "b" and hung at the "This Device Cannot Be Trusted/Bad Key" Screen.
I have no way to test sim unlock as MetroPCS locks their sims to the phone via IMEI and don't let you hotswap them, mostly to charge you 11 bucks reactivation fee. But in theory it should be sim unlocked by flashing to a different Carrier/Retail Rom, or at least that is how in the more budget line phones it worked.

Articul8Madness said:
Make sure it is okay, because when I flashed it the first time and it flashed to "a" and it bootlooped the Moto intro, I only flashed the boot image again and it flashed to "b" and hung at the "This Device Cannot Be Trusted/Bad Key" Screen.
I have no way to test sim unlock as MetroPCS locks their sims to the phone via IMEI and don't let you hotswap them, mostly to charge you 11 bucks reactivation fee. But in theory it should be sim unlocked by flashing to a different Carrier/Retail Rom, or at least that is how in the more budget line phones it worked.
Click to expand...
Click to collapse
I have been using it for couples of days, and definitely, everything is fine:laugh:
For metro, it's controlled by their Unlock app, you can't simply flash a different rom to unlock it... used to $10 on eBay, now $40... too expensive

edwardxi said:
I have been using it for couples of days, and definitely, everything is fine:laugh:
For metro, it's controlled by their Unlock app, you can't simply flash a different rom to unlock it... used to $10 on eBay, now $40... too expensive
Click to expand...
Click to collapse
Well, on My E4 I was able to unlock it by flashing Lineage Nougat. I could put any sim in it but Metro, because they lock by IMEI. Can't speak for this one, I just jumped back to Metro from Tmobile, who was HIDDEOUS.
Maybe you might get lucky and get some Moto support from Chimera. Then for 11 euro you could unlock it with their tool. But stay on their behinds and make sure its working first.

Articul8Madness said:
Well, on My E4 I was able to unlock it by flashing Lineage Nougat. I could put any sim in it but Metro, because they lock by IMEI. Can't speak for this one, I just jumped back to Metro from Tmobile, who was HIDDEOUS.
Maybe you might get lucky and get some Moto support from Chimera. Then for 11 euro you could unlock it with their tool. But stay on their behinds and make sure its working first.
Click to expand...
Click to collapse
yeah, can't agree more, they are terrible...

@Spaceminer. This is the post I'm talking about

If you want to get rid of the bad key message at boot, you can flash the logo.bin file from the link below with fastboot. Just place the downloaded logo.bin in the minimal adb and fastboot folder, open a cmd window and type fastboot flash logo logo.bin and press enter. Next boot you should have a plain white screen with a large black moto symbol instead.
https://forum.xda-developers.com/g7-power/themes/remove-bad-key-start-boot-t3947359

Going to root mumy G7 power from metroPCS. Can anyone confirm is there a way to SIM unlock after root?

aggresive said:
Going to root mumy G7 power from metroPCS. Can anyone confirm is there a way to SIM unlock after root?
Click to expand...
Click to collapse
There is no SIM unlock per se with MetroPCS. They tie their SIMS into the IMEI of the phone you're using. So you can't just take the sim out and put it in another phone easy peasy without going through them and paying them to do it.
However, if a custom rom comes out, which will happen once we get a TWRP, you'll be able to do that probably on Lineage. But until then, there will be no confirmation.

Beetle84 said:
If you want to get rid of the bad key message at boot, you can flash the logo.bin file from the link below with fastboot. Just place the downloaded logo.bin in the minimal adb and fastboot folder, open a cmd window and type fastboot flash logo logo.bin and press enter. Next boot you should have a plain white screen with a large black moto symbol instead.
https://forum.xda-developers.com/g7-power/themes/remove-bad-key-start-boot-t3947359
Click to expand...
Click to collapse
This is correct and I have contributed my custom made logo.bin image on said thread, even though you can still see bad key its cute, lol.

i got it all rooted but now it shows i have no imei and sim status not available any suggestions do i need to flash modem or radio

626jose said:
i got it all rooted but now it shows i have no imei and sim status not available any suggestions do i need to flash modem or radio
Click to expand...
Click to collapse
try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

Thanks figured it out i used the 2nd download like the op said. I didnt check to see if it was the same version i was on so it bootlooped and i flashed the whole thing so i downloaded the original firmware reflashed it that didnt work so i let it update and it came back good as new. So for anyone else doing this make sure its the same version youre on i found it on a different site just google it

626jose said:
Thanks figured it out i used the 2nd download like the op said. I didnt check to see if it was the same version i was on so it bootlooped and i flashed the whole thing so i downloaded the original firmware reflashed it that didnt work so i let it update and it came back good as new. So for anyone else doing this make sure its the same version youre on i found it on a different site just google it
Click to expand...
Click to collapse
I used the RETUS version and didn't have that problem; are you sure you didn't accidentally click the wrong version and flashed that (like a CDMA version)? At any rate, glad you got it back. Interesting you updated....I NEVER EVER EVER EVER do that because updating can break root if the manufacturer patches it.
Also, make sure you are on the OS version March1st; I didn't update my phone and used that stock.

Articul8Madness said:
I used the RETUS version and didn't have that problem; are you sure you didn't accidentally click the wrong version and flashed that (like a CDMA version)? At any rate, glad you got it back. Interesting you updated....I NEVER EVER EVER EVER do that because updating can break root if the manufacturer patches it.
Also, make sure you are on the OS version March1st; I didn't update my phone and used that stock.
Click to expand...
Click to collapse
Yep made sure to follow everything word for word pretty sure thats why it bootloops the 1st time then after you flash the whole thing it works ive looked at them and the one that matches my firmware is the last 1 with the 2nd one i had 2 unlock apps one from metro and one from tmobile idk if thats your case or something didnt flash right or dirty flashed i was wondering also if that twrp river works has anyone tried it or is there twrp for this device and is there a way to rewrite the imei using adb or some other way

626jose said:
Yep made sure to follow everything word for word pretty sure thats why it bootloops the 1st time then after you flash the whole thing it works ive looked at them and the one that matches my firmware is the last 1 with the 2nd one i had 2 unlock apps one from metro and one from tmobile idk if thats your case or something didnt flash right or dirty flashed i was wondering also if that twrp river works has anyone tried it or is there twrp for this device and is there a way to rewrite the imei using adb or some other way
Click to expand...
Click to collapse
@Geofferey has created an unofficial TWRP here https://forum.xda-developers.com/g7-power/development/port-twrp-g7-power-t3963738
Warning: DO NOT USE RIVER twrp - Our device is Ocean and River will Bootloop and possibly brick it.
We can't rewrite the imei or any of that yet - we still are working on custom roms. I've been trying to make stock roms for our variant, but unlike the old Moto I had, the new android OS has new permissions and all that with Pie and it keeps messing up on the porting.

Well after installing adaway and it not working i tried uninstall phone froze so i turned it off by holding the power button now its stuck in a bootloop idk if it finally ran out of power everytime i shut it off it kept rebooting can i recover without reflashing everything or do i have to start from scratch tia for the help

626jose said:
Well after installing adaway and it not working i tried uninstall phone froze so i turned it off by holding the power button now its stuck in a bootloop idk if it finally ran out of power everytime i shut it off it kept rebooting can i recover without reflashing everything or do i have to start from scratch tia for the help
Click to expand...
Click to collapse
I've never had that problem before, so I'll give my suggestions.
1. Try a factory restore from the Fastboot Menu. That may set everything easy peasy BUT it will wipe the phone.
2. If #1 doesn't work, then see if you can just reflash the magisk patch. That may do it.
3. If #1 and #2 don't work, then yeah, back to the drawing board.
Adaway maybe messed with Magisk; did you set the proper permissions in Adaway to give it root access? Anybody else care to weight in?

I'm not able to upload Magisk or boot.img directly to moto g7 phone from computer through Windows. I can transfer both to SD card, but doesn't allow access directly to phone file directly. Yes, bootloader is unlocked.

[GUIDE] Relock bootloader (Should work in all versions)

Guide updated!!!!!
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Download the "Lock Script" here, according to your android version and PC's OS.
For example: if your PC uses Windows as OS, and your phone is in android 10, download the "Lock-10q_windows.bat" file.
Or if you have a Linux distro on your PC and android 9 on your phone, download "Lock-9pie_linux.sh" file.
Place the file inside the platform-tools folder, where the ROM was extracted too.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM and re-locking bootloader
Just double click on the Lock.bat/.sh file and it will reflash stock ROM and lock bootloader. Now all you have to do is wait till it finishes. This should take a few minutes to be done.
The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.

Very nice, it's really working! Thanks!

Works on xt1955-4 thanks very much, will the warranty still apply?

piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Will tell you if warranty is voided.
Sent from my ali using XDA Labs

piotr1859 said:
Works on xt1955-4 thanks very much, will the warranty still apply?
Click to expand...
Click to collapse
Yes, should work fine. Afaik, once you unlock your bootloader, your warranty is avoid, theoretically. But I guess you can send it to service center (if it's needed) with no problems. They don't always check if you have unlocked your bootloader or not.

Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!

Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?

DarkAngelNoctis said:
Hello guys. I have Motorola Moto G7 Power (XT1955-4). I've tried to put in twrp and a rom, but when I rebooted my device it don't power on anymore. So I've searched many guides to repair. I've used "blankflash" and after many times I was finally power on my device and go in Fastboot Mode. But now there's another problem. When I connect with usb and open CMD and type "adb devices" appear:
LIST OF DEVICES ATTACHED
or
WAITING FOR DEVICES
I tried many things to fix it but nothing work. Now I've uninstalled everything on my pc, drivers too.
Maybe I've installed bad "blankflash"???
How can I fix my troubles?
Click to expand...
Click to collapse
If the device is in fastboot mode only fastboot commands will work
Code:
fastboot getvar all
edit:grammer
Sent from my ali using XDA Labs

sd_shadow said:
If the device is in fastboot mode only fastboot commands work like
Click to expand...
Click to collapse
Ok. Thanks!

LuisLFSS said:
Warning: Due to some changes in bootloader and people getting hard bricks in February security patch, i don't recommend to relock bootloader in that version, do it in December security patch instead!
Click to expand...
Click to collapse
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks

darko454 said:
hey would it be safe to use this method on security patch version April1,2020? if not please point me in the right direction.
thanks
Click to expand...
Click to collapse
Yes, it's safe. Now we have blankflash so it's safe

LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
ok thanks!

LuisLFSS said:
Yes, it's safe. Now we have blankflash so it's safe
Click to expand...
Click to collapse
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.

hawkdown77 said:
Hi, can you send a link to blankflash for XT1955-1?
THANK YOU.
Click to expand...
Click to collapse
Yes, join in my group: t.me/motog7brasil

LuisF201707 said:
If you wanna get back to stock ROM and relock bootloader + get OTAs working again, this is the right place!
DISCLAIMER: Relocking bootloader erases all your data/internal storage and (off course) remove TWRP/modules/root, so do a backup of all your data first. Also, I'm not responsible for any bricked devices (phones, SD Cards, etc). I tested it in my XT1955-1 and it worked fine, but we all know that errors might occur.
Finally, let's go to the steps.
Step 1 - Downloading necessary files
Download Android Platform Tools here and then extract it.
Install Motorola Drivers on your PC (download here).
Download the lastest firmware according to your variant/software channel here and extract it in the same folder you had extracted Android Platform Tools.
Step 2 - Preparing your phone
Remove all your google account in device's settings and then go to Developer Options. Enable Android debugging and OEM unlocking (if you can't enable OEM unlocking, you may need to root your device first to get it avaible again (see Rooting thread)).
Power off your phone and put it fastboot mode. Connect it on PC using USB cable.
Step 3 - Installing Stock ROM
If you're already in stock ROM with no modules and stuff installed on it, just skip this and jump to the next step. If you're not, then stay here.
Open CMD (command prompt) in the same folder you had extracted firmware and android platform tools.
Shift+right click and then "Open command window here" or just type CMD in the folder path bar at the top in windows explorer. Run this commands all at once in CMD:
Once it is done, DON'T power on your phone, just leave it as it is and let's go to the last step.
Step 4 - Relocking Bootoader
In cmd, run this commands all at once
Done! The phone will boot automatically after the last command is executed.
It seems to be a little hard, but it's easy. If you have any questions, let me know, I'll try to answer ASAP.
Click to expand...
Click to collapse
There is an bat file out to relsash stock rom with out trying all that stuff in manually

Help
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch

JPalomo1997 said:
I followed all the steps and managed to block the bootloader but when I turn on the phone I get "start up failed" can someone help me.
I did it in the April 1 patch
Click to expand...
Click to collapse
Which android version? There's april security patch for android 9 and 10...

roadkill42 said:
There is an bat file out to relsash stock rom with out trying all that stuff in manually
Click to expand...
Click to collapse
I know... I'll update the thread soon

chrisbchrisb85 said:
For step 4 relocking the bootloader what does "run these commands all at once" mean??? As soon as I lock the bootloader I can no longer flash anything else, therefore still stuck with a boot screen warning
Click to expand...
Click to collapse
"run these commands all at once" = copy all the commands and execute them in cmd...
And which android version did you install? because the commands to flash android 10 are different than android 9 ones

Guide updated!!!!!
I removed those annoying commands and put a link to download Scripts that already do everything automatically. Now the guide is simpler and easier

Question Update to January HELP

I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much

I just updated from Dec/rooted to Jan/rooted by running Flash-all -nowipe while having my phone in Fastboot mode. I then patched the boot.img. Went very smoothly.

clipdawg05 said:
I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
Click to expand...
Click to collapse
Here ya go. Let's try to keep all rooting questions in this forum. It will make it easier to get an answer and the OP has put in a lot of work to keep this up to date. Otherwise we have 'update to January help' which says nothing. Give it a try and there are a lot of people there willing to help you.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com

bobby janow said:
Here ya go. Let's try to keep all rooting questions in this forum. It will make it easier to get an answer and the OP has put in a lot of work to keep this up to date. Otherwise we have 'update to January help' which says nothing. Give it a try and there are a lot of people there willing to help you.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Click to expand...
Click to collapse
ok thank you

clipdawg05 said:
I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
Click to expand...
Click to collapse
I'd recommend using this method from the linked Thread above
Don't forget to get the boot.img from the new Firmware (extract factory image, find it) and patch that with Magisk, then transfer it back to your PC ADB folder and use that as "master root").

Morgrain said:
I'd recommend using this method from the linked Thread above
View attachment 5509367
Don't forget to get the boot.img from the new Firmware (extract factory image, find it) and patch that with Magisk, then transfer it back to your PC ADB folder and use that as "master root").
Click to expand...
Click to collapse
This is the boot img from when I rooted the phone the first time, or do I have to patch the boot from this new January update

clipdawg05 said:
This is the boot img from when I rooted the phone the first time, or do I have to patch the boot from this new January update
Click to expand...
Click to collapse
Patch the new January boot image and use that instead of the old one.
Also when you do step 4, (after the system boots normally and you see the update bar slowly rising until the OS comes), unlock the phone and look into notifications, it will say something like "finishing updates", only when that finishes you reboot into bootloader.

This happened as soon as i pressed enter. What to do now

What I did (p6p, november update, rooted, bootloader unlocked):
1. Downloaded latest Jan factory image https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip, extracted boot.img and put it aside for step 6.
2. Disabled all magisk modules (not necessary, just in case).
3. Went to flash.android.com via Edge, agreed to all prompts on the page and phone screen.
4. UNCHECKED all checkboxes. There were 3 of them, something like Wipe All, Lock Bootlocker, Flash All Partitions).
5. Follow all prompts - "Reselect your device" etc.
6. Successfully rebooted, put boot.img file into phone's memory, run Magisk app and patched boot file.
7. Moved the patched file "magisk_patched-23016_IVwVbT.img" (your file name may be different) back to my pc and run via cmd "fastboot flash boot <location of your patched boot img file>".
8. Rebooted and re-enabled all magisk modules.
With the January update I experience no issues and honestly no changes that I could notice. At least I'm happy there is nothing worse

clipdawg05 said:
This happened as soon as i pressed enter. What to do now
Click to expand...
Click to collapse
If you reboot and come back to the same screen I'm afraid your only option is to wipe data/factory reset.

asdor said:
If you reboot and come back to the same screen I'm afraid your only option is to wipe data/factory reset.
Click to expand...
Click to collapse
ok i will reset. i tried adb devices and it says unauthorized

I think there is something wrong with my phone. When i try a normal update it fails. When i try the android flash tool it tells me my phone is already in use and sideloading does not work.
Finally got past the phone already in use by restarting, only to have another failure flashing

clipdawg05 said:
This happened as soon as i pressed enter. What to do now
Click to expand...
Click to collapse
What does that even mean? What're you doing when you hit enter to get that screen? I'm assuming you're issuing a fastboot command but you need to provide more details.
clipdawg05 said:
ok i will reset. i tried adb devices and it says unauthorized
Click to expand...
Click to collapse
You need to enable developer options on your phone if you haven't already. Go into settings > about phone > click on build number until it says "you're a developer" at the bottom. Then, go into settings > system > developer options and enable USB debugging. Try running adb devices again and clock on "allow" prompt on your phone when it pops up.
clipdawg05 said:
I think there is something wrong with my phone. When i try a normal update it fails. When i try the android flash tool it tells me my phone is already in use and sideloading does not work.
Finally got past the phone already in use by restarting, only to have another failure flashing
Click to expand...
Click to collapse
It says phone is in use because you need to issue a "adb kill-server" command and then try the flash tool again.
I had the same OTA issue yesterday. You can try using the flash tool again once you issue the "adb kill-server" command, but if it doesn't work try applying the update via sideload.
Download the OTA image from here - https://dl.google.com/dl/android/aosp/raven-ota-sq1d.220105.007-3a7aafbf.zip
You will also need the stock image so you can extract the boot img. Get it from here - https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip
Once you do that, follow these steps.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image:
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
You can find full instructions in this thread:
https://forum.xda-developers.com/t/guide-root-pixel-6-pro-raven-with-magisk.4356231

RetroTech07 said:
What does that even mean? What're you doing when you hit enter to get that screen? I'm assuming you're issuing a fastboot command but you need to provide more details.
You need to enable developer options on your phone if you haven't already. Go into settings > about phone > click on build number until it says "you're a developer" at the bottom. Then, go into settings > system > developer options and enable USB debugging. Try running adb devices again and clock on "allow" prompt on your phone when it pops up.
It says phone is in use because you need to issue a "adb kill-server" command and then try the flash tool again.
I had the same OTA issue yesterday. You can try using the flash tool again once you issue the "adb kill-server" command, but if it doesn't work try applying the update via sideload.
Download the OTA image from here - https://dl.google.com/dl/android/aosp/raven-ota-sq1d.220105.007-3a7aafbf.zip
You will also need the stock image so you can extract the boot img. Get it from here - https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip
Once you do that, follow these steps.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image:
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
You can find full instructions in this thread:
https://forum.xda-developers.com/t/guide-root-pixel-6-pro-raven-with-magisk.4356231/[/CODE]
[/LIST]
Click to expand...
Click to collapse
The first picture of a failure was when I was trying to sideload the update.
Thanks for your response but i finally got it done on Android flash tool with the wipe enabled

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