Database Develop

[Q] ATT Update to 5.0.1 fails, confirming a solution

It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.

xdafly said:
It has been over a year since I last flashed a S4A phone, so refreshing my notes and hoping someone can confirm the bits below are correct.
In case another, shorter way to accomplish same exists, kindly suggest it.
Background first.
Phone is SG4 Active, running Android 4.4.2. Baseband I537UCUCNH3, model is Samsung SGH I537, Build KOT49H.I537UCUCNH3
Phone is unlocked and was flashed with Odin one year ago to 4.3 and then ATT updated automatically to current version.
Status today.
When ATT offers download and install the 900 plus MB 5.0.1 update, it fails at 27 percent, reboots phone, repeatedly.
Phone has about 8 GB free space on internal memory and about 10 GB on SD card. As far as I can determine, no special mods have been done to phone and I have uninstalled all user installed apps so it has only ATT, Samsung and Google apps.
Proposed solution.
Found the original I537UCUBML2 bundle *2gb* (Android 4.3) with BL,AP,CSC,CP and I think that since Bootloader already installed, it should be possible to run Odin again and just flash AP,CSC and CP.
Once flashed the system will be back to 4.3 and the OTA updates should work, first to 4.4 and later to 5.0.1.
Can not recall right now just how to do the Odin flash but will use search to figure it out but is my thinking correct or am I missing something important ? For example, don't remember if I have to reboot phone first or if Odin handles it all once the USB cable is connected.
Thank you.
Click to expand...
Click to collapse
ML2 won't help you. If you give me about 5-10 minutes I'll link you to the file you need (I'm slow because I'm on mobile and it's a tiny screen for my fat fingers lol)
---------- Post added at 02:43 PM ---------- Previous post was at 02:37 PM ----------
OK here is the file you need. Download and save it to your EXTERNAL SD card (internal storage won't work) and flash the file in stock recovery. You can boot to recovery by shutting the phone off, then holding down power and vol+simultaneously
If you want to be rooted, don't do this, I can point you to a different method

Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.

xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
Use Odin to restore NE3 kit kat instead of ML2. I can link to that too if you need
NE3 kit kat
You have to extract all 4 tar files and flash all 4 with Odin simultaneously

xdafly said:
Ok, downloading. Now, in case this "manual method" also fails at 27 percent and just reboots with Install failed, what then ? That was the original reason I proposed to use Odin re-flash the SG4A back to some semblance of original state. Thank you.
Click to expand...
Click to collapse
The reason your install is failing is because you've modified the stock firmware. When you try to install an AT&T update, manually or automatically there is a script in that update that checks all the files on your phone to ensure that they are the original, unmodified files. If any single one of them is not original or modified, then the update will fail as you have experienced. So if you root your phone you are modifying system files. Even if you unroot, the system files were still modified at one point and the update will fail. I suspect you've done something like this.
The only way you can update to stock OC6 (5.0.1) is to flash your phone back to stock firmware and in your case it should be NE3. As has been explained you will need to flash the NE3 Odin package, but beware this will completely wipe your phone so backup anything you don't want to lose. There is a method for updating your phone without flashing back to stock described in this thread. Also, if you're ever looking for information on rooting and updating your phone it would be a good idea to familiarize yourself with the links in the i537 Firmware Guide.

Use Odin to restore NE3 kit kat instead of ML2.
Click to expand...
Click to collapse
Got it. Downloading (as suspected, the update.zip failed) and will hook up cable and run Odin 3.09 with all 4 files
All important data is backed up to Google so unless I lose some ATT settings, such as the IMEI code or similar, all should be well
Does the phone have to be in recovery mode before starting Odin ? Can't remember now and all Youtube videos show only AP being applied, not all 4 files simultaneously.
Edit, read http://www.samsungodindownload.com/odin-tutorial/
Thank you

BL file to bootloader (BL), CP file to phone (CP), CSC file to CSC, like below:
{
"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"
}

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...).

Confused About Different Options to Root P10 VTR-L09

Hi all,
My build number is
VTR-L09C432B171
I am at the stage where I can now run either of those TWRP version:
1. twrp-3.1.1-0-vtr.img
MD5: 47e83bee437506e1308ca2e29fe30e9c
2. twrp_3.1.1_fromfuture.img
MD5: a4dd832349d345e187b4c125f2a81e18
Before going further, I would like to ask some advice. As a newbie, I want to go SLOW so I don't take a step I might regret.
First, let me clarify my goal. At this stage I am not looking for a custom ROM, but just root access so I can run things like AdAway, Titanium, Uninstall, NotificationsOff...
I found different information about rooting the P10.
For my goal, which will be best?
1. SuperSU-v2.82.zip
http://www.teamandroid.com/2017/04/19/root-huawei-p10-emui-51-android-nougat/
2. Magisk
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
3. SuperRoot_noverity_nocrypt.zip
https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946
4. fRomFuture
https://forum.xda-developers.com/p10/development/rom-fromfuture-stock-rom-b164-t3657812
Thank you in advance for helping me out of this confusing place!

Hey Mate,
i also did try some of your posted links on my Huawei P10 but i runned in some problems. I think you also need an external SD Card to work with.
My experience so far :
1. SuperSU-v2.82.zip
When i flashed the ZIP, i didnt got any root rights on my devices.
The Phone wasn't brick, but i just had no root rights on it.
I am not sure this is defintly not working, i readed some postive Feedbacks in the internet. Its just my experience.
http://www.teamandroid.com/2017/04/19/root-huawei-p10-emui-51-android-nougat/
3. SuperRoot_noverity_nocrypt.zip
The behavoir was the same like the 1. SuperSu-v2.82.zip
I am not sure this is defintly not working, i readed also some postive Feedbacks in the internet. Its just my experience. Maybe if you got time to try i would be happy to get a Feedback from you.
https://forum.xda-developers.com/p10...0-p10-t3589946
2. Magisk
After my Trys with the Root Zips, i tried to enable the "Root" by systemless Rooting with Magisk.
First i tried the Version 14, which didnt worked for me.
After that i tried the Version 12 from Magisk, which i did exactly like the information as you got from MusicHeat:
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
This got me the Root rights on my P10.
Important: When you try to Root your phone systemless with Magisk you must have your Stock Firmeware installed. It will get you some error by flashing magisk if you already tried another root methode. Like, if you tried your first or third opinion you have to flash your Stock Firmeware again (i did this in the fastboot with the extractet Update.app (Firmeware) from Huawei. The Boot.img, Recovery.img and System.img (also the Cust.img) is in the Update.app.) To extract the Update.app you can use HuaweiUpdateExtractor from worstenbrood.
https://forum.xda-developers.com/showthread.php?t=2433454
After all i tried xposed Framework on my systemless rooted P10, which was working fine.
The "Hide Root" Methode is also nice to have.
4. fRomFuture
I didnt try that on my own. But there is a requierment that you have prerootet with Magisk.
So in my opinion you should give a try at Number 2 (Magisk).
But its up to you. If you try 1 or 3 Possibility give me a Feedback in this thread
Kind regards

@ChipCollector
Wow, it's really lucky (for me) that you tried all these methods!
Thank you so much for sharing your experience. Isn't it weird that there are web pages out there saying the SuperSU method is the best, when in fact you and others have a completely different experience?
Alright then, based on your comments, I will probably try Magisk.
So far I have only unlocked, not rooted, so starting from a "fresh system".
Just so I am 100% sure I understand what Magisk does:
1. This is not a whole replacement ROM, right?
I am just trying to get root -- for the time being I still want to use the standard camera program for example as I would like to get to know the phone.
2. With Magisk, can you still get Huawei updates, or is that a problem?
Of course I'll go study the Magisk thread, but if you have any thoughts on those, I'd love to hear them.
Thanks, man! :good:

TRY
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
6a or 6b version 100% working!
but still the data partition remains encrypted.
The developer of Twrp describes this error precisely so that it does not work, they are looking for a solution.
It only works if the kernel is turned off by forced encryption and reformatted the whole data partition.

Update:
Tried Magisk v. 14
Device bricked immediately.
Now following unbricking steps from this thread.
Question: for my build number (VTR-L09C432B171) several firmwares are found (see screenshot). How do I know what to choose (OTA-MF / FullOTA-MF?) On that screenshot, where do I click to download a firmware?
Thanks in advance.
{
"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"
}
Update: these are three files I can download, looking like the latest on the screenshot (VTR-L09C432B201, FULLOTA-MF)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1901/g1604/v102599/f2/full/update.zip
http://update.hicloud.com:8180/TDS/...99/f2/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L09_hw_eu/update_full_VTR-L09_hw_eu.zip
Any thoughts on which is more appropriate?

I should add that I did a full backup with TWRP before bricking by installing Magisk 14.
But I am not managing to load TWRP to restore that backup. What I am trying: Press Power, when it vibrates press Volume Up and hold, quickly release power, keep holding Volume Up.
The phone boots into Huawei Recovery, with "Download latest version and recovery" the only meaningful option, and it sees my WIFI connection, but it keeps failing to download.

Update:
- Finally got TWRP to run.
- Restored the backup
- Phone is booting
- After that, tried to run TWRP again to try to install Magisk 12
NotificationsOff and other apps are saying Root Not Available, so I'm not sure what's going on. But at least the phone is booting.

Finally Working
Finally Working!!!
The steps:
- Restored the TWRP backup
- Installed Magisk 12 via TWRP
- Installed Magisk Manager via APK
- Within Magisk Manager, following this advice, checked the two boxes, selected Update, selected Direct (recommended), which updated to Magisk 14. Within SafetyNet Check, both come back Green.
Absolutely stoked. :good:
Huge thanks to everyone who puts these wonderful resources together.

[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.

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.