Well, it is a Waste of time, this Phone is a Failure, since August the Phone Stopped getting IMPORTANT Updates monthly and now POCO is considering to Release POCO F5 in January
Whats your Opion on the Phone
Its a Wasted Product for 469€
POCO F4 IS A FAILURE said:
Well, it is a Waste of time, this Phone is a Failure, since August the Phone Stopped getting IMPORTANT Updates monthly and now POCO is considering to Release POCO F5 in January
Whats your Opion on the Phone
Its a Wasted Product for 469€
Click to expand...
Click to collapse
Nah I've been getting updates Using a Custom ROM ever since I got the phone. MIUI is garbage. It's a solid phone just use It with Custom ROM's and you'll be good they're way better anyway and you get monthly updates.
Poco f5 won't be released in January, redmi k60 series isn't even announced in china
POCO F4 IS A FAILURE said:
Well, it is a Waste of time, this Phone is a Failure, since August the Phone Stopped getting IMPORTANT Updates monthly and now POCO is considering to Release POCO F5 in January
Whats your Opion on the Phone
Its a Wasted Product for 469€
Click to expand...
Click to collapse
You don't have to buy it right? If you don't like it, skip it. It's that simple. My opinioin? If you happen to need a new phone when poco f4 is around, it's quite good "flagship killer". Updates are likely postponed because xiaomi prepares for android 13 released
alfZKI said:
Poco f5 won't be released in January, redmi k60 series isn't even announced in china
Click to expand...
Click to collapse
Its boxes has already manufactured if I recalled correctly. But you are right, it's not yet showing in TENAA yet. My guess it will be around march/april to show up.
It says everything about you if you register extra for this.
This is what is called a troll.
Vega56 said:
It says everything about you if you register extra for this.
This is what is called a troll.
Click to expand...
Click to collapse
Not a Troll, its blant and Just a Waste of Money, i have this Phone since July and i only have August Patch .... No sign of MIUI 14 or Android 13 and No News about the Phone on POCO Twitter Account
I have unlocked Bootloader only and Nothing else
Fail only when you can't do anything about it, get an Official custom ROM for this amazing phone will fill your FOMO...
I got an update yesterday on xiaomi.eu. Drama much? :-D
MarkRobert said:
I got an update yesterday on xiaomi.eu. Drama much? :-D
Click to expand...
Click to collapse
Yeah new android 13 beta and miui 14 dev just released yesterday, but miui global updates are usually much slower than china
As far as i remember i haven't see any Xiaomi phones on MIUI getting monthly security patches. If that is the case OP meaning about "important updates"
What do you recmd for me
I think xiaomi.eu is fine, unless you really need to customise something specific on your phone.
I been trying to Flash TWRP on this Phone but everytime .... I do that it says Error, the Phone Crashes and reboots and i have to unbrick it all the time ....
I cant even Install TWRP on it
I have ADB Fastboot, I have a USB Driver which also doesnt recognize this Phone (original Cable is there) and so
I unlocked the Bootloader only
I appreciate Help there too
POCO F4 IS A FAILURE said:
I been trying to Flash TWRP on this Phone but everytime .... I do that it says Error, the Phone Crashes and reboots and i have to unbrick it all the time ....
I cant even Install TWRP on it
I have ADB Fastboot, I have a USB Driver which also doesnt recognize this Phone (original Cable is there) and so
I unlocked the Bootloader only
I appreciate Help there too
Click to expand...
Click to collapse
Just get the OrangeFox recovery you can find It here on XDA under POCOF4 there should be a thread with It. It works perfectly for me.
Edit: You have to use
fastboot boot filename.img
And NOT
fastboot flash recovery filename.img
when flashing recovery. Never ever flash a zip file through fastboot. If the file is in a zip package extract It and use the img file inside. I'm guessing you're trying to flash the zip file which is completely wrong. You flash zip files inside the recovery not through fastboot. Hope this helps.
HARDWELL919 said:
Just get the OrangeFox recovery you can find It here on XDA under POCOF4 there should be a thread with It. It works perfectly for me.
Edit: You have to use
fastboot boot filename.img
And NOT
fastboot flash recovery filename.img
when flashing recovery. Never ever flash a zip file through fastboot. If the file is in a zip package extract It and use the img file inside. I'm guessing you're trying to flash the zip file which is completely wrong. You flash zip files inside the recovery not through fastboot. Hope this helps.
Click to expand...
Click to collapse
I been doing that Fastboot Boot Filename.img but the System doesnt regonize it (My PC)
IS there a one where i can Download for it
POCO F4 IS A FAILURE said:
I been doing that Fastboot Boot Filename.img but the System doesnt regonize it (My PC)
IS there a one where i can Download for it
Click to expand...
Click to collapse
The file has to be in adb directory and you have to open cmd in that directory. If the file is not in that directory you have to enter the full path to the file. And of course the phone has to be in fastboot mode. If the system doesn't recognize your phone then u probably aren't using platform tools like you should.
Something like this:
fastboot boot C:\Users\Username\Downloads\filename.img.
This is a path example find the path of your file and paste It in the command should work then. Or even easier just copy the file in adb directory and launch cmd in adb and you can use the first option in my previous comment.
HARDWELL919 said:
The file has to be in adb directory and you have to open cmd in that directory. If the file is not in that directory you have to enter the full path to the file. And of course the phone has to be in fastboot mode. If the system doesn't recognize your phone then u probably aren't using platform tools like you should.
Something like this:
fastboot boot C:\Users\Username\Downloads\filename.img.
This is a path example find the path of your file and paste It in the command should work then. Or even easier just copy the file in adb directory and launch cmd in adb and you can use the first option in my previous comment.
Click to expand...
Click to collapse
Thanks for explain, therefore If i do this Method, the Phone Reboots and Crash in a Loop, i didnt found a Way to fix it and would it be nice to you to send me a IMG File
Is it a Stock ROM File and IMG or Just Like the one that i need it
HARDWELL919 said:
The file has to be in adb directory and you have to open cmd in that directory. If the file is not in that directory you have to enter the full path to the file.
Click to expand...
Click to collapse
POCO F4 IS A FAILURE said:
Thanks for explain, therefore If i do this Method, the Phone Reboots and Crash in a Loop, i didnt found a Way to fix it and would it be nice to you to send me a IMG File
Is it a Stock ROM File and IMG or Just Like the one that i need it
Click to expand...
Click to collapse
if you want you can add me on ig and I can help you further from there.
HARDWELL919 said:
if you want you can add me on ig and I can help you further from there.
IG: tim_cesnovar
Click to expand...
Click to collapse
Sorry i dont use IG only Telegram or FB
POCO F4 IS A FAILURE said:
Sorry i dont use IG only Telegram or FB
Click to expand...
Click to collapse
write on messenger then.
Related
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
Hello fellow XDA'ers
I have waited and unlocked the phone, running the MIUI 12.5.1.0 (RKHEUXM) the EU Official Rom that came with the phone, and was following the guide on how to root from NaldoTech, but i'm stuck, magisk can't patch any Firmware file i throw at it...
Don't know what i am doing wrong, i opened the zip files manually looking for the boot.img file but i cant seem to find it in any of the Firmwares i download from XiaomiFirmwareUpdater.
Also tried downloading the rom file and extracting the contents using the xiaomi-flashable-firmware-creator, but no luck with that either, throws some permission error at extracting the payload.bin
what can i do from here??
thanks in advance
Easy peasy
Steps
Download Adb and fastboot tool.
Or just download TWRP image and start CMD from there "the folder containing the twrp img" (in destination bar type cmd and press Enter) /the drivers should be installed and working properly ofc.
1- set phone in fastboot mode then plug it in to PC
2- Type: fastboot boot twrp.img (twrp here is the img file)
Then the phone will boot into twrp.
The phone will be shown in PC. Paste Magisk in the phone. Then go back and flash it using TWRP. Then reboot to system. And you're all done.
laid1995 said:
.
Click to expand...
Click to collapse
doesnt boot to twrp just turns off :S
Fyat said:
doesnt boot to twrp just turns off :S
Click to expand...
Click to collapse
You're doing something wrong then.
Check all drivers are set up properly. Try flashing twrp then boot to it using Volume UP + Power button.
Make sure you download Nebrassy's twrp 3.5.10
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Fyat said:
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Click to expand...
Click to collapse
Whatever was your way, I'm glad you managed to do it
sir i need boot.img file for poco f3
ZAki6464 said:
sir i need boot.img file for poco f3
Click to expand...
Click to collapse
Good
Which version do you need?
Is this international version I should get to use in USA on T-Mobile to root the same way as you?
Amazon F3
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Fyat said:
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Click to expand...
Click to collapse
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Greenspoof said:
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Click to expand...
Click to collapse
I'm not sure where to find these options as i do not use the turbo mode, can you point to it?
Trying to root my phone but can't find a boot.img for the following- BD: 11.0.2.BE82CF MODEL:BE2015-METRO by T-Mobile. Thanks in advance for the help.
yuhh_chris said:
Trying to root my phone but can't find a boot.img for the following- BD: 11.0.2.BE82CF MODEL:BE2015-METRO by T-Mobile. Thanks in advance for the help.
Click to expand...
Click to collapse
Dude I been looking for this one for a while now bro... You brick your phone?
yuhh_chris said:
Trying to root my phone but can't find a boot.img for the following- BD: 11.0.2.BE82CF MODEL:BE2015-METRO by T-Mobile. Thanks in advance for the help.
Click to expand...
Click to collapse
If I had that version I'd do it myself. I was on the Metro by T-Mobile version but changed the firmware to the Global version to install a GSI Rom but I can still help you. The easy way is to use the Android 10 twrp.img for this device. Of course oem unlock should be enabled in developer options. You can either use ADB to reboot to bootloader or power off your device then hold the power + volume up and down together and it'll reboot into bootloader. Assuming you have adb and fastboot installed correctly on your PC and have added the binaries to path, just go into the folder where the twrp.img is, hold down shift then right click and choose open PowerShell here. Enter the command fastboot boot twrp.img. Once you boot into twrp you'll either need the Magisk zip on your SD card or you'll have to use adb sideload to flash the zip. You can't use the Magisk zip if it's stored somewhere in your internal storage because the data is encrypted. Honestly everything is much easier and better if you flash the Global firmware to the Metro by T-Mobile device. Here's the link to an already modified msm download tool. Msm download tool
sdflowers32 said:
If I had that version I'd do it myself. I was on the Metro by T-Mobile version but changed the firmware to the Global version to install a GSI Rom but I can still help you. The easy way is to use the Android 10 twrp.img for this device. Of course oem unlock should be enabled in developer options. You can either use ADB to reboot to bootloader or power off your device then hold the power + volume up and down together and it'll reboot into bootloader. Assuming you have adb and fastboot installed correctly on your PC and have added the binaries to path, just go into the folder where the twrp.img is, hold down shift then right click and choose open PowerShell here. Enter the command fastboot boot twrp.img. Once you boot into twrp you'll either need the Magisk zip on your SD card or you'll have to use adb sideload to flash the zip. You can't use the Magisk zip if it's stored somewhere in your internal storage because the data is encrypted. Honestly everything is much easier and better if you flash the Global firmware to the Metro by T-Mobile device. Here's the link to an already modified msm download tool. Msm download tool
Click to expand...
Click to collapse
I did get the global since i had bricked my phone but then updated it to android 11 seeming as i couldnt find a boot img, I can go back and flash it to that one if that link you sent to me is already rooted.
yuhh_chris said:
I did get the global since i had bricked my phone but then updated it to android 11 seeming as i couldnt find a boot img, I can go back and flash it to that one if that link you sent to me is already rooted.
Click to expand...
Click to collapse
No, it's not already rooted. It's just the stock firmware for the global version 10.5.5. I do have the boot.img for it as well as 11.0.4 global. Here they are if you need them.OnePlus boot.img
Hello !! I have a BIG problem. My Xiaomi 12x was on weekly update, until today. I wanted to update it by fastboot because the new update led to Miui 14 and therefore Android 13. I downloaded the Xiaomi.eu Rom on my pc, unzipped it and put my phone in Fastboot mode. In the file there was a .bat file which allowed to launch the update, and I launched it. Everything worked fine, but my phone won't start now. Could you help me please it's VERY important
UNMECOOL said:
Hello !! I have a BIG problem. My Xiaomi 12x was on weekly update, until today. I wanted to update it by fastboot because the new update led to Miui 14 and therefore Android 13. I downloaded the Xiaomi.eu Rom on my pc, unzipped it and put my phone in Fastboot mode. In the file there was a .bat file which allowed to launch the update, and I launched it. Everything worked fine, but my phone won't start now. Could you help me please it's VERY important
Click to expand...
Click to collapse
Thread for 12X: https://forum.xda-developers.com/f/xiaomi-12x.12615/
no fastboot mode, no recovery?
NOSS8 said:
Thread for 12X: https://forum.xda-developers.com/f/xiaomi-12x.12615/
no fastboot mode, no recovery?
Click to expand...
Click to collapse
Thank and yes, no fastboot or recovery mode, just a black screen with no responses at all
UNMECOOL said:
Thank and yes, no fastboot or recovery mode, just a black screen
Click to expand...
Click to collapse
Have you tried with the charger plugged in?
What rom did you flash(full name)?
UNMECOOL said:
Hello !! I have a BIG problem. My Xiaomi 12x was on weekly update, until today. I wanted to update it by fastboot because the new update led to Miui 14 and therefore Android 13. I downloaded the Xiaomi.eu Rom on my pc, unzipped it and put my phone in Fastboot mode. In the file there was a .bat file which allowed to launch the update, and I launched it. Everything worked fine, but my phone won't start now. Could you help me please it's VERY important
Click to expand...
Click to collapse
Try to install from fastboot with format data
jholfran3 said:
Try to install from fastboot with format data
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...tboot-update-xiaomi-12x.4531729/post-87877055
NOSS8 said:
Have you tried with the charger plugged in?
What rom did you flash(full name)?
--------------------------------------------------------------------------------------------------Reply : Yes i tried, but no signal even if i plug the charger in, the phone is still full black.
And i give you the name of the fastboot rom here and the link :
== xiaomi.eu_multi_XM12X_V14.0.22.12.8.DEV_v14-13-fastboot LINK == https://sourceforge.net/projects/xi...mi.eu/MIUI-WEEKLY-RELEASES/V14.0.22.12.8.DEV/
Click to expand...
Click to collapse
Download link == https://sourceforge.net/projects/xi...14.0.22.12.8.DEV_v14-13-fastboot.zip/download
Its seems that you bricked your phone
Do these and report here
1- Is PC recognize something when you connect your phone to it
Please look at device manager. Something like qusb bulk or qdloader 9008 port
2- If the answer of the above question is no press volume down and power button together for 15 sec
emprazol said:
Its seems that you bricked your phone
Do these and report here
1- Is PC recognize something when you connect your phone to it
Please look at device manager. Something like qusb bulk or qdloader 9008 port
2- If the answer of the above question is no press volume down and power button together for 15 sec
Click to expand...
Click to collapse
Hello, for the first, no my pc recognize nothing at all, for the second, also nothing just a black screen with no responses at all
Can anyone confirm if we would be able to easily root Xiaomi 13 pro?
I want to buy the phone only if it is possible to root this phone.
droidkoder said:
Can anyone confirm if we would be able to easily root Xiaomi 13 pro?
I want to buy the phone only if it is possible to root this phone.
Click to expand...
Click to collapse
Yep,possible but only with V14.0.4.0.TMBCNXM/V14.0.8.0.TMBCNXM ,for the moment
NOSS8 said:
Yep,possible but only with V14.0.4.0.TMBCNXM/V14.0.8.0.TMBCNXM ,for the moment
Click to expand...
Click to collapse
Hi, do you have a tutorial on how to root this device? I have tried using Magisk but it does not work at all. The patched boot.img flashes successfully but nothing happens after reboot. Nothing is installed at all and the system is exactly the same as before. My bootloader is unlocked. Booting directly using the patched boot.img does nothing as well. It is as if nothing has been flashed at all.
Edit: I found a solution. You have to use init_boot.img instead of boot.img.
VincentThacker said:
Hi, do you have a tutorial on how to root this device? I have tried using Magisk but it does not work at all. The patched boot.img flashes successfully but nothing happens after reboot. Nothing is installed at all and the system is exactly the same as before. My bootloader is unlocked. Booting directly using the patched boot.img does nothing as well. It is as if nothing has been flashed at all.
Edit: I found a solution. You have to use init_boot.img instead of boot.img.
Click to expand...
Click to collapse
And is Magisk usable, zygisk, modules etc...?
NOSS8 said:
And is Magisk usable, zygisk, modules etc...?
Click to expand...
Click to collapse
Yeah, I've managed to get it working on 14.0.10.0.TMBCNXM. The only module I've tested is Universal SafetyNet Fix which is working. Google Play showing certified. Updating can be done without a PC as well. I first installed on 14.0.8.0, then installed 14.0.10.0 from the device updater itself. Before rebooting, simply go to Magisk and select the option to install to inactive slot. Reboot and you have Magisk working on the new version.
VincentThacker said:
Yeah, I've managed to get it working on 14.0.10.0.TMBCNXM. The only module I've tested is Universal SafetyNet Fix which is working. Google Play showing certified. Updating can be done without a PC as well. I first installed on 14.0.8.0, then installed 14.0.10.0 from the device updater itself. Before rebooting, simply go to Magisk and select the option to install to inactive slot. Reboot and you have Magisk working on the new version.
Click to expand...
Click to collapse
Bro can write a guide how to root? I try follow this method, but failed. https://forum.xda-developers.com/t/...urself-and-optionnal-debloat-privacy.4337693/
Cuz i have a m3 pro. I thinking should be same. But seems like its not
darrenlimch said:
Bro can write a guide how to root? I try follow this method, but failed. https://forum.xda-developers.com/t/...urself-and-optionnal-debloat-privacy.4337693/
Cuz i have a m3 pro. I thinking should be same. But seems like its not
Click to expand...
Click to collapse
Nope,this not the same method.
https://forum.xda-developers.com/t/root-gained.4290689/
VincentThacker said:
Hi, do you have a tutorial on how to root this device? I have tried using Magisk but it does not work at all. The patched boot.img flashes successfully but nothing happens after reboot. Nothing is installed at all and the system is exactly the same as before. My bootloader is unlocked. Booting directly using the patched boot.img does nothing as well. It is as if nothing has been flashed at all.
Edit: I found a solution. You have to use init_boot.img instead of boot.img.
Click to expand...
Click to collapse
Cuz you mention here use init_boot.img, i try use magisk patch the init_boot.img and flash it via adb, but then bootloop into fastboot. Mind write a tutorial for us? As i believe you are the first to root succesfully. Thanks in advance bro.
NOSS8 said:
Nope,this not the same method.
https://forum.xda-developers.com/t/root-gained.4290689/
Click to expand...
Click to collapse
Misunderstood bro. I have a mi 13pro as well. China version. Need to root it. Im just saying that i have another poco m3 pro. I though they use same method
darrenlimch said:
Misunderstood bro. I have a mi 13pro as well. China version. Need to root it. Im just saying that i have another poco m3 pro. I though they use same method
Click to expand...
Click to collapse
Understood,You have to use init_boot.img instead of boot.img.
Common tutorial
1. Find or redownload the TGZ file for your current ROM or other rom.
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
NOSS8 said:
Understood,You have to use init_boot.img instead of boot.img.
Common tutorial
1. Find or redownload the TGZ file for your current ROM or other rom.
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
Click to expand...
Click to collapse
Tried this method. But like VincentThacker mentioned at first. After flash that modded.img, nothing was change. So might need his help already. No idea which init_boot.img is mentioning.
darrenlimch said:
Tried this method. But like VincentThacker mentioned at first. After flash that modded.img, nothing was change. So might need his help already. No idea which init_boot.img is mentioning.
Click to expand...
Click to collapse
I guess it is in the Fastboot rom or a command and root for what no rom or twrp currently available.
If it is to delete apps there are many tools or with ADB commands.
NOSS8 said:
I guess it is in the Fastboot rom or a command and root for what no rom or twrp currently available.
If it is to delete apps there are many tools or with ADB commands.
Click to expand...
Click to collapse
I need android auto to work, this china version doesnt have android auto
So yea, need use magisk to install that android auto module.
darrenlimch said:
I need android auto to work, this china version doesnt have android auto
So yea, need use magisk to install that android auto module.
Click to expand...
Click to collapse
This is the guide. It's basically the standard method but you patch init_boot.img instead of boot.img. Both can be extracted from the fastboot firmware.
VincentThacker said:
This is the guide. It's basically the standard method but you patch init_boot.img instead of boot.img. Both can be extracted from the fastboot firmware.
Click to expand...
Click to collapse
So to summarize, extracting the boot.img from the Fastboot rom, V14.0.10.0.TMBCNXM/V14.0.22.12.26.DEV/V14.0.8.0.TMBCNXM/V14.0.4.0.TMBCNXM roms doesn't work?
NOSS8 said:
So to summarize, extracting the boot.img from the Fastboot rom, V14.0.10.0.TMBCNXM/V14.0.22.12.26.DEV/V14.0.8.0.TMBCNXM/V14.0.4.0.TMBCNXM roms doesn't work?
Click to expand...
Click to collapse
Yeah, as I mentioned above, boot.img does not work; you have to use init_boot.img which has a size of exactly 8 MiB. If it does not have this size, you've got the wrong file. It probably has to do with the boot method used by the device as described here. The flashing command must also use init_boot_ab instead of boot_ab.
Guys i was in the same boat.
I have successfully root Mi 13 Pro, but i have another issue if anyone can help. Mi Wallet keeps changing as default payment method even though i have GPay selected.
VincentThacker said:
Yeah, as I mentioned above, boot.img does not work; you have to use init_boot.img which has a size of exactly 8 MiB. If it does not have this size, you've got the wrong file. It probably has to do with the boot method used by the device as described here. The flashing command must also use init_boot_ab instead of boot_ab.
Click to expand...
Click to collapse
Is it a must to include the "_ab" part in the command?
Jaberbenet said:
Is it a must to include the "_ab" part in the command?
Click to expand...
Click to collapse
Can I use magisk hide and passing safetynet with this device? Gonna buy this phone in Europe.
Wanna be sure that the module magisk hide props and universal safetynet-fix passes safetynet.
Can anyone confirm it for me?
aygul12345 said:
Can I use magisk hide and passing safetynet with this device? Gonna buy this phone in Europe.
Wanna be sure that the module magisk hide props and universal safetynet-fix passes safetynet.
Can anyone confirm it for me?
Click to expand...
Click to collapse
Yeah everything works with EU beta + DFe neo + magisk 25.2.. my phone passes safetynet without safetyfix module and google certified