Related
I followed these steps and now my Asus zf2 (ze551ml) is back alive! For the issue mentioned below, I didn't find much anywhere so I thought I'd put here what helped me.
Issue: Only fastboot mode accessible, can't enter recovery. (Also my bootloader was locked, MM bootloader, No OS). After selecting recovery mode from bootloader, again it enters fastboot, i.e the process in video above couldn't install the recovery (This must be because my bootloader was locked). I tried unlocking the bootloader by the .bat files available on XDA but since I'd not enabled OEM unlocking, unlocking failed everytime. My OS got wiped out, so only fastboot mode was accessible.
Solution:
I believe you have installed Minimal ADB and fastboot on your PC.
Download the raw file from the XDA thread.
Now first of all, change extention of the .raw firmware file to .zip.
Then just extract all files from it into adb and fastboot folder.
Now in folder (where you placed files from raw firmware and adb and fastboot tool folder) at empty place anywhere in folder hold Shift on computer keyboard and right click with mouse. Now click open command window here.
Perform the following commands one after another:
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again, if USB debugging was on then this will definitely work)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. Don't worry, first boot gonna take a little longer time.
Download raw file
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
bb04 said:
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
Click to expand...
Click to collapse
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
FYI, I didn't add the links because one can't add external links in their first posts.
mukunds11 said:
FYI, I didn't add the links because one can't add external links in their first posts.
Click to expand...
Click to collapse
it could be better if you would have removed or edited last line while copying commands
help. my phone condition is just like this. at first when i connected my phone to computer, powershell detected it, but then after a while, my phone disappeared from powershell. can someone help me ?
edit, i just did the thing and its doing fine even though my phone look like it is not detected
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
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
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------
toxinburn said:
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
Click to expand...
Click to collapse
I am gonna check one thing I had it all working another method before but after installing something thru magisk it soft bricked I think it was vanced youtube maybe also cant seem to find a way to get vipre to work sadly.
Question
Does this method bypass the screen lock password on the phone? I have this phone that is locked with a passcode, so I can't easily get it into developer mode. Sorry, I'm a total newbie to this but am trying to learn. Thanks in advance!
A tip for linux users. If you are getting "< waiting for any device >" after the "fastboot oem get_unlock_data". Ctrl-c to exit the command. Su to root and then "fastboot oem get_unlock_data".
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Hyoretsu said:
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Click to expand...
Click to collapse
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Linux-Lord said:
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
The thing is, "stopped working" literally, it doesn't have out of service, phone number, no signal, not even the "emergency calls only", heck I can't even find my IMEI in settings nor *#0606#, I think that's what's causing the problem. This SIM also came from that Custom ROM device (originally inserted there, but bought as a standalone data plan)
Linux-Lord said:
and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
If you're talking about how it showed up like that on the G7 Play it used to work just fine in there, and no, that's not the original phone, it's just a phone I used to test if my SIM was still working
Linux-Lord said:
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
Click to expand...
Click to collapse
In this phone, G7 Power, it doesn't even recognize a card is in the tray anymore (unlike the G7 Play which at least knows there's one and G5+Custom ROM, in which it works)
Linux-Lord said:
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Click to expand...
Click to collapse
Not that it's gonna help much but OI (Brazil), and if that's on Motorola support page my G7 Power is main phone already.
Is the force encrypt disable necessary? And what does it do?
So, I have successfully rooted my Moto G7 Power by using the method above, but i tried not doing the "format data" and fortunately, I have rooted my phone. For the 1st attempt, I kinda soft-bricked my device by doing the steps briefly, my phone would always bootloop back to recovery mode, but after not doing the "format data" step, it led to a success. So for anyone who are currently experiencing bootloop, flash the stock firmware to your phone and root it again by using the method above but don't do the "format data" step. (flashing the stock firmware would not re-lock the bootloader, so you can try to root your phone again easily.)
error
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
---------- Post added at 08:07 AM ---------- Previous post was at 07:49 AM ----------
gladiatorbong said:
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Click to expand...
Click to collapse
same here
brokenlocked22 said:
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
Click to expand...
Click to collapse
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Hyoretsu said:
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Click to expand...
Click to collapse
same thing as always.. no matter what lol
brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
If it's same thing as always then you're still using "adb push magisk adb push Magisk-v20.1(20100).zip /tmp/". There's no "but I'm not", if it's indeed the same error as before you're messing up on the syntax. Make sure you've put Magisk inside Minimal ADB folder, rename it to magisk.zip and run "adb push magisk.zip /tmp/"
why is magisk pushed to tmp and not to internal storage . Why not just push magisk to internal sotrage and just install that way through twrp or that wont work. just wondering.
Anyone tried this on XT1955-4?
dirtyscout said:
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
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
Click to expand...
Click to collapse
IM a bit confused should I flash a fresh installed firmware first right after i unlock the boot loader?
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
[Redacted]
Excellent guide, rooted my Moto G7 from Metro PCS.
brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
I LOVE IT!!! :good:
First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device!
Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device.
So, after that, let's dive into the steps of rooting it
First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process )
You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device!
So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it.
Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file'
Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer.
The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! )
After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command:
fastboot boot magisk_patched.img
( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) )
REMEMBER TO TEST EVERYTHING ON YOUR DEVICE IN THIS PART BEFORE CONTINUING!!!!!
IF YOUR PHONE DIDN'T BOOT OR BOOTED BUT WITH MALFUNCTION STOP NOW AND REBOOT IT, MAYBE YOUR STOCKROM WASN'T CORRECT OR SOMETHING ELSE...
After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version.
If so and your device runs fine, reboot again to fastboot then run on the terminal window:
fastboot flash boot magisk_patched.img
This will make the root persistent after reboots
Now as you expected, you're rooted
A bonus tip:
Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe )
I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it
Also I'm new to XDA too hihi
Thanks a lot for sharing your experience!
Has there been anyone else who managed to root this device?
I really want to buy one but first I want to make sure I will be able to root it from day 1. I don't like to use an unrooted phone
I bought my device last Black Friday and rooted it this week with this guide.
I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone.
I’ve also enabled oem unlock in developer settings.
It’s not so difficult.
The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
ReneZeiss said:
I bought my device last Black Friday and rooted it this week with this guide.
I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone.
I’ve also enabled oem unlock in developer settings.
It’s not so difficult.
The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
Click to expand...
Click to collapse
Amazing tips. I think in the end we are free to root it without screwing the device for good
Thanks!!
Ok, I got mine yesterday, and today I successfully root it.
It worked flawlessly!!
Thanks for the guide and advices!!
Root now si possible with twrp, new update thanks @seba_3567
MrZeroXD said:
First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device!
Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device.
So, after that, let's dive into the steps of rooting it
First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process )
You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device!
So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it.
Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file'
Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer.
The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! )
After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command:
fastboot boot magisk_patched.img
( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) )
After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version.
If so and your device runs fine, reboot again to fastboot then run on the terminal window:
fastboot flash boot magisk_patched.img
This will make the root persistent after reboots
Now as you expected, you're rooted
A bonus tip:
Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe )
I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it
Also I'm new to XDA too hihi
Click to expand...
Click to collapse
yes or yes I must download the full firmware, can't find the boot.img directly?
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
pmb6000 said:
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
Click to expand...
Click to collapse
I think u'll need to port your custom fonts as Magisk Modules, since you can't change system files directly ( even with root ).
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
taboelephant said:
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
Click to expand...
Click to collapse
So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems...
I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
MrZeroXD said:
So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems...
I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
Click to expand...
Click to collapse
Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
taboelephant said:
Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
Click to expand...
Click to collapse
Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
MrZeroXD said:
Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
Click to expand...
Click to collapse
OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
taboelephant said:
OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
Click to expand...
Click to collapse
It's should work since it's an official tool, any news tell us. Good lucky buddy.
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here:
https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
taboelephant said:
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here:
https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
Click to expand...
Click to collapse
So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe
Here's the code
Spoiler
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash radio_a radio.img
fastboot flash radio_b radio.img
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
MrZeroXD said:
So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe
Here's the code
Spoiler
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash radio_a radio.img
fastboot flash radio_b radio.img
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
taboelephant said:
Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
Click to expand...
Click to collapse
Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
MrZeroXD said:
Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
Click to expand...
Click to collapse
Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
taboelephant said:
Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
Click to expand...
Click to collapse
No prob, we're all learning, and all you need to fix a device that doesn't boot, is an unlocked bootloader, since u can re-flash, I did this on a few devices ( moto x4 ; moto G5s ; moto g9+ ) and succeeded on repairing those...
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
numbawon said:
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
Click to expand...
Click to collapse
so what can i do? i dont have stock recovery,and twrp recovery dont start, what fastboot command can i try to repair? only what i have its global rom downloaded from nubia homepage but i dont now how to flash stock rom and repair all this i try miflash tool,but mi flash tool not support zip formats
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
numbawon said:
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
Click to expand...
Click to collapse
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Merlousek said:
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Click to expand...
Click to collapse
Several of us are in the waiting game for the unbrick tool at this point.
i try bumper what you send me but another im stuck here
Merlousek said:
i try bumper what you send me but another im stuck here
Click to expand...
Click to collapse
I'll see if I can get it all extracted for you and post it someplace. I've not done it myself, I just knew where the information was.
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Merlousek said:
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Click to expand...
Click to collapse
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
numbawon said:
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
Click to expand...
Click to collapse
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Merlousek said:
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Click to expand...
Click to collapse
Just use fastboot. Forget mi tool.
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do you means?
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
you mean this fastboot commands?
and flash all files from stock recovery in fastboot?
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do youmeans?
fastboot flash system system.img
fastboot flash recovery recovery.img
like that?
another error when i try flash all files from fastboot
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Merlousek said:
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Click to expand...
Click to collapse
Nice job!
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
What TWRP did you install? Make sure you're downloading a TWRP that's available for this device. So far, to my knowledge, there isn't a TWRP recovery for this device yet.
Hello there, how did u just unlock bootloader by fastboot command? didn't use OEM unlock option on dev setting?
Btw can you share me your twrp that you used?
I need it so badly my rom bugged stuck at google account setup
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler.
If you have a Chinese version (K40s)and you have locked the bootloader on a rom other than Chinese, it comes from that.
bvyral said:
after flash stock rom using miflash and click clean all and lock , the flashing was successful then the phone was stuck on bootloader and now i cant even turn off the phone, the screen stay in fastboot..what should i do? please help me and tell me what to do step by step cz now the bootloader is locked..
Click to expand...
Click to collapse
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
System23 said:
you know the Steps to Flash StockROM, only look 4 another Firmware, iam Think its Not the Correct
Click to expand...
Click to collapse
What do you mean( only look 4 another Firmware)?
NOSS8 said:
What do you mean( only look 4 another Firmware)?
Click to expand...
Click to collapse
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
System23 said:
you must Flash the Correct Firmware 4 ya Device, when ya have this the Device Boot Corectly after Flash it!! thats why iam Think its not the Correct Firmware you used!!
Click to expand...
Click to collapse
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
System23 said:
look here to Find your Firmware Xiamoi Pocco F4 Firmware Archiv
Click to expand...
Click to collapse
But i got the firmware from here..i choose poco f4 global fastboot type
NOSS8 said:
I'm not the OP.
With the bootloader unlock you can flash any version of stock rom, EEA, Global, etc, and lock the bootloader.
Except if you have a K40S or you have to let the bootloader unlock.
Click to expand...
Click to collapse
Yea..the bootloader is now locked..what should i do?..and can it be done?..
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
Do you have a Poco F4 or a K40S?
Can you post the Miflash log?
Miflash/log folder, Txt file + or -25kb.
Use spoiler
bvyral said:
Yea..the bootloader is now locked..what should i do?..and can it be done?..
Click to expand...
Click to collapse
If you need to leave Fastboot mode, just press and keep a combination of the Power button + the Volume Down for about 10 seconds.
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
hope one of the Options will Work!!
Click to expand...
Click to collapse
You cannot use Mi Flash with a locked bootloader.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
not working...error:FAILED (remote: Erase is not allowed in Lock State)
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Boot Recovery via fastboot
fastboot boot xxx/Images/recovery.img
or
Reboot Recovery
fastboot reboot recovery
or
Flash Boot/Recovery
fastboot flash boot xxx/Images/boot.img
fastboot flash recovery xxx/Images/recovery.img
fastboot reboot
when this not working you can use EDL-Mode!!!
Poco F4 test Point Reboot 9008 EDL - ROM-Provider
Poco F4 test point is typically a set of pins on the device's circuit board that can be shorted together in order to put the device into edl mod
romprovider.com
Than you can Flash it with QPST or QFiL Tool from Qualcomm!!! but i must look when i at home if the fastboot Firmware includes all needed Files!!! rawprogrammer0.xml patch0.xml firehosexxxx.mbn
System23 said:
OK, original Tools and Firmware cannot Flash in locked BL!! than you can Flash in Recovery or in EDL Mode!! you stuck at Fastboot Mode so you cant Flash via Recovery!!! or you use fastboot in Terminal and test the following commands!!!
Click to expand...
Click to collapse
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Poco F4 (Munch) Firmware Flash File (Stock ROM) - ROM-Provider
Download Poco F4 Firmware Flash File stock ROM, here we share latest firmware for Xiaomi Poco F4 with flash tool & usb driver
www.google.de
with MiFlash in EDL-Mode and the EDL-Firmware GLO, its like this Article a working Solution!! and i dont know if fastboot reboot edl with special edl fastboot work, and I dont know if it can Start with ButtonsCombo!!! adb reboot edl is not availible wile stuck at Fastboot-Mode!! iam only give ideas to test them out, in variants they i know!! Iam Testing my variants out to find a way that works!!!
NOSS8 said:
Stop posting non-solutions.
Miflash unusable with the bootloader locked. (Yet noted on the OP).
Regarding your last post, the command syntax is wrong and it will not change anything.
For EDL mode, you don't know, it is not necessary to open the phone to enter EDL mode and anyway, it will not have permission to flash.
QPST or QFiL Tool from Qualcomm may work but not on this device (too recent) and Sahara is a very sensitive program and requires some experience to avoid errors such as:
ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:983 Sahara protocol error
ERROR: function: main:320 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail process fail.
Click to expand...
Click to collapse
give me more Input, iam intressted to read more!!!
System23 said:
give me more Input, iam intressted to read more!!!
Click to expand...
Click to collapse
This is not the subject of the thread. (do some research).
If it is impossible to enter recovery or fastboot mode and if it is not a HW problem, the phone is in EDL Mode.
It will not appear on the PC unless you install the Qualcomm drivers and will be detected by Miflash (in Fastboot mode, no need to log in) on a com port (login mandatory), but you will not have permission to flash (requires a special account).
This permission is not needed on very old devices.
Until the OP has answered my questions, I could not provide him with a possible solution.
System23 said:
have you any Expierience with Fastboot and the Terminal? than i have Read that your Device has A/B Partitions!!! That means SLOT A has now your Flashed Firmware & SLOT B has the older StockROM!!! Normaly when a Partition is Broken it changes the SLOT Automaticly!!!! with Terminal and fastboot can you Interact with the Device via PC!!!! so that you can use this commands to become the Information witch SLOT is Active, and SET one of the Booth Partitions!!!!
Show Activ SLOT
fastboot getvar current-slot
SET a SLOT
fastboot set_active b
or
fastboot set_active a
Show Activ SLOT
fastboot getvar current-slot
Reboot the Device
fastboot reboot
I have write a simple script that Downloads the Firmware,Extract it,copy Files 4 Flash,and Start Flash!!!
you Found that in my Onlinestorage Here >> Xiaomi_POCCO_F4_Firmware_Flash
Only Download it and extract it!!!
Run "Download_Firmware.cmd" and Connect Device via USB to PC and start it in Fastboot-Mode!!!
The Firmware is
Device: POCO F4 Global
Codename: munch
Version: V14.0.2.0.TLMMIXM
Branch: Stable
Type: Fastboot
Size: 6.3 GB
Release Date: 2023-03-12
Package Name: munch_global_images_V14.0.2.0.TLMMIXM_20230312.0000.00_13.0_global_cad4c8f425.tg
After the Download its extract it and delete the Archives and still 1 Firmware Folder exists!!!
After that its start the "flash_all.bat" that comes with this Firmware!!!! So make sure you have Connected the device via USB
to PC and have started Fastboot-Mode!!
than let it Flash the MIUI ROM!!!! if this Method working the Device will be Start normaly!!!
If this not work use "MIFLASHTOOL" and click on select and choose the Firmware Folder!! and Flash it with this Method!!!!
hope one of the Options will Work!!
Click to expand...
Click to collapse
thanks, after managing to unlock the phone just by moving it to local disk c, after some googling n youtubing, and i tried ur method again ,editing some flash_all bat.((
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *munch" || exit /B 1))
and run it....it works.. i sincerely thanks you..