Hey guys, I have been working on this for a while an I think I finally have the answer as to keep stock AS990 and have a custom recovery.
Please note I will not be responsible for bricked devices. If you don't understand something do some research before you start.
Lets get started.
To get roms to install, I had to use the whole guide found here then install a custom rom, create a TWRP backup, take the backup off the internal sd card then once I finished the steps below I put the backup back onto my internal sdcard and used TWRP. Now some of you may be asking "Why the heck did he do that for?". Well when I went to install a ROM, I could not mount the system partition so therefore I used this work around because I had made a backup before I found out the method below. If anyone has a fix for this please be sure to comment.
Download and extract the files here
First off you will need to be on Stock AS990 and rooted. If you have not done this please follow the guide located here to do that.
If you are on a rom that cannot be rooted, follow this guide and use the files found in the restore bullet point to downgrade then root. Backing up your build.prop should not be necessary in this case since you are doing a downgrade.
After you have done this, root and use flashify to install ls990 TWRP.
Reboot your device into recovery.
If all goes well, You should now be stuck in fastboot mode.
Flash the following files found in the folder you downloaded earlier.
Open the folder you extracted the files to earlier, hold shift, right click in a section of the folder where no files are then select "open command window here".
Type the following commands into the CMD window.
fastboot flash aboot aboot.bin
fastboot flash boot boot.bin
fastboot flash dbi dbi.bin
fastboot flash factory factory.bin
fastboot flash misc misc.bin
fastboot flash modem modem.bin
fastboot flash persist persist.bin
fastboot flash PrimaryGPT PrimaryGPT.bin
fastboot flash recovery recovery.bin
fastboot flash rct rct.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash tz tz.bin
Pull the battery and turn back on and the rom should now boot back into your stock system.
Again use flashify to install ls990 TWRP.
Make a recovery of your current rom.
Flash the rom you backed up.
For me I have figured out how to get mms, data texting and calling on a custom rom with my carrier (Carolina West Wireless).
I installed Google Hangouts then used shortcut master lite to find the apn settings in hangouts which are not the same as using other methods.
If I left out anything please let me know thanks.
Well that's all for now.
Not sure who all to give credit to but this is a compilation of my work as well as all the guys who made the post above.
You may be able to use this method to root as well but have not tired that yet.
Related
I need this clear in my head, cos I am going around in circles trying to get a ROM working on my HOX.
I have an unlocked HOX and I use a MAC.
My understanding of what I need to do to get a custom ROM working is as follows (please correct me if/where I go wrong):
Phone needs to be unlocked: YES, DONE.
Preferred ROM downloaded from chosen XDA link: YES, DONE.
Boot.img file from said ROM also obtained: YES, DONE.
Via fastboot, I need to firstly flash the recovery (This, I can do. I'm using ClockworkMod 5.8.4.0)
I know that I then need to flash the downloaded 'Boot.img' (I don't know if it needs to be located on the SDCard first, or straight from the Mac).
Looks like I now need to flash empty the cache (Again, this I can do).
Then I know that I need to boot into recovery.
Copy ROM.zip over onto the SDCard.
Mount the SDCard and select 'install zip from sdcard' then select the ROM.zip.
Reboot system now.
ROM should work.
So, why am I getting stuck on the ROM's boot up splash screen
You need to flash the boot.img from the fastboot folder on the mac
Its the same as flashing the recovery
But replace :
Fastboot flash recovery recovery.img with
Fastboot flash boot boot.img
And don't forget to make a full wipe in the recovery before installing the new rom
Mr Hofs said:
You need to flash the boot.img from the fastboot folder on the mac
Its the same as flashing the recovery
But replace :
Fastboot flash recovery recovery.img with
Fastboot flash boot boot.img
And don't forget to make a full wipe in the recovery before installing the new rom
Click to expand...
Click to collapse
FINALLY! Success. Thank you.
No problem ! :thumbup:
CASE CLOSED !
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
you didnt search very well...
there's a return to stock thread in the general section.
Just use this: http://forum.xda-developers.com/showthread.php?t=1766475
Read last 3-4 pages.
AbhishekS said:
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
Click to expand...
Click to collapse
search again... and in short if u are flashing your rom with stock image u dont have to install the bootloader and radio img again... search how to flash stock image using adb..
Sent from my Galaxy Nexus using xda premium
AbhishekS said:
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
Click to expand...
Click to collapse
Hi, let me try to help you
Galaxy Nexus is my first smartphone. So i'm pretty new at flashing things. I did some research last year to learn how to flash stuff in it and that's how i learned to make a fresh install:
-Make sure you have the SDK platform-tools and the Galaxy Nexus driver properly installed on your PC. Also, make sure you have USB debuging enabled on your device.
-Download the factory image that fits your phone at https://developers.google.com/android/nexus/images
-Open up the tgz file you just downloaded and extract the files:
-boot.img
-bootloader-maguro-primemd04.img
-radio-maguro-i9250xxlj1.img
-recovery.img
-system.img
-userdata.img
Extract the files in the platform-tools folder to make things easier.
-Connect your Nexus to your PC, open the command prompt, go to the platform-tools folder and type
(Do not turn off, disconnect or close the cmd prompt windows until everything is done. Again, make sure you have the nexus driver properly installed on your Windows)
Code:
adb reboot-bootloader
(this command will reboot your device to recovery mode)
With your device on recovery mode, type the following commands to erase your device:
Code:
fastboot erase boot
Hit enter, then:
fastboot erase cache
Hit enter, then:
fastboot erase recovery
Hit enter, then:
fastboot erase system
Hit enter, then:
fastboot erase userdata
-Now you're going to flash the new files you have downloaded and extracted steps before:
Code:
fastboot flash bootloader bootloader-maguro-primemd04.img
(or whatever name your bootloader img file has. In this case the bootloader file is "bootloader-maguro-primemd04.img")
Code:
fastboot reboot-bootloader
(you'll need to reboot after flashing the bootloader)
Code:
fastboot flash radio radio-maguro-i9250xxlj1.img
Flash the radio
Code:
fastboot reboot-bootloader
Reboot again
Code:
fastboot flash system system.img
Flash system
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot-bootloader
We are almost done!
Code:
fastboot erase cache
Code:
fastboot reboot
Done! Reboot to Android. The first boot may take some more time than the usual. Don't worry!
-
If you want to flash a custom recovery, download it from their website, go into fastboot mode and flash it using the command to flash the recovery.
Code:
fastboot flash recovery [recovery filename].img
The same command used when flashing the recovery on the fresh install above
That's the way i learned how to do it from scratch. In case someone more experienced has any thoughts about it, i'd like to hear as i'm not an expert and learned by researching it on my own...
This is how it's done, PROPER. Well done, mnoguti.
a maguro wrote this.
@mnoguti: You have said that to flash a custom recovery, one needs to go to the recovery mode and flash the custom recovery, but you said that flashing the stock recovery should be done in bootloader.
Is it fine to flash custom recovery from bootloader instead of recovery?
AbhishekS said:
@mnoguti: You have said that to flash a custom recovery, one needs to go to the recovery mode and flash the custom recovery, but you said that flashing the stock recovery should be done in bootloader.
Is it fine to flash custom recovery from bootloader instead of recovery?
Click to expand...
Click to collapse
you don't have to go into the recovery mode to flash recovery, just boot into fastboot mode and flash recovery using command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
obviously replace the recovery.img with the name of the custom recovery file you downloaded, make sure the custom recovery file is in the same folder as fastboot/adb otherwise you'll have to do it like:
fastboot flash recovery C:\Downloads\recovery.img
Click to expand...
Click to collapse
Yes, that's what I thought. Thank you.
I had initially felt that stock recovery can flashed only in bootloader and custom recoveries can be flashed only by booting into stock recovery. But somewhere in my mind had a doubt on it and so asked. Thanks for clearing the doubt.
And a big thanks to @mnoguti for posting those steps. Worked like a charm for me.
Obviously he meant fastboot mode..
a manta wrote this.
AbhishekS said:
Yes, that's what I thought. Thank you.
I had initially felt that stock recovery can flashed only in bootloader and custom recoveries can be flashed only by booting into stock recovery. But somewhere in my mind had a doubt on it and so asked. Thanks for clearing the doubt.
And a big thanks to @mnoguti for posting those steps. Worked like a charm for me.
Click to expand...
Click to collapse
It's "fastboot mode". Sorry for the mistake!
I've updated my post and now it's right
Hello everyone,
Need some help here, i don't want to factoy flash again, i have a nexus 7 2013 wifi on Lollipop (5.0) rooted with a custom kernel and TWRP.
How to update with the new OTA to 5.0.1, without loosing data and without having FC after the flash ?
Is there a way to flash it with TWRP or with Nexus Root Toolkit ?
I read that i can download the 5.01 system image from Google, extract the system.img from it and flash it in fasboot and i will conserve my data and be updated to 5.0.1.
Is that correct and without issues?
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?
yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
Is running fastboot format cache necessary?
^I'm no expert but I can't see why not to run it, not going to hurt anything and could possibly save you some problems later.
anhhuy1605 I'd just go to the factory images page download it and do a full clean install. I would not recommend trying to upgrade from KK and keeping data. Though I'm sure it's worked fine for lots of people.
yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
It's all done, i flashed only the system.img then TWRP and elementalx, i can't live without the DT2W.
Thank You for your very detailed post.
anhhuy1605 said:
Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?
Click to expand...
Click to collapse
First thing first:
1. Uninstall any mod and busybox and xposed (Make sur that your system is clean) thant Unroot with supersu
2. Flash the stock boot (kernel) and stock recovery
3. Sideload the ota for 5.0 and flash it
Hopefully it will be allright but don't forget to backup your data with titanium backup to your computer.
Hello eddy0147,
from where did you get the system.img for 5.0.1?
eddy0147 said:
It's all done, i flashed only the system.img then ...
Click to expand...
Click to collapse
Thanks!
tungdil
tungdil said:
Hello eddy0147,
from where did you get the system.img for 5.0.1?
Thanks!
tungdil
Click to expand...
Click to collapse
If you decompress the new Factory Image from here : https://developers.google.com/android/nexus/images
You're welcome
Thank you very much! :good:
Actually I expected that this factory image would also only contain a system.new.dat just like the LRX21P did before. That's why I din't even have a look at it. I just downloaded and extracted it, and could convert it to a mountable image (using simg2img)
Cheers,
tungdil
P.S.: Just finished flashing Stock 5.0.1 as secondary ROM with MultiROM after building a flashable zip using this system.img. Thanks again eddy0147 for the hint :good:
Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.
Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
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).