Database Develop

AT&T 4G/LTE not working after flashing stock boot.img

Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!

tiduscrying said:
Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!
Click to expand...
Click to collapse
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.

mrmazak said:
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.
Click to expand...
Click to collapse
My phone came out of the box with version 6.1, so i was able to flash the modified stock update from here that updates the phone from 6.1 all the way to 7.4.2. I took the boot.img from the vanilla 6.1 prime update and flashed it, so that is probably what the issue is. I assume the next step would be to flash the boot.img from the 7.4.2 version, but I can't seem to find a normal version of the v.7.4.2 update that I can just take the boot.img from (unless I can take it from one of these flashable zips?). If it helps, here is a screenshot of my system info which has all the version numbers and whatnot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Okay, so I flashed the boot.img from a slightly modified zip of the 7.4.2 update (from here) and thankfully, everything is working fine now. 4G LTE is working swimmingly and I feel like a moron. Lesson learned. Kids, make your backups!

Well, now here is another weird issue. The 4G LTE data is working perfectly fine and speedy as ever, but MMS messages are not being received or sent for whatever reason now. I've already manually entered the correct APN settings and reset them as well to no avail. Any suggestions on this? I've also tried some other SMS apps (such as Pulse) and cleared Messenger's cache and data settings, but that all seems like it did nothing.
Edit: Well, I just flashed the modified 7.4.2 rom that's from the Rom's section of the Blu R1 HD board and MMS is working again. Looks like something other than the boot.img was messed up or something. I did a dirty flash so luckily my roms are in tact.
Edit 2: Sigh, I have no idea what's happening. MMS keeps getting screwey whenever I even start playing around with Xposed (more specifically, Gravity Box). I have no idea why this is happening now all of the sudden. A few days ago before I messed with Magisk, Gravity Box wasn't messing with my MMS messages (at least... I don't think it was...).

[GUIDE] How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader

I'm not responsible for any damage on your phone. Do it at your own risk. Don't come angry or get mad at me, because I'll totally ignore them. I'm just trying to help, if you think this is dangerous for your phone or not worth it, please do back down.
If my thread here is a duplicate, then please feel free to report it so it would be brought down.
I don't own this device, It was my friends device, and I just messed around with it because he bootlooped the phone by doing things without understanding'em. After getting frustrated over and over, suddenly an idea dawned inside my head to do 'what you're about to do' to your phone. This thread here is just to help other ZE500KG users that are as frustrated as I am (was). I didn't find any guide to unlock the ZE500KG here so I decided to do one. If anyone wants to redo this guide, feel free to do it! I'm just here to help even if with very limited knowledge and resources.
First of all, before reading or doing this guide, I'd like to give you a small note, I WON'T BE GIVING LINKS OF THE FILES ITSELF, please search them yourself, you've got google and the threads here (another reason why I'm not giving you links of the files is because my external HDD got corrupted and I lost nearly every file there is for the Z00RD). Plus I did this unlocking like 8-6 months ago, in frustration, so I've forgotten lots of things about the Z00RD.
Now I'd like to explain whats about to happen:
As you guys might know, the only official bootloader unlocking is only available for the Z00ED. What you are about to do is tricking the Z00RD as if it was Z00ED by flashing the Z00ED's stock recovery and flashing stock rom of Z00ED to Z00RD (I hope some users can automatically get the idea of what to do after reading this). After it boots just download the official unlock tool for Z00ED and unlock it. How is this possible? Currently Z00RD (ZE500KG) & Z00ED (ZE500KL) are siblings. They're using the same hardware inside, the only difference is in the camera and modem. So theoretically we can flash ROMs of Z00ED to Z00RD.
Prerequisites:
First of all, please download the respective stock recoveries of Z00ED as per current OS version. Search for them. There is a link somewhere in the forums, just try searching for it. If you're on Lollipop, download the LP stock recovery of Z00ED (ZE500KL) and if you're on Marshmallow download the MM stock recovery Z00ED. Technically this it's just upgrading to latest stock MM ROM.
Download the final stock rom for Z00ED in ASUS's Official Website
Download the official unlock tool for Z00ED that is in the ASUS Official Website too
Optional:
Download stock recovery and stock ROM of ZE500KG and after the unlocking process is finished try reverting back to stock ROM with stock recovery of ZE500KG <- Just incase you are afraid something will go wrong and don't know how to edit build.prop-s to change your device type.
MOST IMPORTANT IS THAT YOU UNDERSTAND & KNOW HOW TO USE ADB & FASTBOOT COMMANDS! I won't be helping you with this, because I'm pretty sure if you're here on XDA, it means you've done some research and pretty much have the knowledge to use the commands.
Okay lets get started:
Move the downloaded stock rom of Z00ED to your phone (I forgot if it has to be renamed and forgot if it has to be in internal or can be put to external) or you could just skip this and later on uise ADB commands to sideload the file.
Boot to fastboot mode / bootloader
Flash the stock recovery via fastboot
Boot to stock recovery that can be done via fastboot command 'fastboot boot' or manually doing it (I forgot the combinations, I'm pretty sure you guys have this covered)
Once it boots to recovery, install the stock rom of Z00ED that has been downloaded (I'd prefer using adb sideload, but it's up to you guys)
You don't have to wipe data, because if you're on MM the data will stay, if you came from LP, it'll be migrated.
Reboot the device and after it wait until it finishes booting (If you're lucky nothing would go wrong in this step)
After it finishes booting, just install the official unlock bootloader app that you've downloaded, open the app and follow the instructions.
Voila device will reboot and you've (somehow) officially unlocked the bootloader of ZE500KG! You're free to flash custom recoveries, custom roms and blablabla without any restriction!
This last step is optional:
If you're planning on sticking with stock ROM, I suggest you to revert back to ZE500KG stock ROM. I don't know if this is a must or optional, but for safety measures I did this to my friends phone.
Notes:
If you've tried rooting this phone via hotbooting a custom kernel (boot.img) that you've found in the threads here (Sorry if I'm not mentioning any names here) and have the fastboot error in every reboot, this will fix it, but if you plan on sticking with stock rom, you won't be able to flash SuperSU in it, because the su binaries will be occupied. On the other hand, MagiskSU works flawlessly.
If somehow this guide doesn't work for you, Try to do other things, or flash other stock recoveries of different stock rom releases of Z00ED. At least you've got the idea on how it works.
If nothing works for you, maybe you're just unlucky, because as usual, ASUS ships different variants of it's phone that may prove to be incompatible with my guide.
There you go! Happy unlocking! Sorry if my post was semi "TL : DR" or I don't reply your posts ASAP, I'm not always online on XDA. Just try your luck and give it a shot! Trial and error is bound to happen when you're dealing with Android phones. Good luck!

Lucky enough my friend sent me some screenies. If this isn't enough, I'll ask him to make a video to see his unlocked status and device type.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader
Need Help
Please Contact

Shafkat said:
How to Officially Unlock Z2L Z00RD - ZE500KG Bootloader
Need Help
Please Contact
Click to expand...
Click to collapse
It's all in the first post friend, just read the guide slowly and enjoy the process.

A question for a developer

What is my twrp password for user 0?
How do I get the phone running after updating to v22?

You need to provide much more information if you want anyone to help you…
What’s you phone brand and model ?
How did you install Magisk ?
What messages do you get ?
After doing what ?
What are you trying to achieve ?
Etc.
Please note that these are basic information that pretty much any person/service looking to help you will ask, be it here on a forum, a service hotline, your car mechanic, and even your doctor.
No one can read your mind, while you know what you did/what happened.
Also a title like "A question for a developer" doesn’t help a lot, as it doesn’t describe what is the issue or your goal.
A much better title could be "TWRP asks me for user 0 password".
Help the others help you !

Xiaomi Mi Mix 3
I update Magisk to v22 via Magisk app
In TWRP i have message: Enter password for user [0]
After update process via app is nessesary to reboot phone, after that it stuck in TWRP asking for password.
Flashing boot.img not help
Flashing same rom without wipe data also doesn't help.
The developer should test the application first. Now I am wasting hours recovering my data and being able to use my phone! It's ridiculous.

QVA said:
The developer should test the application first. Now I am wasting hours recovering my data and being able to use my phone! It's ridiculous.
Click to expand...
Click to collapse
If you did not pay the developer, you have no right to complain.
You got a product for free, without any guarantee, and can’t expect any support either.
You are, however, encouraged to try and solve your problem, post your findings here, and help others.

we know that you update Magisk to v22 via Magisk app the question is how you "install" it... most devices would not have magisk pre-installed on there system

QVA said:
Xiaomi Mi Mix 3
I update Magisk to v22 via Magisk app
In TWRP i have message: Enter password for user [0]
After update process via app is nessesary to reboot phone, after that it stuck in TWRP asking for password.
Flashing boot.img not help
Flashing same rom without wipe data also doesn't help.
Click to expand...
Click to collapse
This is a much better report !
I hope someone will be able to help you out.

I wanted to install using the first option in the application. The terminal showed up, performed some operations and wanted to reboot the phone. After that, only TWRP starts.

It look's like my boot.img file is not patched by magisk, and thats why im stuck in twrp.
There is any way to patch my image without Magisk apk?

QVA said:
It look's like my boot.img file is not patched by magisk, and thats why im stuck in twrp.
There is any way to patch my image without Magisk apk?
Click to expand...
Click to collapse
upload it and i'll patch it

@QVA There's no need for you to keep opening threads regarding the very same issue. You're currently posting about the very same issue in this thread and these two others:
https://forum.xda-developers.com/t/camera-stop-working.4248233/
https://forum.xda-developers.com/t/magisk-v22-update-encrypted-my-phone.4248421/
Keep everything in one thread, it makes it easier to follow the discussion and it keeps clutter in the forum down (please also note forum rule #5).
I suggest that you decide which thread you want to keep discussing this in and report the others for closure (I'm not a moderator in these forums, or I would have helped you with that myself).

Here is the file:
boot.img

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I also tried to remove Magisk but it failed:

Thanks for your time, but the file you sent did not solve the problem.
Still booting into twrp screen.

you device don't run a/b partition like boot_a.img and boot_b.img??

I don't know, it's a normal phone with a normal system. There is a single boot.img file in the system archive.

looking at the magisk uninstaller log you have error "Boot image is patched by other programs! Cannot uninstall!" lmao you really messed up

why don't you just do a factory reset?

I do not want to lose 100gb of photos and application from the bank.

By the way @QVA, was your device encrypted before all this?
And have you tried the default TWRP decryption password (default_password)?
And judging from that photo you posted of the TWRP flash screen you were using an ancient uninstaller... Better to try the current (just rename the Magisk apk to uninstall.zip).

Question Root Guide

Method To Root New Oneplus Nord CE 5G?

Pradeep1407 said:
Method To Root New Oneplus Nord CE 5G
Click to expand...
Click to collapse
Are you asking or telling?

I just ordered and my phone is on its way. It will be my first time with anything that is not a Samsung.
I'd love to root it with Magisk but I understand its a new model, I won't find detailed procedures etc. Anyway, do any of the more experienced rooters and modders have advice for me?
Should I start by trying unlocking the bootloader with some procedure from another OnePlus model? Which one? Thanks
EDIT:
let me elaborate a bit more on why I am asking. I realize it might not be possible to fully root the phone now, maybe some details need to be ironed out. But I would love to avoid having to do later any steps that involve losing data.
Typically, the unlocking of bootloader clears everything in your phone, right? So it would be nice to get that part done as soon as it arrives, even if I can only do the rest later, once the pros develop the tutorials here.
By "do the rest later" I mean install a recovery like TWRP or OrangeFox, and put Magisk on it, EdXposed, etc.
Does my strategy make sense?

pgorod said:
I just ordered and my phone is on its way. It will be my first time with anything that is not a Samsung.
I'd love to root it with Magisk but I understand its a new model, I won't find detailed procedures etc. Anyway, do any of the more experienced rooters and modders have advice for me?
Should I start by trying unlocking the bootloader with some procedure from another OnePlus model? Which one? Thanks
EDIT:
let me elaborate a bit more on why I am asking. I realize it might not be possible to fully root the phone now, maybe some details need to be ironed out. But I would love to avoid having to do later any steps that involve losing data.
Typically, the unlocking of bootloader clears everything in your phone, right? So it would be nice to get that part done as soon as it arrives, even if I can only do the rest later, once the pros develop the tutorials here.
By "do the rest later" I mean install a recovery like TWRP or OrangeFox, and put Magisk on it, EdXposed, etc.
Does my strategy make sense?
Click to expand...
Click to collapse
Hey! Congrats on the new phone! I got it too. Your strategy does make sense to me but there are other things that need to be figured out too like the A-B system of Rom handling phones have. So I'd say wait for a bit and take a backup and restoe it when you root eventually.

The main reason I want root is to have proper, complete backups.
How exactly does one backup without root? I know, Google data is on the cloud, and I can copy files form the SD card, but that means dozens of wasted hours re-configuring every single option in every single app (I'm that kind of guy)... sigh...
Thanks for the tip on A/B updates, I went reading about it, it's news to me and it is quite interesting.

almost.lunatic said:
Hey! Congrats on the new phone! I got it too. Your strategy does make sense to me but there are other things that need to be figured out too like the A-B system of Rom handling phones have. So I'd say wait for a bit and take a backup and restoe it when you root eventually.
Click to expand...
Click to collapse
exactly, wait for a sometime and then rooting is better.

You can download the oos ZIP and extract the boot image, patch it with magisk app, unlock the bootloader (this will wipe your data!) boot to the boot image you made and install magisk via the app (direct install)
Rooting oneplus phones are fairly easy tho.
No idea about SafetyNet on the CE yet

SafetyNet is working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Manugamé said:
SafetyNet is working
Click to expand...
Click to collapse
Interesting - mine isn't!
How exactly did you root?
I downloaded the stock ROM from OTA, patched with Magisk on the device, moved it back to a PC, and flashed it from fastboot.
More details here: https://forum.xda-developers.com/t/...-stock-roms-for-nord-ce.4296379/post-85427971

pgorod said:
Interesting - mine isn't!
How exactly did you root?
I downloaded the stock ROM from OTA, patched with Magisk on the device, moved it back to a PC, and flashed it from fastboot.
More details here: https://forum.xda-developers.com/t/...-stock-roms-for-nord-ce.4296379/post-85427971
Click to expand...
Click to collapse
I used the same method, it's weird. do you have magisk hide activated ? I don't know if it's necessary.

Manugamé said:
I used the same method, it's weird. do you have magisk hide activated ? I don't know if it's necessary.
Click to expand...
Click to collapse
I tried turning it on (both MagiskHide and Hide the Magisk app, which renames the app), rebooted, but still the Safety Net check fails.
I am using Magisk 23.0...
Strange!

Im far from pro and after 3h on windows 10 trying to extrakt the payload.bin file with diffrent tools i have failed . Asking for help getting the boot.img i need to use with magisk.

krille74 said:
Im far from pro and after 3h on windows 10 trying to extrakt the payload.bin file with diffrent tools i have failed . Asking for help getting the boot.img i need to use with magisk.
Click to expand...
Click to collapse
You can use https://github.com/vm03/payload_dumper to dump the payload.bin.
Just follow the guide.

Manugamé said:
You can use https://github.com/vm03/payload_dumper to dump the payload.bin.
Just follow the guide.
Click to expand...
Click to collapse
thanks finaly was alot of work had problems with all thinks about windows possible .

So is it working with safety net or no . Bcuz I use payment apps , which require this.

ksulaiman579 said:
So is it working with safety net or no . Bcuz I use payment apps , which require this.
Click to expand...
Click to collapse
Safety net works with magisk hide + renaming magisk app

Installing ROOT
1. Reboot the device in TWRP recovery
2. Flashing Magisk
3. Reboot into the system.
4. Install Magisk manager. Rebuild Magisk with a different name and check the box on Magisk Hide.
5. Install 4 add-ons from under Magisk.
Checking.
ROOT is, Safety net is passing. Gpay working.

TWRP recovery? For Nord CE 5G? That's a novelty for me!
.... seaching ...
Here it is!
[RECOVERY] [11] [ALPHA] TeamWin Recovery Project (ebba) (2021-09-09)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com

I tried installing the 4 Magisk 4 addons you provided, but my SafetyNet check still fails.
Desite all the installs apparently going well, now I only see these listed as installed:
MagiskHide Props v6.0.2
Riru 26.1.2
Riru-Edxposed (I already had this) 0.5.2.2
Universal SafetyNet Fix 2.0.0
Do I need to do something else?

pgorod said:
I tried installing the 4 Magisk 4 addons you provided, but my SafetyNet check still fails.
Desite all the installs apparently going well, now I only see these listed as installed:
MagiskHide Props v6.0.2
Riru 26.1.2
Riru-Edxposed (I already had this) 0.5.2.2
Universal SafetyNet Fix 2.0.0
Do I need to do something else?
Click to expand...
Click to collapse
Rebuild Magisk with a different name and check the box on Magisk Hide. Did you?

Question How to root Redmi Note 11?

Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The first step is to unlock your bootloader which usually takes a week. Do that first, then you can browse more and wait for answers while you wait

I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img

parker_04 said:
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
View attachment 5807325
Click to expand...
Click to collapse

notBradPitt said:
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
Click to expand...
Click to collapse
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.

parker_04 said:
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
Click to expand...
Click to collapse
I think this sums it pretty well: https://forum.xda-developers.com/t/installing-miui-eu-rom-and-root.4426937/
- Backing up data: Back up your data so it won't be lost during bootloader unlock
- Unlock bootloader: allows you to flash into your phone
- Flashing Xiaomi.eu (optional): Their ROM is based on MIUI Global/China which has way more features than region based ROMs and no bloatware. Cons is you have to manually update it and you can't update system apps (as they're also modified to disable ads). Pros is, you know the version you just flashed and the boot.img is also there.
- Finding boot.img: This is the file you want to patch if you want to root your phone. You can find this by extracting the fastboot ROM and it should be inside. In case of stock MIUI, you have to download the exact version that you have right now on https://xiaomifirmwareupdater.com/ , get the flashboot version, extract, and boot.img should be inside
The rest should be explained in the post above and I think this will also help in installation of Magisk https://topjohnwu.github.io/Magisk/install.html

@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download

parker_04 said:
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
Click to expand...
Click to collapse
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)

notBradPitt said:
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
Click to expand...
Click to collapse
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.

parker_04 said:
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
Click to expand...
Click to collapse
No problem How do you like it? Have you proceeded with root yet?

notBradPitt said:
No problem How do you like it? Have you proceeded with root yet?
Click to expand...
Click to collapse
It's nice.
Xiaomi eu is certainly cleaner than stock. Adless and bloatless. It has new features although some of the stock's features are missing. Play Store is jittery for unknown reasons.
And when I try to open a file in another app, the app list appears quite late and it's laggy too. But that's all and I don't mind it.
Thanks again for recommending it.

notBradPitt said:
Have you proceeded with root yet?
Click to expand...
Click to collapse
Yeah. Rooting with magisk is so easy. And it's uninstallation is easy too.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?

creepystaircase66 said:
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
Click to expand...
Click to collapse
Yes, data is only needed when you request for permission

Assuming you have unlocked the bootloader
Step by Step Guide:
1. Download Magisk APK and install it
2. Patch your Recovery (Stock, TWRP, Skyhawk, etc) in magisk app and copy the patched img to Computer
3. Switch it off, then boot to bootloader, and type "fastboot flash boot recovery_patched.img" where recovery_patched.img is your file name.
4. Reboot (Might take longer than usual) and open magisk to confirm the the result of actions.