Related
Hello every body
i cant find the magisk_patched 10.3.3 (Indian version), i searched every were but unfortunately i couldn't find it, i also try to extracted the boot.img from the update zip through payload dumper and then batch it on old nexus 6 device which is retired as workaround solution then try to flash the file via fastboot but it keeps looping at fastboot screen
please help guy i need the magisk_patched 10.3.3 (Indian version) file so my phone work back to normal
any help is highly appreciated
God bless you all
suhb20 said:
Hello every body
i cant find the magisk_patched 10.3.3 (Indian version), i searched every were but unfortunately i couldn't find it, i also try to extracted the boot.img from the update zip through payload dumper and then batch it on old nexus 6 device which is retired as workaround solution then try to flash the file via fastboot but it keeps looping at fastboot screen
please help guy i need the magisk_patched 10.3.3 (Indian version) file so my phone work back to normal
any help is highly appreciated
God bless you all
Click to expand...
Click to collapse
from Next time do this,
Don't ever flash some random Boot image from Internet, just boot it -
In short -
Get a recently magisk patched boot image (either recent beta or recent stable build patched boot image)
Connect your phone to PC
now reboot to bootloader and run this command,
fastboot boot magisk_patched.img
Don't flash boot image
Install Magisk manager and from it select Install > Direct install
Reboot
But since you have already flashed the wrong one. Here , flash the magisk_patched boot img of 10.3.3 Indian Build -
https://androidfilehost.com/?fid=8889791610682876433
Note : I am not responsible if anything goes wrong, Flash it at your own risk.
Aswin08 said:
from Next time do this,
Don't ever flash some random Boot image from Internet, just boot it -
In short -
Get a recently magisk patched boot image (either recent beta or recent stable build patched boot image)
Connect your phone to PC
now reboot to bootloader and run this command,
fastboot boot magisk_patched.img
Don't flash boot image
Install Magisk manager and from it select Install > Direct install
Reboot
But since you have already flashed the wrong one. Here , flash the magisk_patched boot img of 10.3.3 Indian Build -
https://androidfilehost.com/?fid=8889791610682876433
Note : I am not responsible if anything goes wrong, Flash it at your own risk.
Click to expand...
Click to collapse
Thank you very much for your reply, allow me to explain what happened before i proceed to your solution
- After updating from 10.3.2 to 10.3.3 i was able to flash magisk_patched file but the problem is no WIFI & SIM
- after many attempts by flashing magisk_patched the device keeps looping to either fastboot mode or unlocked boot screen.
- I extracted the boot.img file from original full update file by using using Payload Dumper then i moved that boot.img file to an old NEXUS phone which is rooted so i can patched it by using magisk which i then flash it back to my OnePlus 7T but it keeps looping to fastboot mode
- By some how i was able to work after downloading from (https://drive.google.com/drive/folders/1MCfCPci7F7FGl5ZHVTNRKVq9j8RBCUih)
- when i reached home i wanted to update magisk (i select to inactive OTA slot) everything is missed up , but unfortunately the device keeps looping even though i used this file (https://forum.xda-developers.com/oneplus-7t/how-to/oos-10-0-11-magisk-patched-boot-img-t4106435)
- Suddenly the device shows "Qualcomm crash dump mode" which is a bad sign but after pressing Power + Vol UP + Vol DOWN i was able to get back the fastboot screen (which i think its a good sign)
- i flashed magisk_patched.img 10.0.11 but the device keeps looping to unlocked boot screen.
How can i find the correct magisk_patched.img for 10.3.3 ? i am using Titanium Back, is there a way that i can connect the phone to my PC and copy all my files before i flash a new Stock OS if this is the last solution !!
Question : If i use another solution by using "TOOL ALL IN ONE" then flash factory image ? will this fix the problem and keep my data
Note : i am very optimistic that my data is safe but its an issue of booting...... I hope so
Wating for your reply and thank you very much
suhb20 said:
Thank you very much for your reply, allow me to explain what happened before i proceed to your solution
- After updating from 10.3.2 to 10.3.3 i was able to flash magisk_patched file but the problem is no WIFI & SIM
- after many attempts by flashing magisk_patched the device keeps looping to either fastboot mode or unlocked boot screen.
- I extracted the boot.img file from original full update file by using using Payload Dumper then i moved that boot.img file to an old NEXUS phone which is rooted so i can patched it by using magisk which i then flash it back to my OnePlus 7T but it keeps looping to fastboot mode
- By some how i was able to work after downloading from (https://drive.google.com/drive/folders/1MCfCPci7F7FGl5ZHVTNRKVq9j8RBCUih)
- when i reached home i wanted to update magisk (i select to inactive OTA slot) everything is missed up , but unfortunately the device keeps looping even though i used this file (https://forum.xda-developers.com/oneplus-7t/how-to/oos-10-0-11-magisk-patched-boot-img-t4106435)
- Suddenly the device shows "Qualcomm crash dump mode" which is a bad sign but after pressing Power + Vol UP + Vol DOWN i was able to get back the fastboot screen (which i think its a good sign)
- i flashed magisk_patched.img 10.0.11 but the device keeps looping to unlocked boot screen.
How can i find the correct magisk_patched.img for 10.3.3 ? i am using Titanium Back, is there a way that i can connect the phone to my PC and copy all my files before i flash a new Stock OS if this is the last solution !!
Question : If i use another solution by using "TOOL ALL IN ONE" then flash factory image ? will this fix the problem and keep my data
Note : i am very optimistic that my data is safe but its an issue of booting...... I hope so
Wating for your reply and thank you very much
Click to expand...
Click to collapse
Did you try flashing the 10.3.3 boot image i have provided above?
And btw you can't get out the data in any other way without booting because of encryption.
Aswin08 said:
Did you try flashing the 10.3.3 boot image i have provided above?
And btw you can't get out the data in any other way without booting because of encryption.
Click to expand...
Click to collapse
Hello,
You know what today afternoon i was just getting the USB cable so i can connect my OnePlus 7T to my laptop when i just picked up my phone i noticed that its not on the Unlocked boot loader screen" its was just normal as before (every is was working fine...every thing) i was really astonished what happened when i checked the OS its 10.3.3 and every thing is working fine even root is working, what i need to do is update magisk (direct install) as you told me
I really don't know what happened but i am very happy for that
i really appreciate your prompt help and assistance even thought i didn't do any thing.
one question please ..what is the difference between :
- fastboot boot magisk_patched.img
- fastboot flash boot magisk_patched.img
Best regards and wishes
suhb20 said:
Hello,
You know what today afternoon i was just getting the USB cable so i can connect my OnePlus 7T to my laptop when i just picked up my phone i noticed that its not on the Unlocked boot loader screen" its was just normal as before (every is was working fine...every thing) i was really astonished what happened when i checked the OS its 10.3.3 and every thing is working fine even root is working, what i need to do is update magisk (direct install) as you told me
I really don't know what happened but i am very happy for that
i really appreciate your prompt help and assistance even thought i didn't do any thing.
one question please ..what is the difference between :
- fastboot boot magisk_patched.img
- fastboot flash boot magisk_patched.img
Best regards and wishes
Click to expand...
Click to collapse
boot command just boots that img temporarily, when you restart the phone 2nd time, your original img will be retained . If anything goes wrong you won't get into trouble.
flash is.. usual permanently flashing the boot image into your system.
I saw a lot of outdated methods of rooting this phone that will cause a lot of bugs to the device, because of the outdate magisk_patched boot image
HERE'S AN UPDATED VERSION
REQUIREMENTS
Unlocked bootloader
Minimal ADB + Fastboot ( I use 1.4.3 PORTABLE) https://forum.xda-developers.com/showthread.php?t=2317790
Pack with required images, including the new magisk_patched.img (required_files.zip, at the bottom of the post)
INSTRUCTIONS
Extract both the minimal adb + fastboot and required_files.zip to a folder
Boot your device in fastboot mode (power if off, then press power button + volume down until you see a bunny working on a Android robot)
Connect the device to the PC via a USB cable (I suggest the one you use of the charger too)
Copy the images from required_files.zip to the folder where you extracted minimal adb + fastboot
Open a cmd/powershell window in minimal adb + fastboot folder (make sure once again that you copied the files from required_files here)
Type these commands:
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
Enjoy! Your phone will reboot (it shouldn't take more than usual btw)
WARNING!
I'm not responsable for any damaaged device, you take the risk
What I basically did is gave you guys an updated magisk_patched image because the the one seen on the internet for now is an old one that caused several problems on some devices, if you're running any other version that the one in the title you should make your own magisk_patched image
Does this method erase user data and do a factory reset, as other guides say?
I know there is always a risk and it's important to make a backup, but my question is if everything goes as expected, is the phone data erased?
Other guides do the command "fastboot erase userdata" before "fastboot erase cache".
alpersoft said:
Does this method erase user data and do a factory reset, as other guides say?
I know there is always a risk and it's important to make a backup, but my question is if everything goes as expected, is the phone data erased?
Other guides do the command "fastboot erase userdata" before "fastboot erase cache".
Click to expand...
Click to collapse
I removed the erase data line cuz I didn't saw why it would be required since it was working great without it
@Bogdi_P
Can you please share how you did modifications?
I am on MIUI Global 12.0.2 Stable 12.0.2.0(QJOINXM) which is an Indian ROM. Model is M2003J15SI.
I downloaded my firmware zip from Updater -> Download latest package.
I can take boot.img, vbmeta.img from it.
After I can patch the boot.img with Magisk.
But what I have to do with vbmeta.img?
HemanthJabalpuri said:
@Bogdi_P
Can you please share how you did modifications?
I am on MIUI Global 12.0.2 Stable 12.0.2.0(QJOINXM) which is an Indian ROM. Model is M2003J15SI.
I downloaded my firmware zip from Updater -> Download latest package.
I can take boot.img, vbmeta.img from it.
After I can patch the boot.img with Magisk.
But what I have to do with vbmeta.img?
Click to expand...
Click to collapse
You can manually patch vbmeta file using an Hex Editor or you can download any already patched vbmeta file for any MIUI version for this device and flash it.
Successfully rooted + edXposed on STOCK rom and GSI roms.
Patched my own boot image (magisk_patched.img) with magisk manager.
To make Netflix & some other apps work, get the liboemcrypto disabler module in Magisk Manager
Also, to pass SafetyNet:
- Enable Magisk Hide
- Install and activate the Riru - Core and Riru - EdXposed (YAHFA or SANDHOOK, both work) modules in magisk manager
- Get EdXposed manager
- Get the HiddenCore Module and activate it
- In EdXposed Manager: Compat List, and tick HiddenCore Module
To avoid issues (Chrome crashes, potential SIM issues, etc..) with HiddenCore:
- In EdXposed Manager, go to Settings > Framework > Enable "App List mode"
- Still in EdXposed Manager, go to Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Play Store, Google Services Framework
- Reboot and enjoy, you're all set and SafetyNet should pass just fine, and you can do whatever you want.
i have question: vbmeta.img above can be used for all versions of miui or only ver 12.0.2
i am using ver 12.0.3 eea
Pls help not working 12.0.3
tanks
I have patched the image with magisk manager
ma259 said:
You can manually patch vbmeta file using an Hex Editor or you can download any already patched vbmeta file for any MIUI version for this device and flash it.
Click to expand...
Click to collapse
can i download your vbmeta and work for 12.0.4? maybe? yes? no?
New member here! Will this work also on miui 12.0.5 global?
I have not installed root and the phone is not restored
What is working for MERLIN ?
Take a look: https://forum.xda-developers.com/t/...aomi-redmi-note-9-xiaomi-redmi-10x-4g.4204873
V11.0.5.0:
MAGISK: Working.
MAGISK MANAGER: Working.
TWRP: Working.
RIRU-CORE: Working.
RIRU-EDXPOSED: Working.
EDXPOSED-MANAGER: Working.
XPRIVACYLUA: Working.
MINMINGUARD: Not tested yet.
TITANIUMBACKUP: Not tested yet.
Hi,
I was in 12.0.2 following your method :
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
my phone can only boot in fastboot no longer in system.
I am able to go to stock recovery using power + up but I would like to avoid to reset my phone.
Please help what's wrong, can someone help ?
accnetdev said:
Hi,
I was in 12.0.2 following your method :
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
my phone can only boot in fastboot no longer in system.
I am able to go to stock recovery using power + up but I would like to avoid to reset my phone.
Please help what's wrong, can someone help ?
Click to expand...
Click to collapse
same here
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Windwell said:
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Click to expand...
Click to collapse
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
Hey mate,
Thanks for responding. Sorry for the late reply.
From what you had suggested, I did "fastboot --set-active=a" , "fastboot flash boot boot.img", and "fastboot reboot" (with the stock unpatched boot.img) the commands were successful once again, but there were no effective changes.
Afterwards, I did "fastboot --setactive-b", "fastboot flash boot boot.img", and "fastboot reboot" the commands were successful once more, and this time, I was finally able to go into recovery mode. On the other hand, in recovery mode I wiped the cache and erased everything, but unfortuantely I still could not boot into Android, even though I tried to flash boot the image once more.
Thank you for these commands, as I was at least able to recover recovery mode.
Any other suggestions maybe?
Hello,
Use this tool and it will fix it, I had the same problem. Just download the software and flash it in Qualcomm EDL mode.
MSMDownload image needed
Hello guys, I managed to flash the wrong image to OnePlus NORD N100 BE2013, I overlooked for the first time what I'm doing and messed it up Now it's in Qualcomm EDL mode and I need and image to flash it to bring it back do life, anyone I can...
forum.xda-developers.com
I alsp posted boot.img which is compatible you can flash it. Link is in the comments.
Thanks
Boot.img from nord n100 in this thread, I exctracted and rooted it myself.
I WHANT RECOVERY Boot.img FOR ROOT MY ONEPLUS NORD N100
I unlock bootloader and i whant to root with magisk my phone, i need boot.img for rocovery..I try anather boot.img from One plus nord, etc, i sucessfull flash this recovery's with command in windows but is no go in recovery, stay in bootloop..Can...
forum.xda-developers.com
Hello,
I used the tool MSMDownload but unfortunately I was unable at all to boot into Qualcomm Edl mode, even though I have installed correctly all the drivers for Windows Qualcomm, and OnePlus USB drivers, and used the correct method (Volume Button UP and Down at the same time whilst connecting the phone via USB). I tried flash booting with the boot.img you gave me, but still no changes. I am still stuck in Fastboot.
If you had encountered the same issue back then, can you tell me the excat procedure you did please?
Thank you so much.
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
oh
thts ok man
بلوک سبک
I will try to make a fastboot image for OnePlus NORD N100 BE2013 with 10.5.5 and upload it to mega, I'll send you the link. If you are in fastboot mode you will be able to flash it I believe, let me have a look.
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
motovnet said:
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
Click to expand...
Click to collapse
For some reason Qualcomm Mode Edl does not launch whatsoever.
motovnet said:
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
Click to expand...
Click to collapse
Thank you that's very kind of you. I think the only way to fix it by flash boot.img, but I have doubts because it does not work.
The only commands I am doing are "fastboot devices", "fastboot flash boot boot.img"
With the fastboot image you will be able to flash everything, it contains not only boot.img but system and etc. I managed to boot mine and bring it back to life by reflashing everyhing.
So the only thing I need to do is "fastboot flash boot ''.img" right?
Where can I get all the nesscary files?
And how did you manage to root it?
The fastboot image flashes all partitions, not just boot with stock Oxygen OS 10.5.5
What you need to do is run flash-all.bat from the archive and it will flash the entire os not just boot.img.
If you can't get to EDL mode, fastboot flash is the only solution. What model does it say in the back? This one was EUROPE BE2013.
Is your EU or Global device?
Archive is uploading still.
Thanks
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
2.55 GB file on MEGA
mega.nz
This is a fastboot image for OnePlus NORD N100 EU BE2013 device.
Extract it to a new folder, it contains fastboot in it.
Right click flash-all.bat and run as admin.
You can open the flash-all.bat file with notepad to check yourself there is nothing strange in it. I used a bat file from the forum that was fastboot image for OnePlus NORD and changed it to use the .img files for OnePlus NORD N100.
Contains Oxygen 10.5.5, once you bring it back to life (IF YOU HAVE THIS MODEL), you can use magisk to patch the boot.img and flash it via fastboot.
This is how I rooted it and it worked properly.
Please use it with caution and ensure your model matches! I can not guarantee it will work on other devices.
If you can't go to EDL mode, this is your way to go, but I don't know if flashing GLOBAL version will work.
Thanks
Windwell said:
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
Click to expand...
Click to collapse
I would guess BE2013 is the EU one, as this worked on mine.
motovnet said:
I would guess BE2013 is the EU one, as this worked on mine.
Click to expand...
Click to collapse
Okay thank you for helping me. I will try this later and keep you in touch.
Windwell said:
Okay thank you for helping me. I will try this later and keep you in touch.
Click to expand...
Click to collapse
Thanks, let me know if it works for you. If you're unable to flash it via fastboot, only EDL will help.
So I have tried to flash a GSI on my Nord N100 and while it boots the phone gets stuck at the boot animation for a good long while. The steps I have taken to flash the GSI were to oem unlock the phone, boot into the bootloader,fastboot reboot fastboot, flash the gsi system image,flash the stock vbmeta image, flash the stock vbmeta system image I also have and then finally rebooting the device after using the fastboot -w command. Did I maybe do something wrong in the steps I took or use a wrong file?
Hi, I think you have to disable AVB, not try to use vbmeta from stock
Here are instructions from Oneplus Nord, you can try again with those vbmeta files
How to: Run an GSI on NORD
To run an GSI on your Nord: Unlock bootloader Toogle oem unlock in Developer options Reboot to fastboot (turn of phone, press volume down and start) Run -fastboot oem unlock Install GSI (check...
forum.xda-developers.com
Wouldn’t using vbmeta files made for a different phone mess up my phone?
svaethier said:
Wouldn’t using vbmeta files made for a different phone mess up my phone?
Click to expand...
Click to collapse
I'd guess it's an empty image created as described here: https://wiki.postmarketos.org/wiki/Android_Verified_Boot_(AVB) section disable verrified boot. And an empty image should be universal I would think
well i tried using that vbmeta file and the phone still gets stuck at the boot animation so maybe it's not the vbmeta file that's not working
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.
dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance
Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.
I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)
chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).